• Like
  • Save
Open source masterclass - Life in the Apache Incubator
Upcoming SlideShare
Loading in...5
×
 

Open source masterclass - Life in the Apache Incubator

on

  • 1,355 views

 

Statistics

Views

Total Views
1,355
Views on SlideShare
1,333
Embed Views
22

Actions

Likes
6
Downloads
14
Comments
0

1 Embed 22

https://twitter.com 22

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Open source masterclass - Life in the Apache Incubator Open source masterclass - Life in the Apache Incubator Presentation Transcript

  • Open source masterclass - Life in the Apache Jukka Zitting | repeat mentor, activist chairman of the IPMC© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
  • Agenda Introduction to the Incubator Entering the Incubator IP review and releases Community growth and diversity Self-evaluation and graduation© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 2
  • Introduction to the Incubator© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
  • The Incubator charter “a Project Management Committee charged with accepting new products into the Foundation, providing guidance and support to help each new product engender their own collaborative community, educating new developers in the philosophy and guidelines for collaborative development as defined by the members of the Foundation, and proposing to the board the promotion of such products to independent PMC status once their community has reached maturity.”© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 4
  • Why? Community  We want all Apache projects to succeed as communities  Community structure and processes are important factors of long-term success IP clearance and releases  A key purpose of the ASF is to provide legal shelter to individual contributors  To do that, we need to follow a few processes designed to guarantee that:  the community, not just an individual, know and understand what is being released Infrastructure  The ASF provides lots of infrastructure support to its projects  Projects should know what infrastructure is available and how to best work with the half-volunteer team behind it  Note that some infrastructure decisions are limited by community and IP© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 5
  • Who? Incubator PMC  ASF members and other experienced open source people  Oversees all podlings, decides on acceptance, releases, graduation, etc. Mentors and the Podling PMCs (PPMC) Podling communities  committers, contributors, users, trolls, etc.© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 6
  • Incubation process Establishment Rejection Acceptance Retirement Graduation Retirement© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 7
  • Entering the Incubator© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
  • Establishment, see http://incubator.apache.org/guides/proposal.html© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 9
  • Proposal template  Background  An excessive fascination with the Apache brand  Rationale  Documentation  Initial goals  Initial source  Current status  Source and intellectual property  Meritocracy submission plan  Community  Core developers  External dependencies  Alignment  Cryptography  Known Risks  Required resources  Orphaned products  Mailing lists  Inexperience with open source  Subversion directory  Homogenous developers  Issue tracking  Reliance on salaried developers  Other resources  Relationship with other Apache  Initial committers products  Affiliations  Sponsors© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 10
  • Then what? The basics  Set up the mailing list  Set up other infrastructure  Migrate your source code  Get hacking! The harder bits  IP review  Apache release  Community growth  Self-evaluation Finally  Graduation!© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 11
  • IP review and releases© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
  • IP review Contributor license agreements and software grants  http://www.apache.org/licenses/#clas  http://www.apache.org/licenses/#grants Source headers  http://www.apache.org/legal/src-headers.html Licensing of dependencies  http://www.apache.org/legal/resolved.html© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 13
  • Apache release Lots of details!  http://www.apache.org/dev/#releases  Your mentors are there to help and explain  Plan for a few weeks to a few months for your first release  It gets easier after the first time Typical problems  Source headers, see Apache RAT  Licensing of dependencies  Binaries© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 14
  • Community growth and diversity© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
  • Identifying and inviting new committers Who’s contributing patches?  Look at the issue tracker Make sure all patches are reacted to  Even just a comment why it’s not ready yet Better too many committers than too few© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 16
  • Community diversity Who’s committing stuff?  Substantial contributions from more than one committer/company Are people participating in decision?  Mailing list discussions  Votes on releases and new committers  etc. If in trouble  Raise awareness  Focus on potential new contributors/committers  Getting started guide  Easier build and first startup© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 17
  • Self-evaluation and graduation© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
  • Self-evaluation Quarterly reports to the Incubator PMC and the ASF board  Monthly for the first three months, or when requested/desired  Reports due on the first wednesday of the month Why?  Let the IPMC and the board know what’s going on  Opportunity for introspection - how are we doing? where are we going?  Record of project history What?  Typically a few paragraphs to a single page in size  Records all essential topics since the last report  Summarizes current status and outlook for the future  Highlights any issues that the IPMC or the ASF board should be aware of  IP problems, trademark issues, community trouble, etc.© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 19
  • Report template  One-sentence summary of the project  Date of entry to the Incubation  Top 2-3 issues to resolve before gradation  Summary of project status© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 20
  • Graduation criteria Complete (and sign off) tasks documented in the status file Ensure suitability for project name and product names Demonstrate ability to create Apache releases Demonstrate community readiness Ensure that mentors and the IPMC have no remaining issues© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 21
  • Graduation schedule© 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 22
  • © 2012 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.