All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Christian Couder <christian.couder@gmail.com>
Cc: "Jeff King" <peff@peff.net>, git <git@vger.kernel.org>,
	"Pranit Bauva" <pranit.bauva@gmail.com>,
	"Lars Schneider" <larsxschneider@gmail.com>,
	"Carlos Martín Nieto" <cmn@dwim.me>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Thomas Gummerer" <t.gummerer@gmail.com>,
	"Siddharth Kannan" <kannan.siddharth12@gmail.com>
Subject: Re: GSoC 2017: application open, deadline = February 9, 2017
Date: Thu, 09 Feb 2017 11:15:58 +0100	[thread overview]
Message-ID: <vpqzihvpt41.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAP8UFD3aygSf5U2abnpCfRzEf-hH5fSNuzFBBtgCjSQC3F8c5A@mail.gmail.com> (Christian Couder's message of "Thu, 9 Feb 2017 10:42:14 +0100")

Christian Couder <christian.couder@gmail.com> writes:

> On Wed, Feb 8, 2017 at 3:54 PM, Matthieu Moy
> <Matthieu.Moy@grenoble-inp.fr> wrote:
>> Jeff King <peff@peff.net> writes:
>>
>>> On Mon, Jan 23, 2017 at 04:02:02PM +0100, Matthieu Moy wrote:
>>>
>>>> * We need to write the application, i.e. essentially polish and update
>>>>   the text here: https://git.github.io/SoC-2016-Org-Application/ and
>>>>   update the list of project ideas and microprojects :
>>>>   https://git.github.io/SoC-2017-Ideas/
>>>>   https://git.github.io/SoC-2016-Microprojects/
>>>
>>> That can be done incrementally by people who care (especially mentors)
>>> over the next week or so, and doesn't require any real admin
>>> coordination. If it happens and the result looks good, then the
>>> application process is pretty straightforward.
>>>
>>> If it doesn't, then we probably ought not to participate in GSoC.
>>
>> OK, it seems the last message did not raise a lot of enthousiasm (unless
>> I missed some off-list discussion at Git-Merge?).
>
> I think having 2 possible mentors or co-mentors still shows some
> enthousiasm even if I agree it's unfortunate there is not more
> enthousiasm.

A non-quoted but yet important part of my initial email was:

| So, as much as possible, I'd like to avoid being an org admin this
| year. It's not a lot of work (much, much less than being a mentor!),
| but if I manage to get some time to work for Git, I'd rather do that
| on coding and reviewing this year.

and for now, no one stepped in to admin.

Other non-negligible sources of work are reviewing microprojects and
applications. Having a few more messages in this thread would have been
a good hint that we had volunteers to do that.

> Someone steps in to do what exactly?

First we need an admin. Then as you said a bit of janitoring work on
the web pages.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2017-02-09 10:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 15:02 GSoC 2017: application open, deadline = February 9, 2017 Matthieu Moy
2017-01-24 11:28 ` Johannes Schindelin
2017-01-24 13:32   ` Christian Couder
2017-01-25 20:45 ` Jeff King
2017-02-08 14:54   ` Matthieu Moy
2017-02-08 15:43     ` Jeff King
2017-02-09  9:42     ` Christian Couder
2017-02-09 10:15       ` Matthieu Moy [this message]
2017-02-09 10:28         ` Siddharth Kannan
2017-02-09 10:49           ` Christian Couder
2017-02-09 10:45         ` Christian Couder
2017-02-09 12:11           ` Matthieu Moy
2017-02-09 12:22             ` Matthieu Moy
2017-02-09 12:28               ` Matthieu Moy
2017-02-09 13:17               ` Christian Couder
2017-02-09 21:38       ` Johannes Schindelin
2017-02-09 21:47         ` Stefan Beller
2017-02-09 12:18   ` Pranit Bauva
2017-03-18  9:01 ` Duy Nguyen
2017-03-18 17:42   ` Junio C Hamano

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=vpqzihvpt41.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=christian.couder@gmail.com \
    --cc=cmn@dwim.me \
    --cc=git@vger.kernel.org \
    --cc=kannan.siddharth12@gmail.com \
    --cc=larsxschneider@gmail.com \
    --cc=peff@peff.net \
    --cc=pranit.bauva@gmail.com \
    --cc=t.gummerer@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.