7.3 Snippet administration

Wiki administrators should shepherd users who create or modify snippets. An atom feed is available to track changes in the Wiki; see the ‘about’ info page for more.

Here is a checklist of the necessary tasks.

1. All snippets should have the ‘Category:Snippet’ category set.
2. Does the snippet make sense and does it actually do what the author claims that it does? If you think the snippet is suited to be included into the LilyPond documentation, add the ‘Category:Included in the official documentation’ category and at least one other category to classify it by topic.
3. If the snippet is tagged with the ‘Category:Included in the official documentation’ category, check whether the LilyPond source code matches our formatting guidelines, see LilyPond formatting.

   Also, snippets tagged with this category should not be explaining (or replicating) existing material in the documentation. They should not refer to the documentation either; the documentation should rather refer to them.

4. If the snippet uses Scheme code, check that everything looks good and that 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.