Skip to main content
Jump to: navigation, search

Difference between revisions of "Committer Contributor Hangouts/september 19"

(Presentation)
(added discussion script)
Line 25: Line 25:
 
== Discussion Script ==
 
== Discussion Script ==
  
Will be added after video is posted
+
== Hangout questions for September 19/2014 ==
 +
 
 +
=== Contributors ===
 +
 
 +
==== Speaker introduction ====
 +
 
 +
Richard Burcher from the Eclipse Foundation.
 +
 
 +
=== Structure of talk ===
 +
 
 +
==== Summary ====
 +
 
 +
Contributions to an Eclipse project take many forms. As a committer, you should do everything possible to encourage contribution by members of the community that surrounds your project. Contributions take the form of code, input into your project's wiki pages, answering questions on newsgroups/stackoverflow and more.
 +
 
 +
==== Discussion ====
 +
 
 +
We'll talk about contributions in the form of code. This is usually what folks think about when you mention contributors. It's in the projects interest to really help these folks about when they arrive at your project. Contributors bring new ideas, patches, features and may ultimately become involved with the project long term as a committer. Remember they've shown interest in your project (awesome!) so be extra nice to them:) In all of this, there's a few things that you the contributor and project committers must keep in mind when accepting code contributions. We'll touch more on this below.
 +
 
 +
===== Basics =====
 +
 
 +
Broken down by theme:
 +
 
 +
* Contributor<br />
 +
* What does that mean at the Eclipse Foundation?<br />
 +
* This is an individual who is not a project committer but has offered some form of code contribution to an Eclipse project.<br />
 +
* Before submitting code, you should be familiar with the following documents in principle:
 +
** The [http://www.eclipse.org/projects/dev_process/development_process.php Eclipse Development Process (EDP)].<br />
 +
** The [http://eclipse.org/legal/EclipseLegalProcessPoster.pdf Eclipse Intellectual Property (IP) Due Diligence Process].<br />
 +
* Project committers handle the code review and process (merge to master) to accept the contribution.<br />
 +
* Project specific points:
 +
** You'll need to become familiar with the specific projects workflow you plan to contribute to. Find the project on the [https://projects.eclipse.org/list-of-projects Eclipse projects site].<br />
 +
** Project specific details are listed under the tab &quot;Developer Resources&quot;.<br />
 +
** Check for bugs listed as help needed.<br />
 +
** Reach out to the project on its mailing lists. You'll find these under the &quot;Contact Us&quot; tab of the projects page.<br />
 +
** Getting Help<br />
 +
** Projects have at least one mailing list.<br />
 +
* Code submission and acceptance by a project committer<br />
 +
* As a committer you are responsible for maintaining the IP cleanness of the projects code. Care must be taken when accepting contributions.<br />
 +
* All Eclipse projects must abide by the [https://www.eclipse.org/projects/dev_process/development_process.php Eclipse Development Process (EDP)] and [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf IP Due Diligence] processes.<br />
 +
* Once you (the committer) is satisfied that the code is okay to commit, you must also check the following:<br />
 +
* The contributor has a valid and signed [http://www.eclipse.org/legal/CLA.php Eclipse CLA]. You can check this via the projects PMI page, under Committer Tools, there's a subsection called Contributor Agreement. Just enter the users Eclipse account email to verify.<br />
 +
* Contributors must sign-off on their contributions via the [http://www.eclipse.org/legal/CoO.php Certificate of Origin (CoO)].<br />
 +
* Code contributions &gt; 1000 lines of code need a [https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire Contribution Questionnaire (CQ)] for the IP Team to review.
 +
 
 +
<pre>To verify whether a contribution requires a CQ, use one of the following git commands to check:
 +
 
 +
    If it's committed:  git log --shortstat
 +
    If not committed: git diff --stat
 +
 
 +
These commands tell you the number of insertions(+), and deletions(-). If the total number of lines inserted (e.g. added) in a contribution is greater than 1000 (yes, this includes comments) then a CQ is required.</pre>
 +
* [https://wiki.eclipse.org/Development_Resources/Becoming_a_Committer Becoming a project committer]<br />
 +
* Contributions are the path to gaining committer status to an existing project.<br />
 +
* Meritocracy is one of the Eclipse Foundation's guiding principles.<br />
 +
* This means, providing high quality contributions that demonstrate your seriousness and value/merit to the project. Each project will define it's own guidelines around what constitutes high quality contributions.<br />
 +
* An existing project committer must nominate you. This will trigger an election, whereby every project committer will vote. the vote is successful if you receive three +1's with no -1 votes. For projects with fewer than three committers, everyone must +1.<br />
 +
* You'll then need complete the required [https://wiki.eclipse.org/Development_Resources/HOWTO/Nominating_and_Electing_a_New_Committer#What_Paperwork_Does_the_New_Committer_Need_.28and_Why.29.3F committer paperwork]. The IP Team will help you here:)

Revision as of 11:00, 19 September 2014

Time

10:30hr EST

Presentation

We'll be talking about Contributors.

What the term means at the Eclipse Foundation, how to get involved, how to contribute (code), getting help and working towards becoming a project committer:)

Richard Burcher from the Eclipse Foundation will be your host.

Hangout Link

Watch Event.

Participating in Q/A

  • Email questions to emo@eclipse.org.
  • Ask questions inside Hangout using chat function.

Hangout Video

  • Video will be uploaded to the Eclipse YouTube channel after the Hangout here.

Discussion Script

Hangout questions for September 19/2014

Contributors

Speaker introduction

Richard Burcher from the Eclipse Foundation.

Structure of talk

Summary

Contributions to an Eclipse project take many forms. As a committer, you should do everything possible to encourage contribution by members of the community that surrounds your project. Contributions take the form of code, input into your project's wiki pages, answering questions on newsgroups/stackoverflow and more.

Discussion

We'll talk about contributions in the form of code. This is usually what folks think about when you mention contributors. It's in the projects interest to really help these folks about when they arrive at your project. Contributors bring new ideas, patches, features and may ultimately become involved with the project long term as a committer. Remember they've shown interest in your project (awesome!) so be extra nice to them:) In all of this, there's a few things that you the contributor and project committers must keep in mind when accepting code contributions. We'll touch more on this below.

Basics

Broken down by theme:

  • Contributor
  • What does that mean at the Eclipse Foundation?
  • This is an individual who is not a project committer but has offered some form of code contribution to an Eclipse project.
  • Before submitting code, you should be familiar with the following documents in principle:
  • Project committers handle the code review and process (merge to master) to accept the contribution.
  • Project specific points:
    • You'll need to become familiar with the specific projects workflow you plan to contribute to. Find the project on the Eclipse projects site.
    • Project specific details are listed under the tab "Developer Resources".
    • Check for bugs listed as help needed.
    • Reach out to the project on its mailing lists. You'll find these under the "Contact Us" tab of the projects page.
    • Getting Help
    • Projects have at least one mailing list.
  • Code submission and acceptance by a project committer
  • As a committer you are responsible for maintaining the IP cleanness of the projects code. Care must be taken when accepting contributions.
  • All Eclipse projects must abide by the Eclipse Development Process (EDP) and IP Due Diligence processes.
  • Once you (the committer) is satisfied that the code is okay to commit, you must also check the following:
  • The contributor has a valid and signed Eclipse CLA. You can check this via the projects PMI page, under Committer Tools, there's a subsection called Contributor Agreement. Just enter the users Eclipse account email to verify.
  • Contributors must sign-off on their contributions via the Certificate of Origin (CoO).
  • Code contributions > 1000 lines of code need a Contribution Questionnaire (CQ) for the IP Team to review.
To verify whether a contribution requires a CQ, use one of the following git commands to check:

    If it's committed:  git log --shortstat
    If not committed: git diff --stat

These commands tell you the number of insertions(+), and deletions(-). If the total number of lines inserted (e.g. added) in a contribution is greater than 1000 (yes, this includes comments) then a CQ is required.
  • Becoming a project committer
  • Contributions are the path to gaining committer status to an existing project.
  • Meritocracy is one of the Eclipse Foundation's guiding principles.
  • This means, providing high quality contributions that demonstrate your seriousness and value/merit to the project. Each project will define it's own guidelines around what constitutes high quality contributions.
  • An existing project committer must nominate you. This will trigger an election, whereby every project committer will vote. the vote is successful if you receive three +1's with no -1 votes. For projects with fewer than three committers, everyone must +1.
  • You'll then need complete the required committer paperwork. The IP Team will help you here:)

Back to the top