Difference between revisions of "Contribute"

Line 26: Line 26:
  
 
After your first merge request has been approved, you will be granted access to the [https://gitlab.com/samba-team/devel/samba samba devel gitlab repo]. Subsequent merge requests should be made from this repository. Pushing branches to samba devel will initiate a CI build test.
 
After your first merge request has been approved, you will be granted access to the [https://gitlab.com/samba-team/devel/samba samba devel gitlab repo]. Subsequent merge requests should be made from this repository. Pushing branches to samba devel will initiate a CI build test.
 +
 +
===Mailing patches to samba-technical===
 +
 +
While not ideal, submitting patches via the mailing list is still considered acceptable. To submit patches, [[Using_Git_for_Samba_Development#Creating_patches_if_you_don.27t_have_write_access_to_git.samba.org_repositories|use git format-patch]] and mail your patches to the [https://lists.samba.org/mailman/listinfo/samba-technical samba-technical mailing list].
 +
 +
The preferred format for patch sets is a single-file bundle attached to the email you send to the list. Bundling can be automated by invoking <code>git format-patch</code> with the flag <code>--stdout</code>.
 +
 +
The disadvantage to this approach is that your patches risk being missed by an interested samba team member. Submitting a merge request is preferred, because your patches become persistent and will not be forgotten.
 +
 +
===Policies===
 +
Regardless of how you send us your patches, please ensure you have added [[CodeReview#commit_message_tags|Signed-off-by tags]] to your commits, and follow the [https://www.samba.org/samba/devel/copyright-policy.html Samba copyright policy]
 +
 +
Whenever participating the Samba community, please follow and respect the guidelines in [[How to do Samba: Nicely]]

Revision as of 15:32, 22 May 2020

How to contribute to Samba?

Like all OpenSource projects, Samba is reliant on volunteers. You don't need special skill to help this project. Everybody can help! :-)

There are several category groups you can work on, e.g.:

  • Improve documentation
  • Update/provide Wiki articles
  • Help testing
  • Report bugs
  • Help to verify patches in Bugzilla
  • Create patches (C developers)
  • Anything else you can imagine

Submitting Patches

The preferred method for submitting patches to samba is via the official mirror on GitLab. For more information see Samba CI on gitlab.

First Merge Request

The Using Git for Samba Development page has details on how to prepare patches using git.

After forking the samba git repo, preparing your patches, and submitting a merge request, the patches will be reviewed by samba team members who will post comments on your merge request.

Subsequent Merge Requests

After your first merge request has been approved, you will be granted access to the samba devel gitlab repo. Subsequent merge requests should be made from this repository. Pushing branches to samba devel will initiate a CI build test.

Mailing patches to samba-technical

While not ideal, submitting patches via the mailing list is still considered acceptable. To submit patches, use git format-patch and mail your patches to the samba-technical mailing list.

The preferred format for patch sets is a single-file bundle attached to the email you send to the list. Bundling can be automated by invoking git format-patch with the flag --stdout.

The disadvantage to this approach is that your patches risk being missed by an interested samba team member. Submitting a merge request is preferred, because your patches become persistent and will not be forgotten.

Policies

Regardless of how you send us your patches, please ensure you have added Signed-off-by tags to your commits, and follow the Samba copyright policy

Whenever participating the Samba community, please follow and respect the guidelines in How to do Samba: Nicely