Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Development Resources/Committer Bootcamp"

(The Eclipse Development Process)
(Intellectual Property Due Diligence)
(4 intermediate revisions by the same user not shown)
Line 11: Line 11:
 
* [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
 
** 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])
+
*** 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)
 
*** Use Bugzilla to capture discussion for new features (all code should have some corresponding Bugzilla or Gerrit record)
 
** Openness: Accept participation
 
** Openness: Accept participation
Line 30: Line 30:
 
** [[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.
* Dash Overview
 
  
 
==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 40: Line 40:
 
** 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==

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.

Agenda

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

Appendices

Starting a New Open Source Project


This page is moderated by the EMO.

Back to the top