CONTRIBUTIONS
=============
-If you want to contribute to the development of the software then
+1. To contribute via GitHub
+ - fork the official Samba team repository on GitHub
+ * see https://github.com/samba-team/samba
+ - become familiar with the coding standards as described in README.Coding
+ - make sure you read the Samba copyright policy
+ * see https://www.samba.org/samba/devel/copyright-policy.html
+ - create a feature branch
+ - make changes
+ - when committing, be sure to add signed-off-by tags
+ * see https://wiki.samba.org/index.php/CodeReview#commit_message_tags
+ - send a pull request for your branch through GitHub
+ - this will trigger an email to the samba-technical mailing list
+ - discussion happens on the samba-technical mailing list as described below
+ - more info on using Git for Samba development can be found on the Samba Wiki
+ * see https://wiki.samba.org/index.php/Using_Git_for_Samba_Development
+
+2. If you want to contribute to the development of the software then
please join the mailing list. The Samba team accepts patches
(preferably in "diff -u" format, see http://samba.org/samba/devel/
for more details) and are always glad to receive feedback or
A list of Samba documentation in languages other than English is
available on the web page.
-If you would like to help with the documentation, please coodinate
+If you would like to help with the documentation, please coordinate
on the samba@samba.org mailing list. See the next section for details
on subscribing to samba mailing lists.