Charles, Kevin, every one,
Citrus looks good. But as we explained, if there's no one wrting
specicications for eaxh part of citrus nothing will get done.
ok yes we do need to start on some specifications so that we can get
started, but we have not talked about it all that much. first we need
to decide on what we all agree on and change what we do not. if we get more
people to agree with some things I would start some specifications, but I
still don't know exactly what is needed to write one. could someone write a
templet on what needs to be written. that would really help. till then
there are still some people that have not said what they do not like about
Citrus. if you wait any longer we'er going to have to just go with Citrus.
It looks like we need to blog so that people don't get their hopes up. :-/
all the more reason to get this started NOW. and before you guys say it ONE
MORE TIME. I know that we can not get this done in one shot, and that we
need to do this ONE STEP AT A TIME. but now that we have some press on this
and people know that we are working on this we NEED to get things rolling.
Andrew
--
Unsubscribe instructions: E-mail to design+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
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.