From: flameeyes@gmail.com (Diego 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: One request for the next SoC: non already-devs students
Date: Sun, 02 Mar 2008 21:45:10 +0100 [thread overview]
Message-ID: <m2ejaskg89.fsf@gmail.com> (raw)
In-Reply-To: b41005390803021237u40bd6fc3tcd6b81af8fcc62d3@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
"Alec Warner" <antarus@gentoo.org> writes:
> Your entire argument is based on the assumption that the Summer of
> Code program's primary goal is to recruit new developers for Open
> Source projects. While this is one goal I am unsure if holding it
> above the others is necessary.
I know it's not the _sole_ goal of Summer of Code as intended by
Google. But I do think it should be the main goal for Gentoo as a
project. I also knew it was already discussed in the FAQ, and that there
is no _Google_ rule stopping Gentoo developers from partecipating as
Gentoo students. And that is why I'm bringing up the point on Gentoo
ground.
If this works, I'd take this time to add this as an official point for
the next council meeting.
--
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2008-03-02 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 15:47 [gentoo-dev] One request for the next SoC: non already-devs students Diego 'Flameeyes' Pettenò
2008-03-02 18:48 ` Thilo Bangert
2008-03-02 19:02 ` Richard Freeman
2008-03-02 19:25 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-03-02 19:57 ` Wulf C. Krueger
2008-03-02 20:52 ` Brian Harring
2008-03-02 18:57 ` [gentoo-dev] " Robin H. Johnson
2008-03-02 20:37 ` Alec Warner
2008-03-02 20:42 ` Alec Warner
2008-03-02 20:45 ` Diego 'Flameeyes' Pettenò [this message]
2008-03-02 22:56 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-03-03 0:30 ` Christian Faulhammer
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=m2ejaskg89.fsf@gmail.com \
--to=flameeyes@gmail.com \
--cc=gentoo-dev@lists.gentoo.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