...
| Info | ||
|---|---|---|
| ||
But, my code's not ready! Don't worry! Think of it like this: open source software development is like a conversation. The conversation has to start somehow. Here's what you can do right now: create a JIRA issue, explaining your idea, and make a new branch, using that issue number in the branch name. Now, commit your new code to that branch, and push it up to your fork on GitHub. Now, the conversation has already started, and people have a way to discuss your idea in a meaningful fashion–referring to the JIRA issue number, perhaps reviewing and commenting on your branch on GitHub. It would probably be a good idea to link to your work in progress branch from the JIRA issue, as it will make finding you work, and the process of reviewing it, easier. Before you know it, you'll be ready to make a pull request, and your work will already have champions within the DSpace community, all because you put it out there and made it available for review early. |
...
| Note | |
|---|---|
|
...
|
...
|
...
| |
Once your code is ready, you must make your code available to the SimplyE Committers Group for review. The easiest way for us to review your code is by putting your code into GitHub (just create your own account – it's free!). Then, submit a "Pull Request" to our GitHub repository (see Development with Git). Alternatively, if you are not yet comfortable with GitHub, you may create a patch (and upload it to our Issue Tracker). However, please be aware that submitting a patch may delay the review process (see below note.) |
...
In either case, you must also create a new ticket in our Issue Tracker. This ensures that the SimplyE Developers are notified of your contribution, and acts as a place for us to comment on the work or make suggestions for improvements. |
Code Standards
Code contributions that meet certain standards are much more likely to be accepted immediately. For a list of our current standards, please read through the Code Contribution Standards section below.
...