From: Hamish D <dmishd@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] what can i help with?
Date: Sun, 21 Apr 2013 10:16:05 +0100 [thread overview]
Message-ID: <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com> (raw)
In-Reply-To: <1366514503-turnsole-37382@cugel>
Hello William
Nice to hear from you again.
> My sincere apologies for the complete and utter abandonment of Sup and
> Heliotrope.... I apologize.
Life happens.
> But I'm thrilled to see that there is enough community momentum to keep
> things going. I'd love to enable this as best I can. What is the list of
> things you need from me to take over maintenance of Sup?
>
> 1. Add some new owners to the sup gem. (Who?)
> 2. Add some administrators to the Rubyforge page. (Who?)
> 3. What else?
Does the rubyforge page manage these email lists? It would be good to
be able to admin them.
It's a long shot, but any chance you have some back ups of the old
wiki before it got spammed into oblivion? We've recovered what we can
and started re-writing what we can't, but it would be lovely to get a
dump of the old wiki (in whatever format).
As to who - Gaute Hope appears to have been the most active in the
recent renaissance, so I would definitely give him access. Then as we
sort ourselves out Gaute can give others access. (Not that I'd oppose
others, but it would be good to get at least one person on quickly).
Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2013-04-21 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 3:31 William Morgan
2013-04-21 9:16 ` Hamish D [this message]
2013-04-21 10:11 ` Gaute Hope
2013-04-21 10:18 ` Gaute Hope
2013-04-21 16:41 ` William Morgan
2013-04-21 17:53 ` Gaute Hope
2013-04-21 16:43 ` William Morgan
2013-04-21 19:22 ` Hamish D
2013-04-21 18:16 ` Matthieu Rakotojaona
2013-04-21 22:52 ` William Morgan
2013-04-22 9:32 ` Justin Mason
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=CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=sup-talk@rubyforge.org \
--cc=wmorgan-sup@masanjin.net \
/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