Skip to content

Add contributing guide. #732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 14 commits into from
Oct 25, 2018
Merged

Add contributing guide. #732

merged 14 commits into from
Oct 25, 2018

Conversation

waylan
Copy link
Member

@waylan waylan commented Oct 10, 2018

A first draft. It's still a little rough and incomplete.

Any and all feedback is welcome.

For the record I found inspiration from

Copy link
Collaborator

@mitya57 mitya57 left a comment

Choose a reason for hiding this comment

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

I suggest some minor corrections.

@mitya57 mitya57 dismissed their stale review October 11, 2018 15:39

The typos are fixed, so removing my “Changes requested” status.

`MAJOR.MINOR.POINT(PRERELEASE/DEV)` format for specifying releases. The status
of the `master` branch should always be identified in the `__version_info__`
variable defined in [`markdown/__init__.py`][markdown/__init__.py] and should
conform to [PEP 440].
Copy link
Member Author

Choose a reason for hiding this comment

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

Note that we currently conform to PEP 386, which had been superseded by 440. We will need to make a minor adjustment before we conform to this guide.

Copy link
Member Author

Choose a reason for hiding this comment

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

Just a note that pypa/packaging officially implements PEP 404. And as of pypa/setuptools@9382fa0c, (version 8.0) setuptools and pkg_resources vendor and use pypa/packaging to do all version parsing. Finally, since 52b8da8 (version 3.0) we are using setuptools for installation.

Therefore, the differences between pkg_resources and PEP 440 listed in the PEP are presumably outdated and we should be able to use pkg_resources for all version handling without any added dependencies. In other words, we can remove our own version parsing code when conforming to PEP 440.

@waylan waylan mentioned this pull request Oct 17, 2018
waylan added a commit to waylan/markdown that referenced this pull request Oct 19, 2018
Also update to be PEP 440 compliant in preparation for Python-Markdown#732.
@waylan waylan mentioned this pull request Oct 19, 2018
waylan added a commit that referenced this pull request Oct 21, 2018
Update version format to be PEP 440 compliant in preparation for #732.

Add `pyproject.toml` file and configure tox to use it. Define requirement for `setuptools>=36` which validates and normalizes the version format.
@waylan waylan dismissed mitya57’s stale review October 21, 2018 21:11

All issues raised have been addressed.

@waylan
Copy link
Member Author

waylan commented Oct 22, 2018

I just pushed a change which now allows usage questions to be asked as GitHub Issues. I also included a list of [labels] and a description of each. Note that many new labels have been introduced. Please provide any feedback you may have before I update GitHub with the new labels.

@facelessuser
Copy link
Collaborator

I have no complaints.

@waylan waylan added docs Related to the project documentation. work-in-progress A partial solution. More changes will be coming. labels Oct 23, 2018
@waylan
Copy link
Member Author

waylan commented Oct 23, 2018

I have updated the labels here in GitHub. I used a color scheme for the status labels which is reminiscent of traffic lights:

green: various approved states (expect for someday-maybe which is gray).
yellow: waiting on something
red: various rejected states

All other labels (types and categories) arbitrarily use blue, orange, purple, brown... not shades of green/yellow/red.

Copy link
Collaborator

@mitya57 mitya57 left a comment

Choose a reason for hiding this comment

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

The latest changes look good to me. And I really like the proposed issue/PR labels! 👍

@facelessuser
Copy link
Collaborator

Yeah, I may steal the label convention or at least adapt it for some other projects. I've always had problems coming up with a label system I was happy with.

@waylan
Copy link
Member Author

waylan commented Oct 24, 2018

I think this is done. I did a final review and only found a couple minor tweaks.

I also color coded the labels in the docs. Any tweaks to the CSS are welcome:

screenshot_2018-10-24 contributing to python-markdown python-markdown 3 0 1 documentation

@waylan waylan merged commit d9ee723 into Python-Markdown:master Oct 25, 2018
@waylan waylan deleted the contrib-guide branch October 25, 2018 13:35
@waylan waylan added approved The pull request is ready to be merged. and removed work-in-progress A partial solution. More changes will be coming. labels Oct 25, 2018
@waylan waylan added this to the Version 3.1 milestone Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved The pull request is ready to be merged. docs Related to the project documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants