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


Hi Norbert,

Quoting Norbert Thiebaud <nthiebaud@gmail.com>:

On Thu, Oct 4, 2012 at 7:37 AM,  <d.ostrovsky@idaia.de> wrote:
Hi,

Quoting David Tardon <dtardon@redhat.com>:

It would be the committer's responsibility to build the extension and
continue maintaining the code (if there is anything to maintain there
:-) I suppose that unfortunate maintainer is going to be me, unless we
decide to put the code in a repo under libreoffice on fd.o; then
everyone of us would have access to it (but see the pros and cons in my
original email). Of course I welcome volunteers :-)

Why not use an gerrit project for it?

david, you missed the original email from david tardon, specifically that part:
"
1. a repo on fd.o under libreoffice
[...]
CONS:
* it is somehow tied with libreoffice, so people might expect us to put
  the extension into the install sets (which is what I wanted to avoid in
  the first place :-)
"
No, i didn't miss it. The (read only) repository is located on guthub, or gitosis or ... While it is replicated from gerrit.libreoffice.org there, this and other extensions hosted there are *not* bundled into LO's installation
set per definition (it is documented, underlined, bold and blinking
for that matter).

Of course I welcome volunteers :-)
Another advantage if it is hosted on gerrit: i am going to contribute to it ;-)

Regards
David

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.