Professional Documents
Culture Documents
The most crucial thing that we can do is to move away from a top-down,
campaign-driven "organization" to become a resource for empowering
individuals with tools that help them to be successful, encourages deep
participation in the community and promotes cross-pollination between
parts of the MozillaUniverse that rarely connect.
Agenda
In order to accomplish these goals, over the next 3-6 months, we will
need to:
Part of our work on SFX will have the secondary eect of giving us tools
to support localization teams around the world. In particular, things that
we take for granted (primarily hosting and bandwidth) are very hard to
find, in addition to the needs for well-implemented technical
infrastructure.
If Mozilla can provide a specific and robust toolset for language projects,
international adoption would be much improved. This toolset would be
hosted in a sister Drupal install found at MozillaLocalizers.com. It would
be designed very similar to SpreadFirefox except that it would focus on
translation and localization tools, as opposed to marketing and
promotional tools.
MozillaEurope
MozillaEurope is anxious to see more support for their work from Mozilla
proper and SpreadFirefox. In particular, many visitors to SFX are not
native english speakers or are looking for localized versions of
mozilla.org. We need to address this need and MozillaEurope should take
on the responsibility for this work once we create the tools to support
their eorts.
MozillaNetwork
This should be the name for the interwoven network of sites that
represent Mozilla's online footprint. It would include SFX and mozilla.org
but also sites like MozDev, UMO, mozillazine and others.
Thus the fact that there is an "ocial" network should be made more
apparent; ocial sites should share design elements (as mozilla.org and
SFX do now) and also place a higher priority on coordinating branding,
messaging and chain of command.
I only recently found out about the DevMoProject, but apparently Mozilla
has hired someone to coordinate the creation of a Mozilla Developer's
Network, almost identical to the project that Robin Monks has begun to
organize. Although the description of the project appears to be more like
MSDN for Mozilla, nevertheless, the similarities between this project and
Robin's are unmistakable.
Technology selection
There seems very little benefit in trying to reinvent a CMS solution again,
as it's already been tried on a number of occassions. As it is, both
MozillaEurope and a number of other sites in the network are using
cludged solutions that are simply not cut out for the task of community
building.
Rather than starting from scratch, we should leverage the countless hours
that Drupal developers have invested in the platform and add to it.
In addition, the next version of Drupal will see significant changes in the
flexibility of its node/content system. Mozilla should increase its
participation in the Drupal community multi-fold in order for these
changes to support its goals.