[Publishing your changes] --- https://www.pld-linux.org/developingpld?rev=1387914043 +++ https://www.pld-linux.org/developingpld @@ -100,17 +100,18 @@ ==== Publishing your changes ==== - As a wannabe developer you most likely won't have read/write access to the CVS repository so you'll have to find someone to check your changes in and add them to the repository. The best way to do it is to send a //unified diff// of your changes against the original files (or the whole files in case you are adding any) in a mail message along with a brief description of what you did to the ''pld-devel-en'' (or ''pl'') mailing list. - Once one of the other developers has time to review your changes, you will be notified of any errors that need to be fixed and eventually your files will get commited. + As a wannabe developer you most likely won't have read/write access to the GIT repository so you'll have to find someone to check your changes in and add them to the repository. The best way to do it is to send a //unified diff// of your changes against the original files (or the whole files in case you are adding any) in a mail message along with a brief description of what you did to the ''pld-devel-en'' (or ''pl'') mailing list. - Once you provide enough valuable changes, other developers might decide to give you full access to our repositories. This process is always initiated by someone who already has read/write access, asking for access on your own will not do you any good. + It's also acceptable to make your changes in your git repository, perhaps published in [[https://github.com|github]] and let somebody to pull your changes to pld repository. - When that happens, you will be able to do regular CVS commits. Remember to check the files you are committing before sending them to the repository. Make sure you also provide a meaningful commitlog. All logs have to be in the following format: + Once existing developer, who has time to review your changes, you will be notified of any errors that need to be fixed and eventually your files will get committed or pushed. + Once you provide enough valuable changes, other developers might decide to give you full access to our repositories. This process is always initiated by someone who already has read/write access, asking for access on your own will not do you any good. + When that happens, you will be able to do GIT commits and push them to PLD servers yourself. Remember to check the files you are committing before sending them to the repository. Make sure you also provide a meaningful commitlog. All logs have to be in the following format: <file>- first change - second change - third change
Diff URL: https://www.pld-linux.org/developingpld?do=diff&r1=1387914043&r2=1387914245 -- This mail was generated by DokuWiki at https://www.pld-linux.org/ _______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
