MDN/Archives/Community meetings/2011/2011-03-30: Difference between revisions
< MDN | Archives | Community meetings | 2011
Jump to navigation
Jump to search
m (Jswisher moved page MDN/Archives/Community meetings/2014/2011-03-30 to MDN/Archives/Community meetings/2011/2011-03-30: reorganizing) |
|||
| (6 intermediate revisions by 5 users not shown) | |||
| Line 8: | Line 8: | ||
* We need to come up with a system for tracking and managing documentation in the [http://mozilla.github.com/process-releases/draft/development_overview/ new multi-branch development plan]. | * We need to come up with a system for tracking and managing documentation in the [http://mozilla.github.com/process-releases/draft/development_overview/ new multi-branch development plan]. | ||
* Tentative proposal: tag articles with "branch:''branchname''" so we can find them and set the versions on them when the tiem comes. But how do we handle sections and notes? | ** Tentative proposal: tag articles with "branch:''branchname''" so we can find them and set the versions on them when the tiem comes. But how do we handle sections and notes? | ||
* Sheppy is working on a sample of a tabbed interface for looking at mobile vs. desktop compatibility information. | |||
== Doc sprints == | == Doc sprints == | ||
* This Friday and Saturday, [[MDN/Doc_sprints/2011April|April 1-2]] | * This Friday and Saturday, [[MDN/Doc_sprints/2011April|April 1-2]] | ||
* A major focus of this sprint will be adding compatibility tables to web standards (HTML/CSS/JS) pages. We discussed and rejected the idea of creating the tables with a template. We will create a blank table that can be copied and pasted. It will have columns for the various browsers (with Chrome and Safari separated), and tabs for desktop vs. mobile. Sheppy will create a prototype and share it with the community before the sprint. | |||
Latest revision as of 19:30, 6 May 2015
Agenda/Notes
Site admin
- Access SNAFU
- IT has updated the staging server to MindTouch 2010 10.0.7; working on getting QA on to testing it.
Documentation planning
- We need to come up with a system for tracking and managing documentation in the new multi-branch development plan.
- Tentative proposal: tag articles with "branch:branchname" so we can find them and set the versions on them when the tiem comes. But how do we handle sections and notes?
- Sheppy is working on a sample of a tabbed interface for looking at mobile vs. desktop compatibility information.
Doc sprints
- This Friday and Saturday, April 1-2
- A major focus of this sprint will be adding compatibility tables to web standards (HTML/CSS/JS) pages. We discussed and rejected the idea of creating the tables with a template. We will create a blank table that can be copied and pasted. It will have columns for the various browsers (with Chrome and Safari separated), and tabs for desktop vs. mobile. Sheppy will create a prototype and share it with the community before the sprint.