From: Christian Couder <christian.couder@gmail.com>
To: Thomas Rast <tr@thomasrast.ch>
Cc: git <git@vger.kernel.org>, "Ben Straub" <bs@github.com>,
"Carlos Martín Nieto" <cmn@elego.de>,
"David Michael Barr" <davidbarr@google.com>,
"Edward Thomson" <ethomson@microsoft.com>,
"Florian Achleitner" <florian.achleitner2.6.31@gmail.com>,
"Jakub Narebski" <jnareb@gmail.com>, "Jeff King" <peff@peff.net>,
"Jens Lehmann" <Jens.Lehmann@web.de>,
"Martin Woodward" <martin.woodward@microsoft.com>,
"Matthieu Moy" <Matthieu.Moy@imag.fr>,
"Michael Haggerty" <mhagger@alum.mit.edu>,
"Michael Schubert" <schu@schu.io>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
"Pat Thoyts" <patthoyts@gmail.com>,
"Paul Mackerras" <paulus@samba.org>,
"Philip Kelley" <phkelley@hotmail.com>,
"Ramkumar Ramachandra" <artagnon@gmail.com>,
"Ramsay Jones" <ramsay@ramsay1.demon.co.uk>,
"Russell Belfer" <rb@github.com>,
"Scott Chacon" <schacon@gmail.com>,
"Shawn Pearce" <spearce@spearce.org>,
"Thomas Gummerer" <t.gummerer@gm>
Subject: Re: GSoC 2014: Summary so far, discussion starter: how to improve?
Date: Thu, 21 Nov 2013 10:43:34 +0100 [thread overview]
Message-ID: <CAP8UFD0n3gs0ynP8f_RgbpE4rugodcWQ_CtqvtbV0bnc9fzi9Q@mail.gmail.com> (raw)
In-Reply-To: <87txf6jgmi.fsf@linux-k42r.v.cablecom.net>
On Thu, Nov 21, 2013 at 9:36 AM, Thomas Rast <tr@thomasrast.ch> wrote:
> Thomas Rast <tr@thomasrast.ch> writes:
>>
>> * Find an org admin and backup. In previous years Shawn and Peff did
>> this. Would you do it again?
If Shawn and Peff don't answer, it probably means that you should volunteer :-)
> Any opinions on these points?
>
> I would actually favor a move to a wiki of the style that Peff proposed,
> hosted by github and backed by git with either a very mild ACL or none
> ("bots don't know git push"). k.org wiki had a grand total of three
> edits in the last 30 days (plus some bot edits for user creation).
If we are provided a wiki of the style Peff proposed, then I am ok using it.
But until we have it, let's use the k.org wiki.
Thanks,
Christian.
next prev parent reply other threads:[~2013-11-21 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 6:09 GSoC 2014: Summary so far, discussion starter: how to improve? Thomas Rast
2013-10-19 10:41 ` Christian Couder
2013-10-19 12:00 ` Felipe Contreras
2013-10-19 21:51 ` Fredrik Gustafsson
2013-10-26 8:21 ` Thomas Rast
2013-10-20 10:00 ` Thomas Gummerer
2013-10-22 21:31 ` Junio C Hamano
2013-10-26 8:14 ` Thomas Rast
2013-11-21 8:36 ` Thomas Rast
2013-11-21 9:43 ` Christian Couder [this message]
2013-11-21 10:04 ` Jeff King
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=CAP8UFD0n3gs0ynP8f_RgbpE4rugodcWQ_CtqvtbV0bnc9fzi9Q@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=Matthieu.Moy@imag.fr \
--cc=artagnon@gmail.com \
--cc=bs@github.com \
--cc=cmn@elego.de \
--cc=davidbarr@google.com \
--cc=ethomson@microsoft.com \
--cc=florian.achleitner2.6.31@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=martin.woodward@microsoft.com \
--cc=mhagger@alum.mit.edu \
--cc=patthoyts@gmail.com \
--cc=paulus@samba.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=phkelley@hotmail.com \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=rb@github.com \
--cc=schacon@gmail.com \
--cc=schu@schu.io \
--cc=spearce@spearce.org \
--cc=t.gummerer@gm \
--cc=tr@thomasrast.ch \
/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;
as well as URLs for NNTP newsgroup(s).