git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "André Walker" <andre@andrewalker.net>
To: Jeff King <peff@peff.net>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: Git and Google Summer of Code 2012
Date: Tue, 20 Mar 2012 15:01:08 -0300	[thread overview]
Message-ID: <4F68C5E4.3050306@andrewalker.net> (raw)
In-Reply-To: <20120320175422.GA20669@sigill.intra.peff.net>

Well, one way or another, I do want to subscribe. I tried to do it 
though, but somehow I'm still not subscribed.

I mailed majordomo@vger.kernel.org with the message body "subscribe 
git". I did it twice, yesterday, and today again. Am I doing something 
wrong, or should I just wait?

On 03/20/2012 02:54 PM, Jeff King wrote:
> On Tue, Mar 20, 2012 at 06:44:54PM +0100, Jakub Narebski wrote:
>
>>>> Actually the discussion of GSoC project application ideas with mentoring
>>>> organization[1] should take place in the open, on git mailing list,
>>>> git@vger.kernel.org.  (You don't need to be subscribed to send email to
>>>> it, and there is custom on this mailing list of Cc-ing all people
>>>> participating in discussion; you can read git mailing list via other
>>>> interfaces e.g. via GMane.)
>>> The parenthesized part applies to general audience but not to GSoC
>>> students, I would think. Isn't the participation in the mentoring
>>> community mandatory for them?
>> Perhaps being subscribed to git mailing list, and participating in
>> #git or #git-devel IRC channel (and perhaps also #gsoc channel) is
>> mandatory for GSoC students (though I think if it is so it should
>> be stated clearly in materials such as SoC-2012-Template application
>> template)...
>>
>> ...but is it required also for _prospective_ (would-be) students?
> I would hesitate to ever call anything _mandatory_. A student who is
> aware of how the git community works, is up-to-date with recent
> discussions on the proposed area of work, and who has interacted with
> the developer community will have a much stronger application and be
> more likely to succeed in their project.
>
> Given that the mailing list is the center of the development community,
> I would expect reading at least some of it to be part of the above
> tasks. But whether they want to subscribe, read via nntp, read via list
> archives on gmane, or whatever, is up to the student. And I certainly
> wouldn't expect them to read every message; instead, they should read
> parts that interest them and seem applicable to their proposed work.
> Because there is a lot of traffic on the list, it often helps to cull
> uninteresting bits by their subject, or whole threads after reading the
> first message of a thread and deciding it's boring.
>
> -Peff
>

  reply	other threads:[~2012-03-20 18:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001636c5c21b02c35904bba0ff9a@google.com>
2012-03-20 15:37 ` Git and Google Summer of Code 2012 Jakub Narebski
2012-03-20 17:26   ` Junio C Hamano
2012-03-20 17:44     ` Jakub Narebski
2012-03-20 17:54       ` Jeff King
2012-03-20 18:01         ` André Walker [this message]
2012-03-20 18:18           ` Jeff King
2012-03-20 18:26             ` André Walker
2012-03-20 18:32               ` majordomo subscription woes Jeff King
2012-03-20 18:42                 ` André Walker
2012-03-20 18:47                   ` Jeff King
2012-03-21 14:36                 ` André Walker
2012-03-20 19:47   ` Git and Google Summer of Code 2012 André Walker
2012-03-20 22:50     ` Jakub Narebski

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=4F68C5E4.3050306@andrewalker.net \
    --to=andre@andrewalker.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=peff@peff.net \
    --cc=spearce@spearce.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
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).