Documentation IRC meeting 2021-12-16

From Koha Wiki

Jump to: navigation, search
Koha > Community > Participation > IRC Meetings > Documentation IRC Meetings
Koha > Community > Participation > IRC Meetings > Documentation IRC Meetings > Documentation IRC Meetings 2021

Contents

Place

The #koha IRC channel (IRC server irc.oftc.net).

If you don't have an IRC client you can join the meeting using your web browser.

Time

Agenda

  • Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
  • Updates
    • Review of action points
      • Starting fresh - will review the last few minutes and add as tasks to Bugzilla if required. (David Nind)
    • Project updates
    • What's been done so far
      • ..please add a short update on what you've been working on since the last meeting...
  • Content development guidelines
    • Using Bugzilla for managing documentation tasks (David Nind)
      • I've been adding [DOCS] to the title for documentation task - is this useful? (I find it is.)
      • Should we expand this to make it easier to help identify different task types, or is this over complicating things? For example:
        • [DOCS-Translation] for translation system tasks,
        • [DOCS-Systems] for any tasks for producing the output (such as GitLab continuous integration),
        • [DOCS-Content] for actual content changes,
        • [DOCS-Maintenance] for maintenance tasks such as link checking.
      • Updating the bug for the change once the manual is updated: I'm proposing that once a change from a bug in a release is documented, that we add a comment to the bug saying:
        • Changes for this bug are now incorporated into the manual.
        • Here are the changes we have made (a link to the commit and section in the manual).
        • Indicate that any feedback or suggestions are welcome.
        • Remove the Manual keyword from the bug, if it was used.
        • This will give contributors to the bug a chance to make sure we've reflected the change correctly.
    • Commit messages: generally we should follow the guidelines in the Wiki Git guide for documentation - commit messages and Commit messages - open for discussion. (David Nind) Deferred to the next meeting
    • Translating the manual: I've been attempting to document the process, any input welcome. (David Nind) Deferred to the next meeting
  • Next steps.
  • General business
    • ..add any items not covered under the other headings..
  • Set time of next meeting
    • For discussion, including alternatives:
      • IRC: monthly on Thursday/Fridays, alternate between two times (such as 15:00 and 19:00 UTC time) or a set time that suits most (such as 16:00 UTC), during "work" time or evenings?
      • Video conference: every three months using Jitsi, Zoom, or Google Meet (recordings added to YouTube channel, similar to what koha-US does for SIG meetings)

Apologies

Please list your name here if you would like to attend, but cannot make this meeting:

  • -

Minutes

Next meeting

Personal tools