Community

Mailing Lists

When an Autoprotocol Standard Change (ASC) is accepted into the official standard it is announced on the autoprotocol-announce list. It is recommended that everyone who wishes to track Autoprotocol sign up for the mailing list, which is very low volume.

Announcements
autoprotocol-announce@autoprotocol.org
Users
autoprotocol-users@autoprotocol.org
Development & ASC Discussion
autoprotocol-dev@autoprotocol.org

Autoprotocol Standard Change ("ASC") Process

Changes to the Autoprotocol specification are made using the Autoprotocol Standard Change ("ASC") process. Anyone can write an ASC. Community-accepted ASCs are necessary for any changes to the Autoprotocol standard, such as:

  • Adding a new instruction, for example to support a new class of device.
  • Changing the parameters of an instruction in case something is over- or under-specified.
  • Adding a new section to the protocol structure.

To submit an ASC, simply email a properly-formatted proposal to autoprotocol-dev@autoprotocol.org. An ASC must contain at least five mandatory sections:

Title
A unique descriptive name of between three and twenty words to identify the proposal.
Authorship
The name, email address, and affiliation of record for the individual author(s) of the ASC.
Motivation
A brief prose description of the problem being solved and why a change to the standard deserves consideration.
Proposal
A complete description of the change being proposed in sufficient depth and detail for the community to evaluate the change in question.
Compatibility
A detailed discussion of any possible backwards incompatible implications, being careful to identify any prior underspecifications that might lead to backwards incompatibility not explicity defined in the standard.

ASCs must be formatted using Markdown syntax. Each of the section titles shall be encoded as h1 (#) and code example blocks shall be delimited using three backticks rather than indentation. (Semantic indentation must not be used in an ASC.)

Submitted ASCs may be published on autoprotocol.org at some time when the sufficient merit of the ASC has been determined by the standard curators. When an ASC is published on autoprotocol.org, it is assigned a sequential integer ASC number. Publishing of an ASC does not imply endorsement or acceptance of the proposal, though it is a necessary step in that direction.

Curators

Jim Culver
jim@transcriptic.com
Vanessa Biggers
vanessa@transcriptic.com
Peter Lee
peter@transcriptic.com
Yang Choo
yangchoo@transcriptic.com