MDN/Archives/Community meetings/2013/2013-12-18

< MDN‎ | Archives‎ | Community meetings‎ | 2013

Contents

Agenda/Notes

The MDN community meeting takes place in the #devmo channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). See the meeting time in your time zone. It's open to anyone that would like to participate, so please feel free to join in!

Events

Content

Organization of the Firefox OS section

The section of the docs related to Firefox OS need an overall organization.

The root page is: https://developer.mozilla.org/en-US/Firefox_OS

The organization (or lack thereof) can best be seen in the outline given in the white boxes with blue text on the left in the part of the page with a blue background: the 'navigation' accordion in the page source.

High level decisions related to this content include:

  • the target audience: the second section is 'Usage tips' but seem to be for developers, either of Gonk, Gecko, or Gaia, not sure, but *not* anyone that could be considered a 'user' in the normal sense of that term.
  • a consistent structure between sections: for me, this would be the three layer split (kernel/os/drivers/gonk parts, Gecko/?ril?, Gaia, User Apps), which would determine the platform presentation, the build presentation, and the hacking presentation.
  • a systematic presentation of each section, starting with an overview, and working down into details.

This high level outline is properly the work the documentation team since it is editorial in nature, needs broad scale buy-in, and facilitates targeted contributions by the community.

Chris M. is already aware of this request and thinking about when and how to work on it.

Organization of the Event Guide

The section of the docs currently called "Event developer Guide" needs an overall organization.

The landing page is: https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Events

This is part of the 'Web developer guide': https://developer.mozilla.org/en-US/docs/Web/Guide

The Event Guide has no overall organization. An attempt to start one is given in the paragraphs written on the landing page.

High level decisions related to content include:

  • the audience (which seems to be a 'Web developer')
  • the relation of the Event Guide and Web Dev. Guide
  • the location of the Event Guide (current WebDev/API/DOM ) which is not accurate
  • the structure for the 'Built-in' or 'Browser defined' events

The latter could be done by 'type of event' as was attempted on the landing page. Such an approach is the most 'natural' for outsiders. A second approach might be by 'object Emitter' i.e. ('window', 'document', 'window.screen', ...) which while easy since it requires little thought suffers from the haphazard history of Event addition to the Browser. This would benefit greatly from community consideration.

This high level outline is properly the work the documentation team since it is editorial in nature, needs broad scale buy-in, and facilitates targeted contributions by the community.

Bug 950811 (https://bugzilla.mozilla.org/show_bug.cgi?id=950811) was started on this topic.

Style/user guides

Sheppy is going to be buckling down and finishing up the MDN user guide, MDN contributor guide, and MDN style guide over the next few weeks. This is important to get done, and now is a good time to dive in and do so. Please feel free to comment on the bugs as listed below if you have suggestions or requests.

Process

  • So the Trello thing never took off; do we want to make another attempt to get people to start using it after the holiday break, or figure out another approach?

Kuma

Redesign

  • Shipped! The redesign launch went very smoothly. Let's talk about initial feedback and what's next.

Community

  • No MDN Community meeting on January 1, 2014.
  • Next meeting January 15, 2014.