On 19.07.2016 11:26, Nathan Chou wrote:
My other question regards the footnote-spanner acknowledger in
Dynamic_align_engraver, which calls Axis_group_interface::add_element
to add footnote spanners for dynamics to the DynamicLineSpanner. In
what situation is this is actually needed?
Well, I
Hello,
I have (except for one question below) finished adapting
Dynamic_engraver and Dynamic_align_engraver to work cross-voice. I
plan to continue with other spanners (perhaps slurs next), but I want
to make sure I am on the right track. I organized my current progress
in the gsoc-2016-spanners
Nathan Chou writes:
> Hello,
>
> A quick question regarding the key-list argument to \= : if the list
> only has one key, it is assumed to be the id, as the share context is
> optional. When both the context and id are given, however, should the
> order of the keys be
Hello,
A quick question regarding the key-list argument to \= : if the list
only has one key, it is assumed to be the id, as the share context is
optional. When both the context and id are given, however, should the
order of the keys be (context id) or (id context)? I initially
implemented the
Hello,
(@David: I did not know about that function, thanks)
I'm wondering how Dynamic_align_engraver should deal with cross-voice
dynamic spanners. I don't have any good ideas at the moment (the best
possibility I thought of is to have a DynamicLineSpanner follow a
cross-voice dynamic to the
Nathan Chou writes:
> On Tue, Jul 5, 2016 at 1:54 AM, David Kastrup wrote:
>> Nathan Chou writes:
>>> That is a good point; I might agree with spanner id's not being shared
>>> across voices if nothing has been indicated. To make this
On Tue, Jul 5, 2016 at 1:54 AM, David Kastrup wrote:
> Nathan Chou writes:
>> That is a good point; I might agree with spanner id's not being shared
>> across voices if nothing has been indicated. To make this less
>> tedious, however: what if after the parent
Nathan Chou writes:
> On Fri, Jul 1, 2016 at 12:48 AM, David Kastrup wrote:
>> But that means that you can no longer let people write individual parts
>> with several spanner ids independently even when there never is even
>> going to be any cross-Voice
On Fri, Jul 1, 2016 at 12:48 AM, David Kastrup wrote:
> But that means that you can no longer let people write individual parts
> with several spanner ids independently even when there never is even
> going to be any cross-Voice spanner. Spanner-ids like \=1 \=2 are not
> likely to
Nathan Chou writes:
> Thanks David and Urs for replying.
>
>>> There is a detail I would like to clarify. David suggested allowing \=
>>> to optionally specify the parent context in which a cross-voice
>>> spanner's information is shared (although I am not sure how that
Urs Liska writes:
> Am 01.07.2016 um 09:28 schrieb Jan-Peter Voigt:
>>> Hm. If this is a limitation required by the implementation then it's
>>> acceptable. But from a user perspective I would be very surprised if an
>>> ID isn't recognized without an explicitly named
Am 01.07.2016 um 09:28 schrieb Jan-Peter Voigt:
>> Hm. If this is a limitation required by the implementation then it's
>> acceptable. But from a user perspective I would be very surprised if an
>> ID isn't recognized without an explicitly named context around it. Isn't
>> that the (one) idea of
Am 01.07.2016 um 09:21 schrieb Urs Liska:
Am 01.07.2016 um 09:01 schrieb Nathan Chou:
Thanks David and Urs for replying.
There is a detail I would like to clarify. David suggested allowing \=
to optionally specify the parent context in which a cross-voice
spanner's information is shared
Am 01.07.2016 um 09:01 schrieb Nathan Chou:
> Thanks David and Urs for replying.
>
>>> There is a detail I would like to clarify. David suggested allowing \=
>>> to optionally specify the parent context in which a cross-voice
>>> spanner's information is shared (although I am not sure how that
Thanks David and Urs for replying.
>> There is a detail I would like to clarify. David suggested allowing \=
>> to optionally specify the parent context in which a cross-voice
>> spanner's information is shared (although I am not sure how that would
>> be done with a key-list, since I think the
Urs Liska writes:
> Am 30.06.2016 um 14:47 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Am 30.06.2016 um 14:37 schrieb David Kastrup:
>>>
How does that differ from symbols?
>>> Ah, not in the Scheme domain, of course. But you can't *enter*
Am 30.06.2016 um 14:47 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 30.06.2016 um 14:37 schrieb David Kastrup:
>>
>>> How does that differ from symbols?
>> Ah, not in the Scheme domain, of course. But you can't *enter* them as
>> LilyPond code, isn't it?
> Can you
Urs Liska writes:
> Am 30.06.2016 um 14:37 schrieb David Kastrup:
>
>> How does that differ from symbols?
>
> Ah, not in the Scheme domain, of course. But you can't *enter* them as
> LilyPond code, isn't it?
Can you give an example for symbols "entered as LilyPond code" as
Am 30.06.2016 um 14:37 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 30.06.2016 um 14:05 schrieb David Kastrup:
>>> Urs Liska writes:
>>>
Am 30.06.2016 um 11:52 schrieb David Kastrup:
>> There is a detail I would like to clarify. David
Urs Liska writes:
> Am 30.06.2016 um 14:05 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Am 30.06.2016 um 11:52 schrieb David Kastrup:
> There is a detail I would like to clarify. David suggested allowing \=
>> to optionally specify the
Am 30.06.2016 um 14:05 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 30.06.2016 um 11:52 schrieb David Kastrup:
There is a detail I would like to clarify. David suggested allowing \=
> to optionally specify the parent context in which a cross-voice
>
Urs Liska writes:
> Am 30.06.2016 um 11:52 schrieb David Kastrup:
>>> There is a detail I would like to clarify. David suggested allowing \=
>>> > to optionally specify the parent context in which a cross-voice
>>> > spanner's information is shared (although I am not sure
Am 30.06.2016 um 11:52 schrieb David Kastrup:
>> There is a detail I would like to clarify. David suggested allowing \=
>> > to optionally specify the parent context in which a cross-voice
>> > spanner's information is shared (although I am not sure how that would
>> > be done with a key-list,
Nathan Chou writes:
> Hello,
>
> I have tried the same idea with context properties, and it seems to
> work just as well as my previous approach with a static member. (To
> summarize: cross voice spanners and the voice they currently belong to
> are stored in a property of
Hello,
I have tried the same idea with context properties, and it seems to
work just as well as my previous approach with a static member. (To
summarize: cross voice spanners and the voice they currently belong to
are stored in a property of some context containing both voices, like
Score. Each
Thank you Dan, David, Jan-Peter; I will try the suggestions out.
Nathan
On Sun, Jun 26, 2016 at 8:43 AM, Jan-Peter Voigt wrote:
>
>
> Am 26. Juni 2016 17:06:51 MESZ, schrieb David Kastrup :
>>Jan-Peter Voigt writes:
>> ...
>>> Whenever you are up
Am 26. Juni 2016 17:06:51 MESZ, schrieb David Kastrup :
>Jan-Peter Voigt writes:
> ...
>> Whenever you are up to using static members, change it to properties
>> of the Score context - or look for session global objects.
>
>"Session global" does not work with
Jan-Peter Voigt writes:
> Hi all,
>
> @David: thank you for your "emergency call"!
> @Nathan: sorry, for giving you bad advise in this case!
>
> To summarize, what to do with spanners, tagged with an ID: Use context
> properties to store them "globally". You can consider the
Hi all,
@David: thank you for your "emergency call"!
@Nathan: sorry, for giving you bad advise in this case!
To summarize, what to do with spanners, tagged with an ID: Use context
properties to store them "globally". You can consider the Score context
"global". If there is a context defined
Jan-Peter Voigt writes:
> Hi Nathan, hi Dan,
>
> the "nearest" context might be on Staff level - or, if (for example)
> you have voices switching staves, on StaffGroup level, where a
> StaffGroup also might be a GrandStaff or the like. If the context
> property turns out to
Hi Nathan, hi Dan,
the "nearest" context might be on Staff level - or, if (for example) you have
voices switching staves, on StaffGroup level, where a StaffGroup also might be
a GrandStaff or the like. If the context property turns out to complex (I don't
see all consequences yet), you'll have
> On Jun 24, 2016, at 07:41 , Nathan Chou wrote:
>
> Hello,
>
> spanners with an id are handled as potentially being cross-voice. Each
> engraver maintains a static list member (so it is shared between all
> instances of an engraver) of named spanners and the voice each
Hello,
Just wanted to update on my progress for the GSoC cross-voice spanners
project. The approach I am currently trying uses the existing
spanner-id property (which can be set like { c\=hello\< d\=hello\! });
spanners with an id are handled as potentially being cross-voice. Each
engra
Nathan Chou writes:
> Hello,
>
> Thank you for the information! I have been thinking more and a few
> questions have come to mind:
>
> * However the cross voice Spanner object is created, is it expected to
> be identical to the object currently created by the hidden voice
>
Hello,
Thank you for the information! I have been thinking more and a few
questions have come to mind:
* However the cross voice Spanner object is created, is it expected to
be identical to the object currently created by the hidden voice
workaround? Just to make sure, Spanners are Grobs, which
Nathan Chou writes:
> Hello,
>
> I have somewhat looked at the code and want to confirm my
> understanding of the current behavior:
> * While the file is parsed in Scheme, spanners cause a START and STOP
> event with an appropriate type to be created in the context they
>
. Any
suggestions or things I should keep in mind?
Nathan
On Sun, May 15, 2016 at 11:44 AM, Paul <p...@paulwmorris.com> wrote:
> Hi Nathan and Jeffrey,
>
> Great to have you on board for LilyPond GSoC! I'll be working on a GSoC
> project for Mozilla Calendar, so won't be as ac
Hi Nathan and Jeffrey,
Great to have you on board for LilyPond GSoC! I'll be working on a GSoC
project for Mozilla Calendar, so won't be as active with LilyPond, but
I'll try to help with development questions if I can.
Cheers,
-Paul
___
lilypond
Nathan,
Welcome to GSoC and to LilyPond development!
I'm excited to have you on board working on the cross-voice spanners
project. It's a great project, and will resolve one of the consistent
difficulties with LilyPond.
Please feel free to ask for help on lilypond-devel. We'd love to help you
Hello list, hello Nathan,
I want to second Nathans introduction and gracefully advocate for
supporting him/us in this endeavor - to support polyphonic slurs and the
like!
More to come!
Cheers
Jan-Peter
Am 07.05.2016 um 07:00 schrieb Nathan Chou:
Hello all,
I am a second-year student
Hello all,
I am a second-year student studying computer science at UCLA, and I
will be working on the cross-voice spanners project this summer as
part of the Google Summer of Code program. I'm glad to have this
opportunity to contribute to Lilypond---I've written music with
Lilypond before and
> Hi devs,
>
> we have a potential student looking for a GSoC project
> (http://lists.gnu.org/archive/html/lilypond-devel/2016-03/msg6.html
> and following messages). He has expressed interest in the "Allow
> spanners to cross voices" project where I am list
On 25.03.2016 21:43, Urs Liska wrote:
Paul Morris and Isaac David have both applied for the "Chord Structures"
project which would be mentored by Carl Sorensen. So that means there
will have to be a choice between these two.
David Garfinkle has applied for both "MusicXML export" and "Emmentaler
Hi all,
GSoC students' application is completed, and now its our turn again. We
have time until April 11 to propose a list of projects we want to have
and request slots for. The maximum number of slots we can request is the
number of mentors we have available, and we will have to assign
David, et al.,
An interesting test of both MusicXML export and import would be to make the
round trip and see what errors result. There is already a set of MusicXML files
for testing in input/regression/musicxml. Each of these could be converted to
LilyPond using musicxml2ly and then back to
On 3/24/16 3:23 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
behalf of David Garfinkle"
wrote:
>
>*In short I'm asking:* what expressions would
>you prioritize for MusicXML export? That
a priority over other music
> expressions like chord symbols, fingering, glissandos, dynamics, etc.
My view is that the aspects that are more complex and harder to implement
should be given priority. GSoC provides the time needed to tackle those
things, whereas simpler aspects will more easily fit in
Hi developers,
I'm preparing an application to continue working on MusicXML export under
GSoC. The whole application is viewable here:
https://docs.google.com/document/d/12zLGWrf6a_0J9H44Coo25s-pYsv-zH_g-oBqw6Shnrc/edit?usp=sharing,
but I am wondering about concrete goals in particular.
I've
Greetings everyone and welcome to LilyPond Isaac!
I have started working on my application for GSoC, and having checked in with
David Garfinkle and since there is currently no mentor for the MusicXML
project,[0] I am basing my proposal on the idea of improving LilyPond’s
internal chord
Just a heads-up for us to know:
The student application window has now opened, but we need to list our
mentors only until the window closes again, that is until March 25.
Urs
Am 14.03.2016 um 01:08 schrieb Urs Liska:
> Given the advent of a fifth potential applicant I find it inacceptable that
iewing code should be
> no problem :-)
You might want to look at the GSOC “Mentoring Manual”:
http://write.flossmanuals.net/gsoc-mentoring/about-this-manual/
Here’s its description of the mentor role:
Mentor: Mentors are people from the community who volunteer to work with a
student. Men
rk as a developer community (which is of course the spirit of GSoC).
IISC the most important (and least predictable) task of the mentor is to
keep an eye on the project, to keep in touch with the student and ensure
that his work is proceeding sufficiently.
Any coding issues may freely be shared a
Hi Urs,
you asked me off-list, if I would be a mentor (in hogwards they are called
dementor, aren't they?) - I didn't answer yet, so I do it on-list now. I would
be generally ready with being a mentor for the cross-voice-spanner-application.
Still, I would like to know, how much effort would
o free software projects,
>most prominently the Parabola distro.
>
>As you might have guessed I am interested in participating as a GSoC
>student improving the internal chord representation and output format,
>as suggested in your GSoC ideas page. Paul Morris has also expressed
>inte
Given the advent of a fifth potential applicant I find it inacceptable that we
don't seem to make any progress in raising our mentor number beyond two.
Is it really true that I am the only one pushing this?
Urs
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
a GNU/Linux user and occasional contributor to free software projects,
most prominently the Parabola distro.
As you might have guessed I am interested in participating as a GSoC
student improving the internal chord representation and output format,
as suggested in your GSoC ideas page. Paul Morris
>>
>>>>> Hi guys,
>>>>>
>>>>> it seems there's the chance this year that we end up with more GSoC
>>>>> applications than available slots. Right now there are four people
>>>>> having expressed interest in it, and my impr
Hi devs,
we have a potential student looking for a GSoC project
(http://lists.gnu.org/archive/html/lilypond-devel/2016-03/msg6.html
and following messages). He has expressed interest in the "Allow
spanners to cross voices" project where I am listed as
potential/secondary mentor.
Am 07.03.2016 um 09:58 schrieb David Kastrup:
> Urs Liska <u...@openlilylib.org> writes:
>
>> Am 07.03.2016 um 09:26 schrieb David Kastrup:
>>> Urs Liska <u...@openlilylib.org> writes:
>>>
>>>> Hi guys,
>>>>
>&g
Urs Liska <u...@openlilylib.org> writes:
> Am 07.03.2016 um 09:26 schrieb David Kastrup:
>> Urs Liska <u...@openlilylib.org> writes:
>>
>>> Hi guys,
>>>
>>> it seems there's the chance this year that we end up with more GSoC
>>> app
Am 07.03.2016 um 09:26 schrieb David Kastrup:
> Urs Liska <u...@openlilylib.org> writes:
>
>> Hi guys,
>>
>> it seems there's the chance this year that we end up with more GSoC
>> applications than available slots. Right now there are four people
>&g
Urs Liska <u...@openlilylib.org> writes:
> Hi guys,
>
> it seems there's the chance this year that we end up with more GSoC
> applications than available slots. Right now there are four people
> having expressed interest in it, and my impression so far is that the
> major
Hi guys,
it seems there's the chance this year that we end up with more GSoC
applications than available slots. Right now there are four people
having expressed interest in it, and my impression so far is that the
majority (or even all) may go the way through to an application.
That raises
Am 07.03.2016 um 05:48 schrieb Carl Sorensen:
> On 3/6/16 9:33 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Nathan Chou" <lilypond-devel-bounces+c_sorensen=byu@gnu.org
> on behalf of starry...@gmail.com> wrote:
>
> ...
>
>>
y an
\override or \tweak. When the user chooses to do an \override or \tweak
they are responsible for all of the settings.
So it seems like you should be ready to prepare a patch and post it for
review. Please do so!
The Frog issues are intended to be easy issues like 3947, so they
shouldn't tak
regarding GSoC, currently allowing spanners to cross voices seems to
be of most interest to me. Who should I contact (Urs?) to discuss this
project and writing a proposal, if it is still a possibility this summer?
Nathan
___
lilypond-devel mailing list
Hi all,
I’m thinking of applying for GSoC 2016. I will basically be done with the work
for my degree before GSoC starts on May 23, but I will still be a full-time
student on April 22, which makes me eligible.
I’m thinking I’d like to apply to work on the "Improve internal chord
stru
Hi Jeffery,
Am 03.03.2016 um 06:03 schrieb jeffery shivers:
> Dear LilyPond team,
>
> I'd like to apply for GSoC to contribute to ScholarLY as
> a student with Urs Liska.
This is great news!
>
> I've been a user of LilyPond and LaTeX for a while now,
> and am intri
Dear LilyPond team,
I'd like to apply for GSoC to contribute to ScholarLY as
a student with Urs Liska.
I've been a user of LilyPond and LaTeX for a while now,
and am intrigued by the ScholarLY/openLilyLib project.
I have less familiar, but basic, understandings of Python
and Scheme, from
On 02.03.2016 20:56, Carl Sorensen wrote:
There are some issues that have been identified as easy. You can locate
them by searching for "Frog" on the issues list:
https://sourceforge.net/p/testlilyissues/issues/search/?q=frog
Or, to exclude closed issues:
On 3/1/16 9:07 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
behalf of Nathan Chou" wrote:
>I've downloaded LilyDev and successfully compiled the current master, and
>was looking through the issue
for the GSoC (which is a good thing) you should start
with reading our list of project suggestions at
http://lilypond.org/google-summer-of-code.html. This is not
authoritative but gives you an idea about how (large) we think GSoC
projects may look like.
Browsing the issue tracker is less likely
Hello,
I am a second-year student looking to contribute for Google Summer of Code
(and perhaps afterward). I've used Lilypond to make some relatively simple
scores before, and have some experience in C/C++ (not yet familiar with
Scheme, but learning).
I've downloaded LilyDev and successfully
l
> extension language.
Looks like they have announced the accepted orgs for GSOC:
https://summerofcode.withgoogle.com/organizations/
GNU is one of them and it would be good to request for LilyPond to be listed on
the GNU projects page:
http://www.gnu.org/software/soc-projects/ideas-2016.html
Hi Urs,
> On Feb 19, 2016, at 4:34 AM, Urs Liska <u...@openlilylib.org> wrote:
>
> now that our modified GSoC page is online we should think about
> spreading the word.
> Of course the mentoring project applications are not done yet, but I
> think we should act as if i
Hi all,
now that our modified GSoC page is online we should think about
spreading the word.
Of course the mentoring project applications are not done yet, but I
think we should act as if it were clear that we can offer that project.
So, as the student application window starts March 14th I think
Am 8. Februar 2016 15:35:33 MEZ, schrieb paulwmor...@gmail.com:
.
>
>> Hm, my intention was to draw the attention to the fact that this
>project relates
>> to actual engraving quality. But I've taken your suggestion.
>
>Hmm... that's a good idea. Maybe add this to the title? "Improve
LGTM, with one minor suggestion.
Thanks Urs, I think this really improves this page.
-Paul
https://codereview.appspot.com/285400043/diff/1/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
in
developing LilyPond.
On 2016/02/06 20:53:30, pwm wrote:
Why don't we just shorten this paragraph to:
Below is a list of suggested projects for GSoC or for anyone who is
interested
in developing LilyPond. (Last updated: February 2016)
Done.
https://codereview.appspot.com/285400043/diff/1
/diff/1/Documentation/web/community.itexi#newcode909
Documentation/web/community.itexi:909: anyone who is interested in
developing LilyPond.
Why don't we just shorten this paragraph to:
Below is a list of suggested projects for GSoC or for anyone who is
interested in developing LilyPond. (Last
Section 2.5 of the Mentoring Organization agreement specifies that projects
cannot be documentation.
http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/org_admin_agreement
So it seems to me that unless we turn this project into a texi2html-to-texi2any
translator
}
>>
>> That gives the user one property to change to simply increase or decrease
>> vertical spacing without having to look up default values (or guess) or have
>> to decide whether to change padding, minimum-distance, or basic-distance or
>> some combination of
>
> What do you think?
>
Unfortunately Graham "is not in a position to provide GSoC style mentoring".
However, he would be willing to offer a few hours of feedback to a
LilyPond developer.
So: if someone volunteers to at least make a GSoC-page-like project
description of it I can
gt; to decide whether to change padding, minimum-distance, or basic-distance or
> some combination of them.
>
> Thoughts on this idea in general? And/or as a GSoC project? (I’m not sure
> that it would be enough or well-suited for GSoC.)
>
> [1]
> https://github.com/openlil
> On Feb 4, 2016, at 5:20 AM, Carl Sorensen <c_soren...@byu.edu> wrote:
>
> Section 2.5 of the Mentoring Organization agreement specifies that projects
> cannot be documentation.
>
> http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/org
mentor (see the PS to
http://lists.gnu.org/archive/html/lilypond-devel/2016-01/msg00197.html
for a description).
And finally I have one more suggestion for a project, but I wouldn't
volunteer mentoring it as I don't even know where/how to tackle it.
Consequently I can't really judge if it is suitable as a GS
chord project that Carl describes sounds like a nice addition to me, as
>> does your
>> project on spanners crossing voices.
>
> Should I prepare a description even if I think I can't serve as mentor?
I don’t see why not. It might be nice to get more feedback from those who know
Am 29.01.2016 um 05:01 schrieb Paul Morris:
> Hi Urs,
>
> Well, David K mentored “MusicXML” last summer so he would surely qualify
> as a potential mentor if he wants to be listed as such. David, what
are your
> thoughts and your availability and interest for this summer?
>
> Also, Janek was
https://codereview.appspot.com/282290043/diff/1/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
https://codereview.appspot.com/282290043/diff/1/Documentation/web/community.itexi#newcode917
Documentation/web/community.itexi:917: ScholarLY is a library in
Paul Morris <p...@paulwmorris.com> writes:
> Possibly we could add a description like this (from the 2012 GNU GSoC page):
>
> LilyPond is a music engraving program, devoted to producing the
> highest-quality sheet music possible. It is somewhat similar to TeX —
Ouch. LilyPond
ctual task of it
as there is a multitude of possible fields to work on. There are several
options, the following being a non-exhaustive list:
- backporting the improvements in musicxml2ly-dev to the main musicxml2ly
- working on MusicXML export through the python-ly appraoch
- following up on last year's GS
> On Jan 28, 2016, at 3:36 AM, David Kastrup wrote:
>
> Ouch. LilyPond is very dissimilar from TeX regarding a whole lot of
> things but certainly in the context of a call for programmers.
[…]
> Python is just used for some scripting but not in the core application.
Good
Hi Urs,
Well, David K mentored “MusicXML” last summer so he would surely qualify as a
potential mentor if he wants to be listed as such. David, what are your
thoughts and your availability and interest for this summer?
Also, Janek was willing to mentor “Slurs and Ties” last summer, so he
Paul Morris writes:
>> On Jan 28, 2016, at 3:36 AM, David Kastrup wrote:
>>
>> Ouch. LilyPond is very dissimilar from TeX regarding a whole lot of
>> things but certainly in the context of a call for programmers.
>
> […]
>
>> Python is just used for some
Hi all,
as mentioned I have done a little "survey", asking all those currently
listed as (potential) mentors for GSoC projects. I asked them if they
are still available and if they consider "their" projects still current
and important. The results are not really surprising
LGTM with an edit and a broader question about the mentor listings.
-Paul
https://codereview.appspot.com/282290043/diff/1/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
So students can find us as one of the GNU projects, we should get LilyPond
listed on the GNU GSoC suggestions page. Here’s the one for last summer:
http://www.gnu.org/software/soc-projects/ideas-2015.html
Seems we should just have a listing like those that point to external webpages,
like
y due to the feedback
from those listed as potential mentors.
Description:
Web: Add GSoC entry for ScholarLY
It has been discussed on lilypond-devel
(https://lists.gnu.org/archive/html/lilypond-devel/2016-01/msg00139.html)
that the ScholarLY library might be an appropriate suggestion for a GSoC
p
Am 27.01.2016 um 21:02 schrieb Paul Morris:
> So students can find us as one of the GNU projects, we should get LilyPond
> listed on the GNU GSoC suggestions page. Here’s the one for last summer:
> http://www.gnu.org/software/soc-projects/ideas-2015.html
>
> Seems we s
t;u...@openlilylib.org> Date: 27/01/2016 10:12 PM (GMT+02:00) To:
lilypond-devel@gnu.org Subject: Re: GSoC 2016 - GNU website listing
Am 27.01.2016 um 21:02 schrieb Paul Morris:
> So students can find us as one of the GNU projects, we should get LilyPond
> listed on the GNU GSoC sugg
401 - 500 of 662 matches
Mail list logo