I ran this by a couple of the engineers here at work. The conclusion we
came to is that all the words that correctly describe the group have be
used already in software terminology. The best suggestions were to use
'accessories' or to make up a new word. A manufactured word will be the
same in
For reasons outlined by Jürgen:
+1 Extensions
For the extensions wiki I used ext.openoffice.org.nz.
I don't think it would be much of an issue to have extension and
extensions.openoffice.org mapping to the same location.
Thanks, Ian
Hi Laurent,
Laurent Godard wrote:
Hi Mathias
My concern about addons is that this term is already used for a very
special though important kind of "extension". But there are other
potential extensions of OOo that e.g. can be deployed as a package and
that are not (technically spoken) addons.
Hi Mathias
My concern about addons is that this term is already used for a very
special though important kind of "extension". But there are other
potential extensions of OOo that e.g. can be deployed as a package and
that are not (technically spoken) addons.
but addons could become a generic
Pavel Janík wrote:
>From: Laurent Godard <[EMAIL PROTECTED]>
>Date: Wed, 26 Oct 2005 16:14:36 +0200
>
> Hi,
>
>> - addon.openoffice.org (already 1 vote)
>
> I'd prefer addons...
My concern about addons is that this term is already used for a very
special though important kind of "ex
From: Laurent Godard <[EMAIL PROTECTED]>
Date: Wed, 26 Oct 2005 16:14:36 +0200
Hi,
> - addon.openoffice.org (already 1 vote)
I'd prefer addons...
--
Pavel Janík
In theory, practice and theory are the same, but in practice they are
different.
-- Larry McVoy
-
Joerg Barfurth wrote:
> Hi,
>
> Laurent Godard wrote:
>
>> - extensions.openoffice.org (already 3 votes)
>
> -1,
>
> We already have a cvs module named 'extensions' in the 'util' project.
>
> This situation (a module in one project is named like another project)
> is prone to cause confusion.
Hi,
Laurent Godard wrote:
- extensions.openoffice.org (already 3 votes)
-1,
We already have a cvs module named 'extensions' in the 'util' project.
This situation (a module in one project is named like another project)
is prone to cause confusion. Unfortunately we already have at least one
