Author: rbaxter85
Date: Thu May 31 01:07:30 2012
New Revision: 1344521
URL: http://svn.apache.org/viewvc?rev=1344521&view=rev
Log:
updated community page
Modified:
shindig/site/trunk/cms/trunk/content/community_overview.mdtext
Modified: shindig/site/trunk/cms/trunk/content/community_overview.mdtext
URL:
http://svn.apache.org/viewvc/shindig/site/trunk/cms/trunk/content/community_overview.mdtext?rev=1344521&r1=1344520&r2=1344521&view=diff
==============================================================================
--- shindig/site/trunk/cms/trunk/content/community_overview.mdtext (original)
+++ shindig/site/trunk/cms/trunk/content/community_overview.mdtext Thu May 31
01:07:30 2012
@@ -68,6 +68,45 @@ For new people to the project, creating
6. Click "Attach file" and select the fix-xxx-bug.patch file
7. Check the "Grant license to ASF for inclusion in ASF works" option
8. Click on "Watching" and then click on "Start" watching to get updates
-7. If your patch includes major changes, the Apache Shindig project uses
[reviews.apache.org](https://reviews.apache.org/dashboard/) to review your
patch. You need a Google Account to process. Go to the sign up form to create
an account if you don't already have one. When creating a codereview issue add
[email protected] as the reviewer and DO NOT add dev@.
+7. If your patch includes major changes, the Apache Shindig project uses
+ [reviews.apache.org](https://reviews.apache.org/dashboard/) to review your
patch. You will need to create an account in
+ order to submit a patch for review. Go to the sign up form to create an
account if you don't already have one.
+ 1. Click create new review
+ 2. Select Shindig as the project and set the path to trunk.
+ 3. Attach your patch file.
+ 4. Fill out the subject, description, and describe any testing you did.
+ 5. In the bugs section list the JIRA you created for the issue, all you
need to do is enter SHINDIG-XXXX and a linke will be created.
+ 6. Add Shindig as the group to review the code. You may also specify
individuals who you would like to review your patch.
+ An email will automatically be sent to the Shindig dev list and any
individuals you listed as reviewers.
+8. You should also subscribe using [email protected] to see
all the feedback,
+ in which case you'll get the updates on the issue without needing to
"Watch" them individually.
+9. After your patch is reviewed and the community deems it acceptable a
committer will commit the code to SVN.
-The newly created issue will automatically be sent to [email protected].
You should also subscribe using [email protected] to see all the
feedback, in which case you'll get the updates on the issue without needing to
"Watch" them individually.
+## How do I join the Project?
+
+Projects at Apache operate under a
[meritocracy](http://www.apache.org/foundation/how-it-works.html#meritocracy),
+meaning those that the developers notice participating to a high extent will
be invited to join the project as a committer.
+
+This is as much based on personality and ability to work with other developers
and the community as it is with proven
+technical ability. Being unhelpful to other users, or obviously looking to
become a committer for bragging rights and
+nothing else is frowned upon, as is asking to be made a committer without
having contributed sufficiently to be invited.
+
+## Developer Conventions
+
+There are a number of conventions used in the project, which contributors and
developers alike should follow for
+consistency's sake.
+
+* Code Style And Code Conventions
+* Jira Conventions
+* SVN Conventions
+
+## Developer Documentation
+
+* Apache Shindig Release Process
+
+## Apache Resources
+
+* [About the Apache Software Foundation](http://www.apache.org/foundation/)
+* [Developer Resources](http://www.apache.org/dev/)
+* [Mailing List
Stats](http://people.apache.org/~coar/mlists.html#incubator.apache.org) (browse
to find shindig lists)
+* [Apache Wiki](http://wiki.apache.org/)
