Action-TC-2017-07 Forum on Discourse

[rogers492]

End the trials of NodeBB and Disqus and tidy them up. Establish the Forum on Discourse. Request feedback on what Category/Tag/Topic structure we want to start with, to use the Forum in earnest for the next year. Carry out a review at the end of the year to decide if we should continue with Discourse.

[rogers492]

I have given some thought to how we might use the Forum and what Discourse provides, ie: 2 levels of Categories, with unlimited Topics containing unlimited posts; with Tags applied at Topic level. Here is a generalised example of how I think we should set it up, based on the primary objectives of:

1. Making it easy to find what you're looking for
2. Making it easy to know where you should put your new post or topic.
   The Categories, Sub-categories and Tags would be preset; the topics and posts would not, the ones I give here are just examples.

• OpenWIS Association (category)
  • Governance (sub-category)
    • TC Meeting May 2017 (topic)(tag: Technical Committee)
      • Provisional agenda (post)
      • Provisional agenda - updated (post)
      • Change of date (post)
      • Meeting papers (post)
      • Meeting minutes and actions (post)
    • Contributor License Agreement Update 2017-09 (topic)(tags: Steering Committee, CLA)
      • Draft CLA Update 2017-09-16 (post)
      • NWS feedback on CLA Update 2017-09-16 (post)
      • Draft CLA Update 2017-09-23 (post)
      • Why KMA cannot accept Draft CLA Update 2017-09-23 (post)
      • Draft CLA Update 2017-09-27 (post)
      • CLA Update 2017-09-27 approved by SC (post)
    • etc...next topics and posts under 'Governance'
  • Facilities and Tools (sub-category)
    • Forum feedback (topic)
      • What did the Romans ever do for us? (post)
    • Website feedback (topic)
      • Should we have a webpage for ...? (post)
      • etc...
    • Testing tools (topic)
      • etc...
• Project: OpenWIS-Core (category)
  • Project Management Committee (sub-category)
    • Release 3.14.10 (topic)(tag: v3)
      • Should we include the blue widget in this release? (post)
      • Should we avoid the public holiday in Guatemala? (post)
    • OpenWIS-Core v6 (topic)(tag: v6)
      • Should Option 7 also include...? (post)
    • Skills required for... (topic)(tag: v5)
    • etc...
  • Developers (sub-category)
    • Java (topic)
      • Java scope problem (post)
      • Does anyone have an adapter pattern for...? (post)
    • next topic etc...
  • System Admins (sub-category)
    • Deployment of 3.14.17 (topic)(tag: v3)
      • Is anyone using Ubuntu 17.5.67.1.342 (NOT 17.5.67.1.343)? (post)
      • etc...
    • System Reporting and monitoring (topic)
      • Should we have a report that shows...? (post)
      • We already have... (post)
      • Ah, but it's... (post)
      • Let's raise an RFC (post)
    • etc...
  • Users (sub-category)
    • Metadata (topic)
      • Is there a tool that allows me to upload metadata in bulk? (post)
      • Yes our sister project excel2wis does that (post)
    • etc...
• Project: excel2wis (category)
  • Project Management Committee (sub-category)
    • Release 3 (topic)(tag: v3)
    • etc...
• Project: XYZ (category)
  • Project Management Committee (sub-category)
    • Release NN (topic)(tag: vN)
    • etc...
• Community
• General

If we can agree this structure then we can flesh out the list of headings and pass it to @cassie-stearns for implementation - sooner the better.

Please comment @solson-nws @cassie-stearns @lmika-bom @mclaudon-mto @mgiannoni @woollattd @remy-gibault

[cassie-stearns-NOAA]

@rogers492 I think that structure seems fine. I would just want to make sure that we make a cateogory/subcategory in there somewhere that we have to exclusively use for comment threads posted on website pages. It will make life easier to manage the plugins.

[mclaudon-mto]

@rogers492 It seems fine

[rogers492]

@solson-nws Can we progress this now?

[jude2018]

The Annual meeting TC approved the proposal to adopt the initial categories, sub-categories, and topics. Therefore close.