Proposal to migrate repo

[meatballhat]

I propose that travis-ci/gimme be migrated to urfave/gimme so that Travis CI may be relieved of the time and costs associated with maintenance.

There's a lovely community of volunteer maintainers over in the urfave org who I believe are better-equipped to maintain this repo into the future, so my proposal is that travis-ci/gimme be migrated to urfave/gimme. In practical terms, we can do this right now by pushing the history to urfave/gimme outside of the GitHub forking flow, and then pointing various packaging wrappers to that location instead. Consider this issue an artifact in a paper trail 😁

I realize that for anyone who is continuing to use Travis CI as a service, getting changes into this repo and then getting someone at Travis CI to bump the version in use is still necessary, so I don't think migrating this repo elsewhere will make your lives any better 🙁. I'm sorry ❤️. I have opened this pull request to travis-build: travis-ci/travis-build#2051

[iMichka]

Hi. Homebrew maintainer here. Can we get an official statement from Travis? We would like to know if you plan to continue maintaining this or would like to abandon this repository and give @meatballhat the new ownership of this project?

[eshack94]

Also wondering about this. What is the future of gimme? Is this something TravisCI can continue to maintain actively, or should its ownership be transferred to @meatballhat? Trying to make some decisions about the future of our CI support for Go

[eshack94]

@r-arek What are your thoughts on this?