I'm afraid the devil might be in "Essential parts needed aren't publicly accessible for now."
I went through /Design and /Project pages on the wiki I like what I see. Previewing translations with restartless language packs instead of waiting a full day for the new build to come is a big step forward. I'm particularly curious about how and if we are going to tackle merging strings on new releases. Is there a plan to automate the process of adding new strings and removing obsolete ones (while still keeping them in TM)? If there is such plan, what happens to translated strings or entire files that move to a new location? -Matjaž On Fri, Oct 24, 2014 at 9:05 AM, Francesco Lodolo [:flod] <[email protected]> wrote: > Il 24/10/14 00:14, Axel Hecht ha scritto: >> >> https://github.com/aisle-moz/moz.aisle. > > At the risk of sounding not smart, in that page it says: "Firstly, you want > to get c9v3, and get that running locally. Please follow the docs there." > > I found this blog post about the release: > https://c9.io/site/blog/2014/07/the-new-cloud9-one-week-later/ > So, I went to c9.io, signed up and did a bit of testing with the demo > workspace. But that's definitely not installing c9v3 locally. > > The only thing I found with Google is this page: > https://github.com/ajaxorg/cloud9/ > But it hasn't received updates in almost a year. Is this the documentation > to use? > > I confess everything is a bit cryptic for someone who didn't know what c9 > was until yesterday. > > Francesco > > _______________________________________________ > tools-l10n mailing list > [email protected] > https://lists.mozilla.org/listinfo/tools-l10n _______________________________________________ tools-l10n mailing list [email protected] https://lists.mozilla.org/listinfo/tools-l10n
