Closed Bug 785935 Opened 9 years ago Closed 4 years ago
Branding for L20n
(Not sure if this is the right component, please guide me where to best file this bug if it isn't.) The localization team has been working hard at work for the past few months developing a new localization technology/platform to replace the current, limited approaches, like gettext, xliff, properties files etc. The ultimate goal is to work with the ECMA's TC39 group towards the standardization of this new technology as part of the ECMAScript. The project has been codenamed "L20n", a geeky-humorous word play on "L10n" (Localization) and "2.0". The motto of the project is "Make simple things simple, and complex things possible." The project aims to be language-agnostic (no specific grammar features are better supported than others) and transparent to developers, giving all of the expressive power of the language to the localizers. You can find more information about the project on the wiki: https://wiki.mozilla.org/L20n We recently moved all the code to github: https://github.com/l20n. The codename has served us well so far, but we would love to get the engagement team's input on the branding. We'd also like to create a mozilla.org website for L20n, similar to what B2G has for instance (http://www.mozilla.org/b2g/)
John -- can we talk about this this week or next week?
Hey Stas. Yes, we can definitely talk about this further. Just let me know when you'd like to do that. Also, re: the bugs it sounds like this is actually multiple projects so we'd need multiple bugs for that (ex. one for the website, one for the branding, etc). This could be used a tracking bug, with all the others set as blockers.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.