Why is the repo now at sharpstone/rack-timeout?

[wuputah]

To all those interested in this issue, I'm happy to explain what happened.

The @heroku team account has been locked down to Salesforce employees only, with very limited access given to external collaborators through an approval process which involves senior leadership. This conflicts with what I believe is appropriate for open source projects, as follows:

• It is my opinion that open source projects should not be tied strictly to a corporation's or employee's lifecycle, and in order for such a project to be maintained beyond that lifecycle, outside collaborators may need to be added.
• Despite explaining my rationale, my open source account ( @wuputah ) was rejected access to this repo if it stayed under @heroku. While I could use my employee account, that account's access is tied to the lifecycle of my employment at Salesforce. I would like the option to either continue maintaining rack-timeout or giving a community member the ability to maintain it at any time in the future (regardless of my employer), which would not be possible using my employee account or under the @heroku team.

As such, I believe it to be in the best interest of the rack-timeout project to not be restricted by the @heroku team. The code is MIT licensed and thus it can live anywhere -- it can be forked and maintained by anyone. What matters is that it is being maintained, and being done so in a responsible way. Insomuch as I work for Heroku, it continues to be "maintained by Heroku." (For the record: working on open source is not officially part of my job.)

The @sharpstone open source team was available to me as an option, and I chose it because it contains only a small number of trusted co-workers that all participate in open source. However, it seems unlikely that this project will remain here indefinitely, so this is a temporary home. For instance, I've suggested creating an "@heroku-oss" team or similar but haven't gotten clear up/down on that -- the only issue doing so is assuring that such a team's members/collaborators would not be restricted to employees at any point in the future, and use of the "Heroku" name.

Please let me know if you have any questions or concerns and I'll do my best to answer them.

Cheers,
JD