or Create a profile

Home → Problems →

Taking ownership of "fcgi gem" due to dead upstream

mva's Avatar

mva

31 Jan, 2013 07:00 PM

Hi there!
I've already forked project to "ruby-fcgi-ng" (because of dead upstream), but distro maintainers (and many package mainteiners), that I asked to change gem name in depnds of packages, asking me to try to get ownership of the old, original "fcgi" gem.

Is it possible?

  1. Support Staff 2 Posted by Nick Quaranto on 20 Feb, 2013 01:35 AM

    Nick Quaranto's Avatar

    I've added the existing maintainers of this gem to this thread. Usually we try to contact the existing maintainers first, and we in very rare and extreme cases will forcibly give ownership over. saks or evaryont, can you add mva to this gem?

  2. 3 Posted by Aliaksandr Rahalevich on 20 Feb, 2013 06:27 AM

    Aliaksandr Rahalevich's Avatar

    Hi there!

    Done. mva added as an owner.

  3. Support Staff 4 Posted by David Radcliffe on 12 Apr, 2013 12:57 PM

    David Radcliffe's Avatar

    mva, you now have ownership of this gem.
    -David

  4. David Radcliffe closed this discussion on 12 Apr, 2013 12:57 PM.

Comments are currently closed for this discussion. You can start a new one.

5 people watching.

  • New Issue

  • Conversation Started

  • The discussion is closed

    No more actions from RubyGems.org or the discussion starter are required.

  • Re-open the discussion

Recent Discussions

21 May, 2013 11:33 PM Many connectivity errors from production.cf.rubygems.org
04 Aug, 2012 05:46 PM No registration email received
10 Oct, 2012 12:56 AM Can't create a new user account
08 May, 2013 07:56 AM Connection reset while pushing gem

Recent Articles

Supporter FAQ
Gem ownership
Installing gems with no network
Removing a published RubyGem
Why do I get HTTP Response 302 or 301 when installing a gem?