[Top][All Lists]

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

Re: Web: Add GSoC entry for ScholarLY (issue 282290043 by address@hidden

From: git
Subject: Re: Web: Add GSoC entry for ScholarLY (issue 282290043 by address@hidden)
Date: Wed, 27 Jan 2016 19:53:45 +0000

Reviewers: pwm,
File Documentation/web/community.itexi (right):
Documentation/web/community.itexi:936: @strong{Mentor(s):} Urs Liska
On 2016/01/27 19:44:38, pwm wrote:
Just use "Mentor:" if there's only one listed.  (See issue 4750 which
drops the
use of "(s)".)

OK, didn't realize this. I was consistent with *current* convention.

Maybe use "Potential Mentor:" for consistency with the other listings?

Do we want to make a distinction between "Mentor" and "Potential
Mentor" here?
Using "Potential Mentor" for all listings means less to update from
one year to
the next.  Then, if and when a student expresses interest, at that
point we
would confirm whether the potential mentors listed are willing and
available to
be mentors.

Again, I didn't realize that change in your pending request.
I've updated this.

But if there's no other reason I won't upload a new patchset for this.

We'll have to reconsider much of that page anyway due to the feedback
from those listed as potential mentors.

Web: Add GSoC entry for ScholarLY

It has been discussed on lilypond-devel
that the ScholarLY library might be an appropriate suggestion for a GSoC

This is intended to start the reviewing of the GSoC page.

Please review this at

Affected files (+26, -0 lines):
  M Documentation/web/community.itexi

Index: Documentation/web/community.itexi
diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index d27978ed35e10aafa69b4e794c759c277688208f..8344ad167446510131525f1fd917d99b9c12f229 100644
--- a/Documentation/web/community.itexi
+++ b/Documentation/web/community.itexi
@@ -912,6 +912,32 @@ A full list of all the current open issues can be found

address@hidden ScholarLY
+ScholarLY is a library in @uref{, openLilyLib} that provides functionality
+for annotating scores, making it possible to manage scholarly
+workflows completely in the context of the score document.  So far
+it is possible to enter annotations of different types, produce
+clickable messages in the console output and export to text and
+LaTeX files.
+There are numerous feature requests to turn this library into an
+even more powerful and comprehensive tool, for example: Inserting
+music examples, producing footnotes, automatically applying styles
+to the annotated item (e.g. dash a slur, parenthesize an accidental),
+creating reports with point-and-click entries.  For a full description
+of this project suggestion please visit
address@hidden:} medium
address@hidden:} Scheme, possibly LaTeX, (optionally Python)
address@hidden:} Experience with or interest in scholarly
+edition and collaborative workflows.
address@hidden(s):} Urs Liska
 @subheading Grace notes

 Fix problems with synchronization of grace notes.  Grace notes can

reply via email to

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