Skip to main content
Jump to: navigation, search

Difference between revisions of "Development Resources/Committer Bootcamp"

(The Eclipse Development Process)
(Intellectual Property Due Diligence)
Line 33: Line 33:
==Intellectual Property Due Diligence==
==Intellectual Property Due Diligence==
* Intellectual Property Overview (Who, What, Why)
* Intellectual Property Overview (Who, What, Why)
** [[ IP Due Diligence Process]]
** [ IP Due Diligence Process]
* Contribution Types  
* Contribution Types  
**EPL (Project Licensed)
**EPL (Project Licensed)

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.


The Eclipse Development Process

Intellectual Property Due Diligence

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

Managing Intellectual Property

Downloads, Builds

  • CBI, Hudson/HIPP and producing a build
  • Signing
  • Where to store build artifacts, linking, using mirrors
  • Download statistics
  • Cleaning up


Starting a New Open Source Project

This page is moderated by the EMO.

Back to the top