Originally assigned to: @alexandrtovmach on GitHub.
Hello community 👋
I just got maintainers rights and hope to make this project active, again. Of course, the development of specifications never stopped, and we have stable updates from the maintainers and the community:
Specifications shouldn't be changed twice a day, because it's stable monolith that using by millions products around the world, and it's totally fine to merge to master once in 3 months. But... on other hand we have hundreds issues/PRs, that should be resolved, that's why I'm here 👷♂️💪
I have a plan how to do this:
Resolve legacy
mark each open issue/PR with labels
ping authors of staled contributions to help with resolving their questions
resolve critical issues/PRs
close staled things
investigate to the rest of issues/PRs and try to resolve them
Any notes or suggestions about this plan really appreciated. Thanks!
Originally created by @alexandrtovmach on GitHub (Jun 10, 2020).
Original GitHub issue: https://github.com/semver/semver/issues/573
Originally assigned to: @alexandrtovmach on GitHub.
Hello community :wave:
I just got maintainers rights and hope to make this project active, again. Of course, the development of specifications never stopped, and we have stable updates from the maintainers and the community:
Specifications shouldn't be changed twice a day, because it's stable monolith that using by millions products around the world, and it's totally fine to merge to `master` once in 3 months. But... on other hand we have hundreds issues/PRs, that should be resolved, that's why I'm here :construction_worker_man: :muscle:
I have a plan how to do this:
#### Resolve legacy
- [x] mark each open issue/PR with labels
- [x] ping authors of staled contributions to help with resolving their questions
- [x] resolve critical issues/PRs
- [x] close staled things
- [ ] investigate to the rest of issues/PRs and try to resolve them
#### Updates
- [x] add validation tools to standardize contributions and translations (https://github.com/semver/semver.org/pull/270, https://github.com/semver/semver/pull/578)
- [x] configure CI/CD (GitHub Actions) (https://github.com/semver/semver.org/pull/266, https://github.com/semver/semver.org/pull/270, https://github.com/semver/semver/pull/578)
- [ ] write/update contribution guidelines and community related docs (#421, #410, https://github.com/semver/semver.org/issues/57)
- [x] add process to sync [semver/semver.org](https://github.com/semver/semver.org) with [semver/semver](https://github.com/semver/semver) (#407, https://github.com/semver/semver.org/pull/265)
Any notes or suggestions about this plan really appreciated. Thanks!
@alexandrtovmach commented on GitHub (Jun 10, 2020):
mark each open issue/PR with labelsDONE
Went through all issues and PRs and tagged them with labels, now it's easy to manage everything
<!-- gh-comment-id:642151101 -->
@alexandrtovmach commented on GitHub (Jun 10, 2020):
~mark each open issue/PR with labels~ **DONE**
Went through all issues and PRs and tagged them with labels, now it's easy to manage everything
@alexandrtovmach commented on GitHub (Jun 10, 2020):
ping authors of staled contributions to help with resolving their questionsDONE
Issues that was created earlier 2019 and haven't open questions marked as staled. In 10 days it will be closed if there are no objections from author.
<!-- gh-comment-id:642162043 -->
@alexandrtovmach commented on GitHub (Jun 10, 2020):
~ping authors of staled contributions to help with resolving their questions~ **DONE**
Issues that was created earlier 2019 and haven't open questions marked as [`staled`](https://github.com/semver/semver/issues?q=is%3Aissue+is%3Aopen+label%3Astaled). In 10 days it will be closed if there are no objections from author.
@alexandrtovmach commented on GitHub (Jun 19, 2020):
7 days summary
33 issues and PRs resolved 🚀🚀🚀
Plan progress: resolve critical issues/PRsDONE close staled thingsDONE add validation tools to standardize contributions and translationsDONE configure CI/CD (GitHub Actions)DONE
I'm really happy to be a part of SemVer community! Let's move on and make versioning better 🏃
Thanks to all contributors, you're the best 🥇
<!-- gh-comment-id:646835930 -->
@alexandrtovmach commented on GitHub (Jun 19, 2020):
## 7 days summary
**33 issues and PRs** resolved 🚀🚀🚀
Plan progress:
~resolve critical issues/PRs~ **DONE**
~close staled things~ **DONE**
~add validation tools to standardize contributions and translations~ **DONE**
~configure CI/CD (GitHub Actions)~ **DONE**
I'm really happy to be a part of SemVer community! Let's move on and make versioning better 🏃
Thanks to all contributors, you're the best 🥇
hi @alexandrtovmach , first of all: thanks for the great work in getting this repo maintained! You indicated:
Any notes or suggestions about this plan really appreciated. Thanks!
I have the following idea to contribute: should SemVer go for "official Web Standard" status by becoming a W3C Recommendation (https://www.w3.org/standards/faq.html#std)? What do you think?
Best, Robert
<!-- gh-comment-id:702614901 -->
@ghost commented on GitHub (Oct 2, 2020):
hi @alexandrtovmach , first of all: thanks for the great work in getting this repo maintained! You indicated:
> Any notes or suggestions about this plan really appreciated. Thanks!
I have the following idea to contribute: should SemVer go for "official Web Standard" status by becoming a W3C Recommendation (https://www.w3.org/standards/faq.html#std)? What do you think?
Best, Robert
Why would the w3c standardize something browsers have no interest in using?
<!-- gh-comment-id:702865433 -->
@ljharb commented on GitHub (Oct 2, 2020):
Why would the w3c standardize something browsers have no interest in using?
Hi there @ljharb , true, maybe not w3c then? What about the IETF, or others? Do you have someone in mind who would be a suitable standardization body?
<!-- gh-comment-id:703464217 -->
@ghost commented on GitHub (Oct 5, 2020):
Hi there @ljharb , true, maybe not w3c then? What about the IETF, or others? Do you have someone in mind who would be a suitable standardization body?
True, issue #253 it is. Sounds to me like there's no desire of the community (fine if it is like this)?
<!-- gh-comment-id:703558434 -->
@ghost commented on GitHub (Oct 5, 2020):
True, issue #253 it is. Sounds to me like there's no desire of the community (fine if it is like this)?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @alexandrtovmach on GitHub (Jun 10, 2020).
Original GitHub issue: https://github.com/semver/semver/issues/573
Originally assigned to: @alexandrtovmach on GitHub.
Hello community 👋
I just got maintainers rights and hope to make this project active, again. Of course, the development of specifications never stopped, and we have stable updates from the maintainers and the community:
Specifications shouldn't be changed twice a day, because it's stable monolith that using by millions products around the world, and it's totally fine to merge to
masteronce in 3 months. But... on other hand we have hundreds issues/PRs, that should be resolved, that's why I'm here 👷♂️ 💪I have a plan how to do this:
Resolve legacy
Updates
Any notes or suggestions about this plan really appreciated. Thanks!
@alexandrtovmach commented on GitHub (Jun 10, 2020):
mark each open issue/PR with labelsDONEWent through all issues and PRs and tagged them with labels, now it's easy to manage everything
@alexandrtovmach commented on GitHub (Jun 10, 2020):
ping authors of staled contributions to help with resolving their questionsDONEIssues that was created earlier 2019 and haven't open questions marked as
staled. In 10 days it will be closed if there are no objections from author.@indirect commented on GitHub (Jun 10, 2020):
@alexandrtovmach awesome, thanks for all your hard work on this. 🎉
@alexandrtovmach commented on GitHub (Jun 12, 2020):
3 days summary
39 issues and PRs already resolved 🎉🎉🎉
Big thanks to everyone who helps with resolving issues and PR reviews 🙏 🙏 🙏
Keep moving forward 🏃
@alexandrtovmach commented on GitHub (Jun 19, 2020):
7 days summary
33 issues and PRs resolved 🚀🚀🚀
Plan progress:
resolve critical issues/PRsDONEclose staled thingsDONEadd validation tools to standardize contributions and translationsDONEconfigure CI/CD (GitHub Actions)DONEI'm really happy to be a part of SemVer community! Let's move on and make versioning better 🏃
Thanks to all contributors, you're the best 🥇
@ghost commented on GitHub (Oct 2, 2020):
hi @alexandrtovmach , first of all: thanks for the great work in getting this repo maintained! You indicated:
I have the following idea to contribute: should SemVer go for "official Web Standard" status by becoming a W3C Recommendation (https://www.w3.org/standards/faq.html#std)? What do you think?
Best, Robert
@ljharb commented on GitHub (Oct 2, 2020):
Why would the w3c standardize something browsers have no interest in using?
@ghost commented on GitHub (Oct 5, 2020):
Hi there @ljharb , true, maybe not w3c then? What about the IETF, or others? Do you have someone in mind who would be a suitable standardization body?
@klehelley commented on GitHub (Oct 5, 2020):
Regarding writing an IETF RFC, see issue #253
@ghost commented on GitHub (Oct 5, 2020):
True, issue #253 it is. Sounds to me like there's no desire of the community (fine if it is like this)?
@Neustradamus commented on GitHub (Jun 3, 2025):
Any progress?