We should do a first round of work planning. The goal is to define work topics and assign people who will be committed to each topic and take “hat” for it.
Topics according to the initiative overall working plan:
- Improving Contributor Guidance
- Write a Guide for Editing and Preview with Forgejo
- Review the local Authoring guide and proposal for improvement
- Improvement of the current local authoring tool
- Integrate the web server into the container
- Impromptu rebuilding of a document instead of manual initializing an overall rebuild
- Create a container with ARM support
- Document analyses and improvement
- Analyze Quick docs and make a list: Document title | last review 1 - 2 -3 - older (years) | Status: fine | akzept. | outdated
- Determine areas where to start work on
- Initialize contact with maintainers / developers if required
- Analyze Administration guides
- parts that can be reused / updated
- parts that are hopelessly outdated and need to be recreated
- parts that can be dropped
- Analyze Quick docs and make a list: Document title | last review 1 - 2 -3 - older (years) | Status: fine | akzept. | outdated
- Way of collaboration
- Using git Features: Fork /Branch and using Forgejo Preview or local preview
- Get a group workspace on hackmd.io
- Problem: we would start with Markdown and had to rework it for AsciiDocs at the end
- Pro: very good discussion and comment facility
- get some etherpad anywhere
- question: is there an etherpad with AcsiiDoc support?