From: Gaute Hope <eg@gaute.vetsj.com>
To: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup: Fix for an UndefinedMethodError
Date: Sat, 13 Apr 2013 15:29:08 +0200 [thread overview]
Message-ID: <51695DA4.4030906@gaute.vetsj.com> (raw)
In-Reply-To: <20130413124946.GA22905@kpad.otokar.looc2011.eu>
On 13. april 2013 14:49, Matthieu Rakotojaona wrote:
> I guess it's also the occasion to think about the mailing list. I guess
> no one has the rights on this one ? I don't see anything in github for
> this functionality.
Yup - maybe its time for 'sup2' - from rubyforge:
http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned
Project xyz seems to be abandoned. Can you pass it to me?
This comes up occasionally - a well-named or positioned project gets
started, then the project admin falls out of sight and can't be reached.
Patches pile up, people start wondering what's going on, and it seems a
shame to lose the project name by forking it. So someone will ask if we
as RubyForge admins will pass over control of the project to them.
We really, really, hesitate to transfer admin privileges from one person
to another, even if the original admin has completely disappeared. I
suspect there are legal complications, and we don't have the budget to
deal with those. Furthermore, suppose the original admin has been off on
furlough for a year and comes back to find that his project has been
moved away from him. Not a pleasant situation.
In situations where the project admin can't be reached for a long time
and folks want to move forward, I suggest forking the project. You're
welcome to host a xyz2 version of project xyz on RubyForge, and if the
original admin ever shows up again and wants to hand over the project to
you, we can help facilitate that.
next prev parent reply other threads:[~2013-04-13 13:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 18:09 Jonathan Lassoff
2013-04-12 18:46 ` Steven Hum
2013-04-12 19:46 ` Hamish D
2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:09 ` Jonathan Lassoff
2013-04-13 13:17 ` Gaute Hope
2013-04-13 16:35 ` Jonathan Lassoff
2013-04-13 17:14 ` Gaute Hope
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff
2013-04-13 20:48 ` Jonathan Lassoff
2013-04-13 22:17 ` Gaute Hope
2013-04-14 11:31 ` [sup-devel] " Eric Weikl
2013-04-14 12:05 ` Gaute Hope
2013-04-14 17:39 ` Eric Weikl
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
2013-04-17 8:51 ` Gaute Hope
2013-04-17 3:31 ` Steven Hum
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2013-08-15 13:35 ` [sup-talk] " Steven Schmeiser
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2013-04-14 22:32 ` Gaute Hope
2013-04-15 11:42 ` Gaute Hope
2013-04-13 19:15 ` Jonathan Lassoff
2013-04-13 22:20 ` Gaute Hope
2013-04-13 12:49 ` Matthieu Rakotojaona
2013-04-13 13:29 ` Gaute Hope [this message]
2013-04-13 15:42 ` Steven Hum
2013-04-13 10:06 ` Jonathan Lassoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51695DA4.4030906@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=matthieu.rakotojaona@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox