Return-Path:
Note, there are not too many questions and answers here right now, this is
+ Note, there are not too many questions and answers here right now, as this is
a very new project. Please ask any new questions on
-mailto:dev@community.apache.org (subscribe with
-mailto:dev-subscribe@community.apache.org first).
We do have a system that we call meritocracy that allows those who have demonstrated commitment and understanding to the community to earn certain privileges, such as being able to make changes directly to documentation -and programme code. However, these privileges simply streamline the +and program code. However, these privileges simply streamline the process, they do not (in most cases) give additional powers over the project.
In summary, Apache Projects work because people like you participate @@ -169,7 +169,7 @@ constructively within them.
You should consider applying to the Apache Mentor Programme . We will help you find a mentor within the project of your choice. They -will take you through a semi-formal mentoring programme] that will ensure +will take you through a semi-formal mentoring programme that will ensure you quickly find your feet. There is no cost other than a promise to commit some of your time to the goals you agree with your mentor.
@@ -181,8 +181,8 @@ mailto:dev-subscribe@community.apache.orEveryone active in ASF projects is here as a volunteer, nobody is paid to -provide support here. So the first thing to realise is that you need to be -careful not to waste peoples time, so do your homework. Generally, if +provide support here. So the first thing to realize is that you need to be +careful not to waste people's time, so do your homework. Generally, if people can see that you have tried to solve your problem they are more likely to help. So, before asking a question do the following:
Be patient waiting for a response, give it at least three working days +
Be patient waiting for a response: give it at least three working days before you send a second message. People are busy, they will deal with your request when they can. If you need urgent help it is best not to rely on the community support channels and find someone willing to support you for @@ -211,7 +211,8 @@ the future.
A second way of contributing is to provide user support to others as your expertise grows. Again, earning merit in this way will help ensure you get the support you need in the future.
-If you are visible within the community
+If you are visible within the community, the community will likely reach out +for you whenever you need too.
The key to working on projects at Apache (and any open source for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue, you might be looking to learn a new -technology or you might simply want to do somethiung fun in your free time. +technology or you might simply want to do something fun in your free time. The key is that you must want to get involved. It is also important that you have appropriate skills to be able to help the project.
-Our projects +
Our projects page provides a useful index of projects which allows you to view projects alphabetically, by category or by language. When you view a projects detail page in this list you will find details of their mailing lists, issue -tracker and other resoutrces.
+tracker and other resources.In the projects issue tracker you will find details of bugs and feature requests the project would like to work with, this should give you some inspiration about how you might be able to help the project community. If -you see an issue you would like to tackle its time to join the projects +you see an issue you would like to tackle, it's time to join the projects mailing list and get started.
You can certainly improve your programming skills by watching the commit -lists, receiving code reviews and participating in discussion. Howeverm +lists, receiving code reviews and participating in discussion. However this learning opportunity is a healthy side effect of open source activities rather than a goal in itself. Nobody in an Apache project is going to spend time teaching you programming 101, technical writing or @@ -243,7 +244,7 @@ testing (to pick just a few skills we ne and be willing to research the rest.
To learn more about getting involved with an Apache Project see our getting started guide. You will also find our get involved - page a uaseful starting point.
+ page a useful starting point.Here at Apache projects are free to define their own code of conduct. @@ -275,7 +276,7 @@ initial contribution to an ASF project.<
Take a look at our mentoring page. If you are planning on working on an Apache project as part of your formal education you -should also read [mentoring in formal education|mentorProgrammeFormalEducation].
+should also read mentoring in formal education.From the mentoring page you will see that you need to complete an application. This gives us enough background information to enable us to approach your