-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gimme 1.6.0 #113296
gimme 1.6.0 #113296
Conversation
43992af
to
a533608
Compare
Is there any reference upstream announcing that you are the new maintainer? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me; thanks for the update!
Given there was no answer on travis-ci/gimme#206 but it has only been 9 days, I would like to wait a little bit (let's say max 30 days). It's a weird situation, and the explanation is really clear. If we get no answer, I'm fine with going ahead with the fork. |
It's a bit weird, because I personally have been the maintainer for most of the project history, but I got laid off from Travis CI in 2019 after an acquisition. I'd like to get maintenance flowing again, and my attempts to work with current Travis CI maintainers haven't gone anywhere 😐 But, to @iMichka's point, I'm happy to wait a bit longer 😁 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a |
@meatballhat I sympathise with your position, that sounds rough ❤️. I feel like we need to hold off a migration until the "official" upstream approves it somewhere/somehow, just to avoid setting a precedent with this in future. Hopefully you understand we need to be overly cautious on this sort of thing 🙇🏻 |
@MikeMcQuaid Absolutely, I understand! Thank you ❤️ |
I've asked upstream one more time for a clarification: travis-ci/gimme#206 (comment) |
Upstream is still silent on this. I think it is time for us to make a decision one way or another. How do we want to handle it? |
@p-linnane If upstream is silent: we need to create a new formula with a new name and can consider deprecating this one. |
@MikeMcQuaid Last commits were this past June, and v1.5.5 was cut then. Maybe we should wait a few more months on deprecation. @meatballhat If you'd still like to add your fork, please open a PR for it with a new name. |
Created with
brew bump-formula-pr
.Given new home and new release.
I realize there are security and/or political implications here given I'm requesting the formula point at a different source. You should be able to see in the history at travis-ci/gimme that I have been a core contributor since the beginning when the repository was at
meatballhat/gimme
. I'm happy to answer any questions around why I'm taking over maintenance again (see relevant issue).Closes urfave/gimme#5