Hi all,
I added the good pratices concerning the patches and the commits in the developper guide.
How to provide a patch
(For further information, see http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf)
When a non-committer wants to contribute to Papyrus, he must create patchs and attach them to a bug. In the comment of each patch, he must write :
- (1) I, Forename Name, wrote 100% of the code I've provided.
- (2) This code contains no cryptography
- (3) I have the right to contribute the code to Eclipse.
- (4) I contribute the content under the EPL.
[edit] How to commit a patch
Before commiting a patch, you should verify that the contributor has written the following lines in the comment :
- (1) I, Forename Name, wrote 100% of the code I've provided.
- (2) This code contains no cryptography
- (3) I have the right to contribute the code to Eclipse.
- (4) I contribute the content under the EPL.
If not, he must do that before you commit its patch!
- If the writer is an employee of the same company and if the compagny has signed a Member Commiter Agreement : after the commit, you should comment the attachment writing :
- Here is a contribution from one employee of "the name of the company"
- The company has signed a Member Commiter Agreement.
- The contribution does not need a CQ.
- I've committed this contribution.
- Committed revision xxx.
Note : In reality, you should have the autorization of the PMC before doing this commit.
[edit] How to commit
- Before to commit, you should verify these items :
- your code is formatted using the Papyrus Template
- each file has an header with the EPL licence and your name
- all strings are externalized
- Moreover, if you want to commit a patch, please see the point "How to commit a patch".
- During the commit :
- you should comment your commit and precise the id of the bug
- After the commit
- Write the following comment in the bug : Commited in Rxxx
Best Regards,
--
Vincent Lorenzo
01-69-08-17-24
CEA Saclay DRT/LIST/DILS/LISE
91191 Gif/Yvette CEDEX
