From: Philippe LeCavalier <support@plecavalier.com>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: sup-talk@rubyforge.org
Subject: Re: [sup-talk] replacement sup wiki
Date: Mon, 14 Jan 2013 05:20:56 -0800 [thread overview]
Message-ID: <CAKada-4peOZihAwo4nD32jG_6FQsbBeXd-+4DVRjF1rennVOeg@mail.gmail.com> (raw)
In-Reply-To: <50F3C71C.1070807@gaute.vetsj.com>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Mon, Jan 14, 2013 at 12:51 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> Great! I agree with the organization-plan (github or whatever with a
> full project page: repository, issues, wiki..) - it really strains the
> project with these administrational bumps.
>
> Most importantly: A admin group with full access to the organization to
> allow for admins/devs to go off for a while without the project staggering.
>
> Personally I think the best is to keep everything on the same place.
>
I second that!
Phil
[-- Attachment #2: Type: text/html, Size: 904 bytes --]
next prev parent reply other threads:[~2013-01-14 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 15:22 Hamish D
2013-01-13 21:06 ` Matthieu Rakotojaona
2013-01-13 23:40 ` Hamish D
2013-01-14 8:51 ` Gaute Hope
2013-01-14 13:20 ` Philippe LeCavalier [this message]
2013-02-01 9:54 ` Gaute Hope
2013-02-03 19:10 ` Hamish D
2013-02-04 13:35 ` Matthieu Rakotojaona
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=CAKada-4peOZihAwo4nD32jG_6FQsbBeXd-+4DVRjF1rennVOeg@mail.gmail.com \
--to=support@plecavalier.com \
--cc=eg@gaute.vetsj.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