git@vger.kernel.org mailing list mirror (one of many)
 help / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Matthieu Moy <git@matthieu-moy.fr>
Cc: Git Mailing List <git@vger.kernel.org>,
	Christian Couder <christian.couder@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: GSoC 2018 Org applications. Deadline = January 23, 2018 at 18:00 (CET)
Date: Tue, 16 Jan 2018 12:08:35 -0800
Message-ID: <CAGZ79kax5Hip1wP3U60im__Dm0GvH8nNd+ByxG5OxMXrRkRvdQ@mail.gmail.com> (raw)
In-Reply-To: <q7h9lghcob2s.fsf@orange.lip.ens-lyon.fr>

On Fri, Jan 5, 2018 at 2:26 AM, Matthieu Moy <git@matthieu-moy.fr> wrote:
> Hi,
>
> The Google Summer of Code Organization application is open. The deadline
> is rather soon (23/1).
>
> Like last year, I won't have much time to dedicate to it. I can try to
> help, but don't expect much from me.
>
> The first obvious question is: does the Git organization want to
> participate? If so, the application process itself is relatively easy,
> and anyone can do it (no need to be officially part of the legal
> entities behind Git or whatever): just create an accont on
> https://summerofcode.withgoogle.com/.
>
> If we go for it, we need:
>
> * Admins
>
> * Potential mentors
>
> * 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)
>
> * Fill-in the application. Essentially update and copy-paste text from
>   https://git.github.io/SoC-2017-Org-Application/
>
> Regards,

I'll be fine as a co-mentor this year.

  parent reply index

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 ` Johannes Schindelin
2018-01-07 23:03   ` Christian Couder
2018-01-08 18:46     ` Matthieu Moy
2018-01-13 19:47     ` Christian Couder
2018-01-16 20:08 ` Stefan Beller [this message]
2018-01-17 12:28   ` Christian Couder

Reply instructions:

You may reply publically 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=CAGZ79kax5Hip1wP3U60im__Dm0GvH8nNd+ByxG5OxMXrRkRvdQ@mail.gmail.com \
    --to=sbeller@google.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=christian.couder@gmail.com \
    --cc=git@matthieu-moy.fr \
    --cc=git@vger.kernel.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

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox