Skip to content

Add CONTRIBUTING.md#533

Merged
pganssle merged 3 commits into
dateutil:masterfrom
pganssle:contributing
Dec 5, 2017
Merged

Add CONTRIBUTING.md#533
pganssle merged 3 commits into
dateutil:masterfrom
pganssle:contributing

Conversation

@pganssle

@pganssle pganssle commented Dec 1, 2017

Copy link
Copy Markdown
Member

This is an initial version of CONTRIBUTING.md. It adds the stipulation that all new contributions will be dual-licensed under Apache 2.0 and BSD 3-clause license so it's more explicit what the licenses are.

@pganssle

pganssle commented Dec 5, 2017

Copy link
Copy Markdown
Member Author

@mariocj89 MInd doing a quick review here?

Comment thread CONTRIBUTING.md

3. A description of the problem - what *is* happening and what *should* happen.

While pull requests fixing bugs are accepted, they are *not* required - the bug report in itself is a great contribution.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you accept xfailing test cases as bug reports?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't been a huge fan of that in the past, but it's a good point. I think it should be added when #519 is fixed.

Comment thread CONTRIBUTING.md Outdated

### Feature requests

If you would like to see a new feature in `dateutil`, it is probably best to start an issue for discussion. You are welcome to prepare a pull request to start, but if it's going to be a lot of work, it's probably best to start by opening an issue so that you can know.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd refrase that. I can see the meaning but "reads weird" for me

Comment thread CONTRIBUTING.md Outdated

### Pull requests

If you would like to fix something in `dateutil` - improvements to documentation, bug fixes, feature implementations, fixes to the build system, etc - pull requests are welcome! Try to keep your coding to [PEP 8 style](https://www.python.org/dev/peps/pep-0008/), with the minor modification that the existing `dateutil` class naming style does not use the CapWords convention.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the tests there are many non pep8 violations, like method names being camelcase.
Should the contributor just "adhere" to the existing style or follow PEP8?

@mariocj89

Copy link
Copy Markdown
Member

just FYI in case it is of your interest there is a support for issues/pr templates by using .github.

Example: https://github.com/python/cpython/tree/master/.github

@pganssle

pganssle commented Dec 5, 2017

Copy link
Copy Markdown
Member Author

I think I skipped on the templates because as a bug reporter / PR submitter, I've often find they just get in the way. That said, the median contributor would probably benefit from them.

@pganssle

pganssle commented Dec 5, 2017

Copy link
Copy Markdown
Member Author

@mariocj89 Updated.

@pganssle
pganssle merged commit 72e57da into dateutil:master Dec 5, 2017
@pganssle pganssle mentioned this pull request Mar 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants