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

RESOLVED FIXED

Status

addons.mozilla.org Graveyard
Public Pages
RESOLVED FIXED
14 years ago
2 years ago

People

(Reporter: Benjamin Smedberg, Assigned: wolf)

Tracking

({fixed-aviary1.0})

Details

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
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.

Updated

14 years ago
Blocks: 245948
(Assignee)

Updated

14 years ago
No longer blocks: 245948

Updated

14 years ago
Blocks: 254496
(Assignee)

Updated

14 years ago
No longer blocks: 254496
(Reporter)

Comment 1

14 years ago
blocking, per triage team
Flags: blocking-aviary1.0+
(Assignee)

Comment 2

14 years ago
Created attachment 156712 [details]
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.
(Assignee)

Comment 3

14 years ago
bsmedberg: if you would, go ahead and check this in. :-) thanks.
OS: Windows 2000 → All
Hardware: PC → All

Comment 4

14 years ago
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?
(Reporter)

Comment 5

14 years ago
Landed. This is now at mozilla/webtools/update (on the CVS trunk). Next task is
to get a test server.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
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

14 years ago
myk: would you please explain why new webtools should land in mozilla/tools
instead of mozilla/webtools and if possible, when this changed?
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

14 years ago
well, i like the distinction...
(Assignee)

Updated

14 years ago
Component: Update → Web Site
Product: mozilla.org → Update
Version: other → unspecified
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.