Difference between revisions of "Portal:Contribute"

From MNE-CPP Wiki
Jump to: navigation, search
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''Project Management:'''
+
This portal features information on how the code contribution process works in the MNE-CPP project.
 +
== The MNE-CPP Contribution Cycle ==
  
The MNE-CPP project is maintained by an agile management approach, using JIRA. JIRA is a well known issue tracking tool by Atlassian, which let's you post bug reports, improvement tasks, wishes for new features and much more. It gives you a way to directly participate in the development of MNE-CPP. Please go to [https://mne-cpp.atlassian.net MNE-CPP's JIRA website] and sign up for an account if you wish to help to improve MNE-CPP.
+
=== How to contribute your code ===
 +
This guide will show you how to contribute your own code to the MNE-CPP project:
  
Next to JIRA we also use Atlassian's Confluence to share documents, meeting notes and other project related files. You can find our confluence page [https://mne-cpp.atlassian.net/wiki/ here].
+
# If you have not already done so, fork the repository to your own Git Hub repository (see step 1 of the [[Get the MNE-CPP source code|getting the MNE-CPP source code guide]]).
 
+
# If you have not already done so, clone your remote (forked Git Hub) repository to your local machine (see step 3 of the [[Get the MNE-CPP source code|getting the MNE-CPP source code guide]]).
'''How to contribute your code:'''
+
# Create a new branch and make your changes to the code (please follow the [[Coding Conventions & Style|coding conventions]]) and do a commit (please follow the [[Commit Policy|commit policy]]).
 
+
# Push your changes to your remote (forked Git Hub) repository.
This guide will show you how to contribute your own code to the mne-cpp project:
+
# Go to your remote (forked Git Hub) repository via the GitHub website and create a pull request:
 
+
## Right next to the branch selection tool, look for the ''New pull request'' button and click it.
# If you have not already done so, fork the repository to your own Git Hub repository.
+
## The ''Compare Changes'' page will appear.
# Clone your remote (Git Hub) repository to your local system.
+
## Select the appropriate ''base'' and ''compare'' branch . The ''base'' branch is the branch of the repository you want to merge your changes to (by default the ''base'' branch is a branch of the repository you forked from). The ''compare'' branch is the branch where you implemented the new feature(s), bugfix(es), etc.
# Make your changes to the code and do a commit (please follow the [[Commit Policy|commit policy]] and [[Coding Conventions & Style|coding conventions]]).
+
## Name the pull reqest, describe your changes and hit ''Create pull request'' button.
# Push your changes to your remote repository.
+
# After you created the pull request, wait for the peer review process to be finished:
# Go to your remote repository via the GitHub website and create a pull request:
+
## Two MNE-CPP developers will review your code.
# After you created the pull request, wait for the peer review to be finished:  
+
## Please change your code on your local machine based on the comments made by the reviewers. Note: There is no need to create a new pull request for every new change you make to your code. Just commit the changes and push your code to your remote (forked Git Hub) repository. The changes will automatically be added to your already created pull request.
## Two full developers will review your code.
+
## As soon as your code suits all of the MNE-CPP coding conventions and possible inconsistencies were dealt with, your code will be merged into the main MNE-CPP repository.
## Please change your code on your local machines based on the comments made by the reviewers.
+
# Congratulations! You are now an official contributor to the MNE-CPP project. Keep up the good work!
## There is no need to create a new pull request for every new change you make to your code. Just commit the changes and push your code to your repository. The changes will automatically be added to your already create pull request.
+
## As soon as your code suits the mne-cpp coding guidelines and all tests were successfull, the code will be merged into the main mne-cpp repository.
+

Latest revision as of 23:33, 15 May 2019

This portal features information on how the code contribution process works in the MNE-CPP project.

The MNE-CPP Contribution Cycle

How to contribute your code

This guide will show you how to contribute your own code to the MNE-CPP project:

  1. If you have not already done so, fork the repository to your own Git Hub repository (see step 1 of the getting the MNE-CPP source code guide).
  2. If you have not already done so, clone your remote (forked Git Hub) repository to your local machine (see step 3 of the getting the MNE-CPP source code guide).
  3. Create a new branch and make your changes to the code (please follow the coding conventions) and do a commit (please follow the commit policy).
  4. Push your changes to your remote (forked Git Hub) repository.
  5. Go to your remote (forked Git Hub) repository via the GitHub website and create a pull request:
    1. Right next to the branch selection tool, look for the New pull request button and click it.
    2. The Compare Changes page will appear.
    3. Select the appropriate base and compare branch . The base branch is the branch of the repository you want to merge your changes to (by default the base branch is a branch of the repository you forked from). The compare branch is the branch where you implemented the new feature(s), bugfix(es), etc.
    4. Name the pull reqest, describe your changes and hit Create pull request button.
  6. After you created the pull request, wait for the peer review process to be finished:
    1. Two MNE-CPP developers will review your code.
    2. Please change your code on your local machine based on the comments made by the reviewers. Note: There is no need to create a new pull request for every new change you make to your code. Just commit the changes and push your code to your remote (forked Git Hub) repository. The changes will automatically be added to your already created pull request.
    3. As soon as your code suits all of the MNE-CPP coding conventions and possible inconsistencies were dealt with, your code will be merged into the main MNE-CPP repository.
  7. Congratulations! You are now an official contributor to the MNE-CPP project. Keep up the good work!