Documentation: A few more updates #18
Conversation
doc/backlog.rst
Outdated
There was a problem hiding this comment.
@matriv: Let me know if you would like to have some items listed in the backlog.rst file to be converged into issues already. In general, I think it will be fine to pick them from here, but one or another item may deserve better visibility.
There was a problem hiding this comment.
It looks very good, but why not have an open issue instead of a committed backlog file?
I'm afraid with the backlog file it can get more easily forgotten in the future, wdyt?
There was a problem hiding this comment.
In general, I agree. But I don't want to create single issues for each and every of those items yet. We may identify and refactor important ones into dedicated issues, and let the rest sit in the backlog file, or link them into a bundle/meta-issue.
My main intention was to write down notes what could be worked on in the future. If you think we should just put all that content into a single public issue, with bullet points, I will also be happy to do it.
There was a problem hiding this comment.
I think, because "General » Next steps" will go away anyway soon, there would be three dedicated issues to create, when following the "bundling approach" - one for each of:
- General » Actionable
- General » Research
- Cloud readiness
That would be acceptable. WDYT?
There was a problem hiding this comment.
I've dissolved the backlog file again with 67c4294, and created three bundle issues, as outlined above. Individual items may become dedicated issues, based on priority or urgency.
amotl
changed the title
amotl
force-pushed
the
amo/more-docs
branch
2 times, most recently
from
d7073bc to
71e0ad6
Compare
This patch is a little follow-up to GH-17, in order to:
The rendered version of the documents can be inspected at the updated README and the backlog.