Make a separate section for editing musical scores in the user guide at https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide . This will be similar to the one for poems, but with different screenshots.
I'm deliberately planning to not work on this task until it is higher priority than the other things in my (short) list. Based upon available information, this means that the answer to your question is "no" – and maybe not the quarter after that, either.
This sounds indeed like a good GCI task! Who would (co-)mentor this?, and could edit the task description to
- provide a test page link (where to test musical scores in VE?),
- link to guidelines how screenshots should look like (if we have any guidelines),
- elaborate on skill requirements for a contributor (e.g. basic knowledge of image manipulation/editing software to crop a screenshot; basic English writing skills, etc),
- where to put an initial draft of such a user guide addition.
Then we should be ready to go here! :)
The basic documentation goes in the user guide after the math section:
The end result should look approximately like the sections on math formulae and poems.
The desired music (e.g., for screenshots and examples) is here: https://www.mediawiki.org/wiki/Help:Sample_page#Music Screenshots should be made from the sample page (working in English requires extra effort, so I've made a clean (i.e., without translation markup) copy at https://simple.wikipedia.org/wiki/User:Whatamidoing_(WMF)/Sandbox#Music That wikitext can be copied to any blank page for the purpose of making screenshots, and everything is in the public domain). Screenshots including the music from that section should presumably get descriptions and licenses that match https://commons.wikimedia.org/wiki/File:VisualEditor_tables_post-merge_cell.png and similar pages. Instructions on uploading screenshots can be found here: https://en.wikipedia.org/wiki/Wikipedia:Screenshots_of_Wikipedia
This task will require figuring out wikitext tables, and possibly figuring out translate markup (at least enough to not break it when editing the main page; a translation admin can add markup after the task is approved). The content should probably be created in a sandbox/user subpage on mediawiki.org first, because that will be much easier.
@John_Broughton, would you like to mentor this particular project? Andre assures me that it's a fairly simple process.
@Esanders: Any links to information how to do use generated screenshots, to help a new contributor understand how complex this task is?
@John_Broughton: Great! Please see https://www.mediawiki.org/wiki/Google_Code-in_2016 for more information!
I believe that automatically generated screenshots only work when you're showing an empty page (e.g., an empty dialog box). Right now, the screenshots have to be hard-coded into the program that makes them. That doesn't seem like a beginner's task. However, making one set of screenshots manually would let us sort out which ones are amenable to automation later.
Okay, I've registered. Am I supposed to create the task(s), or has someone already done so, and I can just attach my name to it/them? (I have listed my name at https://www.mediawiki.org/wiki/Google_Code-in_2016 , for what that's worth.) If I can just attach my name, how exactly do I do that?
@John_Broughton: Thank you! Imported as https://codein.withgoogle.com/tasks/6205691471593472/ (for students); as a mentor you can see the task at https://codein.withgoogle.com/dashboard/tasks/6205691471593472/ - feel free to edit it. :)