me
Proposed definition of levels and applicable standards
by Sven Laux - Tuesday, 17 June 2014, 2:17 PM
 

Hi,

I wanted to address some important discussion points around 'levels' and standards and have written the attached document in an attempt to bring clarity and start a discussion.

In summary, the document recognises three different levels of feature (repository):

  • The core bundle
  • Contrib features / repositories 
  • Community features / repositories

The document defines each of these and captures some thinking about what characteristics / standards apply to each of these levels. The items mentioned in the document are:

  • Definition of what the term means
  • Ownership / maintenance
  • Cross-platform compatibility
  • Responsiveness
  • Adherence to coding standards
  • Inclusion of unit tests
  • Level of documentation
  • Adherence to accessibility standards
  • Performance requirements
  • RTL support
  • Required metadata
  • Testing requirement
  • Process to change
  • How to report issues
  • Registered in Adapt registry
  • Backwards compatibility
  • Update policy
  • Version numbering

 

I'm keen to discuss this here with the core team and the community. Please comment / raise questions.

Many thanks in advance,
Sven