255444 - Get update.mozilla.org PHP code into CVS, so that we can work on localizing it

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Public Pages, defect)

Description

[Benjamin Smedberg]

After discussions with some of the l10n teams and the update.mozilla.org team,
we would like to get the PHP code that runs update.mozilla.org into a CVS tree
somewhere. This is so that localization contribitors can work on adding
localized support to umo.

This may require a security audit of the PHP code, I don't know how that is handled.

We would like to get the basic localization work done before 1.0.1, so that
localized builds don't end up redirected to English update pages.

Comment 1

[Benjamin Smedberg]

blocking, per triage team

Comment 2

[Wolf [:wolf]]

Attachment: Mozilla Update source for CVS checkin (0.10.20040821)

This is the current development source. Including the current Database schema.
For checkin to the CVS tree. This is roughly the version that'll be up for
Firefox 1.0PR.

This does not include the administration part of the site, since that's
incomplete and has not been through a security audit, at this time.

Comment 3

[Wolf [:wolf]]

bsmedberg: if you would, go ahead and check this in. :-) thanks.

Comment 4

[timeless]

so erm, is anyone doing a source code audit, or are we just going to pray that
no black hats find things before white hats?

Comment 5

[Benjamin Smedberg]

Landed. This is now at mozilla/webtools/update (on the CVS trunk). Next task is
to get a test server.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

Note that new modules require prior approval from Brendan and that new tools
should be landing in mozilla/tools/ rather than mozilla/webtools/.

Comment 7

[timeless]

myk: would you please explain why new webtools should land in mozilla/tools
instead of mozilla/webtools and if possible, when this changed?

Comment 8

[Brendan Eich [:brendan]]

webtools were the suite of bugzilla, bonsai, tinderbox, and i-forget that terry,
ltabb, et al. hacked.  I'm not sure whether they should be considered a brand
name or franchise, but I think when myk and I last spoke, we thought it was just
confusing, not helpful, to continue to put stuff under webtools.

But if server-side stuff is usefully segregated from command-line/client-side
tools, via webtools vs. tools, then maybe it's worth extending the franchise. 
It's really up to folks who care about the "webtools (tm)".

/be

Comment 9

[timeless]

well, i like the distinction...