From: Hamish D <dmishd@gmail.com>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>,
sup-talk <sup-talk@rubyforge.org>,
sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] Github organization for sup and heliotrope
Date: Thu, 17 Jan 2013 21:09:18 +0000 [thread overview]
Message-ID: <CAOxvSbctHrgaVXcpLVzasxKo8B+qLP6PCNLJBb2=YDFc5HObWA@mail.gmail.com> (raw)
In-Reply-To: <50F86471.3000900@gaute.vetsj.com>
> I'd like to be part of the organization, but I am probably not going to
> be active enough to be an administrator, github name: gauteh.
OK, I've set up a team called committers (with commit access to all
repos) and added you. Also happy to make you an owner if you want.
I'm don't have strong views on where the wiki should be, but it would
be nice if people can just go and edit it with minimal fuss. It looks
like you'd have to be given access to edit the github wiki, so a bit
of a higher barrier to entry which I would prefer to not put in
people's way. But if we change our minds later (or if everyone
prefers it) then I have the pages as markdown, so transferring it
across to the github wiki would be very little work.
Right, should probably go and dig up various patches I've copied off
the email list that I wasn't sure about and turn them into pull
requests to open up discussion on them.
Hamish
next prev parent reply other threads:[~2013-01-17 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 20:15 Matthieu Rakotojaona
2013-01-17 20:52 ` Gaute Hope
2013-01-17 21:09 ` Hamish D [this message]
2013-01-17 23:43 ` Hamish D
2013-01-17 23:01 ` [sup-devel] " Hamish D
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='CAOxvSbctHrgaVXcpLVzasxKo8B+qLP6PCNLJBb2=YDFc5HObWA@mail.gmail.com' \
--to=dmishd@gmail.com \
--cc=eg@gaute.vetsj.com \
--cc=matthieu.rakotojaona@gmail.com \
--cc=sup-devel@rubyforge.org \
--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