kdereview/extragear procedure

Albert Astals Cid aacid at kde.org
Mon Apr 3 18:26:42 BST 2006


A Dilluns 03 Abril 2006 11:05, Kevin Krammer va escriure:
> On Monday 03 April 2006 00:51, David Faure wrote:
> > On Sunday 02 April 2006 22:54, Kevin Krammer wrote:
> > > On Tuesday 28 March 2006 20:37, Kevin Krammer wrote:
> > > > Since my understanding is that KDE4 will allow even for other modules
> > > > to be released outside the library schedule, I recommend we come up
> > > > with a procedure for application review, inclusion and possible
> > > > exclusion.
> > >
> > > Summing up the feedback so far:
> > >
> > > - the mail asking for review should be sent to at least kde-core-devel
> >
> > Or "at most"? ;)
> > I'm not sure why we can't discuss app reviews on kde-devel, where we
> > discuss most non-core app code currently.
>
> We can also do it on kde-devel
> This is why I am collecting feedback, there seem to be different
> preferences where to post to
>
> > > - if application is already in SVN, for example in a playground module,
> > > related things like translations have to be moved as well. A procedure
> > > or helper script is needed here as well.
> >
> > The helper script exists already, l10n/scripts/rename_or_move, but it
> > needs a full l10n checkout, which only a few people have. Someone on IRC
> > a few days ago (iirc the katapult author) started to write a script that
> > does a partial checkout using svn ls + svn up -N, but it's probably not
> > stable/generic yet, and I guess it will take longer than rename_or_move
> > for those with a full checkout, and then we have two scripts to
> > maintain....
>
> Ok, in this case maybe the developer shouldn't move the app at all, but
> someone who can also move the l10n stuff?

I try to have a semi recent full l10n checkout so count on me to do the moving 
if needed.

Albert

>
> > > - feedback from the TWG would be nice
> >
> > Well this was some of it :)
>
> Thanks :)
>
> > > additional thoughts:
> > >
> > > instead of a mail to a specific mailinglist, we could have a "product"
> > > for this on bugs.kde.org, with one "component" for each KDE module.
> > > The respective "owner" could be the suitable mailinglist(s)
> >
> > You mean one product like "review"? Assuming we can hide it from users...
> > We wouldn't gain much though; more setup just for archiving, which lists
> > give us too?
>
> It would be some kind of abstraction. The target mailinglist can be
> changed, rewiew request could be queried for, one could subscribe to
> specific review requests, etc
>
> However, I am just brainstorming, we are currently doing fine with
> mailinglists when we know which one to use.
>
> Cheers,
> Kevin

	
	
		
______________________________________________ 
LLama Gratis a cualquier PC del Mundo. 
Llamadas a fijos y móviles desde 1 céntimo por minuto. 
http://es.voice.yahoo.com





More information about the kde-core-devel mailing list