[Koha-bugs] [Bug 30998] [DOCS] Managing documentation tasks - simplify processes and integrate more with the development process

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30998

--- Comment #23 from David Nind <david at davidnind.com> ---
Comments on comment #15 (Arthur) and comment #16 (Victor).

I think Martin has tried to encourage that type of work flow - where a bug
isn't pushed until the docs are done, but that hasn't worked that well for
Koha.

I'd more than welcome, and certainly encourage, contributions from developers
for their bugs, but I realise that this may not necessarily be a strength or
something they are interested in doing.

Everyone can contribute to the docs, but there is a bit of a learning curve
(although developers are at least familiar with git, so that is once less
hurdle!). I'll take a look at updating our instructions and guidance, which I'm
trying to cover in a "Content Development Guide".

Slightly off-topic, but I'd probably like developers to focus on adding release
notes before they tackle the documentation, for example:

- This new feature [does XYZ].
- This enhancement [adds X and Y to Z].
- This fixes [XYZ] so that it does [expected behaviour], [instead of whatever
error or problem was happening]. 

That way, it makes it much easier to identify if documentation updates are
required (instead of having to read through the bug history/latest patches).

-- 
You are receiving this mail because:
You are watching all bug changes.