Hey,
Sorry for the top-posting
Yes, it was general, maybe we should separate it out. I dont know
How does this sound ?
3. Students are highly encouraged have committed some code / package
or some other form of contribution to openSUSE prior to GSoC. This
will help new comers familiarize with the community before GSoC and
also give ample time to mentors and the community to know the student.
Knowing people around you is a good way to start off and also
strengthen final GSoC proposals.
On Fri, Oct 11, 2013 at 8:23 PM, Robert Schweikert
On 10/11/2013 07:13 AM, Henne Vogelsang wrote:
Hey,
On 11.10.2013 02:03, Robert Schweikert wrote:
On 10/10/2013 12:55 PM, Manu Gupta wrote:
Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer
wrote: On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
wrote: 3. Students must have committed some code / package or some other form of contribution to openSUSE.
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form of contribution to openSUSE. prior to GSoC. This sounds better I believe
GSoC is a good way for us to gain new contributors. Therefore I am not much in favor of such a string statement.
Me neither, GSoC is especially useful for newcommers. I think the goal you want to reach Manu is a set of guidelines for the mentors, not for students. You should differentiate the two.
Agreed on the "we should have guidelines for mentors" part, but I do think some (additional) guidelines for students to set expectation are very useful as well.
Later, Robert
-- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
-- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org