...
- Small number of folks met Oct 28th for doing a one-day documentation review.
- Not a technical review, focused on community perspectives
- Marked docs that could be improved
- Good notes/suggestions on ways things can be improved. Mostly around better organization, de-duplication, defining things better. These notes can drive documentation updates
- There may be a couple people who are interested in documentation during the sprint, but there may be enough suggestions to support a documentation sprint later on this year or next year.
- Most of the suggested improvements are not technical, so it is not necessary for doc writers to be committers, developers, etc
- awoods: Each release has their own wiki space, but we have a 5.x "head". It looks like the 5.x "head" is what was reviewed. Presumably, it'll be re-named to 6.0. A bulk of the review is likely based on 4.x/5.x understanding. New content and/or updates would need to be added for fcrepo6
- dwilcox: Hopefully, the front-facing parts of fcrepo6 won't change that much from 4/5, but new docs will be needed.
- Fcrepo6 documentation was out of scope for this review. That could be its own sprint, not sure if it should be its own separate effort, or part of a fcrepo6 sprint.
- Desire for a regular rhythm for doc updates.
...