git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / 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 13:11:15 +0100	[thread overview]
Message-ID: <vpqlgtfmun0.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAP8UFD1V=WD-EHkBkAVET9ztvsHZr_S5GVBWrQ6F1e0LwJoksQ@mail.gmail.com> (Christian Couder's message of "Thu, 9 Feb 2017 11:45:45 +0100")

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

> Well Peff wrote in reply to your email:
>
>> I did co-admin last year and the year before, but I made Matthieu do all
>> the work. :)
>>
>> I do not mind doing the administrative stuff. But the real work is in
>> polishing up the ideas list and microprojects page.
>
> So I thought Peff would be ok to be the admin (do "the administrative
> stuff").

There are several things the admins need to do:

1) "administrative stuff" about money with Conservancy (aka SFC). As I
   understand it, really not much to do since Google and Conservancy
   work directly with each other for most stuff.

2) Filling-in the application, i.e. essentially copy-past from the
   website.
 
3) Then, make sure things that must happen do happen (reviewing
   applications, start online or offline discussions when needed, ...).

Last year Peff did 1) and I did most of 2+3). My understanding of Peff's
reply was "OK to continue doing 1)".

I think you (Christian) could do 2+3). It's much, much less work than
being a mentor. Honnestly I felt like I did nothing and then Peff said I
did all the work :o). I can help, but as I said I'm really short in time
budget and I'd like to spend it more on coding+reviewing.

> I don't think emails in this thread is what really counts.
> I worked on the Idea page starting some months ago, and as I wrote I
> reviewed it again and found it not too bad.

OK, so giving up now seems unfair to you indeed.

I created a Git organization and invited you + Peff as admins. I'll
start cut-and-pasting to show my good faith ;-).

> About the janitoring part, as I previously said I am reluctant to do
> that as I don't know what Dscho would be ok to mentor.
> And I also think it's not absolutely necessary to do it before
> applying as an org.

Right.

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

  reply	other threads:[~2017-02-09 12:13 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
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 [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpqlgtfmun0.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).