OpenActive Maintainers
  • OpenActive Maintainers
  • Development roadmap
  • Review processes
  • Expert quick start (move to Contributors)
  • Implementation support
  • New dataset approvals
  • Archiving tools
  • Known dependencies
  • Updating External Project Dependencies
    • Node
    • C#
    • Ruby and PHP
  • Guide: Creating a new OpenActive Vocabulary
  • Guide: Adding a custom domain to a Heroku App
  • Guide: Refreshing personal access tokens
  • Guide: Creating a new GitHub repository
Powered by GitBook
On this page

Implementation support

PreviousExpert quick start (move to Contributors)NextNew dataset approvals

Last updated 1 year ago

Peer-to-peer community support is offered for all implementations, however such support should always be overseen by an "implementation expert" (which is currently the same as a maintainer).

Documentation can be misinterpreted, and previous implementations have had to do expensive refactors to fix issues that could have been caught earlier on in delivery.

There is also a risk that even maintainers have a different understanding of documentation, and hence collaboration between maintainers is essential to check for a consensus in understanding on anything that is not clear. As a rule: do not make assumptions; instead always check with the group, discuss and then clarify the documentation with the result.

All implementations must pass OpenActive Test Suite (either in validation-only mode, for open data, or the full test suite, for Open Booking). Validation-only mode is run in CI on the data-catalog

https://github.com/openactive/data-catalogs