How to contribute to CNTK
You want to contribute to CNTK? We're really excited to work together!
Please note, that the information on this page is likely to change as we add more services to our GitHub Repository. So we recommend you to check this page every time you want to make a contribution.
Here are the simple steps you need to follow to see your code as a part of CNTK:
- Note that in most cases you will be required to accept Microsoft Contribution License Agreement (CLA) before you contribution is reviewed. You may study the text of the agreement here. You will be automatically notified whether you need to accept CLA after you make a Pull Request (see below). The procedure is automated and should not take more, than 5-7 minutes. Also, you will have to accept the CLA only once, and we will not bother you with this during the subsequent contributions
- Please, make each contribution reasonably small - it will allow us to review and accept it quicker. Also if you would like to improve several points, divide it in separate Pull Requests
- If you would like to make a really big contribution, like develop a brand new feature of CNTK, please, consult us preliminary by raising an issue. We value your cooperation and respect your time and thus want to ensure that we're ready for your work
- Consult the section describing how to setup your development environment. Get yourself familiar with Developing and Testing and especially Coding Guidelines sections of the CNTK documentation.
Making a contribution
- Fork CNTK Repository
- Code your contribution in the fork just created
- To make a contribution create a GitHub Pull Request using Comparing across forks view. Use
- Please provide a short description of your contribution while creating the Pull Request
- If asked accept CLA (see previous section). Please note, that we can NOT start reviewing your contribution until CLA is in place or is in state "cla-not-required".
- We will start reviewing the Pull Request in no later than two business days. Note, that the actual length of the review depends of the nature of the proposed change and may take longer. You will see the comments in the Pull Request as it goes along
- We ask to ensure that your branch has no merge conflicts with
master(GitHub Pull Request web interface informs you about it). We ask to ensure this conflict-free state both before and after the contribution review. (I.e. in case during the time of the review on-going
masterupdates result in a merge conflict, we will ask you to resolve it and make a new commit before we proceed with the integration)
- If the contribution is accepted and in merge-conflict-free state, it will be merged into the
That's it! We're looking forward to getting your contribution!