[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

David Nind <david at davidnind.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         QA Contact|testopia at bugs.koha-communit |
                   |y.org                       |
             Status|NEW                         |ASSIGNED
           Priority|P5 - low                    |P1 - high
           Assignee|koha-bugs at lists.koha-commun |david at davidnind.com
                   |ity.org                     |
                 CC|                            |aude.charillon at ptfs-europe.
                   |                            |com, bwsdonna at gmail.com,
                   |                            |caroline.cyr-la-rose at inlibr
                   |                            |o.com,
                   |                            |lucy.vaux-harvey at ptfs-europ
                   |                            |e.com,
                   |                            |martin.renvoize at ptfs-europe
                   |                            |.com

--- Comment #1 from David Nind <david at davidnind.com> ---
Message from Martin Renvoize on 16 June 2022 (hope you don't mind me adding
this here...):

"I was chatting to our staff today and they're still keen to contribute to the
manual, but are also still finding the process confusing especially with
regards to choosing area's to document and when.

I came up with a proposal a little whilst ago to try and integrate the process
more into the other community processes and bugzilla.

Would it be helpful/useful to add a 'Ready for documenting' status in Bugzilla
that sits between 'Pushed to X' and 'Resolved Fixed' and encouraging the
Release maintainers to use that when they make the decision to not backport
instead of the current 'Resolved fixed' change.

This would allow for building a queue automatically on
dashboard.koha-community.org for documentors to work through much like the
testers and the QA team do.  So one would look at the list, work on docs
submissions and then update the bugzilla status to 'resolved' upon completion
(or upon making the decision that documentation updates are not needed)?

Just a thought.. I'm happy to do the bugzilla admin changes and update the
dashboard.  What do you think?"

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