[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: Splitting kde-workspace and kde-runtime proposal
From: andrea diamantini <adjam7 () gmail ! com>
Date: 2014-01-23 15:08:51
Message-ID: CAH-ukQRrZ4WSrwDqiLyjvQ2sTU7V_xrCdJXUiq=WNGNZ4gx9=Q () mail ! gmail ! com
[Download RAW message or body]
I don't clearly understand why KUriFilter-Plugins should go to plasma-
workspace. I noticed KUriFilter is defined in kio and its plugins are used
e.g. in kparts (browserextension). Shouldn't these go to kio?
2014/1/22 Kevin Ottens <ervin@kde.org>
> On Tuesday 21 January 2014 12:05:26 Antonis Tsiapaliokas wrote:
> > > 1) Create two different groups named plasma-workspace and
> > > plasma-desktop like frameworks
> > > 2) Split out every component into individual repos
> > > 3) Assign repos to the related group.
> > >
> > > Advantages:
> > >
> > > 1) Easy to assign maintainer to individual component.
> > > 2) If we split only some repos, we can not mark it as part of
> > > workspace but this way we can do it.
> > > 3) More, may be?
> > >
> > > That's my humble suggestion. :)
> > >
> > > > Again, this is a proposal so please! send any feedback you might
> have.
> > >
> > > Thanks!
> >
> > I think that splitting each individual component to its own repo might
> be a
> > bit confusing. Because if we don't have two groups (plasma-desktop and
> > plasma- workspace), then we will not be able to provide something as a
> > standard solution. So each person will consider "Plasma Desktop" as
> > something entirely different.
>
> Note however that it's not a proper argument for splitting repos or not
> since
> nowadays our infrastructure has the concept of grouping independently of
> the
> repos. So we could split in their own repo and still have a way to make a
> plasma-desktop and a plasma-workspace group.
>
> OTOH Sebas argument is much more compelling.
>
> Regards.
> --
> Kévin Ottens, http://ervin.ipsquad.net
>
> KDAB - proud supporter of KDE, http://www.kdab.com
>
--
Andrea Diamantini
WEB: http://www.adjam.org
rekonq project
WEB: http://rekonq.kde.org
IRC: rekonq@freenode
[Attachment #3 (text/html)]
<div dir="ltr">I don't clearly understand why KUriFilter-Plugins should go to \
plasma- workspace. I noticed KUriFilter is defined in kio and its plugins are used \
e.g. in kparts (browserextension). Shouldn't these go to kio?</div> <div \
class="gmail_extra"><br><br><div class="gmail_quote">2014/1/22 Kevin Ottens <span \
dir="ltr"><<a href="mailto:ervin@kde.org" \
target="_blank">ervin@kde.org</a>></span><br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div \
class="HOEnZb"><div class="h5">On Tuesday 21 January 2014 12:05:26 Antonis \
Tsiapaliokas wrote:<br> > > 1) Create two different groups named \
plasma-workspace and<br> > > plasma-desktop like frameworks<br>
> > 2) Split out every component into individual repos<br>
> > 3) Assign repos to the related group.<br>
> ><br>
> > Advantages:<br>
> ><br>
> > 1) Easy to assign maintainer to individual component.<br>
> > 2) If we split only some repos, we can not mark it as part of<br>
> > workspace but this way we can do it.<br>
> > 3) More, may be?<br>
> ><br>
> > That's my humble suggestion. :)<br>
> ><br>
> > > Again, this is a proposal so please! send any feedback you might \
have.<br> > ><br>
> > Thanks!<br>
><br>
> I think that splitting each individual component to its own repo might be a<br>
> bit confusing. Because if we don't have two groups (plasma-desktop and<br>
> plasma- workspace), then we will not be able to provide something as a<br>
> standard solution. So each person will consider "Plasma Desktop" \
as<br> > something entirely different.<br>
<br>
</div></div>Note however that it's not a proper argument for splitting repos or \
not since<br> nowadays our infrastructure has the concept of grouping independently \
of the<br> repos. So we could split in their own repo and still have a way to make \
a<br> plasma-desktop and a plasma-workspace group.<br>
<br>
OTOH Sebas argument is much more compelling.<br>
<br>
Regards.<br>
<span class="HOEnZb"><font color="#888888">--<br>
Kévin Ottens, <a href="http://ervin.ipsquad.net" \
target="_blank">http://ervin.ipsquad.net</a><br> <br>
KDAB - proud supporter of KDE, <a href="http://www.kdab.com" \
target="_blank">http://www.kdab.com</a><br> </font></span></blockquote></div><br><br \
clear="all"><div><br></div>-- <br><div dir="ltr"><pre \
style="color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:normal;lette \
r-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);font-size:medium">
Andrea Diamantini
WEB: <a href="http://www.adjam.org" target="_blank">http://www.adjam.org</a>
rekonq project
WEB: <a rel="nofollow" href="http://rekonq.kde.org/" style="color:rgb(0,0,0)" \
target="_blank">http://rekonq.kde.org</a>
IRC: rekonq@freenode</pre></div>
</div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic