Proposal for Official Fork

[alexandre-leites]

Hi,

As everyone here can see, the project is almost abandoned.

I believe someone or preferable a group of people fluent in Go lang should create an 'official' fork of the project so the community can contribute with PRs which won't be waiting forever at "Pull Requests" tab.

I'm not fluent in Go but I can help with docker images or something like that if needed.

====== Edit =====

According to @russtacular comment on 29 Aug 2018 this project is oficially discontinued. Therefore, while the community is discussing where it will be 'oficially' forked and supported, there are several projects already taking place as a migration path:

https://github.com/pusher/oauth2_proxy (see #628 (comment))
https://github.com/buzzfeed/sso
https://github.com/openshift/oauth-proxy
https://github.com/ploxiln/oauth2_proxy (see #628 (comment) and #628 (comment))

Also, there is a discussion on gofrs gofrs/help-requests#32 (comment)

[eforbus]

Agree. I think many of us would love to see some of these PRs get merged. Like it or not this is one of the simpler to use solutions for integration of OAuth2 or OIDC providers on top of Kubernetes.

[andreacassioli]

It is definitely a pity the project is kind of dead. Looks like a lot of people use it though. There is an interesting fork

https://github.com/openshift/oauth-proxy

but specialized on OpenShift.

If I were proficient in Go I would love to help.

Would be nice to know the maintainers opinion.

[ermik]

Let's find a well-known OSS org on github that could manage having such fork. Security repos shouldn't be on any one personal account. It is important though to have @bitly's support and perhaps have their team add the official fork's releases as a tag on dockerhub.

[alexandre-leites]

I agree with you @ermik. Finding an OSS organization which can take care of the project and assign people (not just one) which can approve PRs and manage the repository.

[bhack]

This is used quite often with K8S. /cc @cncf if it has any suggestion of what group could take care of this.

[bhack]

/cc @jbeda Do you know someone that could be interested to maintain this project active in a fork?

[tanuck]

Have @bitly stopped using this, hence the staleness of the project? If so it would be interesting to hear what they use instead.

[ermik]

Everyone at bitly might be just drones and we are a part of their simulation.

[skwashd]

I have been in touch with people at bitly about the current state of the project. I will post another update when I have more information.

[mohammed90]

If you're going for a hard fork, consider https://github.com/gofrs .

[ajcollett]

I too would like to use this! I recently started using the free Access service from CloudFlare. I really like the concept. So being able to do the same in a stable way with NGINX would be amazing...

[skwashd]

I have exchanged emails with the CEO of @bitly. I thought we were going to get this resolved. Unfortunately once it was passed over to an engineer it died.

I think it is pretty clear that this project is no longer a priority for bitly. For whatever reason they are unwilling to pass it over to new stewards.

I propose the following actions:

• identify a new home for the project
• mirror the repo in new org
• update the docs
• review all outstanding issues/PR and duplicate them in the new project. Add comments on the bitly version with a link to the new issue
• map out what a ???/oauth_proxy 1.0 (or 3.0) release would look like