Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Development Resources/Committer Bootcamp"
(10 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | Are you a new committer or project lead for an Eclipse project? Are you thinking about proposing a new open source project | + | Are you a new committer or project lead for an Eclipse, LocationTech, or PolarSys project? Are you thinking about proposing a new open source project? In this tutorial, Eclipse Foundation staff members will walk you through the information that you need to know to be an effective open source project committer. The discussion includes an overview of the Eclipse Development Process, the Intellectual Property Due Diligence Process, and the Tools and IT Infrastructure made available to open projects by the Eclipse Foundation. |
+ | * [[File:EclipseCommitterBootcampMarch2015.pdf|EclipseCon North America 2015]] (watch for updates) | ||
+ | * [[File:EclipseCommitterBootcampJuly2014.pdf]] | ||
* [[File:EclipseCommitterBootcampOpenMay2014.pdf]] | * [[File:EclipseCommitterBootcampOpenMay2014.pdf]] | ||
* Delivered to the OpenMDM working group ([[File:EclipseCommitterBootcampOpenMDM.pdf|slides]]) | * Delivered to the OpenMDM working group ([[File:EclipseCommitterBootcampOpenMDM.pdf|slides]]) | ||
Line 9: | Line 11: | ||
==The Eclipse Development Process== | ==The Eclipse Development Process== | ||
* [http://eclipse.org/projects/dev_process/#2_1_Open_Source_Rules_of_Engagement Open source rules of engagement] | * [http://eclipse.org/projects/dev_process/#2_1_Open_Source_Rules_of_Engagement Open source rules of engagement] | ||
+ | ** Transparency: Invite participation | ||
+ | *** Record discussion/decisions in mailing list, wiki, or other medium (e.g. [https://dev.eclipse.org/mhonarc/lists/stem-dev/msg00704.html], [https://wiki.eclipse.org/Orion/Meeting_minutes/20120405], [https://wiki.eclipse.org/Dali_R1.0_Planning_meetings_-_Monday]) | ||
+ | *** Use Bugzilla to capture discussion for new features (all code should have some corresponding Bugzilla or Gerrit record) | ||
+ | ** Openness: Accept participation | ||
+ | *** Level playing field: open to all comers | ||
+ | *** Same set of rules for all contributors (even competitors) | ||
+ | ** Meritocracy: Earn your way in | ||
+ | *** Contributors who demonstrate good behaviour may be invited to join the project | ||
+ | *** Earn more responsibility | ||
* Who's who/Who does what | * Who's who/Who does what | ||
** [http://eclipse.org/projects/dev_process/#4_Structure_and_Organization Eclipse Management Organization (EMO)] | ** [http://eclipse.org/projects/dev_process/#4_Structure_and_Organization Eclipse Management Organization (EMO)] | ||
Line 20: | Line 31: | ||
** [[Project Management Infrastructure/Project Metadata|Managing project metadata]] | ** [[Project Management Infrastructure/Project Metadata|Managing project metadata]] | ||
** [[Project Management Infrastructure/Project Metadata#Downloads|Downloads]], charts, etc. | ** [[Project Management Infrastructure/Project Metadata#Downloads|Downloads]], charts, etc. | ||
− | |||
==Intellectual Property Due Diligence== | ==Intellectual Property Due Diligence== | ||
* Intellectual Property Overview (Who, What, Why) | * Intellectual Property Overview (Who, What, Why) | ||
+ | ** [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf IP Due Diligence Process] | ||
* Contribution Types | * Contribution Types | ||
**EPL (Project Licensed) | **EPL (Project Licensed) | ||
Line 30: | Line 41: | ||
** Welcome to IPZilla | ** Welcome to IPZilla | ||
** Tips to ensure success | ** Tips to ensure success | ||
+ | * [[Development Resources/Contribution Questionnaire|Contribution Questionnaire]] (CQ) | ||
+ | ** [[Development Resources/Contribution Questionnaire##Third_Party_Libraries|When do you need a CQ?]] | ||
==Resources and Provisioning== | ==Resources and Provisioning== |
Latest revision as of 15:40, 4 March 2015
Are you a new committer or project lead for an Eclipse, LocationTech, or PolarSys project? Are you thinking about proposing a new open source project? In this tutorial, Eclipse Foundation staff members will walk you through the information that you need to know to be an effective open source project committer. The discussion includes an overview of the Eclipse Development Process, the Intellectual Property Due Diligence Process, and the Tools and IT Infrastructure made available to open projects by the Eclipse Foundation.
- File:EclipseCommitterBootcampMarch2015.pdf (watch for updates)
- File:EclipseCommitterBootcampJuly2014.pdf
- File:EclipseCommitterBootcampOpenMay2014.pdf
- Delivered to the OpenMDM working group (File:EclipseCommitterBootcampOpenMDM.pdf)
- Delivered at EclipseCon North America 2014 (slides)
- Delivered at EclipseCon Europe 2013 (slides).
Contents
Agenda
The Eclipse Development Process
- Open source rules of engagement
- Transparency: Invite participation
- Openness: Accept participation
- Level playing field: open to all comers
- Same set of rules for all contributors (even competitors)
- Meritocracy: Earn your way in
- Contributors who demonstrate good behaviour may be invited to join the project
- Earn more responsibility
- Who's who/Who does what
- Project Management Infrastructure
- Overview
- Managing project metadata
- Downloads, charts, etc.
Intellectual Property Due Diligence
- Intellectual Property Overview (Who, What, Why)
- Contribution Types
- EPL (Project Licensed)
- Non EPL - Third Party
- Preparing an Initial Contribution
- Welcome to IPZilla
- Tips to ensure success
- Contribution Questionnaire (CQ)
Resources and Provisioning
- Overview of Infrastructure
- Your Eclipse Foundation account, committer ID, other forges
- Project provisioning process
- Initial contribution, tools for committers: Git, Gerrit, Bugzilla, Wiki, project website
- Interacting with your users: Forums, mailing lists
- Asking for help: webmasters, other committers
Managing Your Eclipse Project
- Community development, project diversity
- Elections
- Release Cycle
- Reviews
- Graduation, Restructuring, and Termination Reviews
- The automatic IP Log generator: data sources (Bugzilla, Git), etc.
- Technical review of IP Logs
- The download scanner
- Project Management Infrastructure
Managing Intellectual Property
- Using third-party code
- Dependencies
- Build and test
- Parallel IP
- IP review stages (IPZilla cont'd)
- Due Diligence Review
- IP Logs - Review/Approval
- IP Best Practices
Downloads, Builds
- CBI, Hudson/HIPP and producing a build
- Signing
- Where to store build artifacts, linking, using mirrors
- Download statistics
- Cleaning up
Appendices
Starting a New Open Source Project
- Starting a new project: From proposal to creation review
This page is moderated by the EMO.