Changes between Version 5 and Version 6 of en/contribute

Timestamp:

Aug 9, 2011, 12:09:49 AM (10 years ago)

Author:

laurentj

Comment:

--

en/contribute

@@ -15 +15 @@
 The project uses some processes to limit the number of bugs: unit testing, peer-review on patches etc. But this is not enough, and help is needed to test the framework in "real use" in order to track down bugs hidden, or to discover some gaps in components.
 
-So, using Jelix, finding and report bugs (by creating tickets or by discussing in the forum) is already a great help. Even if you are a beginner in PHP or in the use of a framework, (I would say, especially if you are a beginner), or if you are an expert, your opinions, your feedback are important to us! Even the most critical!
+So, using Jelix, finding and report bugs (by creating tickets or by discussing in the forum) is really a great help. Even if you are a beginner in PHP or in the use of a framework, (I would say, especially if you are a beginner), or if you are an expert, your opinions, your feedback are important to us! Even the most critical!
 
-You can also read the code. This is a good way to realize the quality of code and then point out the shortcomings or potential improvements. It also allows you to propose patch later ;-)
+You can also read the code. This is a good way to check the quality of code and then point out the shortcomings or potential improvements. It also allows you to propose patch later ;-)
 
 == Correct bugs or suggest improvements ==
 
-There are two possible cases. The first is when you discover a bug or an improvement to do, during your use of Jelix, and you have decided to fix this bug or to make this improvement. Then create a ticket (by checking first if it does not already exist), and submit your patch.
+There are two possible cases. The first is when you discover a bug or an improvement to do, during your use of Jelix, and you have decided to fix this bug or to make this improvement. Then create a ticket (by checking first if it does not already exist), and propose your patch ([wiki:en/patches see how]).
 
-The second case is that you want to help close tickets. There is [report:3 a list of many things to do], whether bug fixes, suggestions for improvements, or simple tasks. If you have time to devote to jelix, pick among these tickets, one that interests you, then assign this ticket to you, and submit a patch that corresponds to what is indicated on the ticket.
+The second case is that you want to help close tickets. There is [report:3 a list of many things to do], whether bug fixes, suggestions for improvements, or simple tasks. If you have time to devote to jelix, pick among these tickets, one that interests you, then assign this ticket to you, and [wiki:en/patches submit a patch] that corresponds to what is indicated on the ticket.
 
-One thing to know is that if the ticket is selected for a subsequent version to the next version (ie several months), don't hesitate! Contribute on this ticket, and there are chances that it will be integrated earlier in the next releases!
+One thing to know is that if the ticket is selected for a subsequent version to the next version (ie several months), don't hesitate! Contribute on this ticket, and there are chances that it will be integrated earlier in the next release!
 
 If you can not decide on the ticket to choose, here are some ideas:
-  * Try to search for tickets on a list of those concerns a part of Jelix which you know quite well how and code.
+  * Try to search for tickets on a list of those concerns a part of Jelix you know quite well.
   * If you want to start with easy patch, look at the tickets which are highlighted in blue in the lists, they are generally simpler (but not always true)
   * You can also choose the tickets the most urgent need: those in red or yellow, and primarily those who are assigned in future versions.
   * You can also ask other developers, they can possibly help you.
 
-After a few successful proposals patches, you will be part of the team of Jelix developers who have write access to the Mercurial repository, and even have responsibility for specific parts Jelix if it turns out that you were a specialty ;-)
+After a few successful proposals patches, you will be part of the team of Jelix developers who have write access to the repository, and you may even have responsibility for specific parts Jelix if it turns out that you were a specialty ;-)
 
 == Review and prepare documentation ==
@@ -57 +57 @@
 == Assist in development of project sites ==
 
-The Mercurial with the sources of the site is not available publicly. However, you can submit ideas for improvements, report in the shell design, in the content that you can edit. You can also suggest improvements in design. Then you will have an access to the repository.
+The sources of the site is not available publicly. However, you can submit ideas for improvements, report in the shell design, in the content that you can edit. You can also suggest improvements in design. Then you will have an access to the repository.