Revision as of 09:00, 14 July 2014

Are you a new committer or project lead for an Eclipse project? Are you thinking about proposing a new open source project at Eclipse? 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 at Eclipse. The discussion includes an overview of the Eclipse Development Process, the Intellectual Property Due Diligence Process, and the Tools and IT Infrastructure available to Eclipse projects.

• 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).

Agenda

The Eclipse Development Process

• Open source rules of engagement
  • Transparency: Invite participation
    • Record discussion/decisions in mailing list, wiki, or other medium (e.g. [1], [2], [3])
    • 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
  • Eclipse Management Organization (EMO)
  • Architecture and Planning Councils
  • Committers and contributors
  • Project leads (PL)
  • Project Management Committee (PMC)
  • ...
• Project Management Infrastructure
  • Overview
  • Managing project metadata
  • Downloads, charts, etc.

Intellectual Property Due Diligence

• Intellectual Property Overview (Who, What, Why)
  • IP Due Diligence Process
• Contribution Types
  • EPL (Project Licensed)
  • Non EPL - Third Party
• Preparing an Initial Contribution
  • Welcome to IPZilla
  • Tips to ensure success
• Contribution Questionnaire (CQ)
  • When do you need a 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
  • Release Reviews
• 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 release metadata
  • Releases and reviews

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.