Comments - Issues for Consideration and Principles that guide Accessibility #246
helpfultangent
started this conversation in
Standards: Accessibility
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In principle, accessibility aims to include considerations for emerging modeling approaches up to well established and mature code bases.
There may be different standards for developers/modelers versus maintainers of repositories.
Possible categories to consider and important distinctions:
model types (e.g. code base with libraries, executable, ...)
Maturity level (emerging approach to mature active and community maintained)
Portability (place-based; portable across problems and locations)
Licensing levels (also think through embargo needs)
Model versions, configurations, and setups
Users of the standards (developers/domain modelers; repository maintainers)
**Aside, there is a good example in the R community and how to document, package it up, and share your code.
Beta Was this translation helpful? Give feedback.
All reactions