Reviewers: pwm,
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#newcode936
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.
Done
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.
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
project.
This is intended to start the reviewing of the GSoC page.
Please review this at https://codereview.appspot.com/282290043/
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
@divEnd
@divClass{column-center-middle-color3}
+@subheading ScholarLY
+
+ScholarLY is a library in @uref{https://github.com/openlilylib/snippets,
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
+@uref{https://github.com/openlilylib/scholarly/wiki/GSoC}.
+
+@strong{Difficulty:} medium
+@strong{Requirements:} Scheme, possibly LaTeX, (optionally Python)
+@strong{Recommended:} Experience with or interest in scholarly
+edition and collaborative workflows.
+@strong{Mentor(s):} Urs Liska
+
+@divEnd
+
+@divClass{column-center-middle-color3}
@subheading Grace notes
Fix problems with synchronization of grace notes. Grace notes can
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
