On Wed, 2010-11-03 at 21:09 +0100, leif wrote:
I think we may want to have something like that (an idea from Michael
yesterday or this morning): http://go-oo.org/discover/
What do you think?
My question is also about exactly what from Go-oo is in LibO too.
My community is asking me about what's the difference between OOo and
LibO - and I find it rather natural to ask that question.
i would agree - we need to, tastefully, chronicle what is different.
For example the bundled extensions comes to mind as something that is, I
believe, a difference between the two distro's on our first release day,
we should certainly list these IMO.
The integration of Go-oo patches, as Leif points out.
Also, from following along in the ML it seems to be that there should be
mention of the large number of, what I'll call paper cut coding cleanup,
contributions to this release cycle. [*smile* best run that line past
the developers, but I think it's accurate.]
I guess bottom line someone needs to start collecting it, it would be
great if instead of an email answer if it was an email with a link to a
wiki page - even if the wiki page is raw data table and we can spiff
that up for marketing purposes, would be my idea anyway.
E-mail to firstname.lastname@example.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/marketing/
All messages you send to this list will be publicly archived and cannot be deleted
- Re: [libreoffice-marketing] Re: Planning release (continued)
Impressum (Legal Info)
: 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