Release a forked gem

[andytinycat]

You don't have a license in this repository. Would you mind if I released a new gem based on your code and the enhancements contained in this fork? I would credit you and BIAINC and would be happy to give you contributor access to the repository.

I ask because I've got a use-case for resque-heartbeat, plus the enhancements, and I'd like to have it as a public gem rather than installed from GitHub.

[andytinycat]

@jonp I see you've contributed to the fork in BIAINC; would you mind me releasing a gem based on your code? Again, there's no license, and I don't want to assume one. Again, I would credit you.

(I would have left this as an issue on the fork, but issues are turned off for that repository.)

[svenfuchs]

@andytinycat I don't use this code anymore, feel free to use it in any way you want. I'll be happy to slap an MIT license on this repo if that helps, care to send a PR in that case?

[jonp]

I'd be happy to send a PR. I didn't do that before because I changed it to track individual worker processes instead of the whole machine. Knowing that, @svenfuchs, do you still want it?

[andytinycat]

I've created a new gem in this repository. If you're happy, I'm going to release this once I've tested it.

[jonp]

Instead of putting out competing forks, let's improve this one if @svenfuchs is interested. I've submitted a PR

[svenfuchs]

@andytinycat @jonp i've just added you guys as collaborators.

unfortunately i don't really have time to take care of this codebase, but it seems you're having some great ideas. so feel free to take over.

if you'd like to keep using this repository feel free to do so. if you'd like to continue in your forks or other repos, that's perfectly fine, too. i don't feel attached to this code at all :)

[jonp]

Ok, thanks @svenfuchs !
Do you have a problem with my merging my PR, adding the MIT license and then publishing a new version of the gem?

Edit: If not, then I'll need publish permissions in rubygems.

[svenfuchs]

@jonp no, as i said, no problems at all.

you guys feel free to merge, add, change whatever you like :)

[andytinycat]

If you could give us both publish permissions in RubyGems that would be excellent. If you do that, I will happily pull my gem down*. If you've not done it before, it's this command: http://guides.rubygems.org/command-reference/#gem_owner

You need our RubyGems email addresses; mine is [email protected].

• well, basically turn it into a zero code gem that requires resque-heartbeat (like bundle -> bundler)

[svenfuchs]

@andytinycat added

$ gem owner --add [email protected] resque-heartbeat
Owner added successfully.
Owners for gem: resque-heartbeat
- [email protected]
- [email protected]

Will be happy to add @jonp, too. Although you can now also do that, right?

[hlascelles]

What is the current status of this gem? I think it looks like what we need. We have a build up of non-existent workers reported in resque-web as AWS Autoscale terminates boxes.

Can v0.1.0 be cut as a gem?

Thanks!

[jonp]

@andytinycat or @svenfuchs , could you add me to the gem maintainer list? I'll take care of releasing this.

[hlascelles]

@jonp are you going to be the maintainer going forward?

[jonp]

@hlascelles I would be happy to. I need to get on the gem maintainer list, thought. @svenfuchs I haven't heard back from @andytinycat , so could you add me to the list?