mirror of
https://github.com/semver/semver.git
synced 2026-07-11 03:53:53 -05:00
[GH-ISSUE #987] Application to join the SemVer team #6601
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#6601
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 @gwynne on GitHub (Nov 9, 2023).
Original GitHub issue: https://github.com/semver/semver/issues/987
Hi, I would like to apply to join the SemVer team, to represent Swift and the Swift Package Manager ecosystem. SwiftPM has used SemVer for dependency resolution, including supporting minor and patch version qualifications as well as pre-release identifiers, since its original open source release.
Speaking to my qualifications for such a role, I have extensive experience in Swift and all of its components and tools, including and especially SwiftPM; I'm also part of the Core team of Vapor, the largest server-side Swift framework, for which we actively maintain some 40 interrelated packages. I worked at Apple for almost two years, and before that I spent a number of years working in the PHP community, the CocoaPods ecosystem, the iOS developer community, and several other areas. I've written a pure-Swift standalone implementation of semantic versioning, and I sit on the Swift Server Working Group, a steering committee comprised of industry members from Apple, Amazon, and other companies and having significant influence over both the Swift on Server ecosystem and Swift itself.
In summary, I think I’d be a valuable addition to the SemVer team, bringing experience and connections which would hopefully benefit everyone.
@steveklabnik commented on GitHub (Feb 6, 2024):
Hey there @gwynne ,
I apologize for taking so long to respond to you. To be frank, I personally am very burned out, and it seems most of the other maintainers are too. The lack of reply here isn't you, it's us. I would be happy to add you, but also, I'm not exactly sure how functional things are right now. @JohnTitor has been doing a tremendous amount of work triaging, but the rest of @semver/maintainers have been MIA for a long time. So, just setting that expectation out there. I would love to get back to revitalizing things around here but it kinda feels impossible.
@indirect commented on GitHub (Feb 6, 2024):
I'm happy to second adding @gwynne to the maintainers team and see if new contributors help with that revitalization.
@segiddins commented on GitHub (Feb 7, 2024):
Thirded.
@gwynne commented on GitHub (Feb 23, 2024):
If this is still possible, I'd love to at least try to contribute what I can! 🙂
@segiddins commented on GitHub (Feb 27, 2024):
@gwynne invite sent!