SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere Nutzervereinbarung und die Datenschutzrichtlinie.
SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere unsere Datenschutzrichtlinie und die Nutzervereinbarung.
Eclipse FoundationVert.x ExampleDear Vert.x Community,As many of you already know I left VMware at the end ofDecember and started at Red Hat last week.In the spirit of open source and as a commitment to the Vert.xcommunity I had expected (perhaps naively) that VMwarewould continue to let me continue to administer the Vert.x project afterI had left their employment.On the 28th December I received a letter from VMware lawyers(delivered to my door in person, no less!) that I must immediately giveup and transfer to VMware all administrative rights over the followingthings: The Vert.x github project, the Vert.x google group, thedomain vertx.io and the Vert.x blog.Source: Tim Fox, Vert.x Google Group
Eclipse FoundationGovernance = Who Is In ControlIP Ownership Control– Copyright, Trademark, LicenseDevelopment Control– Who controls the code repository– Who makes the decision on project releases andfunctionality– Platform support
Eclipse FoundationGovernance QuestionsHow are decision made?Who is final authority?What are the business motivationsof the final authority?
Eclipse FoundationVert.x Options1) "Netty-style solution". In this solution almost everything continues as-is. Theonly difference is a CLA is crafted that grants rights of the contributions not to RHTor VMW, but to the "Project". This would require VMWare to grant a perpetuallicense to the "Project" for use of the name Vert.x.2) Fork. We wouldnt have permission to use the name Vert.x so wed have torename the project. That means removing all references to Vert.x from thecode, documentation, and other materials. Wed also lose the current githubissues, the wiki, the blog, Google Group and domain. This would not require anypermission from VMware.3) Move project to Apache Software Foundation. This would need approval fromASF and VMware.4) Move project to the Eclipse Foundation. This would need approval from theEclipse Foundation and VMware.Tim Fox - Vert.x Google Forum – January 10, 201301/05/2013 19
Eclipse FoundationGovernance Options1. Fork2. Status quo3. Create a legal entity for the ‘Project’.- Create a Foundation4. Move Project to a Foundation
Eclipse FoundationStatus Quo: IndividualsSomething that isnt a legal entity canthold copyright. I do see frequently that some FreeSoftware projects have notices say Copyright, TheProject". However, if "The Project" isnt a legal entity insome jurisdiction somewhere in the world, thats probablynot a valid copyright notice, and I recommend againstusing it.Bradley KuhnVert.x Google GroupJanuary 10,201301/05/2013 22
Eclipse FoundationCreating a Foundation01/05/2013 24
Eclipse FoundationGoals of Creating a FoundationNo special statusLong-term stability
Eclipse FoundationIncorporation• Incorporation– 501.c3 (a charity)– 501.c6 (trade association)• Write Bylaws• Selecting Board of DirectorsI wanted to keep the project neutral. However, inKorea, it is pretty difficult for an individual tofound a non-profit.Trustin Lee, Netty Project LeaderVert.x Google Forum, January 10, 2013
Eclipse FoundationAgreements• Membership Agreement• Open Source License Selection• Contribution and Committer Agreements• Trademark Guidelines
Eclipse FoundationSetup• Development Process– How are committers determined– How are technical decision made for the project• IT Infrastructure– What forge will be used?• Financials– What is the budget– Professional staff or volunteers– Funding model: donations, memberships, other?
Eclipse FoundationPros and Cons• Pros: Determine your own destiny– Create your own rules to fit your community• Cons: Time and Cost– Legal costs– Time to setup and gain agreement on governanceof the project and legal agreements– Difficult in many countries– Ongoing work
Eclipse FoundationMOVE TO A FOUNDATION01/05/2013 31
Eclipse FoundationTypes of FoundationsSelf-serviceFoundations• Software for thePublic Interest (SPI)• Software FreedomConservatory (SFC)• OutercurveCommunity ofPractice• Apache• Eclipse
Eclipse FoundationCharity (501.c3) vs Trade Association (501.c6)“… Mike has noted in his posts that Eclipse focuses on interactingwith the for-profit industry, which is what trade associations likeEclipse (and Linux Foundation, too) are for. They do a good job atthis task, and if your projects main goal is to interact withfor-profit companies, then a trade associationsolution as a fiscal sponsor is probably right.By contrast, non-profit charities like SPI and Conservancy focuson benefiting the general public. Every time a memberproject at Conservancy wants to do something, the question I ask iswhether the plan helps make the software better (moreavailable, more usable, etc.) for everyone in the general public. Itsnot that charities *ignore* the for-profit corporateuser base, but rather we focus first onthe *individuals* who use and develop the software. ”Bradley KuhnVert.x Google GroupJan. 10 2013
Eclipse FoundationGovernance of Foundation• Charity vs Trade Association• Stakeholders/Membership (Board membership)• Meritocracy• Independent Advisors / Professional Staff
Eclipse FoundationIP Management• License selection and compatibility• Copyright aggregation (or not)– CLA• IP due diligence• Committer records• Trademark ownership
Eclipse FoundationIT InfrastructureIMO, any neutral foundation we go with should providea) Hosting for git repository, mirrorable to the _current_project at github. Please no svn, cvs or mercurialb) Hosting for issue tracker. JIRA preferred. Dont likebugzilla.c) Hosting for mailing listsd) Hosted for project web sitee) Hosting for downloadsf) Hosting for public module repository - in Vert.x 2.0 this islikely to be a Maven repository.g) Ability to use external CI, e.g. CloudBees or Travish) Can accept pull requests via githubTim FoxVert.x Google GroupJanuary 13, 2013
Eclipse FoundationSoftware for Public InterestServices OfferedGovernance 501.c3Individual and organizational membershipDevelopment Process Project DefinedIP Management Rules Project ResponsibilityIT Infrastructure Project ResponsibilityCommunity Development NonePooling Financial Resources Yes, accepts donations on behalf of theproject01/05/2013 38
Eclipse FoundationSoftware Freedom ConservatoryServices OfferedGovernance 501.c3Professional StaffDevelopment Process Project DefinedIP Management Rules • Hold assets on project behalf• Contract negotiations• FLOSS copyright enforcementIT Infrastructure Project ResponsibilityCommunity Development Conference logistical supportPooling Financial Resources Yes, accepts donations on behalf of the project01/05/2013 39
Eclipse FoundationOutercurveServices OfferedGovernance 501.c6Corporate membershipProfessional staffDevelopment Process Provides guidelines and best practicesIP Management Rules Contribution and assignment agreementsLicense agnosticTrademark ownershipIT Infrastructure Project ResponsibilityCommunity Development Events, press support, mentorshipPooling Financial Resources Yes01/05/2013 40
Eclipse FoundationNow that Ive gone through the whole thing, Isee that if one really takes this to the logicalconclusion, youll go the way towardApache/Eclipse style mechanisms. Butthen, one shouldnt have to make the wholeleap in one go, right?Kohsuke KawaguchiSource: Vert.x Google GroupJanuary 10, 201301/05/2013 41