You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 21, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on May 21, 2022. It is now read-only.
I haven't had time to maintain this project for quite a while. I originally made it just for myself, but it appears to have become quite popular. It seems like the best course of action would be to clone this into its own org and then set this repo up to mirror that one until users can fully migrate over. That's probably also a good opportunity to correctly implement go mod support.
Does anybody want to take over as maintainer? It looks like jwt-go already exists as a github org. Name ideas?
Reacted by Gabriele V., Kévin Dunglas, Jack Lindamood, Gabriel-Guimaraes, Ivan Pavlushin, Micha Raze, bartholomew1999, Ferdinand Steenkamp, Michael Fridman, Danny Paul and 18 more
Reacted by bartholomew1999, Eron Castro, Joel Unzain, Christian Banse, grtfou, Maxime V., yunbj, Micah Parks, Rishabhdeep Singh, Michael Fridman and 11 more
I'd be happy to start an org and contribute, but I'd need at least 3 others to stand up and be willing to be co maintainers as this is quite a popular lib I think good coverage is needed.
In the absence I'd vote for:
Merges for the recent security release and one final release from @dgrijalva if he has that much time
README is updated with links to alternative
The project get archived having at least the major security issue fixed, thus sending a clear signal that this is the end for this one.
I haven't had time to maintain this project for quite a while. I originally made it just for myself, but it appears to have become quite popular.
Many thanks for your work on this project @dgrijalva.
I'd be happy to start an org and contribute, but I'd need at least 3 others to stand up and be willing to be co maintainers as this is quite a popular lib I think good coverage is needed.
Happy to be involved, under the same caveat of enough other co-maintainers
Indeed, thank you for the implementation and maintaining it over the many years @dgrijalva
I'd be happy to start an org and contribute, but I'd need at least 3 others to stand up and be willing to be co maintainers as this is quite a popular lib I think good coverage is needed.
I echo this sentiment and would be happy to get involved (with the caveat there would be a few others). I think this is important for a few reasons:
I have (and am familiar with) many downstream projects that either wrap or use this library
It is so widely used in the Go ecosystem and deserves to be maintained
It'd be a shame to see fragmentation as libraries like this benefit from the collective usage of many
Sorry for the delay in my response. Also glad to see that @dgrijalva is alive after all and was just a lack of time issue. I wouldn't mind lending a hand in the project, under the clarification that my availability may be bound to work and study (as I guess it does for most of you folks). Aside from the work I did to locally port the claims fix and perform a quick glance of the code base, I see there is a lot of work which is already done to process (as for the v4 branch and all of the open PRs)
go-jot or jot-go? names are hard. Using the spelling of the pronunciation of JWT instead of the acronym?
As long as it doesn't have got on its name I'm on board with any of both. I'd propose a more descriptive alternative maybe but the only one I can think of (it's 9 AM here 😪) would be the inverse of the package, go-jwt but it is already taken (and also is the package name, jwt-go.
Note that golang-jwt and jwt-golang seem to be available
Using the spelling of the pronunciation of JWT instead of the acronym?
I doubt this would get accepted into the go /x/ package, but that would be the ideal scenario whereby the community would have an "officially" supported JWT package that has some backing from the Go team.
I doubt this would get accepted into the go /x/ package, but that would be the ideal scenario whereby the community would have an "officially" supported JWT package that has some backing from the Go team.
The reason we mentioned 1 as not an option is because (I at least) felt a independantly maintained project is best rather than one associated with some company.
Activity
ripienaar commentedon Apr 12, 2021
Pinging a few who were involved in earlier discussions: @camin-mccluskey @Waterdrips @mcoops @lggomez @adamchalmers @alexells @brianmay
ripienaar commentedon Apr 12, 2021
I'd be happy to start an org and contribute, but I'd need at least 3 others to stand up and be willing to be co maintainers as this is quite a popular lib I think good coverage is needed.
In the absence I'd vote for:
Waterdrips commentedon Apr 12, 2021
Many thanks for your work on this project @dgrijalva.
Happy to be involved, under the same caveat of enough other co-maintainers
mfridman commentedon Apr 27, 2021
Indeed, thank you for the implementation and maintaining it over the many years @dgrijalva
I echo this sentiment and would be happy to get involved (with the caveat there would be a few others). I think this is important for a few reasons:
lggomez commentedon Apr 28, 2021
Sorry for the delay in my response. Also glad to see that @dgrijalva is alive after all and was just a lack of time issue. I wouldn't mind lending a hand in the project, under the clarification that my availability may be bound to work and study (as I guess it does for most of you folks). Aside from the work I did to locally port the claims fix and perform a quick glance of the code base, I see there is a lot of work which is already done to process (as for the v4 branch and all of the open PRs)
ripienaar commentedon Apr 28, 2021
Ok so it looks like we at least have a number of initially interested maintainers.
What should we call the org?
initial names for maintainers appear to be me, @Waterdrips @mfridman and @lggomez
I need to read a bit how to create an org that’s fully independent on GitHub but let’s see if we can agree on a name first
Waterdrips commentedon Apr 28, 2021
go-jotorjot-go? names are hard. Using the spelling of the pronunciation of JWT instead of the acronym?lggomez commentedon Apr 28, 2021
As long as it doesn't have
goton its name I'm on board with any of both. I'd propose a more descriptive alternative maybe but the only one I can think of (it's 9 AM here 😪) would be the inverse of the package,go-jwtbut it is already taken (and also is the package name,jwt-go.Note that
golang-jwtandjwt-golangseem to be availableSomething on this route could work also
mfridman commentedon Apr 28, 2021
I like the explicitness of
golang-jwtand it's also good for search-ability, as most users would search "golang" + "jwt"My vote is for
golang-jwtorgo-jot.An alternative might be to approach existing community orgs with a focus on oss Go packages? E.g.,
https://github.com/pkg
https://github.com/friendsofgo
https://github.com/goware
I doubt this would get accepted into the go /x/ package, but that would be the ideal scenario whereby the community would have an "officially" supported JWT package that has some backing from the Go team.
ripienaar commentedon Apr 28, 2021
Hmm, was not aware of those groups, definitely worth approaching ones with 3+ maintainers I think
lggomez commentedon Apr 28, 2021
I would mention https://github.com/gofrs, which is a group composed of new maintainers of previously abandoned or deprecated projects such as https://github.com/gofrs/uuid
ripienaar commentedon Apr 29, 2021
gofrslook pretty good, do any of us know any of the maintainers on these projects?mfridman commentedon Apr 29, 2021
gofrsis probably the best option. (they are in #gofrs on the gophers slack, if you're there)Just want to throw out other alternatives, thoughts?
ripienaar commentedon Apr 29, 2021
The reason we mentioned 1 as not an option is because (I at least) felt a independantly maintained project is best rather than one associated with some company.
mfridman commentedon May 4, 2021
Unless no objections, I'll submit an issue for
gofrsby end of day.https://github.com/gofrs/help-requests
EDIT: linking for brevity (another issue was already opened) at gofrs/help-requests#41
50 remaining items
Use github.com/golang-jwt/jwt instead of github.com/dgrijalva/jwt-go
chore: update deps to ones that use maintained form3tech-oss/jwt-go (#…
Update JWT library to github.com/golang-jwt/jwt
Update JWT library to github.com/golang-jwt/jwt (#1568)
chore: update deps to ones that use maintained form3tech-oss/jwt-go (#…
Use github.com/golang-jwt/jwt instead of github.com/dgrijalva/jwt-go
Upgrade jwt library
Upgrade jwt library (#5)
Migrate dgrijalva/jwt-go to golang-jwt/jwt-go
Migrate dgrijalva/jwt-go to golang-jwt/jwt-go