github.com/capistrano/unicorn

[jibiel]

Greetings, gentlemen.

Any chance to list `https://github.com/tablexi/capistrano3-unicorn` under `http://github.com/capistrano/unicorn`?

At the time this seems like the best (and only) Unicorn integration solution for 3.x out there, apart from the tons of gists.

Hoping that the new listing will help to keep the `gem` afloat.

Would like to know about any of your additional requirements for that — code organization, style guided code, test coverage etc.

Disclaimer: I haven't contacted the maintainers of the repo yet.

[Lee Hambley]

Theoretically we create a team, and the owner transfers the repo ownership to "capistrano", then we give the owner back their repo control, the old one redirects to the new courtesy of GH's redirect feature, and they continue to work in peace.

Lee Hambley

http://lee.hambley.name/

+49 (0) 170 298 5667

--
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/63e8c294-eb08-4af5-856e-6b560cdacf78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matthew Lineen]

Lee, I'm the owner of capistrano3-unicorn. Is it something you'd like to move over as well as maintain? We've been using a different strategy for monitoring unicorn, so we haven't been keeping up as much on the changes being made to capistrano that should be accounted for in this gem -- it could use some additional eyes and maintenance these days.

--M

[jibiel]

Hey, Matthew.

Thanks for getting in touch. It is very unlikely that Mr. Hambley have time for such matters.

It is obvious then that `capistrano3-unicorn` should get at least a couple of maintainers with enough free time and motivation to support project and release the gem.

The least that can be done is adding the message saying that Maintainer position is vacant to the top of the `README.md` — github.com/guard/guard-livereload.

There's also gem metadata, like `description` and `summary` in your `.gemspec` file, but some may consider it not nice to add such messages there.

Next thing, if someone concerned contacts you, you get acquainted with his GitHub profile / activity / skills etc., and ask this person to handle a couple of open issues. You'll know this is the right person, when you'll get a reply with positive results.

The other thing to consider is picking the most active and cool person from the forks and contacting them about the matter.

— jibiel