Philippe Bossut wrote: > Sounds good. One remark though: we already have another "product" > besides Chandler, it's ChandlerExamples. This contains the localization > files for the extensions (Flickr, Amazon, etc...). See > http://wiki.osafoundation.org/bin/view/Projects/LocalizationProject for > details. It doesn't change anything to your proposal though, just that > we have already an extra level in the hierarchy.
Should that go under chandler/ or should it be a sibling of Chandler? I kind of think sibling... > One question though: what should we store there? The translated po? The > eggs? I'd say the po and have the build system build the eggs (as we do > for parcels) but I'd like to have that stated clearly. I'd say the po and images. Anything that can be generated/built should not be in the repo. > Last: when can we have that done? I've an open task with my name on it > and I'd like to have it "fixed" soon... :) I think we should wait for bear to come back from vacation. This will give others some more time to chime in if they wish. It will be easy to create the repo. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
