General approach to a general edit?
Hi everyone!
I'm a composer, arranger, music editor and multi-instrumentalist based in Vancouver, Canada (originally from LA). I've also been a technical writer for software and website developers since the early Internet days. I've designed documentation, created style guides, and helped other writers and editors write more simply and clearly.
Maybe you'll agree: So much information vies for our attention these days, most of us are overwhelmed. The clearer and more elegantly simple info is, the more likely people will read it, and understand it.
Having switched from Sibelius to MuseScore (which is awesome!), I see many places in the Handbook where I think I could contribute to its simplicity, clarity and consistency. I can't very well storm through it, though, even if the changes I see seem obvious—for AFAIK, the editable version is the actual "live" version, right? (There's no "sandboxed" version, is there, where we can make changes subject to approval?)
So what approach should I take? Shall I type out each of my proposed changes and post them here for your consideration? This would take much longer than simply editing, but I want to do it properly. Thanks!
Comments
The Handbook is transitioning over to Git:
https://musescore.org/en/node/371579
In reply to The Handbook is… by underquark
That means that, at present, it's simply locked and no changes can be made at all.
In the past, there has been no control over who modified the Handbook (as far as I have ever been able to see?). Anyone could make any change they wanted. Perhaps that will change with it being located on github?