• Who’s on the Selection Committee?

    December 13th, 2006 by seth bindernagel with no comments »

    Some have asked who comprises the selection committee that reviews proposals submitted to this program. For the first few meetings, Mitchell, Asa, John Lilly, Mike Schroepfer, Chris Beard, and Chris Hofmann have participated. The committee is open for participation and will include more Mozilla employees and contributors as we continue to scale.

  • Support Update, v.3

    December 12th, 2006 by seth bindernagel with no comments »

    Last Friday, we gathered a small group at Mozilla to review proposals for the community program. The committee considered three individual proposals and two larger, community ideas related to the l10n contributors.

    Of the three individual proposals, we approved one and need further research for the other two. For the approved proposal, we will provide a new PC for one contributor who has been very active in promoting nightly/hourly builds on Mozillazine forums.

    In addition, we approved the purchase of a server for the l10n contributor community. You may have read my last blog post and some comments by Chris Hofmann posted there. Chris Hofmann, Axel Hecht and I will be working to set it up. We welcome any comments on how you think it should be used by the community.

  • l10n Server

    December 6th, 2006 by seth bindernagel with 2 comments »

    A few weeks ago, someone posted the following suggestion for something for us to consider on my blog:

    “how about to host Fx/Tb/Bz etc l10n team’s their own repos/sites? the last month, German l10n person’s domain was expired so people could not take files. that makes me think this ;-) # now most of bugzilla l10n use sf.net for repos pub space.”

    We have been mulling over this idea and I will be putting a proposal for final review this Friday. If all goes well, it looks like we will have something in place for people in the L10N community to use. What needs to be determined is how to engage everyone to use this as a productive workspace that does not expose Mozilla in any unanticipated or harmful way. Frankly, it’s not my expertise, so that is why the selection committee will be reviewing this on Friday to determine what is the next best step. Please look for an update then.