[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: Google Online document Plugin for KOffice
From: Pierre Stirnweiss <pstirnweiss () googlemail ! com>
Date: 2010-07-06 7:08:59
Message-ID: AANLkTilU2M64aSmH8oR2wVBd8cVJgZPhe-ipeJDhPaJB () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Just a quick one to say, both are not mutually exclusive. Indeed, I think it
is even possible to have both a kofficeplugins repo for people who want to
develop plugins without the constraints of the official repo, but still want
an easy install, *and* a plugins/staging subdirectory in our repo for people
who prefer to develop inside the official repo (but with all the constraints
attached).
There is indeed a need to set rules as to how/when a plugin goes in/out from
staging.
And here I agree that our community is neither defined nor limitted by the
repo boudary. Pulling peolpe in our community has much more to do with how
we welcome them on our communication channels (IRC, mailing list), how well
and quick we answer their questions, as well as providing visibility to
their work on our website/blogs realms, so they can feel and are recognised
as part of the koffice realm.
Pierre
On Tue, Jul 6, 2010 at 8:55 AM, Thomas Zander <zander@kde.org> wrote:
> On Tuesday 6. July 2010 08.16.30 Boudewijn Rempt wrote:
> > "The reason I bring this up is that we are getting more and more plugins
> > in our main repository that don't actually pass our main criteria for
> > release."
> >
> > I read that as "not good enough for trunk".
>
> What I wrote was "not ready for release", there is a huge difference there
> :)
>
> First, "trunk" is a misnomer, we have a repository of koffice that is
> subjected
> to the release cycle, to freezes and source incompatible changes every now
> and
> then.
> Second; "the koffice community" does not end at the borders of the koffice
> repo.
> There already is the kofficetest one and we have had izi and other branches
> of
> koffice too. we can easily have a kofficeplugins repo.
>
> You will have to accept that there are people that want to start a project
> outside the koffice repository. They may want to follow only a released
> version
> (since otherwise you have to compile all of KOffice) they may want to
> ignore
> things like strings freeze. People may even not be sure they can put any
> time
> into the project to 'finish' it.
> As I said, you will have to accept that people feel that way. And we should
> pull those people into the community and create a kofficeplugins repository
> to
> accommodate them.
>
> Its growing the community by allowing others that don't work exactly like
> you
> to be part too.
>
> --
> Thomas Zander
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
[Attachment #5 (text/html)]
Just a quick one to say, both are not mutually exclusive. Indeed, I think it is even \
possible to have both a kofficeplugins repo for people who want to develop plugins \
without the constraints of the official repo, but still want an easy install, \
<u>and</u> a plugins/staging subdirectory in our repo for people who prefer to \
develop inside the official repo (but with all the constraints attached).<br> There \
is indeed a need to set rules as to how/when a plugin goes in/out from \
staging.<br><br>And here I agree that our community is neither defined nor limitted \
by the repo boudary. Pulling peolpe in our community has much more to do with how we \
welcome them on our communication channels (IRC, mailing list), how well and quick we \
answer their questions, as well as providing visibility to their work on our \
website/blogs realms, so they can feel and are recognised as part of the koffice \
realm.<br> <br>Pierre<br><br><br><br><div class="gmail_quote">On Tue, Jul 6, 2010 at \
8:55 AM, Thomas Zander <span dir="ltr"><<a \
href="mailto:zander@kde.org">zander@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div class="im">On Tuesday 6. July 2010 08.16.30 \
Boudewijn Rempt wrote:<br> > "The reason I bring this up is that we are \
getting more and more plugins<br> > in our main repository that don't \
actually pass our main criteria for<br> > release."<br>
><br>
> I read that as "not good enough for trunk".<br>
<br>
</div>What I wrote was "not ready for release", there is a huge difference \
there :)<br> <br>
First, "trunk" is a misnomer, we have a repository of koffice that is \
subjected<br> to the release cycle, to freezes and source incompatible changes every \
now and<br> then.<br>
Second; "the koffice community" does not end at the borders of the koffice \
repo.<br> There already is the kofficetest one and we have had izi and other branches \
of<br> koffice too. we can easily have a kofficeplugins repo.<br>
<br>
You will have to accept that there are people that want to start a project<br>
outside the koffice repository. They may want to follow only a released version<br>
(since otherwise you have to compile all of KOffice) they may want to ignore<br>
things like strings freeze. People may even not be sure they can put any time<br>
into the project to 'finish' it.<br>
As I said, you will have to accept that people feel that way. And we should<br>
pull those people into the community and create a kofficeplugins repository to<br>
accommodate them.<br>
<br>
Its growing the community by allowing others that don't work exactly like you<br>
to be part too.<br>
<br>
--<br>
<font color="#888888">Thomas Zander<br>
</font><div><div></div><div \
class="h5">_______________________________________________<br> koffice-devel mailing \
list<br> <a href="mailto:koffice-devel@kde.org">koffice-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/koffice-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/koffice-devel</a><br> \
</div></div></blockquote></div><br>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic