Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On Fri, 2011-11-11 at 08:10 -0500, drew wrote:
On Fri, 2011-11-11 at 11:24 +0100, Jean-Baptiste Faure wrote: 
Le 11/11/2011 11:06, Cor Nouws a écrit :
Hi Andrea,

Someone else explained that a good technical solution, also with a
different look, is no real option. You must have noticed that post.

Really ?
Please have a look at :

Best regards.
So, no argument here that DNS based themes are baked into the platforms

Good day all,

No argument here that DNS based themes are baked into the platforms.

The shared content however - I submit it is not so easy to see how this
easily and successfully works out.

For instance - let's say that a user has come looking for help and as it
turns out the problem the user is having turns out to be in fact a
defect with the this point I would hope that the
individual(s) helping this person out would offer to this user a quick
pointer on how to enter this into our defect tracking system - just some

So - I'm assuming that when user A (let's call her Sarah) came into the
forum it was via our libreoffice address. She found a nice LibreOffice
branded site - [quick question - we would have some type of pinned
information about such things on the forum, and of course this content
would need to change along with our them..yes]

Now user B (let's call her Barb) is a long time user and
quite happy Apache OpenOffice user, so naturally she came in using the
AOO [u.s.oo.o] address - which again, naturally, displays a nice blue
theme and a sticky post about reporting bugs...

See where I'm going here? 

*well* now that I've refilled the coffee cup it seems such an easy thing
to overcome doesn't it - simply have a section (sub_board) for
information on how to interface with each of the different projects -
with separate sticky for each, perhaps.

let's see - links to the documentation in easy reach, again it doesn't
seem so much overhead to handle this.

Then it would be a big help if the two applications AOO and LibO do not
diverge in form or function.

To date it has been pretty good that way, of course the fact that OO.o
hasn't had a release is one of _the_ overarching factors here, IMO 
- and everything I see at the AOO project says that this will certainly
not be the case for long.

Along with that I look forward a TDF launch of an iOS and Android
version and HTML5.canvas (?) on-line version, or other engineering
driven changes such efforts may produce. I also want and expect AOO to
have a series of releases that will have to be different in some ways
from the current OO.o application..and whatever new projects the AOO
project spawns.

Then sure, one gets down to branding, community identity and self
sufficiency questions and I suppose these issues add up to politics of a
kind. IMO good people can in good conscience come to differing
conclusions and take separate paths politely, is this not one definition
of politics. IMO the reality which came out of this last year, the
change from a project, in fact, owned by a single for profit vendor
morphing into two projects, to code lines in fact, each owned by a
non-profit foundations actively moving forward is not a bad outcome, for

So bottom line for myself - could using two URL's pointing to the same
physical server work? - likely for a while _but_ that it will become
increasing more difficult, quickly, versus having each community take
responsibility for it's own user services, across the board. 

Anyway - my long .02 worth

Best wishes,


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.