| [ << LSR work ] | [Top][Contents] | [ Issues >> ] |
| [ < Adding and editing snippets ] | [ Up : LSR work ] | [ The makelsr.pl script > ] |
7.3 Approving snippets
The main task of LSR editors is approving snippets. To find a list of unapproved snippets, log into LSR and select “No” from the drop-down menu to the right of the word “Approved” at the bottom of the interface, then click “Enable filter”.
Here is a checklist of the necessary tasks.
- Does the snippet make sense and does it what the author claims that it does? If you think the snippet is suited to be included into the LilyPond documentation, add the ‘docs’ tag and at least one other tag.
-
If the snippet is tagged with ‘docs’, check whether it matches
our formatting guidelines, see LilyPond formatting.
Also, snippets tagged with ‘docs’ should not be explaining (or replicating) existing material in the documentation. They should not refer to the documentation; the documentation should rather refer to them.
-
If the snippet uses Scheme code, check that everything looks good
and there are no security risks.
Note: Somebody could add code like
#'(system "rm -rf /")to a snippet, which would cause catastrophic results if executed! Take this step VERY SERIOUSLY. - If all is well, check the box labeled “approved” and save the snippet.
| [ << LSR work ] | [Top][Contents] | [ Issues >> ] |
| [ < Adding and editing snippets ] | [ Up : LSR work ] | [ The makelsr.pl script > ] |