Summit2010/Foundation/Ideas

The Foundation is considering running some of the following sessions at the Mozilla Summit 2010:

"Project Communication"

How do we communicate now? What sucks about it? How could we make it better?

Mechanisms covered: Bugzilla/Discussion Forums/IRC/Email/Intranet Forums/Weekly Update/...

Sample topics for discussion:

• Are there any better ways to do the Discussion Groups?
• What moderation options are there, if the alternative is people moving to more closed fora?
• Do we need a "Mozilla Insiders" private forum?

Key people: justdave, dria, dmose

"Branch Management in Bugzilla"

(This seems to be a major remaining Bugzilla pain point.)

• How should this work?
• Is there any chance of getting there?

We could discuss whether a BzAPI-driven new UI is the solution (and if someone can build it), or whether changes need to be made to the Bugzilla core.

Key people: Christian Legnitto, beltzner, johnath, bmoss

"Things You Need To Know" lightning talk

A lightning talk giving a load of very short (one or two sentence) things you really should know about how to work with Mozilla. Probably a governance slant - at least for my ideas! But we could give it a MoFo slant generally. Suggestions from a minute's brainstorming:

• When creating new tri-licensed files, please use the boilerplate from the MPL page rather than copy-pasting.
• The MPL update is hoping to fix the boilerplate verbosity problem.
• If you work for Mozilla, the Initial Developer of the Original Code is "the Mozilla Foundation" (and not "Mike Shaver" - shaverfacts.com)
• If you want new discussion forums - file a bug; it's fairly quick and painless. Don't just set up a Google Group.
• The new commit access policy makes it really easy for you to set up a user Hg repo at Level 1 and get your friends to collaborate with you.
• The Firefox icon files are tri-licensed so official Firefox builds are fully free software.
• You need let the licensing team know before importing third party code into the tree.

... suggestions?

Community Survey

A targetted community survey to find pain points has been on our radar since the beginning of the year. At the beginning of the year we pencilled it into Q2 but I'm now thinking that perhaps it makes more sense to use the Summit as a great opportunity to collar people and interview them.

We'd need to have a discussion about the sort of questions we'd want to ask.

Is it worth trying to tie this into Summit feedback forms, and/or trying to get input from a significant proportion of attendees rather than a hand-picked 20 or 30? There are pros and cons to that...

Mozilla Web Universe

There are over a hundred web sites in the Mozilla community. How can we make sense of this for people? How can we work together to make a more coherent web universe that acts more like one huge site? Can we make cool stuff happening on one site discoverable from another site?

Agenda:

• Present draft web universe map
• Discuss role of a web universe task force
• Discuss other topics people want to cover

Contribute/Participate Session(s)

It sounds like Mary is planning on doing a high-level session about participation and Alina will be doing an in-depth session specifically about the Get Involved process. David will help with both.