-
-
Notifications
You must be signed in to change notification settings - Fork 290
Home
Pomax edited this page Oct 31, 2020
·
3 revisions
The main way to contribute to the primer is to file issues, write content/code, and file pull requests, in that order:
- file an issue for something that you think should be added, modified, or removed. Note that you might want more than one thing: please file one issue for one thing. This ensures others (including me, Pomax) can easily understand the work involved, and prevents issue-associated code changes from growing to immense and unreviewable size.
Discussion of the issue will happen in the issue itself.
- if you want to write code, please fork the project, then write your code changes in any branch that is not master. Never work in the master branch: that branch should be kept up to date with the main repo's master branch.
- When you're happy with your code, form a pull request from your not-master-branch to the Bezierinfo-2 master branch, and make sure to add "fixes #..." with the associated issue number for the
...
part. This lets github crosslink the two so that if the PR gets merged in, the associated issue is automated closed.
Once you have filed a PR, discussion of the code will happen in the form of pull request review notes. Any non-code issues that surface will be discussed in the associated issue.
Click the following link for information on how to Help localize the Primer on Bezier Curves this primer.