Closed Bug 630971 Opened 13 years ago Closed 13 years ago

Integrate l10n systems of www.mozilla.com and www.mozilla.org

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Future

People

(Reporter: davidwboswell, Assigned: Milos)

References

Details

Opening bug to track any changes needed in l10n systems as part of the upcoming merging of www.mozilla.com and www.mozilla.org.
Target Milestone: 1.5 → 1.6
David, what do we need to say that this one is closed?

I don't think we need to change anything in the mozilla.com system for it to be able to support both website localizations.

I have successfully ported everything to the very same codebase we have on mozilla.com, so every single feature that mozilla.com has, both l10n-related and others, are now into projects/mozilla.org/branches/hagege/.
OS: Mac OS X → All
Hardware: x86 → All
To close this out, the person who is leading the merge needs to review and approve the new l10n system and then we need to deploy it.

It may also be necessary to resolve other merge issues before we can deploy this.  For instance, the two staging systems might need to be merged first (and to merge staging we may need to archive much of the legacy content on mozilla.org).
Target Milestone: 1.6 → 2.0
Target Milestone: 2.0 → 2.1
Target Milestone: 2.1 → 2.2
Target Milestone: 2.2 → 2.3
Target Milestone: 2.3 → Future
Assignee: nobody → milos
Milos, was this taken care of during your recent site merge?
Yes, I'm closing this one.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
This is being staged but it isn't completed yet, right?
Hmm, l10n system, as system is all done, and most of the pages are working on it. I just forgot to push and change some files.
If you want to close this, I suppose that's fine.  I don't want people to think that www.mozilla.org has an l10n system now -- which it doesn't yet.
Well, mozilla.org does not have l10n system on production now. If that's what you meant by opening this bug, to have working mozilla.org and mozilla.com with same l10n systems on production, then we can mark this invalid, as it's not going to happen by our current merge plan.
Why would we want to mark this as invalid?  Isn't it a goal to have an l10n system on the merged site?
I'm just saying I don't really understand what is this bug all about, and am trying to figure out.

When can we close this one: 
    a) when we have a working mozilla.com/mozilla.org as a one website
    b) when we have the same codebase on both websites on prod
    c) when we have the same l10n processing php backend on the merged website, on stage
This bug was originally set as a blocker to having a completely merged site, so this seems to fit with option A above.

This was opened before the new phased approach though, so it's possible that original idea doesn't fit anymore.
OK, acknowledged. So, we already have working mozilla.com/mozilla.org website on stage(except for the few pages), meaning that redirects work, includes work, functionality is there...

If you don't feel like having this bug closed while those few pages aren't still working, please do reopen it, and we can close it once I fix those - probably tomorrow morning.
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.