From: Gaute Hope <eg@gaute.vetsj.com>
To: Hamish D <dmishd@gmail.com>
Cc: William Morgan <wmorgan-sup@masanjin.net>,
sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] what can i help with?
Date: Sun, 21 Apr 2013 12:11:23 +0200 [thread overview]
Message-ID: <B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com> (raw)
In-Reply-To: <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
Hi William and list,
No stress and its nice to hear from you again.
I would be happy to take over that responsibility (and share it with for instance Hamish and Matthieu for starters, which I can fix afterwards of course).
I will most likely stay interested in the project for a long time, but it will definitely vary how much time I can spend - so lets quickly get someone else on the admin part as well.
Den 21. apr. 2013 kl. 11.16 skrev Hamish D:
> 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.
>
Perhaps put a note up on the Gitorious sup organization (to avoid confusion)?
As you may know we have put up an organization on GitHub we would be happy to add you there (if for nothing else than as an honorary member).
It is great to be able to continue the original project and not fork it off which definitely would loose some of the original community. Thanks for sharing it!
Cheers, Gaute
next prev parent reply other threads:[~2013-04-21 10:11 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
2013-04-21 10:11 ` Gaute Hope [this message]
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=B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=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