From: Christian Couder <christian.couder@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Matthieu Moy <git@matthieu-moy.fr>,
Git Mailing List <git@vger.kernel.org>,
Stefan Beller <sbeller@google.com>
Subject: Re: GSoC 2018 Org applications. Deadline = January 23, 2018 at 18:00 (CET)
Date: Mon, 8 Jan 2018 00:03:11 +0100 [thread overview]
Message-ID: <CAP8UFD06ZThD=FiccGrYLKpJz6R8NAUzFzMv+zrD4MisfJSbTw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1801051217190.31@MININT-6BKU6QN.europe.corp.microsoft.com>
Hi,
On Fri, Jan 5, 2018 at 12:18 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Fri, 5 Jan 2018, Matthieu Moy wrote:
>
>> If we go for it, we need:
>>
>> * Admins
>>
>> * Potential mentors
>
> Count me in as a potential mentor.
I am ok to be admin and mentor.
>> * List of microproject and project ideas
>> (https://git.github.io/SoC-2017-Ideas/ and
>> https://git.github.io/SoC-2017-Microprojects/ are good starting
>> points)
>
> I have spent a bit of time recently to document a couple of Git for
> Windows-specific projects thoroughly, I could easily copy/paste them
> there, too. (Yaaay, Markdown! Now, if only we could use it in Git's man
> pages, too...)
Nice!
I will fill in the application.
Thanks,
Christian.
next prev parent reply other threads:[~2018-01-07 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <q7h9lghcob2s.fsf@orange.lip.ens-lyon.fr>
2018-01-05 11:18 ` GSoC 2018 Org applications. Deadline = January 23, 2018 at 18:00 (CET) Johannes Schindelin
2018-01-07 23:03 ` Christian Couder [this message]
2018-01-08 18:46 ` Matthieu Moy
2018-01-13 19:47 ` Christian Couder
2018-01-16 20:08 ` Stefan Beller
2018-01-17 12:28 ` Christian Couder
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='CAP8UFD06ZThD=FiccGrYLKpJz6R8NAUzFzMv+zrD4MisfJSbTw@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@matthieu-moy.fr \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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).