LEFT | RIGHT |
1 @c -*- coding: utf-8; mode: texinfo; -*- | 1 @c -*- coding: utf-8; mode: texinfo; -*- |
2 @c This file is part of community.itexi | 2 @c This file is part of community.itexi |
3 @c It's been moved here to reduce maintenance burden on translators. It's up | 3 @c It's been moved here to reduce maintenance burden on translators. It's up |
4 @c to translators the choice of translating this section of community.itexi or | 4 @c to translators the choice of translating this section of community.itexi or |
5 @c not (as GSoC students are required to speak english, a translated page is | 5 @c not (as GSoC students are required to speak english, a translated page is |
6 @c not needed). | 6 @c not needed). |
7 | 7 |
8 @c Current proposals for Google Summer of Code | 8 @c Current proposals for Google Summer of Code |
9 @macro gsocCurrent | 9 @macro gsocCurrent |
10 | 10 |
(...skipping 26 matching lines...) Expand all Loading... |
37 where LilyPond could be improved, and our development team is always | 37 where LilyPond could be improved, and our development team is always |
38 willing to help those who would like to tackle a project similar to | 38 willing to help those who would like to tackle a project similar to |
39 those listed below. As mentor availability varies from project to | 39 those listed below. As mentor availability varies from project to |
40 project and from year to year it is wise to get in touch with us as | 40 project and from year to year it is wise to get in touch with us as |
41 early as possible. | 41 early as possible. |
42 | 42 |
43 A full list of all the current open issues can be found | 43 A full list of all the current open issues can be found |
44 @uref{http://sourceforge.net/p/testlilyissues/issues/, here}. | 44 @uref{http://sourceforge.net/p/testlilyissues/issues/, here}. |
45 | 45 |
46 | 46 |
| 47 @subsubheading Adopt the SMuFL music font encoding standard |
| 48 |
| 49 For several years now a new standard for music fonts has been around: |
| 50 @uref{http://www.smufl.org/, SMuFL}, which is also discussed as becoming part of |
| 51 a future W3C standard for music encoding. As a FLOSS tool LilyPond should |
| 52 adhere to such an open standard instead of using an isolated solution like it |
| 53 does today. Adopting SMuFL will help integrating LilyPond with the world of |
| 54 music notation software and eventually give LilyPond users access to a wider |
| 55 selection of notation fonts. |
| 56 |
| 57 Making LilyPond compliant to SMuFL includes remapping of the glyphs that are |
| 58 built from METAFONT sources, adjusting the glyphs' metrics to SMuFL's |
| 59 specifications, and finally updating the way LilyPond looks up and positions the |
| 60 glyphs. As an optional part of this project LilyPond's font loading mechanism |
| 61 could be modified to use notation fonts installed as system fonts instead of |
| 62 inside the LilyPond installation. |
| 63 |
| 64 @emph{Difficulty}: Easy/medium |
| 65 |
| 66 @emph{Requirements}: C++ and willingness to get familiar with LilyPond |
| 67 internals. |
| 68 |
| 69 @emph{Recommended}: Interest and experience in working with font files. |
| 70 A little bit of METAFONT. |
| 71 |
| 72 @emph{Mentors:} Werner Lemberg, Abraham Lee |
| 73 |
| 74 |
| 75 @subsubheading Adding variants of font glyphs |
| 76 |
| 77 @divClass{keep-bullets} |
| 78 @itemize |
| 79 |
| 80 @item |
| 81 Adding @q{on} and @q{between} staff-line variants. |
| 82 |
| 83 @item |
| 84 Shorter and narrower variants of some glyphs for example, accidentals. |
| 85 Another, more specific example could be an ancient notation breve |
| 86 notehead coming in two variants one with a small or big @q{hole} within |
| 87 it. |
| 88 |
| 89 @end itemize |
| 90 @divEnd |
| 91 |
| 92 @emph{Difficulty:} easy |
| 93 |
| 94 @emph{Requirements:} MetaFont, C++, good eye for details |
| 95 |
| 96 @emph{Recommended knowledge:} basic LilyPond knowledge |
| 97 |
| 98 @emph{Mentor:} Werner Lemberg |
| 99 |
| 100 |
47 @subsubheading Rewrite LibreOffice LilyPond Extension with Python | 101 @subsubheading Rewrite LibreOffice LilyPond Extension with Python |
48 | 102 |
49 The @uref{http://ooolilypond.sourceforge.net/, OOoLilyPond} extension | 103 The @uref{http://ooolilypond.sourceforge.net/, OOoLilyPond} extension |
50 made it possible to conveniently include LilyPond score snippets in | 104 made it possible to conveniently include LilyPond score snippets in |
51 OpenOffice.org/LibreOffice Writer, Draw and Impress documents while | 105 OpenOffice.org/LibreOffice Writer, Draw and Impress documents while |
52 keeping source and image together. After many years without development | 106 keeping source and image together. After many years without development |
53 an initial effort has started to make the extension compatible again | 107 an initial effort has started to make the extension compatible again |
54 with current versions of LibreOffice and LilyPond. | 108 with current versions of LibreOffice and LilyPond. |
55 | 109 |
56 However, as the LibreOffice ecosystem has changed substantially it is | 110 However, as the LibreOffice ecosystem has changed substantially it is |
(...skipping 71 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
128 | 182 |
129 The @uref{https://github.com/openlilylib/scholarly, scholarLY} | 183 The @uref{https://github.com/openlilylib/scholarly, scholarLY} |
130 extension package provides a powerful infrastructure for scholarly | 184 extension package provides a powerful infrastructure for scholarly |
131 editions. With this package it is possible to encode annotations, | 185 editions. With this package it is possible to encode annotations, |
132 to export them for critical reports, or to produce editorial | 186 to export them for critical reports, or to produce editorial |
133 highlighting in the score (e.g. dashing, parenthesizing etc.), | 187 highlighting in the score (e.g. dashing, parenthesizing etc.), |
134 footnotes etc. | 188 footnotes etc. |
135 | 189 |
136 As a GSoC project substantial enhancements can be made to the | 190 As a GSoC project substantial enhancements can be made to the |
137 package. Our suggestion is an infrastructure to encode | 191 package. Our suggestion is an infrastructure to encode |
138 \emph{variants} (alternative readings, corrections, regularizations), | 192 @emph{variants} (alternative readings, corrections, regularizations), |
139 as outlined in | 193 as outlined in |
140 @uref{https://github.com/openlilylib/scholarly/issues/61, this issue}. | 194 @uref{https://github.com/openlilylib/scholarly/issues/61, this issue}. |
141 It could naturally be extended by the ability to produce music examples | 195 It could naturally be extended by the ability to produce music examples |
142 from annotations, to be used in footnotes or reports. | 196 from annotations, to be used in footnotes or reports. |
143 | 197 |
144 @emph{Difficulty:} medium | 198 @emph{Difficulty:} medium |
145 | 199 |
146 @emph{Requirements:} Scheme, ability to assess an extensive existing | 200 @emph{Requirements:} Scheme, ability to assess an extensive existing |
147 package | 201 package |
148 | 202 |
149 @emph{Recommended:} familiarity with scholarly editing | 203 @emph{Recommended:} familiarity with scholarly editing |
150 | 204 |
151 @emph{Mentors:} @emph{NN,} Urs Liska | 205 @emph{Mentors:} @emph{NN,} Urs Liska |
| 206 |
| 207 @divEnd |
152 | 208 |
153 | 209 |
154 @divClass{column-center-middle-color2} | 210 @divClass{column-center-middle-color2} |
155 @subheading Information for Applicants/Participants | 211 @subheading Information for Applicants/Participants |
156 | 212 |
157 In order to have a satisfying experience with GSoC applicants are | 213 In order to have a satisfying experience with GSoC applicants are |
158 strongly advised to thoroughly read the following recommendations. Some | 214 strongly advised to thoroughly read the following recommendations. Some |
159 of these are relevant for the application process, others for the time | 215 of these are relevant for the application process, others for the time |
160 within the project. | 216 within the project. |
161 | 217 |
(...skipping 66 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
228 @end macro | 284 @end macro |
229 | 285 |
230 | 286 |
231 @c Inactive proposals for Google Summer of Code | 287 @c Inactive proposals for Google Summer of Code |
232 @macro gsocInactive | 288 @macro gsocInactive |
233 @subheading Inactive Google Summer of Code project suggestions | 289 @subheading Inactive Google Summer of Code project suggestions |
234 | 290 |
235 The following list describes GSoC projects that had been proposed | 291 The following list describes GSoC projects that had been proposed |
236 in recent years and which are still considered valuable but for | 292 in recent years and which are still considered valuable but for |
237 which we currently don't have mentors available. | 293 which we currently don't have mentors available. |
238 | |
239 | |
240 @subsubheading Adopt the SMuFL music font encoding standard | |
241 | |
242 For several years now a new standard for music fonts has been around: | |
243 @uref{http://www.smufl.org/, SMuFL}, which is also discussed as becoming part of | |
244 a future W3C standard for music encoding. As a FLOSS tool LilyPond should | |
245 adhere to such an open standard instead of using an isolated solution like it | |
246 does today. Adopting SMuFL will help integrating LilyPond with the world of | |
247 music notation software and eventually give LilyPond users access to a wider | |
248 selection of notation fonts. | |
249 | |
250 Making LilyPond compliant to SMuFL includes remapping of the glyphs that are | |
251 built from METAFONT sources, adjusting the glyphs' metrics to SMuFL's | |
252 specifications, and finally updating the way LilyPond looks up and positions the | |
253 glyphs. As an optional part of this project LilyPond's font loading mechanism | |
254 could be modified to use notation fonts installed as system fonts instead of | |
255 inside the LilyPond installation. | |
256 | |
257 @emph{Difficulty}: Easy/medium | |
258 | |
259 @emph{Requirements}: C++ and willingness to get familiar with LilyPond | |
260 internals. | |
261 | |
262 @emph{Recommended}: Interest and experience in working with font files. | |
263 A little bit of METAFONT. | |
264 | |
265 | |
266 @subsubheading Adding variants of font glyphs | |
267 | |
268 @divClass{keep-bullets} | |
269 @itemize | |
270 | |
271 @item | |
272 Adding @q{on} and @q{between} staff-line variants. | |
273 | |
274 @item | |
275 Shorter and narrower variants of some glyphs for example, accidentals. | |
276 Another, more specific example could be an ancient notation breve | |
277 notehead coming in two variants one with a small or big @q{hole} within | |
278 it. | |
279 | |
280 @end itemize | |
281 @divEnd | |
282 | |
283 @emph{Difficulty:} easy | |
284 | |
285 @emph{Requirements:} MetaFont, C++, good eye for details | |
286 | |
287 @emph{Recommended knowledge:} basic LilyPond knowledge | |
288 | 294 |
289 | 295 |
290 @subsubheading Automated testing and documentation for openLilyLib | 296 @subsubheading Automated testing and documentation for openLilyLib |
291 | 297 |
292 @uref{https://github.com/openlilylib, openLilyLib} is an extension | 298 @uref{https://github.com/openlilylib, openLilyLib} is an extension |
293 framework for LilyPond code providing a “snippets” repository and a | 299 framework for LilyPond code providing a “snippets” repository and a |
294 suite of integrated packages such as for example page layout tools or | 300 suite of integrated packages such as for example page layout tools or |
295 scholarly annotations. It is very powerful and promising, but to really | 301 scholarly annotations. It is very powerful and promising, but to really |
296 get off the ground two features are missing: automated testing and | 302 get off the ground two features are missing: automated testing and |
297 documentation generation. | 303 documentation generation. |
(...skipping 114 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
412 Automatic code analysis tools, like valgrind memory leak detection or | 418 Automatic code analysis tools, like valgrind memory leak detection or |
413 callgrind code profilers, provide valuable information about possible | 419 callgrind code profilers, provide valuable information about possible |
414 flaws in our C++ code. Cleaning up warnings would allow us to automate | 420 flaws in our C++ code. Cleaning up warnings would allow us to automate |
415 the rejection of any patch which introduced extra warnings. | 421 the rejection of any patch which introduced extra warnings. |
416 | 422 |
417 @emph{Difficulty:} medium | 423 @emph{Difficulty:} medium |
418 | 424 |
419 @emph{Requirements:} C++ | 425 @emph{Requirements:} C++ |
420 | 426 |
421 @end macro | 427 @end macro |
LEFT | RIGHT |