MozillaWiki:Team/Meetings/2014-09-09
Mozilla Wiki Team Meeting
9 September 2014
= Attendees =
= Agenda / Notes =
- Quick review of work from August (Upgrade, etc.)
- Review roadmap and prioritize things to work on next: https://wiki.mozilla.org/MozillaWiki:Roadmap
- BatchUserRights: https://bugzilla.mozilla.org/show_bug.cgi?id=1051076
- MobileFrontEnd: https://bugzilla.mozilla.org/show_bug.cgi?id=1051189
- Extensions I'd like to explore using (that don't already have bugs filed):
- https://www.mediawiki.org/wiki/Extension:Flow
- http://semantic-mediawiki.org/wiki/Semantic_Result_Formats +1 :D +1
- Bringing other extensions up to date
- Bugzilla extension (needs update to use newer Bugzilla API)
- File bug about optimizing deployment workflow
- Testing RPM work can be folded in here
- Discuss user rights audit/adjust: https://bugzilla.mozilla.org/show_bug.cgi?id=1051201
- I'd like this to be the next thing we roll out. One block yet is that we need to create a process for how people are granted additional permissions.
- I'd like this to be the next thing we roll out. One block yet is that we need to create a process for how people are granted additional permissions.
- Do we want to participate in this? https://www.battleforthenet.com/sept10th/
- (I need to find out if mozilla.org is, which is a prerequisite.)
- MDN is pondering doing something for this: https://bugzilla.mozilla.org/show_bug.cgi?id=1060483
- Facilitating volunteer participation
- Should we have another meeting later in day so that those who work can participate?
- Maybe increase meeting frequency, w/ alt weeks being more friendly for volunteers w/ full-time work
- Maybe increase meeting frequency, w/ alt weeks being more friendly for volunteers w/ full-time work
- Should we have another meeting later in day so that those who work can participate?
Other?
(put any discussion topics here)
- just start adding categories to pages (probably will need to iterate and take feedback)
- thinking of categories as tags (teams can be tags, "meeting notes" can be tags)
- avoid mimicking the org. structure too much (org structure changes)
- current wiki seems to use path names (subpage structure) in a hierarchical way
- getting more categories comes first
- we have pages that look like namespaces but are not
- we have namespaces that probably shouldn't be namespaces anymore
= Action Items =
* Let's talk category hacking! https://docs.google.com/spreadsheets/d/1g6hdBQpFyAWRW0Ll4v2hgKgfVzQ0Q48ng7B0Ih9Z58o/edit#gid=0
1. We should finish the Categories Whiteboard document because it provides information on a lot of interesting / historic projects
: When you're done, maybe put it on the wiki so that it can be wikilinked and used for maintenance? :) —GPH
2. We need to make a decision on whether we want to collapse the categories with 1 member or just put out a "from here on out" statement in a way that doesn't screw up any workflows (eg. L10n and Remo, or is it ReMo?)
: I'd say, don't worry about how many pages are in which categories before you determine which categories should be a part of the encouraged workflow. Build out your ontology, and then the categories can be shifted to fit. (We never got a chance to really discuss bots, but bots will make any major secretarial changes easy, so no need to worry about workload.) —GPH
3. Is there the possibility to do something like this:https://wiki.mozilla.org/Talk:Contribute, which monitors all pages in a space and could possibly serve the same purpose as a category.
: I'm not sure what the purpose of that list is, but I don't think the talk page is the appropriate place for it. It would do better as a subpage or subsection somewhere, I think. And that list doesn't monitor the subpages; it only lists them. No changes to subpages will trigger the watchlist notification for that page; it is only triggered on content edits, and the content will remain the same. —GPH
4. This is a good example where community wiki gardening/sprints will be awesome.
: Please be on the weekend. :) —GPH
