>
> With regard to the org admins there is no room for
> placeholders/switching, I think. Registering as org admin is a
> "permanent" task, so one has to take over *some* responsibility from
> "now" to November. *If* the organization is actually accepted by Google,
> which in the case of Frescobaldi is more than questionable, given our
> small size.


Got it.

The most important point is to do the commitment to - if we're selected
> - stick with it over the year, most of the time having nothing to do but
> ensuring at least one admin is constantly available.


​That sounds just fine. I'm willing/able to take on that responsibility.
Let me know (off list now, I guess) what I need to do or know for now.

Jeffery

On Fri, Feb 3, 2017 at 2:25 PM, Urs Liska <u...@openlilylib.org> wrote:

> Hi Jeffery,
>
> Am 03.02.2017 um 18:58 schrieb Jeffery Shivers:
> > I don't feel (and objectively am not) qualified to mentor someone in any
> > capacity really, but if there is anything I can do to help (such as
> > administrative stuff, or otherwise), do let me know. Other than normal
> > job stuff, I don't have any big commitments from now through most of the
> > summer, so it would be a pleasure to assist in any way possible if even
> > just as a temporary placeholder for someone else more qualified to
> > takeover later.
>
> With regard to the org admins there is no room for
> placeholders/switching, I think. Registering as org admin is a
> "permanent" task, so one has to take over *some* responsibility from
> "now" to November. *If* the organization is actually accepted by Google,
> which in the case of Frescobaldi is more than questionable, given our
> small size.
>
> The primary duties of the two org admins (I'm the other one) is to be
> available for both (potential) mentors and Google. I think the org
> admins for large projects such as GNU, who have to shepard countless
> potential mentors, many organizations and eventually >40 active
> projects, have quite some work to do, but with Frescobaldi, where we
> won't have more than two projects in a first year, this should be really
> manageable.
>
> The most important point is to do the commitment to - if we're selected
> - stick with it over the year, most of the time having nothing to do but
> ensuring at least one admin is constantly available.
>
>
> >
> > I hope others out there will speak up as well, even if you're on the
> > fence for whatever reason. GSoC is a rare and generous opportunity to
> > fund awesome developments for a tool we all love so much; it would be
> > great to see more support for LilyPond's participation this year.
>
> Indeed it would be very good for us!
>
> Best
> Urs
>
> >
> > On Fri, Feb 3, 2017 at 12:32 PM, Urs Liska <u...@openlilylib.org
> > <mailto:u...@openlilylib.org>> wrote:
> >
> >     Hi all,
> >
> >     I have to bump this as the deadline is somewhat approaching and I
> need
> >     some feedback.
> >
> >     We have by now a nice set of project proposals online, but there are
> >     some projects without a mentor yet. Basically what is needed is at
> least
> >     one more mentor who feels comfortable mentoring someone to work on
> the
> >     underlying document representation stuff (the "music tree").
> >
> >     But while this is *important* it is absolutely *required* that we
> will
> >     have a second organization admin. Without that we can't even apply.
> >     Really, this is an opportunity to support Frescobaldi development for
> >     those who don't feel able to contribute any code, so please step up
> and
> >     volunteer. I don't expect this to be overwhelming with workload,
> please
> >     see below in my original post for some more details.
> >
> >     Best
> >     Urs
> >
> >
> >     Am 31.01.2017 um 12:06 schrieb Urs Liska:
> >     > Hi all,
> >     >
> >     > we decided to apply for this year's Google Summer of Code program
> with
> >     > Frescobaldi. We don't expect the chances to be accepted very high,
> but
> >     > it's probably worth the effort. It would give the chance to get
> more
> >     > GSoC slots for the wider LilyPond cause, so it's definitely a good
> >     thing.
> >     >
> >     > In order to complete our application we need a few items *until
> Feb. 9
> >     > (next Thursday)*, and I would be very happy to see concrete
> >     support from
> >     > this community:
> >     >
> >     > 1)
> >     > It is an absolute requisite that we have a second "org admin".
> >     > Org admins are responsible for communication between the project
> and
> >     > Google. I think both Google and the project will hold them
> >     "accountable"
> >     > for that. In addition they promise to be available and reliably
> >     > responsive over the whole project period (i.e. from now on until
> late
> >     > October) (obviously that doesn't rule out any vacancies ...).
> >     > Furthermore they'll have to do some paperwork and possibly channel
> >     some
> >     > money, for example for reimbursing mentors going to the mentors'
> >     summit.
> >     >
> >     > This would be an ideal task for someone interested in actively
> >     > supporting Frescobaldi/LilyPond development who doesn't feel
> >     capable of
> >     > doing actual programming. This is a completely administrative task.
> >     >
> >     > I can't say how much work it will be, but given the (lack of) size
> of
> >     > the organization I can't imagine it's a lot.
> >     >
> >     > 2)
> >     > As part of the application we have to submit a number of potential
> >     > project mentors who have volunteered. Therefore it is crucial to
> >     gather
> >     > that information right now.
> >     >
> >     > On
> >     https://github.com/wbsoft/frescobaldi/wiki/Google-Summer-of-Code
> >     <https://github.com/wbsoft/frescobaldi/wiki/Google-Summer-of-Code>
> I've
> >     > drafted a project idea's list similar to the one on lilypond.org
> >     <http://lilypond.org>. This
> >     > is very much open for discussion and extension.
> >     >
> >     > So I ask anyone who can imagine mentoring a student for a
> Frescobaldi
> >     > project to have a look at that list, consider the options with the
> >     > proposed projects, feel free to suggest other projects you may
> prefer
> >     > mentoring.
> >     >
> >     > From last year's experience I know that it is difficult to get
> >     together
> >     > a team of potential mentors, so *please* take this call seriously
> and
> >     > consider joining the effort. Also from last year's experience I
> >     can say
> >     > that mentoring *does* take its time but it's definitely a worthwile
> >     > thing to do.
> >     >
> >     > Best
> >     > Urs
> >     >
> >     >
> >
> >     --
> >     u...@openlilylib.org <mailto:u...@openlilylib.org>
> >     https://openlilylib.org
> >     http://lilypondblog.org
> >
> >
> >     _______________________________________________
> >     lilypond-user mailing list
> >     lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>
> >     https://lists.gnu.org/mailman/listinfo/lilypond-user
> >     <https://lists.gnu.org/mailman/listinfo/lilypond-user>
> >
> >
> >
> >
> > --
> >
> > Jeffery Shivers
> >  jefferyshivers.com <http://jefferyshivers.com>
> >  soundcloud.com/jefferyshivers <http://soundcloud.com/jefferyshivers>
>
>
> --
> Urs Liska
> https://openlilylib.org
> http://lilypondblog.org
>



-- 

Jeffery Shivers
 jefferyshivers.com
 soundcloud.com/jefferyshivers
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to