airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sma...@apache.org
Subject svn commit: r1139829 - /incubator/airavata/site/trunk/content/airavata/get-involved.mdtext
Date Sun, 26 Jun 2011 16:13:45 GMT
Author: smarru
Date: Sun Jun 26 16:13:44 2011
New Revision: 1139829

URL: http://svn.apache.org/viewvc?rev=1139829&view=rev
Log:
adding website editing and governance templates cloned from ooo and rave

Added:
    incubator/airavata/site/trunk/content/airavata/get-involved.mdtext

Added: incubator/airavata/site/trunk/content/airavata/get-involved.mdtext
URL: http://svn.apache.org/viewvc/incubator/airavata/site/trunk/content/airavata/get-involved.mdtext?rev=1139829&view=auto
==============================================================================
--- incubator/airavata/site/trunk/content/airavata/get-involved.mdtext (added)
+++ incubator/airavata/site/trunk/content/airavata/get-involved.mdtext Sun Jun 26 16:13:44
2011
@@ -0,0 +1,90 @@
+Title: Get Involved
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+You don't need to be a software developer to contribute to 
+Apache Airavata. To be successful this project 
+requires a huge range of different skills, levels of involvement and degrees of 
+technical expertise. So, if you want to get involved in Apache Airavata, there 
+is almost certainly a role for you. 
+
+We are looking for people to:
+
+  - provide feedback
+  - write or update documentation
+  - help new users
+  - recommend the project to others
+  - test the code and report bugs
+  - fix bugs
+  - give us feedback on required features
+  - write and update the software
+  - create artwork
+  - translate to different languages
+  - anything you can see that needs doing
+
+All of these contributions help to keep a project active and strengthen 
+the community. The project team and the broader community will 
+therefore welcome and encourage participation, and attempt to make it 
+as easy as possible for people to get involved. 
+
+## Mailing lists
+
+Your first engagement with the project should be to subscribe to our
+[mailing lists][1].
+
+## Decision Making
+
+The most important thing about engaging with any Apache project is that everyone
+is equal. All people with an opinion are entitled to express that opinion and, where 
+appropriate, have it considered by the community.
+
+To some the idea of having to establish consensus in a large and distributed team 
+sounds inefficient and frustrating. Don't despair though, The Apache Way has a
+set of simple processes to ensure things proceed at a good pace.
+
+In ASF projects we don't like to vote. We reserve that for the few things that need 
+official approval for legal or process reasons (e.g. a release or a new committer). 
+Most of the time we work with the consensus building techniques documented below.
+
+
+### Lazy Consensus
+
+[Lazy consensus][2] is the first, and possibly the most important, consensus building 
+tool we have. Essentially lazy consensus means that you don't need to get explicit
+approval to proceed, but you need to be prepared to listen if someone objects.
+
+### Consensus Building
+
+Sometimes lazy consensus is not appropriate. In such cases it is necessary to
+make a proposal to the mailing list and discuss options. There are mechanisms
+for quickly showing your support or otherwise for a proposal and 
+[building consensus][3] amongst the community.
+
+Once there is a consensus people can proceed with the work under the [lazy 
+consensus][2] model.
+
+### Voting
+
+Occasionally a "feel" for consensus is not enough. Sometimes we need to 
+have a measurable consensus. For example, when [voting][4] in new committers or 
+to approve a release. 
+
+
+  [1]: /airavata/mailing-lists.html
+  [2]: /airavata/docs/governance/lazyConsensus.html
+  [3]: /airavata/docs/governance/consensusBuilding.html
+  [4]: /airavata/docs/governance/voting.html
\ No newline at end of file



Mime
View raw message