summer-of-code
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU participation in GSoC 2012


From: Graham Percival
Subject: Re: GNU participation in GSoC 2012
Date: Fri, 2 Mar 2012 23:48:31 +0000
User-agent: Mutt/1.5.21 (2010-09-15)

On Sat, Mar 03, 2012 at 12:25:03AM +0100, Janek Warchoł wrote:
> On Fri, Mar 2, 2012 at 7:42 PM, Rodrigo Rodrigues da Silva
> <address@hidden> wrote:
> > 1. Then: discuss and implement criteria to choose which projects get the
> > scholarships (we always have less slots than good ideas). Last year's
> > criteria (FSF high-priority projects first, then newcomers) seem OK, but
> > there were complaints.
> 
> When you will decide on this?  From what i know, LilyPond isn't on FSF
> high-priority projects list (and even if it's eligible for inclusion
> there's no time to do this); if this would mean that we will get very
> few slots (less than 3) then we may want to consider applying to GSoC
> on our own.

I'm totally lost as to how GNU, lilypond, and GSoC interact.
We (lilypond) have our git repository on savannah and use the
savannah mailing lists, but we have our own web hosting and
generally do our own thing.

If possible, I would like to:
- use GNU as the "mentoring organization": GNU gets the $500,
  and handles the tax paperwork
- lilypond applies to GSoC on our own (not counting the tax
  paperwork), letting google decide if we are selected at all,
  and how many students we get
- lilypond does the actual mentoring, gets patches from students,
  etc.

I'm not certain what the legal or tax ramifications of this would
be, nor whether GNU would be happy with this approach.  A quick
scan of the 2011 GSoC suggests that GCC, GIMP, and GNUcash applied
separately.  I imagine that GCC and GIMP have their own legal
entities that could deal with the tax information, but I would be
surprised if GNUcash had a distinct legal entity.


- Graham Percival, LilyPond project manager




reply via email to

[Prev in Thread] Current Thread [Next in Thread]