git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git and Google Summer of Code 2012

From
André Walker <andre@andrewalker.net>
Date
Mar 20, 2012, 18:01 UTC
Message-ID
<4F68C5E4.3050306@andrewalker.net>
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:
Show 36 quoted lines
> 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
>
Previous: Jeff KingNext: Jeff King
Message 5 of 13 in “Re: Git and Google Summer of Code 2012”
  1. Jakub NarebskiMar 20, 2012
  2. Junio C HamanoMar 20, 2012
  3. Jakub NarebskiMar 20, 2012
  4. Jeff KingMar 20, 2012
  5. André WalkerMar 20, 2012
  6. Jeff KingMar 20, 2012
  7. André WalkerMar 20, 2012
  8. majordomo subscription woesJeff King, Mar 20, 2012
  9. André WalkerMar 20, 2012
  10. Jeff KingMar 20, 2012
  11. André WalkerMar 21, 2012
  12. André WalkerMar 20, 2012
  13. Jakub NarebskiMar 20, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.