Re: GSoC project ideas

[Urs Liska]

Am 23.01.2017 um 21:53 schrieb Jeffery Shivers:
> This might be selfish, but how about at least one of those ideas be an OLL
> (or even scholarLY) thing?

I'd like to have others comment on this, but technically this could be
very well possible.
I must admit that I felt somewhat uneasy last year for "occupying" a
LilyPond slot with an openLilyLib project, and I had even considered
appyling with OLL to become a mentoring organization of its own. But I
suspect this would be a totally futile effort.

So while it's perfectly possible to put OLL projects on the list and to
apply for them (or others not listed there) in case of doubt projects
working on LilyPond itself might be the preference of the developer
community.

> I can't guarantee what the exact status of scholarLY annotations and the
> LaTeX package will be by April - therefore I definitely don't suggest a
> direct extension of *that/those* projects. (Although I can say that I at
> least will get the ball rolling again in February when I am finally back in
> the States (if anxiously so) and have the current wave of work behind me.)
> But it would be nice to see another project emerge from our little corner
> of the pond again.

Technically it would be possible to continue on scholarLY with the next
GSoC program (as we had on the list with MusicXML export). But I think
this would have to be an extremely good proposal that also makes clear
why continuing on the same project isn't actually a disguised failure of
the previous one. I mean it would have to be very well worded.

What I would see as a better project (and what I intend to suggest for
the list) is developing a system of automated testing and documentation
generation for openLilyLib, both the snippets repo and the other,
"new-style", packages. This would actually bring openLilyLib a huge step
forward to be usable on a broader base.

Urs


>
> On Mon, Jan 23, 2017 at 8:06 PM, Urs Liska <address@hidden> wrote:
>
>> Hi all,
>>
>> GSoC has started and the timeline is proceeding quickly
>> (https://summerofcode.withgoogle.com/).
>>
>> GNU is going to apply until February 9, and by February 27 I expect them
>> to be accepted to the program, which will make LilyPond applicable as well.
>>
>> Students will apply between March 20 and April 3, but we expect them to
>> get in touch with us earlier. This and the fact that the project ideas
>> list might be relevant for GNU's application as well suggests that we
>> update our page ASAP, preferably by February 9. I'm quite positive that
>> having updated the ideas page had its part in having two projects last
>> year.
>>
>> So please everybody think about possible projects we can put on our
>> ideas list on http://lilypond.org/google-summer-of-code.html. Projects
>> should be possible to achieve for someone new to LilyPond within three
>> months of (full-time) work, and it is necessary to have someone ready to
>> mentor the project. If you make a suggestion it's not necessary to
>> volunteer for that project at the same time, although it would make
>> things easier ;-)
>>
>> Best
>> Urs
>>
>> PS:
>> I've also provided a patch containing a section with recommendations to
>> potential students. They draw from my own experience as a mentor last
>> year and suggestions discussed both on the mentors' mailing list and the
>> mentors' summit last year. Please consider these paragraphs too, as they
>> may need more refinement and discussion.
>>
>> --
>> address@hidden
>> https://openlilylib.org
>> http://lilypondblog.org
>>
>>
>> _______________________________________________
>> lilypond-devel mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>>
>
>

-- 
address@hidden
https://openlilylib.org
http://lilypondblog.org