Operations: Difference between revisions

Takev (talk | contribs)
Change "branch" to "group" and link to the organization page
replace documentation with guides
Line 1: Line 1:
FASSAG has three [[Organization|main groups]], to facilitate the development of our resources; The documentation group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.
FASSAG has three [[Organization|main groups]], to facilitate the development of our resources; The guides group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.


== Documentation ==
== Guides ==
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.  
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.  


'''Accessible''' documentation isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the documentation being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:
'''Accessible''' guides isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the guides being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:


* Screen readers
* Screen readers
Line 11: Line 11:
* Scaling settings
* Scaling settings
* Clear design
* Clear design
* Good documentation
* Good guides
* Translations
* Translations
* Low-end hardware
* Low-end hardware