Add a CONTRIBUTING.md file. #425
Conversation
This branch adds a skeleton of contribution guidelines and cleans up little bits that I noticed along the way. For django-json-api#424
Codecov Report
@@ Coverage Diff @@
## master #425 +/- ##
=======================================
Coverage 91.75% 91.75%
=======================================
Files 55 55
Lines 2923 2923
=======================================
Hits 2682 2682
Misses 241 241Continue to review full report at Codecov.
|
| @@ -52,8 +53,9 @@ | |||
|
|
|||
| # General information about the project. | |||
| project = 'Django REST Framework JSON API' | |||
| copyright = '2015, Jerel Unruh and contributors' | |||
| author = 'Jerel Unruh' | |||
| year = datetime.date.today().year | |||
There was a problem hiding this comment.
@mblayman Sorry for this late response. Shouldn't the copyright date not just be the current year but a range or list of years starting from when the code was first released? Or just leave it at the date of first publication? There are lots of opinions around this but it seems that by advancing the copyright notice automatically you are excluding earlier code from the copyright statement. Not that it matters much as copyright applies with or without the statement.
| copyright = '2015, Jerel Unruh and contributors' | ||
| author = 'Jerel Unruh' | ||
| year = datetime.date.today().year | ||
| copyright = '{}, Django REST Framework JSON API contributors'.format(year) |
There was a problem hiding this comment.
Also, I would think @jerel's name should be retained with special emphasis as the original creator. "and contributors" for the rest...
There was a problem hiding this comment.
Oh wait, git says @gaker for the initial commit. Hmm... I'm still uncomfortable with removing a specific name from a copyright statement.
This branch adds a skeleton of contribution guidelines and cleans up
little bits that I noticed along the way.
For #424