Mailinglist Archive: opensuse-kde (249 mails)

[Karsten König <remur@xxxxxxx>]

Am Freitag, 9. April 2010 16:06:40 schrieb Lubos Lunak:
> On Wednesday 07 of April 2010, Martin Schlander wrote:
> > Onsdag den 7. april 2010 15:51:49 skrev Lubos Lunak:
> > >  So there is a place for second repo, which would be 'what is not in
> > >  o:F'
> > >
> > > and contain stuff that would be worth placing at least there. But
> > > 'Community' is not a good name for that. Additionally, since it is
> > > provided in Yast, I would really expect at least some assurance of
> > > quality there[*]. How does KDE:KDE4:Community actually currently work?
> > > The repo-wide maintainer list is pretty long and I don't know many of
> > > those people, to me it looks like it's some free-for-all repo. Or are
> > > others here really fine with providing such a repo in Yast?
> >
> > I think it's very important to have the repo and offer it via yast - no
> > matter what it's called. It enables us to provide more packages as well
> > as new ones appearing with very little hassle for users - like e.g.
> > Synaptiks[*] which didn't exist in time for 11.2 but fills a gaping hole
> > in the kde package set. Therefore having such a repo in yast is a huge
> > asset to the distro - especially from a casual user point of view.
>
>  I think nobody is arguing against that.
>
> > We just need a bit of guidelines and some packager discipline to make it
> > a little less messy and risky.
>
>  And this is my problem (the lack of this, that is).
>
>  Let me put it differently. There is KDE:Backports, which is newer versions
> of what is in the distribution. We can have one more, let's call it
> KDE:Extra, which would be KDE apps that are not part of the distribution.
> There's no problem with that.
>
>  The problem is that KDE:KDE4:Community currently serves this role, and, as
> far as I understand it, has almost no rules or review (I'm right on this,
> am I not?). I think we should do a bit better for a repository that is
> offered to users directly in Yast.

The intentions were propably meant to be welcoming to new contributions, but 
definitivly spun out of order.

>  So what I propose is that KDE:Extra is created and the workflow is not
> free-for-all. I.e. repo-wide maintainers are not handed out to everybody
> but only to some people with certain trust and experience. And by that I
> don't mean that I myself want to rule the repo with an iron hand, but this
> should simply assure certain review and prevent obvious screwups like the
> recent libqt4 inclusion in KDE:KDE4:Community. Repo-wide maintainers would
> be people willing to take care of the repo as a whole.

Sounds to me like you are pressing for this repo to include it in the yast 
community list for 11.3. Fine by me, but as you pointed out there is more 
moving around to be done, so we should make sure it will fit in the future 
layout.

>  If somebody would want a package there, they would ask on this list, then
> do a submit request resulting in creating the package in the repo. Further
> updates would be by additional SRs or, if trusted enough, they would get
> maintainer only for the package.
>
>  Opinion on this?

I like it, but we want that to be open, so the maintainer list needs to be 
lean, as in one will receive a timely response. Also a further path into 
:Factory should be documented, Pablo makes a good example with his midi 
applications that we might want in the main distribution or the contrib 
repository, though the current state of that initiative is unclear to me.

>  I'm not sure what would be less work, simply keeping KDE:KDE4:Community
> and doing a cleanup in it to make it this repo, or start from scratch and
> copy over things.

Copying over would make it easier to review packages, also for stuff like 
linking to _home which some aren't happy with, of course a proper ruleset 
needs to be set before =)



Karsten

-- 
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx