mirror of
https://github.com/semver/semver.git
synced 2026-07-11 08:02:23 -05:00
[GH-ISSUE #421] Semver project should have contributor guidelines. #1176
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#1176
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jwdonahue on GitHub (Dec 16, 2017).
Original GitHub issue: https://github.com/semver/semver/issues/421
Originally assigned to: @steveklabnik on GitHub.
There's currently two repo's here and near zero guidance on where/how to contribute. The semver/semver.org repo does have some guidance for adding translations, but semver/semver has nothing at all. It would be good if the maintainers could provide sufficient guidance in both repo's pertaining to their purpose, where and how to contribute. Should would-be contributors first start an issue describing proposed changes or just go straight for a PR with a well written description/justification?
There should be some statements regarding near, medium and long term goals for the standard. Is there a planned pace for 2.0.x changes? What about 2.x.x? Is it preferable to never release a 3.x.x version?
@haacked commented on GitHub (Dec 26, 2017):
Good idea. I'll think about writing up something.
@steveklabnik commented on GitHub (Feb 11, 2019):
https://github.com/semver/semver/blob/master/CONTRIBUTING.md was merged, which is a large part of this. We should still add some small things before closing, though.
@jwdonahue commented on GitHub (Feb 19, 2019):
That is an excellent start. Thank you! If there's something I can help with, please let me know.
@alexandrtovmach commented on GitHub (Jun 10, 2020):
Closed in favor #573