4. The Four aspects Slide Number:4 Financial Technical Legal Marketing
5. Financial Technical Benefits Initial costs Licensing Maintenance? End of life Concentration on Business Domain Risks Support contracts Copyright/left Risk to customers Benefits Mostly ready Standards Knowhow “Many eyeballs” Tested Fast Turnover Risks Quality? Release Timing CR, bug acceptance Too general Legal Marketing Risks Viral Effect Licenses may be unclear Intellectual Property License incompatibility Risks Manage Customer Benefits Company Image Interaction with other parties Concentration on Business domain Slide Number:5
9. Isolating the OSS in Layers Business Domain Product 1 Product 2 Product 3 Component 1 Component 2 OSS Distribution Layer Third Party Core Platform Platform HW/CLOUD Slide Number:9
19. Third part Case Study: Symas Slide Number:13 Corporate LDAP requirements Replication stability Write performance High availability On a single site and across sites Read performance scaling No manual actions during site failover Full and Fast Replication stability is the only requirement that the current OpenLDAP solution is not able to provide
22. Q/A Slide Number:16 How much? What? How many? Where? Why? Whose? Who? Thank You for Your Attention! Whom? When? Which?
Editor's Notes
Marketing Benefits Creates a better image of the company social awarnessincurages interaction with other companies Allows the company to concentrate on it critical buisness domain Risks Customers must be informed about the use of OSS and impacts this might have on delivery of issues explain to the customer that sharing the source does not hinder the sucurity of software this is achieved today via enrypted keys, firewalls Technical Benefits Tested by many people Allows the reuase of knowladgeaquired elsewhere - university other companiecode reviewed through many eyeballs Risks code quality maybe] unknown this is very important for OSS that do not have a large community Timing of future release with new bug fixes Delay between fix/functionality implemention and community acceptance Financial Benefits Lower cost of maintenance? initial costs are minimal No licencing costs end of life cycle donating software to the community may be a cost effective way to handle maintenance on old software this also gives the customers ability to modify the software to their needs this might be efficient if the company has dicided to concentrate on a different buisness domain Risks Support contracts? it is common for other parties to specialize in this area examples RedhatSuseUbuntuMandrake Symas ~ copyleftThis might also prevent companies from charging for their products Benefits and disbenifits must be shared together with the customer Legal risks viral effect of copy left(GPL) when code is linked or incorporated into a companies domain logic that software might also have to be release it this might go the other way when the company wants to release a product as opernsource by not allow others to utilize it inside of it's products dual licencingsomtimes this gives the possibility to buy enhanced rights from the owner of the software adherence to certain licences may be complicated as they do not have to be clearly drafted possible licencing issues can be provided without any intelectual property idemnification or warranty company may be held legally responsible for any patent or copyright violations example HTC, Samsung These cannot be forwarded to the original contributors must be drafted into the companies outbound licencing terms and made apparent to the customers contractual support of OSS does not have to cover IPR redhat provides some limited guarenteesCompatibility of licenceslicences that contradict each other are incompatible and software cannot be combined Most opensourcelicences are general templates these might be changed for a specific source code never assume two Apache 2.0 licences are the same
Basic platform built on top of RedHat that adheres to the ELO Support guaranteed localized inside of a separate project Distribution Layer incorporates open source packages not present in the basic platform present but with a different version communicates towards the open source community Internal software must adhere to rulesMinimal documentationBenefitsCost Aggregate LicensingAligning ArchitectureLimits Duplication of EffortCommunication with the OSS CommunityFaster UpdatesThird Party Support ContactComponentsLocalization of larger OS projects into separate entities BenefitsCost Aggregate LicensingAligning ArchitectureLimits Duplication of EffortCommunication with the OSS CommunityFaster UpdatesThird Party Support Contact
