Return-Path: X-Original-To: apmail-cordova-commits-archive@www.apache.org Delivered-To: apmail-cordova-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7A8DB10ACD for ; Mon, 7 Oct 2013 18:21:48 +0000 (UTC) Received: (qmail 81426 invoked by uid 500); 7 Oct 2013 18:21:48 -0000 Delivered-To: apmail-cordova-commits-archive@cordova.apache.org Received: (qmail 81355 invoked by uid 500); 7 Oct 2013 18:21:48 -0000 Mailing-List: contact commits-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list commits@cordova.apache.org Received: (qmail 81345 invoked by uid 99); 7 Oct 2013 18:21:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Oct 2013 18:21:47 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.131] (HELO eos.apache.org) (140.211.11.131) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Oct 2013 18:21:45 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 591859F8 for ; Mon, 7 Oct 2013 18:21:24 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: Apache Wiki To: Apache Wiki Date: Mon, 07 Oct 2013 18:21:24 -0000 Message-ID: <20131007182124.84574.29270@eos.apache.org> Subject: =?utf-8?q?=5BCordova_Wiki=5D_Trivial_Update_of_=22BecomingACommitter=22_b?= =?utf-8?q?y_MarcelKinard?= Auto-Submitted: auto-generated X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cordova Wiki" for c= hange notification. The "BecomingACommitter" page has been changed by MarcelKinard: https://wiki.apache.org/cordova/BecomingACommitter?action=3Ddiff&rev1=3D6&r= ev2=3D7 Comment: a bit more clarifying verbage =3D Contributor vs Committer =3D = - Being a contributor is where new members start. A committer makes contrib= utions to Cordova, but those contributions must be reviewed and applied to = the repositories by someone who has write access directly to the repositori= es - the committers. Contributors have read access and can submit requests = for code changes, but those requests are handled by committers. The project= needs contributors, and every committer started as a contributor. You do n= ot need to be a committer to make valuable and important contributions to t= he project - contributors can do that. A request for a code change is calle= d a "pull request", as it is a request for a committer to pull in the contr= ibutor's changes. + Being a contributor is where new members start. A committer makes contrib= utions to Cordova, but those contributions must be reviewed and applied to = the repositories by someone who has write access directly to the repositori= es - the committers. Contributors have read access and can submit requests = for code changes, but those requests are handled by committers. Contributor= s do not have write access to the repositories. The project needs contribut= ors, and every committer started as a contributor. You do not need to be a = committer to make valuable and important contributions to the project - con= tributors can do that. A request for a code change is called a "pull reques= t", 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 a= ccess directly to the repositories, so their changes hit the stream immedia= tely. Committers also process pull requests from contributors. They also re= view and address unresolved Jira items. Steady growth of committers is cons= idered 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 being a committer. + After a contributor has established a track record of quality changes and= understanding, they can request to be a committer. A committer has write a= ccess directly to the repositories, so their changes hit the stream immedia= tely. Committers also process pull requests from contributors. They also re= view and address unresolved Jira items. And they participate in discussions= on the mailing list. Steady growth of committers is considered an indicato= r 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. = =3D Becoming A Committer =3D =20