On Thu, 2011-06-16 at 21:01 -0400, drew wrote:
<snip>
"Let's finally finish the Frick'n transfer of the North America DVD to
SilverStripe CMS, already"
So - I propose a quick sprint and that needs a kick-off - so this email
is it. Also, some type of work plan with a projected end date aren't bad
things to have ether.
How about just a projected end date for the moment - July 7th.
Now for the plan - catch the next email installment in this thread,
which will have a link to an email posted to the projects mailing list.
Howdy,
well, no link to the projects ML yet, but maybe later today.
SO for this mornings stand up meeting:
One quick question:
Shall we layout the structure on the CMS development platform so as to
create a single .iso file with all the files needed to support all three
languages (html files/artwork/add-ons) or in such a way as to be able to
generate three .iso files, once each for each langauge?
I have, quietly, been working on my copy of SilverStripe and exploring
ways to approach this - my preference at this point would be to generate
one .iso file with everything included for the three languages.
How do others feel on this?
Thanks
Drew
--
Unsubscribe instructions: E-mail to marketing+help@us.libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/us/marketing/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.