Merken

Open Source Management - Strategies for comm. with open source projects in companies

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
I know I have the honor to introduce a man doesn't the planet election my opinion Chris's storing i'd seasons the dark ages sorry the nineties being with many begin great companies said come and the I think that you a plate and my scalp throughout land both if the and so you change stops again and
he will tell us how we companies can handle open source projects better and efficiently the result of the rule and just just-in-time that starts this Chris with the ground of across fewer this that you but with the political must have this so there high and this time I'm going this computing actually sense at 3 which means that I'm officially an old fart that's also did indicate for that is that you're given 2 notes and and I'm undoing the open source the yeah 2 decades more so I have been you previously working for a small travel agency in Amsterdam and when I was responsible for the nonexistence of the book and catch the last year and before that I was working for last and before that fall with 2 years a security engineer and before that for hosting company Internet use where did too little bit of PHP contributions from assessing work and various other products mostly they are responsible for my hair color and we have had 2014 and I'm giving a talk about open source companies it seriously because apparently that is necessary the the idea to The Stork came in April this year a lot of people we're asking the question how can I give money to all the necessary I and that is actually not a problem at all or if you give money to over is so that is not solving the problem of open source is in all kinds of companies and has been for at least 10 years even in slow companies and that 20 of 30 years in the faster ones and the question is does your company officially know about this and other handling that property and and if so on what are they actually doing to handle this and many companies have seen in the last 10 years I'm doing open-source properly and that is the problem that the it's solution so we
start out with that of an external
dependencies you're probably doing something and delivering it or hosting it for somebody and and the stuff you do when you're running is probably dependent on other stuff because
semi-definite Google and reinventing the wheel then and you're probably using views of the people made so what are you doing with these extra dependencies be the closed source or open source how are you dealing with them and that is not just licensing and support that this also how testing this term that is to foreigners and how but I do influencing the so that it gets better and actually that is easier with open source and the flow source country true I want to point have bosses may think the that's a big difference between shipping and hosting mostly because of the GPS as shipping a product means that you are producing deliverables that contain what you wrote and then the extra code references that you include and close so that means that you need a proper license that allows redistribution and with open source that means that you need to actually check what kind of licenses you
have and if it's GPL'd but do with that hosting doesn't need these checks and at least not GVA specific and some people see that as a floor under the GPL because you can take stuff that is you create modify it not be distributed and just post the results and not contribute back there is a special variant of the gene the Affero GPL license that is designed to work around this made that the pivotal role the educated considered as a by and and then there are also other ways to work around the GPL if you want to because of you can generally sees itself as ending at process boundaries so if you talk to something over the never even internally you can
and the things that separate the GPS specific licensing to 1 process and to you a preparatory stuff In another process and this is something cases that is not possible and then sometimes the GPL especially is
used so to actually make something open and not open if you remember very old my sister my spare 3 . 23 that had the a library the most client
so and that was actually a
GPS so you could take that libraries negative program and that library implements the proper Costa can actually talk to the south and since my form of 0 and that libraries still exists but is licenses GPS so
if your program is not GPS you can actually link against the minus client library and data talk to the the server without red re implementing the protocol or licensing commercial version of my students for some this is just 1 example we see this and several other places as well and you see this for example another prominent use of that was the 1 that I am instead of set of his was assisted licensed under the CDN and that is technically inhabited despite the fact that it's an open license with the GPS so it's very hard to link all nodes of as that of this kind of modules into a Linux kernel and then shift the resulting product you cannot build a distribution that does that you can do that is home at home for yourself what can they do that inside the company but you cannot create a product that contains things that are are mixed license between the city and the GPS and then ship that as it true and that is for example a wife battery come into a cannon into existence was of that is now part of Florida and both still exist and they actually used to license differently and but otherwise they're very similar projects and products some licenses are just plain weird at this is that the winners example I could find this is summer it's not interesting it's a it's a dictionary and thesaurus and you can use them for free if
you take no more than 2 flights or 1 return flight year otherwise you have to buy commercial license so that the things that you know and then there is another product I don't remember which 1 that that is licensed under the Google modeled don't do users and and they actually they they get regular questions from from the CIA and and the lights of fate are allowed to use this our how is this this clusters licens eco don't do you to and to interpret this this this this is
licensed so not for us and this is something free then there are several very good benchmarks and a lot of examples of that so is your license if or is license-free if you look at this if you look at the Debian Free Software Guidelines about no I'm not bashing didn't today do this every other day or you look at at the time all see our compliant licenses and don't then you will not only get an idea if if this is a free and open source license but you will also get an idea of this competition with anything else because there are some lessons that are free but they are not covered with each other and for example that page he had a very big problem that the might license change if something is GPL license it's basically linkable only against GPL-licensed things but PHP is available under the PHP license which is also a free license but a different 1 sold with Philip my script languages so you don't only find that it's GPL license you also refined the long list of license exceptions so despite the fact that the the most client artists always GPL-licensed you are allowed to link it to and then there is a list of specific projects so it's there is not a general exception you are allowed to link it against anything that this difference comply and there was a compact but you are allowed to link it against say Apache or PHP and some of your project is not on the list is technically impossible to link it against the most Atlanta PHP is on the list but the good somewhat annoyed about the situation that and performance reasons why there is the and mask project which is a reimplementation of the client and so that you can do a PHP that talks to my stress over is more efficient than the origin of the client library and it doesn't have any reliance on any licensing exceptions are strange when you include external dependencies closed source or open source most companies actually do not they're
doing their own internal quality assurance process to
whatever they include and from from external so any external libraries an extended products that they use in our measure can be assumed to be the smallest and back free and if there are problems that there are supposed to go away by sprinkling different when necessary dust over the thing and then then everybody would be happy and decode the just run of that is of course not true in February this
year we learned that close sources is actually pretty dangerous the and and it can actually fail I mean this is this is
happening here so and the definition of closed source of quality of the encryption of the and don't the problem they have here was that they did this happen exit code to 0 then the check for something if it doesn't work they set an exit code you wrote phase cleanup and return the error code and then there was the 2nd go to phase which was unconditional so the article goes to 0 go to failure of clean return the IRA
code which is 0 and then certain as as certificates never got validated data at all so you could just answer anything very hard to spot varies simply are and so very nasty so and we learn closed source open source also bad that's
a trend that that is the reason for all this talk basically because we got a very impressive demonstration that access to the source code doesn't make
programs secure that may be a precondition to verification but you actually have to look at that stuff understand that um and uh rejected that it's actually doing the internet stuff and is only doing the internet stuff and nothing else and the 1st part is boring and the 2nd part is actually quite hot and and the back here is relatively symptomatic and also the set up of this product project has led to this implemented for a certain class of library and if you look at these logos here they are graphically probably I could do worse but I
won't even I would have to to I spend hours to do worse from from the lower part this is on infrastructure code and this is called that is basically the invisible hand it's doing important work it's in almost anything I mean as that live and do you know anything that is not using exactly and if and and it's also very boring cold because it's infrastructure so you're not going going to 2 conferences and talk about that maybe with the exception of things kind of developer conferences or
other negative stuff but In this box are in this code there probably in about anything that you have on you right now or at home running and there also probably in a lot of firms but are embedded stuff so that's that would be very hard to fix because it means getting old devices sort of very inaccessible locations rip them apart change some flesh or even harder bond software and the fixed version and then read it for the interest of and you don't want to do that because these devices also very numerous so you're looking at the at a huge number of devices very many more than than the PC so tops and so when you talk about open source in
companies most of the time you're talking about the need for support and most people think about back 6 year but actually finding a back and then fixing is and half of the problem and we need to talk about that because what is the d
back life cycle and when you look at this you open the case you get a ticket you yell at the 1st level
support because they asked you to remove the stuff and and downgraded the latest worsened and you have already done all this and verify that this on an actor back and you're not too stupid to read the menu and or maybe even the menu is wrong because they didn't understand this better education on interoperability problems or whatever a need to escalate that and finally you get an acknowledgment that this is a bot you probably get a walk around a temporary fix that to deploy which is an annoying situation because you're
not exactly running a standard consideration of and this kind of work-arounds tend to bite each other they accumulate and eventually there will be a new version the fixed and that means that you have to reintegrate your product or new deployment with the new version of the upgrade you enter deployment in the company or even in the future to the new words and this this improvement that is it can be actually quite tedious process the benchmark in my last job was we have at that time 2000 databases and you want to upgrade on databases and each of them this several terabytes data we want to be able to operate all of these databases to enumerate within 20 workdays actually wanted to be able to do this and no matter how many databases there so once a version is validated and verified that it is possible to use this in our environment we want to be able to deploy this within 20 workdays across the entire organization no matter what the size of the organization in that but that's another talk also an interesting topic because it's a hard problem if you look at large numbers but but that's a different thing and in open source the expectation and enterprises is usually that it's hard to get support but that is not true the question is usually not how to
get support but who to talk to because I'm open source projects comes not understand that organization follow the standardization forecloses supposes that you're talking to a company so the interface to support a smaller standardized uh because every when they bought from them and then there is a documented support and the value ask you questions and get fixes and the rest is just quality differences but NOT interface differences and the problem with open source support is not actually getting it of the quality of it but the problem is mostly that interface to support as the standardized because it's very much dependent on the organization of the product so it's not a question of how it's a question of who to talk to you could hire developer next time the developer or and actor committed to the project as part of the company and that have them fix thing so I went to the for example several Apache predicament as working and if you look at booking everybody in there has a site project in some kind of open source the theater minus Cuban to them red or puppet or what much if sometimes there are projects at the back by a single company but are open source that would be his demise can model for example sometimes downloaded companies offering independent support or even are jointly developing the open source project that can be be as much of a good thing as can be a bad thing if you look at the head of a project or the OpenStack project that is very vendor rich environment so also better but and and good and bad ways it's it's a difficult time because it's all very political all of the time what could learn the code
fix it just says and then you just for the project I I mentioned it to maintain the floor on to you have contributed you change that to the upstream and you're getting you fix your code as part of the question back into your company and that is actually quite hot because companies are often very reluctant to contribute to action projects or our organization incapable of actually doing this and ready for example was a company that had a very very strict intellectual property and a guideline so you couldn't actually contribute to the extreme have without had passing it by some lawyers and the laws they're always very busy so you actually know where never got an acknowledgment that you could push the and if you look at the web TV which I admittedly did almost last time I looked at it was almost 10 years ago and they can then about running a true that was no longer as Linux it was at some point is isn't it and then everything that was never tracing and other support libraries have been stopped and fix mutated they're running 1 something that once was an accent but he was talking called onto the back and so in the x and was linked against the call them and a broken the and the and the entire uh that front end was running on the language that was the closest projects for a predecessor company of 30 and now it that company and the product and no longer relevant or the main area of business so the focus of the company completely shifted by the infrastructure was still running on that and outside of that to you could not find developers for that language or that platform very very also situation but basically you have a company here that out of 500 developers made was dedicating 20 full-time equivalents to maintaining FoxO Internet infrastructure code that was not the main area of business and that's actually a considerable amount of of developer power and money and that basically gets wasted on stuff that is not the focus of the company mission and some companies are afraid of contributing because they fear that they might have uh maybe had liability all run into pattern problems
or other stuff then the set code free because some foreign or people would even if you just ask us questions because the other comment about that stuff and the afraid that at 1 point in time you will be able to answer that anymore because the person committed that is no longer working with us and stuff like that happens and actually blocks stream commits and and then there's the the works on my sisters syndrome and that is you have something you want to push it upstream and the abstinence actually denying that and not
allowing that in the prolog project because it doesn't fit informants or in scope or in the theological what things into the axiom project there are also very many the examples for them you can try to to put stuff into all this data already happened for example uh and there is actually quite laborious process In order to be able to do that and 1st you need to sign a country with a licensing agreement that's also the 2nd problem you but it is also completely blocking traffic piconets so you see a spelling error and the documentation and it can be that you can actually fix that directly because you need to sign is still a source of that is the product for example uh was running into this situation with uh the PTO the database and and 1 point in time several years ago Oracle was saying we want to work on the PTO adopted inside the the PHP source code proper solid set of Oracle but in order to be able to do that the PHP project this deputy all subtrees is to be protected by a country with a licensing agreement as you like anybody wants a committed to the string it's assigned the ceiling and the PhD projects that know we don't want that we don't want to raise the transaction cost we want to specifically allowed drive by commits so there won't be such as maybe don't do this and just and that is why there is officially no direct contribution from Oracle as a company to appeal there are a lot of comments from people who would 1 point in their career working with oratorical but oracle as a company is not involved in 0 at all because of that a similar situation this set aside support and to to to support and a few other things so database companies seem to be on the same page because of that but pitch p is not going to change that and OpenStack has a similar situation the next that after the CIA would be than uh you have to you can actually push into the tree you have to generate a model question that has been running through continuous integration of solids run into 1 of 2 regions given fulfill commits in many cases so you also have a latency of about to be good too because the assigned to viewers actually don't have time right now to look at your stuff and the other thing is that you have to if you want to contribute to the other people after that you stuff so they expect you to let you this stuff well and so actually contributing means also being a lot of other people's stuff that is not actually related to any kind of expertise that you have all the tools you or your company interest so you're spending quite some time on the side just in order to maintain the ability to contribute when you need it is a problem here and this
the thinking and there are many companies as well and that is that is especially evident for example in my personal experience with the 1st and the better the case which isn't just explain the
question is what does your company do and by that I mean what's the the company's mission and vision what is actually that they do that makes them special in the market what how do they want to on money so
you see that the really very many enterprises or even in entire branches of the economy that they are not really clear on on what they're doing if you if you look at the
outset of open source really in and have branches of economy if you look at print today or and they and writing in general uh they think they've write books especially German offices and and uh printing institutions do not think that but actually it's not the medium that is printed on paper it's it's actually a story telling or it's actually even communicating certain ideas in an indirect way that this what once the money and the medium changes right now and that creates another problem these people are unclear about what they do and because the economic environment changes they're currently using a lot of ground in terms and the vector case for example that the sum of this predecessor companies synaptic that was selling a content management system that was based on their language which was implemented as a plugin and the rest of the on because it's a property of product you have never seen that but if you and to describe that you could describe it as PHP so that the code is the database selected PHP to with got extensions solids loading code order of an oracle database and then executing that at the level of the language at that point in time was as bad as PHP true especially with the bad powers and everything and and that good strategy would have been as early as possible once the the people became evident in not longer selling a constant management system to leave the property language behind and moved to something anything that is maintained onset of the company because you're no longer in the business of maintaining the platform then to free up a lot of developers and you participate in Advances in advance advances that are being made in the that from outside of your company and you don't have to create all the time the momentum is but and but it can have happened several times in the company but never completely and that that there still things inside current United Internet directly that they're running on cops corporate online publishing system uses this internal property system the and even if you look at the market and you understand what you do you're probably not still not focusing enough what is it that actually makes you different from their closest competition how it is say booking different from
companies like like and MS-PDL interests or for others and it is very important to be very clear about these differentiating factors because that is the stuff that you want to keep secret but you don't want to push on and you also 1 them to push out everything else because everything
ends is actually like a grindstone round enactment and an obstacle to and very often
this advantage is actually not the surface so was not a problem to country would back and that that too could push back all of the the polar code that is running at booking without actually having the company at all because the assets of the company and not in the code base at all that very much it's but if you don't know what you're doing you don't know what is valuable and you don't want so know what can be pushed to the outside without losing agility and results and sharing the responsibility for the if you actually a about what the essence of our of the company and what the liabilities of and then you can efficiently pushed off to the outside and then the remaining problem will use it it's very much because it is then about ensuring that you're running the latest version of the code there you fixes our
in so back to the original problem you fix the black and that means that have for it's still very broken because there the box but and this 1 thing this 6 you want to get the code
after and you have an idea how to do that and and the solution of the name for the solution to put code of upstream are actually get fixed stuff the non broken suffer from the upstream in the 1st place and the name for that is or was my last job then relations so you talk about about this for example and these are my escape hatches and this doesn't include even more I added the order is but they actually do is on the list of morality is not and you see that that there are a lot of companies that have been catching my students and that
maintaining the dominating code bases that diverged lastly even from stock my and that actually post every 1 of these companies down quite a lot and also note the absence of a book and of compaction doesn't exist because that was my job what needing such the pitch that and then that is the way better idea I think talking to then there's about what you want from the product of talking to open source products and about what you want from the product and then find a way to make that happen in either by talking to the vendor and having the appropriate context or by hiring developers and keeping intended to the upstream all by giving money to all the necessary if you think that helps or the and
other way that works the maintaining patches probably the best thing because that means that you're not publicly maintaining 4 and some companies smarten up Google for example is a very small company if you assume Google for a Google and skies here you will find that instead of maintaining a boom attached to my students there's no direct cooperation between the was company and SkyStream or identity so instead of patching stuff and then sending it to my mom and Marie developers they sending developers tomorrow to that they can catch directly then the repository which is that way better way to integrate staff and the way money directly to communicate with each other to talk to each other and understand each other better and there is no longer a patch relief from will fall from optimized here because of patent lawyers in the front and paranoid about that and and don't use a goes on both sides but that's a different story and so when you have that sort and you're not really part
of the of project you have to solve 2 problems have been mentioned that 1 is making sure that the address to the current version of the stuff that actually make it into you of production whatever that is better insulated here I've written like this and pathogen text because whose cellphone was there good I have forgotten but if you said phone rings you only 1 of these the and latest means that you have to weigh a way to find to make an extremely high rates Running a new productions in a way that makes this an operational procedure and not a special project so moving from my school 5 underlies the 5 5 4 from 5 5 2 5 6 must not be something that requires special consent a person name for this particular market procedure and funding and stuff but should be something that just works so if you have validated and
version of something that you should just be able to deploy it and have mechanisms to have it everywhere and the other thing is then how do you get your patches upstream and these are actually both organizational interface problems the first one is in terms of how do I get stopped Running introduction how do I get my my production people into a format that they actually when I say we have validated that must be 5 6 is safe that they're able to deploy that within 20 workers on an average amount of some and the other to get push origin master and is the problem of how to talk to the extreme organization shows How can I send money to the openness said project that's a question that started this talk is actually not
the question you should be asking the question really is how are you using the library what do you require terms of maintenance performances Features double ability and how the user interface with all the necessary and the Open Society as a group in order to influence them in a way that they actually can meet the standards that you 1st have to define for you said and then only if you have done that you
can then talk about measures I hate that you can ever in order to achieve these goals but as long as you are unclear about what you want and you are unclear about how they work you can't do actually any just a waste of money so take these precious 500 EUR notes and just burn them it's about the same only faster the technical
standards internally to granted the version this is pretty easily solvable tools for that exist in in half a dozen and can choose between puppets salt and submit whatever you want the organization of sentences that to build something that can actually do this safely so you need to understand where am I using this what features are made using what do we need to test in order to to guarantee that minerals is all stuff doesn't break How do I organize the role of with canneries 1st never watched them break small hamlets environment and if the countries safe how do escalators to brought roller to a stage
this or do and our 0 role of everything at once what does work in my environment with the minimum amount of destruction and how do I get all of this integrated with my operation people instead of specific projects and that I want things so that I can do that and the amount of times as often as necessary and as fast as possible without additional for so in to know the external dependencies for product the and that can be really complicated booking was I think giving on and all more than a quarter million euros to the foundation and and basically financed the 14 and and what came after that but was running for several years after that 1 point 5 8 because of of uh 1 class that does the equivalent of 1 called the reference and another class that does data civilizations and and they broke with a new version of several other things also broke apart in order to get rid of the specific true dependencies Back then needed to identify them 1st and get rid of them 1st before we could actually rose Hall that true a new version of power
and that then unlock the performance gain of over 25 per cent which was of before because you simply couldn't apply the new variants very very serious situation is spending hundreds of thousands of euros and then you can get the benefit because of some bloody summarization class and so far and a big part of the problem was actually understanding how this could be blocking what how is this class used but features of these classes are being used and how can we replace that how much effort is that in the code heavy font everything is it's safe then after these changes to deployment of this and and it was actually on the calendar
several years more than to actually and before all of that was done next rates would be much easier because the organization as an organization learned how to do that better but it was a very very tiresome an exhausting process for all of the organization the people in your organization directly get to that point and and to actually acknowledge that this is a problem and wants to define what is necessary to make this an operational procedure that is boring stuff magnets attached source code references deploy developers to fix that but it's not something that the company is an organization can do but is also something that the company is an organization and didn't understand was necessary to do and this for the entire group of people was to have party then if you have these external dependencies you might as well defined quality time as for in china stuff what do we require what amount of reliability what features do we rely on the we have tests for them do we have test for their code for that part of that code that makes or breaks all applications if you have that then it becomes a lot safer actually perform creates so we know are testing for the absence or presence of certain things and students that we've depended on and then that then makes the entire these management of Jesus and the other thing is that was sold to establish a backchannel so find the organization understand how they are set up and how can we as an Organization talk to them as an organization as a group and communicate what things depend on and how can they tell us why did you break this well actually if you breakfast assumption that you lie on we can actually make it twice faster in what case so maybe we should change 0 why did you break this way we wasn't aware that anybody was relying on that so we can actually wrote this bank that's the kind of cost discussion that you have been invented relations about the source code of features and and that is all I know about some parts it is actually about I'm about engineering excess again oracle is a is a fantastic example because authors full
of standard engineering people and about that are several kilometres of lawyers and things people that you have to penetrate in order to actually talk to somebody who can understand you when you can actually change something and and so you you have to to drop several Bank of Boston's swath of of stuff on them to actually build time and to talk to people with and source code and organizations our our organized differently and to require an entirely different communication 1 in the end once you talk to people that represent the other organization and our capable of understanding your engineers and our to make the changes you want discuss these changes with you in the 1st place it always takes the same forms but the problem is really getting to these people and then finding an agreement between the 2 organizations to actually realize this channel is complicated and once you have that then it always answers static into teleconferences all and if the people left heavy accents with their chat rooms because don't have accents with design summits with proof of concepts with the agreement on the metrics that need to be collected and targets for these metrics with deployment examples showcases for future sandbox benchmarks and so on so that the problem then becomes 1 of the we understand each other and done what common language between the organization to we've and the next stage behind that would be then contribution the code of Austria that is not
working but actually modifying the upstream in some ways and so it's drive community or it is the also that the KDE browser
code drops or better incremental patches this commons even all documentation while I'm actually useful coded useful contribution and the dialog about code that as of the form of or finally and where our people working within their code base and their organization because that's the easiest way to is a patch and become part of the process and beyond that there
would be to actually talk with the other organizations modify
processes global role of what they do and as part of of this ongoing dialog to become part of the organization as a communication partner but not in the in the in the culprits office consensus so so you you go from cold improvements to process improvements and uh you go also into the product design of the mission statement of vision statements face all over and part of things basically will from
from and related to ensure ecosystem and you have a meaningful discussion between organizations with changing people about about code so a very specialized form of public description language
and that it's expensive and
this is the the the what I already said about trying to get cold integrated into OpenStack all had to do with all the review process and everything that creates something that that I a coil of organizational cognitive load as you keep people busy boring of about problems that are not you but about their call problems and that you need to solve as an add-on to the workload in order to be able to commit into the context of their code within that is committing into the context of the problem that that is good communication overhead you have school creep not from your company but from them so we can do is you get scoping from the upstream
uh and you have an organizational communication delay because if you talk to skies caloric about futures they will be available at the earliest with the next bit of emotions and they will be available in your organization and the next releases so here talking about latency communication latency of half a year to year and that's actually already the good case so this is also an entity antagonist but if it's not contained inside your organization you have to she the parts of your company that need to be fast from the ventilation property by necessity as slow as police and push process to the extreme sometimes that that is actually extremely bad this is that the worst case that found Google wrote something that is part of an android so as part of the Linux kernel is pretty awesome it's make lots and that was in 2009 and then there have been extended discussions Greek think also about this on the on on the linux-kernel mailing lists and in 2010 12 13 and their tasks and that the country I think in early 2014 and said in in an interview was unable to find the exact quote but he said it was a mistake accept these patches and if they're running on the hundreds of million of devices can be broken even if if I think this is hardly so still think the value but that's not the criteria but actually coming to that conclusion accepting the code is in turn around time of 5 years 5 years that so we have 1 very large very stubborn organization this kind of many and so on the other side you have another organization as large and probably was discovered and pushing something into this this is really really hard work was so but it's it's high-pressure work from from each other and actually quite bad communication but even in that case this time you're looking at a turn times of the year level here and uh that is if you're putting it inside your organization if you're not pushing it in your organization and if you look at other organizations would just let things happen then you know looking at software adoption times that actually comes with the deployment of new housing because if you divide and you have be would actually inside the new version of the operating system which contains then the new version of the cell that
libraries and a new pitch period in Poland and you might ask so we're looking at an overall adoption time of 2 or 3 years and if you're pushing this you get to cooperate response times and that our two-digit month so that's 3 months not minutes to talk about here even if you could write that pension 5 minutes you're looking at a latency here and the months or years to when you very clear as a
company what assets are that you need to keep inside the company and what liabilities opportunity to forcefully post outside of the company get rid of them then you
already on on the winning side of open source management but then things can happen very something that once was an asset like the copper online publishing system and they can become a liability for the company if a p those or if the market changes or whatever so the language that that is being used 2000 5 to ride pre-made was an asset of the predecessor companies in 5 years before that but it actually already was a liability for to in in 2005 and so that happens quite a lot you know the Firefox project and the code base they came from and I think this
is more or less final rewrite from scratch and it took them several years actually I think 5 to get from from this that to something usable this is also
very interesting that there was the question why and what the star office for for the notes hundred megabytes larger as a binary then this star office Windows and the answer is because of his on Windows can use a lot of libraries that come with the operating system that has simply not present in the Linux environment and out of that can then be desire to write these libraries and so that was a product that became style and the people who did this that this again outside of of the start of his company and that was then becoming later KDD the foundation of the was due thank you to it was already educated library but there was also a the fear that at 1 point in time the company that was actually producing KDD because that is a a product that was open source but rooted in 1
single company what happens is that companies have acquired what is if the the project is sold to Nokia what happens to the KDD codebase and there was the duty foundation that was this Cedric losses in the in the dimension of the source code uh protecting the Qt called proper from from that
and without knowledge that this would ever happen but obviously as you know no that was precisely what was needed because there's no connection ball contact and entity is not exactly note that England bought by microsoft so is not really exactly in the scope of of the interests of Microsoft as an organization right now but because of security Foundation the vacated the attitude to set themselves up the actually manage to keep that in protected so what was 11 1 can become a liability and you need to
set up infrastructure for that early on if you must not like you to you would like that and and you have to understand that in certain situations and parallel on the sensitive opened that for example it's better to have an open source something and push it into the limits kind of for example is a little relation contended technology that elected by off computer and on the way of doing that you might even transform set survive from suffer company to service company being suffer companies that of course because the revenue is high service is then it's a very hard business but it's better than to go away and so that that
is also a 2 stage thing here need to clean up the licensing protect that you need to build free documentation very important if you look at that the master documentation and dividing the documentation you see the problem here the most the the condition is not free need to teach and tunnels and they're often undocumented need to build a community that is if you look at Open Office it's very hard to find all was very
hard for a long time to find contributions from outside of the 1st sentence in OpenOffice the engineered to grow people from users of use of the contributors and that in the process of that you also need to clean up the source tree and that's basically makes a clear that managing Open source I think this a complicated process because complicated thing about that is really talking to each other on the organizational level not on the people that you see sitting with the developers of then over tonight
and but you companies on organizations and must not many but the company's stamp probably not talking to each other properly and the real work years since setting up these channels and protecting them with contracts or whatever other kind of agreements is appropriate for your organization's and then establish that flow so that it keeps going even if you will this story about thank you very much if
Resultante
Offene Menge
Bit
Open Source
Computersicherheit
Schlussregel
Biprodukt
Computeranimation
Eins
Internetworking
Metropolitan area network
Software
Freeware
Datenverarbeitungssystem
Existenzsatz
Digital Rights Management
Projektive Ebene
Kantenfärbung
Metropolitan area network
Softwaretest
Metropolitan area network
Subtraktion
Punkt
Sichtenkonzept
Benutzerschnittstellenverwaltungssystem
Open Source
Abgeschlossene Menge
Biprodukt
Datenfluss
Term
Code
Computeranimation
Umwandlungsenthalpie
Resultante
Randwert
Prozess <Physik>
Besprechung/Interview
Extrempunkt
Computeranimation
Distributionstheorie
Protokoll <Datenverarbeitungssystem>
Besprechung/Interview
Versionsverwaltung
Programm
t-Test
Ähnlichkeitsgeometrie
Gibbs-Verteilung
Extrempunkt
Biprodukt
Modul
Computeranimation
Kernel <Informatik>
Metropolitan area network
Client
Negative Zahl
Bildschirmmaske
Menge
Offene Menge
Existenzsatz
Mereologie
Programmbibliothek
Server
Projektive Ebene
Wort <Informatik>
Mathematisierung
Besprechung/Interview
Computeranimation
Homepage
W3C-Standard
Metropolitan area network
Client
Freeware
Programmbibliothek
Zoom
Skript <Programm>
Cluster <Rechnernetz>
Benchmark
Meta-Tag
Inklusion <Mathematik>
Umwandlungsenthalpie
Open Source
Ausnahmebehandlung
Mailing-Liste
Biprodukt
Frequenz
Verdeckungsrechnung
eCos
Projektive Ebene
Normalspannung
Versionsverwaltung
Prozess <Physik>
Open Source
Programmbibliothek
Biprodukt
Einflussgröße
Computeranimation
System F
Fehlererkennungscode
Digitales Zertifikat
Chiffrierung
Open Source
Abgeschlossene Menge
Code
Phasenumwandlung
Offene Menge
Präkonditionierung
Klasse <Mathematik>
Programm
Programmverifikation
Quellcode
Biprodukt
Computeranimation
Internetworking
Metropolitan area network
Twitter <Softwareplattform>
Mereologie
Programmbibliothek
Projektive Ebene
Quader
Besprechung/Interview
Versionsverwaltung
Zahlenbereich
Ausnahmebehandlung
Vektorpotenzial
Code
Quick-Sort
Computeranimation
Software
Mereologie
URL
Softwareentwickler
Chatbot
Offene Menge
Computerspiel
Desintegration <Mathematik>
Dreiecksfreier Graph
Besprechung/Interview
Übergang
Computeranimation
Übergang
Offene Menge
Subtraktion
Web Site
Prozess <Physik>
Selbst organisierendes System
Versionsverwaltung
NP-hartes Problem
Code
Computeranimation
Erwartungswert
Prozess <Informatik>
Code
Softwareentwickler
Stochastische Abhängigkeit
Benchmark
Schreib-Lese-Kopf
Schnittstelle
Softwareentwickler
Datenhaltung
Open Source
Biprodukt
Einfache Genauigkeit
Mereologie
Ablöseblase
Wort <Informatik>
Projektive Ebene
Programmierumgebung
Unternehmensarchitektur
Standardabweichung
Punkt
Freeware
Gruppenoperation
Formale Sprache
Besprechung/Interview
NP-hartes Problem
Äquivalenzklasse
Gesetz <Physik>
Systemplattform
Code
Computeranimation
Internetworking
Physikalisches System
Streaming <Kommunikationstechnik>
Freeware
Benutzerbeteiligung
Code
Mustersprache
Programmbibliothek
Softwareentwickler
Leistung <Physik>
Kategorie <Mathematik>
Systemaufruf
p-Block
Biprodukt
Fokalpunkt
Flächeninhalt
Debugging
Mereologie
Projektive Ebene
Extreme programming
Stereometrie
Prozess <Physik>
Punkt
Definite-Clause-Grammar
Besprechung/Interview
Viewer
Computeranimation
Richtung
Netzwerktopologie
Freeware
Informationsmodellierung
Gammafunktion
Open Source
Datenhaltung
Kontinuierliche Integration
Quellcode
Biprodukt
Dialekt
Arithmetisches Mittel
Transaktionsverwaltung
Menge
Ablöseblase
Projektive Ebene
Information
Sigma-Algebra
Ordnung <Mathematik>
Eigentliche Abbildung
Axiom
Personal Area Network
Fehlermeldung
Fitnessfunktion
Orakel <Informatik>
Zeichenkette
Impuls
Stereometrie
Gewichtete Summe
Punkt
Hochdruck
Mathematisierung
Formale Sprache
Term
Systemplattform
Code
Computeranimation
Übergang
Metropolitan area network
Maßerweiterung
Softwareentwickler
Maschinelles Sehen
Informationsmanagement
Leistung <Physik>
Kategorie <Mathematik>
Open Source
Datenhaltung
Verzweigendes Programm
Plug in
Strömungsrichtung
Vektorraum
Physikalisches System
Biprodukt
Content Management
Konstante
Strategisches Spiel
Bildschirmsymbol
Ordnung <Mathematik>
Unternehmensarchitektur
Programmierumgebung
Orakel <Informatik>
Codec
Resultante
Metropolitan area network
Flächentheorie
Endogene Variable
Versionsverwaltung
Unrundheit
Code
Teilbarkeit
Computeranimation
Metropolitan area network
Prozess <Informatik>
Maskierung <Informatik>
Relativitätstheorie
Besprechung/Interview
Mailing-Liste
Ordnung <Mathematik>
Code
Computeranimation
Betragsfläche
Dokumentenserver
Open Source
Stab
Baum <Mathematik>
t-Test
Biprodukt
Code
Computeranimation
Metropolitan area network
Patch <Software>
Prozess <Informatik>
Kompakter Raum
Mereologie
Nichtunterscheidbarkeit
Stützpunkt <Mathematik>
Softwareentwickler
Gammafunktion
Schnittstelle
Kraftfahrzeugmechatroniker
Selbst organisierendes System
Adressraum
Besprechung/Interview
Versionsverwaltung
Bitrate
Biprodukt
Term
Algorithmische Programmiersprache
Computeranimation
Patch <Software>
Selbst organisierendes System
Unterring
Offene Menge
Eigentliche Abbildung
Dateiformat
Projektive Ebene
Große Vereinheitlichung
Schnittstelle
Softwarewartung
Schnittstelle
Benutzeroberfläche
Offene Menge
Singularität <Mathematik>
Programmbibliothek
Gruppenkeim
Ordnung <Mathematik>
Term
Einflussgröße
Computeranimation
Standardabweichung
Nichtlinearer Operator
Punkt
Euler-Winkel
Selbst organisierendes System
Extrempunkt
Klasse <Mathematik>
Versionsverwaltung
Baumechanik
Äquivalenzklasse
Biprodukt
Computeranimation
Auflösbare Gruppe
Ablöseblase
Kontrollstruktur
Ordnung <Mathematik>
Programmierumgebung
Standardabweichung
Leistung <Physik>
Prozess <Physik>
Euler-Winkel
Selbst organisierendes System
Mathematisierung
Klasse <Mathematik>
Besprechung/Interview
Gruppenkeim
t-Test
Kartesische Koordinaten
Code
Computeranimation
Metropolitan area network
Mailing-Liste
Font
Biprodukt
Softwareentwickler
Ganze Funktion
Informationsmanagement
Autorisierung
Softwaretest
Relativitätstheorie
Quellcode
Bitrate
Algorithmische Programmiersprache
Mereologie
Personal Area Network
Orakel <Informatik>
Telekommunikation
Linienelement
Selbst organisierendes System
Browser
Formale Sprache
Mathematisierung
Quellcode
Code
Computeranimation
Bildschirmmaske
Beweistheorie
Chatten <Kommunikation>
Ablöseblase
Modelltheorie
Tropfen
Ordnung <Mathematik>
Benchmark
Standardabweichung
Tropfen
Telekommunikation
Befehl <Informatik>
Mereologie
Prozess <Physik>
Selbst organisierendes System
Mathematisierung
Patch <Software>
Biprodukt
Code
Computeranimation
Office-Paket
Patch <Software>
Code
Mereologie
Maschinelles Sehen
Biprodukt
Tropfen
Maschinelles Sehen
Telekommunikation
Prozess <Physik>
Selbst organisierendes System
Desintegration <Mathematik>
Hardwarebeschreibungssprache
Güte der Anpassung
Systemaufruf
Kontextbezogenes System
Code
Computeranimation
Beanspruchung
Selbst organisierendes System
Last
Bildschirmmaske
Informationsverarbeitung
Last
Overhead <Kommunikationstechnik>
Overhead <Kommunikationstechnik>
Ordnung <Mathematik>
Telekommunikation
Bit
Prozess <Physik>
Kategorie <Mathematik>
Selbst organisierendes System
Besprechung/Interview
Versionsverwaltung
Zellularer Automat
Orakel <Informatik>
Mailing-Liste
Betriebssystem
Humanoider Roboter
Frequenz
Code
Computeranimation
Übergang
Kernel <Informatik>
Metropolitan area network
Modallogik
Software
Mereologie
Programmbibliothek
Response-Zeit
E-Mail
Open Source
Mathematisierung
Formale Sprache
Besprechung/Interview
Projektive Ebene
Physikalisches System
Code
Computeranimation
Informationsmanagement
Punkt
Dämpfung
Open Source
Bildschirmfenster
Besprechung/Interview
Programmbibliothek
Betriebssystem
Biprodukt
Programmierumgebung
Computeranimation
Office-Paket
Einfach zusammenhängender Raum
Einfügungsdämpfung
Selbst organisierendes System
Computersicherheit
Hausdorff-Dimension
Besprechung/Interview
Projektive Ebene
Euler-Winkel
Quellcode
Computeranimation
NP-hartes Problem
Offene Menge
Open Source
Relativitätstheorie
Besprechung/Interview
Dienst <Informatik>
Computeranimation
Office-Paket
Dienst <Informatik>
Software
Bildschirmmaske
Offene Menge
Konditionszahl
Windkanal
Inverser Limes
Versionsverwaltung
Parallele Schnittstelle
Offene Menge
Prozess <Physik>
Selbst organisierendes System
Transformation <Mathematik>
Open Source
Besprechung/Interview
Quellcode
Datenfluss
Computeranimation
Übergang
Design by Contract
Freeware
Reelle Zahl
Softwareentwickler
Offene Menge
Software
Freeware
Computeranimation

Metadaten

Formale Metadaten

Titel Open Source Management - Strategies for comm. with open source projects in companies
Serientitel FrOSCon 2014
Teil 19
Anzahl der Teile 59
Autor Köhntopp, Kristian
Lizenz CC-Namensnennung - keine kommerzielle Nutzung 2.0 Deutschland:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
DOI 10.5446/19638
Herausgeber Free and Open Source software Conference (FrOSCon) e.V.
Erscheinungsjahr 2014
Sprache Englisch

Technische Metadaten

Dauer 54:03

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract Open Source Management Strategies for communication with open source projects in companies The use of open source in enterprises is common, even in Germany. In many companies the imported source is being changed, bugfixed, made compatible with whatever or otherwise changed. Companies are using open source, changing it or contribute otherwise. This can take many forms, leading to company internal forks of software, public neglect of ubiquitous projects such as OpenSSL or Busybox, a variety of patches that are badly integrated into an upstream as in MySQL, or a wrestling for dominance in projects such as Hadoop and Openstack. ······························ Speaker: Kristian Köhntopp Event: FrOSCon 2014 by the Free and Open Source Software Conference (FrOSCon) e.V.
Schlagwörter Free and Open Source Software Conference
FrOSCon14

Ähnliche Filme

Loading...