...
How can working group members help prioritize updates to existing endpoint documentation?
How can WG members effectively share Python/ASnake examples with devs for inclusion in documentation?
What else can we do to expedite this project in the next year?
Action items
Decisions
API Documentation Working group Group members will submit Jira tickets for endpoints that need to be updated, beginning with those identified as high priorityWe will continue to discuss whether and how to add Python/ASnake examples to API docs in the coming months - lower priority than fixing existing docsour recommended updates to the API documentation as JIRA tickets (one per endpoint), which the developers, in consultation with the Development Prioritization team, will address in the course of making other changes in preparation for upcoming releases. This should provide a way for the Working Group and the devs to share the load, with the WG members providing updated documentation without having to go through the process of building, testing and submitting pull requests, which may have been an inhibitor to progress up to this point.
There are improvements that can be made to the way CURL examples are generated, notably in the use of random strings as placeholder values for URIs. This, and other improvements to the build process for API docs, will be explored by the development team.
The addition of Python/ArchivesSnake examples requires further discussion. While we want to support the significant number of Python users in the community, there's some concern that this work may be beyond the scope of what the developers at Lyrasis should take on. To be continued...