[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Google Online document Plugin for KOffice
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2010-07-06 6:16:30
Message-ID: 201007060816.30392.boud () valdyas ! org
[Download RAW message or body]

On Monday 05 July 2010, Thomas Zander wrote:
> On Monday 5. July 2010 09.51.59 Boudewijn Rempt wrote:
> > > I respectfully disagree that putting up a dedicated area for
> > > not-yet-ready plugins is splitting the community. Its doing the
> > > opposite, its pulling in the already split community back into one.
> > 
> > I don't see how telling people to go away to a playpen because their code
> > ise  not good enough is pulling people together.
> 
> I suggest then to not go for a "playpen" and not calling code "not good
> enough". I fully agree that would be really denigrating and not very
> useful. So lets not do that.  Luckly, if you read my mail, thats not what
> was suggested. :-)

"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". Which is silly, since most of 
KOffice is not release-ready. Not that we ever really defined release-ready -- 
there's the "saving" criterum, but that doesn't seem a hard criterium for 
committing to trunk, since code has been committed, and not just by people 
paid by Nokia, that doesn't save either.

Anyway, let's go with Inge's suggestion, at least until we move to git:

New plugins go to

koffice/plugins/staging

But make it part of the default build, and then let's all of us agree upon 
some process to move things from plugins to staging.

-- 
Boudewijn Rempt | http://www.valdyas.org

_______________________________________________
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]