MozillaWiki:Team/Meetings/2014-04-08

From MozillaWiki
Jump to navigation Jump to search

Wiki Working Group - 7 April 2014 3rd meeting

Last meeting's notes: Contribute/Education/Wiki_Working_Group/Notes/2014-03-25

Attendees

(We'll start with quick introductions. Also, write your name down if you're in attendance.)

  • Lyre Calliope / @CaptainCalliope
  • Justin Wood / Callek
  • Rahid
  • jd
  • Larissa
  • Gordon
  • Jennie
  • Surit (imsurit)
  • Joelle

Agenda / Notes

What does it mean to be a module peer?

Christie's suggestion:

  1. help craft and drive the roadmap (take lead on atleast one committee)
  2. take an active part in any governance issues that arise
  3. advocate for the wiki across the Mozilla community
  • add something about decision-making and escalation paths
  • ask laura thompson for guidance, another person to ask is gerv
  • Will folks remind me who would like to be a peer? (I didn't take note from our last meeting)
    • Gordon
    • Lyre Calliope


Organization Structure

Editorial Roadmap

https://cbt.etherpad.mozilla.org/wwg-2014-roadmap

Research

Presented by Joelle

To address "questions of clarity" about wiki's position within different projects, teams, groups

* How are people/groups currently using the Wiki?
* How would people/groups like to use the Wiki?

What tools currently exist to gather data on wiki usage and maintenance?

* https://wikiapiary.com/wiki/MozillaWiki 
* https://wiki.mozilla.org/Special:SpecialPages 
* What else?

Where to begin? Who would like to go forward/assist with this? Short-term

* --Need to gather data analytics 
* --Survey groups

Long-term

* --Build dashboard(s) separate from the wiki that tracks usage

Other / Misc

  • How can we clarify where people should file bugs?
    • Can we get wiki.mozilla.org spun out into its own WebOps component?

^^ I would rather use the existing component under Websites. -ck

      • Oh, I meant for the technical/IT side (Infra & Ops). -GPH

---> when you type in wiki.mozilla.org on https://bugzilla.mozilla.org/enter_bug.cgi you get the option 1) if you type just "wiki" you don't see that option at first 1) Websites > wiki.mozilla.org 2) Infrastructure & Operations > WebOps: IT-Managed Tools

Action Items

  • draft roadmap based on new governance/organizational structure
  • track down GA person on web productions
  • [Joelle, research-type folks] generate list of research questions
  • christie and gordon to connect re spam issue
  • Register the IRC channel and op relevant users
    • Ping on-call in #it to get op permissions in order to register channel
  • Determine how we want to handle long queries


Agenda item for next time:

Webmaker Wiki revamp

Presented by Matt Thompson

  • http://openmatt.org/2014/03/25/open_scrum/
  • https://wiki.mozilla.org/Webmaker
    • This is what not to do.
      • Uses HTML instead of wikimarkup.
        • Wikimarkup tends to be cleaner and easier to maintain (once you get over the learning curve).
      • Uses external links for wikilinks.
        • Wikilinks help us get statistics from the built-in MediaWiki features (e.g. "What Links Here").
      • Has super fancy styling that may get in the way. (This is subjective, of course.)
        • Super fancy styling always requires a foray into HTML and/or CSS, and may clash with the skin (especially given that different people may be using different skins).