cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cordova Wiki] Trivial Update of "BecomingACommitter" by MarcelKinard
Date Tue, 29 Oct 2013 02:46:42 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cordova Wiki" for change notification.

The "BecomingACommitter" page has been changed by MarcelKinard:
https://wiki.apache.org/cordova/BecomingACommitter?action=diff&rev1=7&rev2=8

Comment:
Fix typo

  = Contributor vs Committer =
  
- Being a contributor is where new members start. A committer makes contributions to Cordova,
but those contributions must be reviewed and applied to the repositories by someone who has
write access directly to the repositories - the committers. Contributors have read access
and can submit requests for code changes, but those requests are handled by committers. Contributors
do not have write access to the repositories. The project needs contributors, and every committer
started as a contributor. You do not need to be a committer to make valuable and important
contributions to the project - contributors can do that. A request for a code change is called
a "pull request", as it is a request for a committer to pull in the contributor's changes.
+ Being a contributor is where new members start. A contributor makes contributions to Cordova,
but those contributions must be reviewed and applied to the repositories by someone who has
write access directly to the repositories - the committers. Contributors have read access
and can submit requests for code changes, but those requests are handled by committers. Contributors
do not have write access to the repositories. The project needs contributors, and every committer
started as a contributor. You do not need to be a committer to make valuable and important
contributions to the project - contributors can do that. A request for a code change is called
a "pull request", as it is a request for a committer to pull in the contributor's changes.
  
  After a contributor has established a track record of quality changes and understanding,
they can request to be a committer. A committer has write access directly to the repositories,
so their changes hit the stream immediately. Committers also process pull requests from contributors.
They also review and address unresolved Jira items. And they participate in discussions on
the mailing list. Steady growth of committers is considered an indicator of good health in
a project. If you are going to be in the community for the long term and submit ongoing code
changes, you should consider becoming a committer. It's easier than you think.
  

Mime
View raw message