Re: Splitting kde-workspace and kde-runtime proposal
On Tue, Jan 28, 2014 at 6:34 PM, Aleix Pol aleix...@kde.org wrote: On Mon, Jan 27, 2014 at 3:21 PM, David Edmundson da...@davidedmundson.co.uk wrote: There is an existing page about slitting runtime here: http://community.kde.org/Frameworks/Epics/New_Runtime_Organization linked to from http://community.kde.org/Frameworks/Epics Alex's wiki page looks far more populated. We should make sure we avoid wiki duplication. David ___ Plasma-devel mailing list plasma-de...@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel I merged all the notes about kde-runtime from last Plasma sprint into the old page: http://community.kde.org/Frameworks/Epics/New_Runtime_Organization I'd suggest to remove the notes from the sprint and keep the old one as the official one to keep track of the state. Aleix Since nobody said anything, I decided to remove the new one, removing the duplication. I'll start working on that splitting this week, hopefully. Aleix ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
On Monday 27 January 2014 15:21:05 David Edmundson wrote: There is an existing page about slitting runtime here: http://community.kde.org/Frameworks/Epics/New_Runtime_Organization linked to from http://community.kde.org/Frameworks/Epics Alex's wiki page looks far more populated. We should make sure we avoid wiki duplication. Yeah, Alex, can you look into merging the two tables? Then I'll go through and fill in info about the stuff I know about. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
On Thursday 23 January 2014 16:08:51 andrea diamantini wrote: 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? Agreed. They are needed for kio-based webbrowsers in any workspace. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
There is an existing page about slitting runtime here: http://community.kde.org/Frameworks/Epics/New_Runtime_Organization linked to from http://community.kde.org/Frameworks/Epics Alex's wiki page looks far more populated. We should make sure we avoid wiki duplication. David ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
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 er...@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 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
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 signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
Hello! On Tue, Jan 21, 2014 at 3:35 PM, Antonis Tsiapaliokas kok...@gmail.com wrote: 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. Yes having group is essential, otherwise it will create confusion.. repo like kde:kf5umbrella will be also needed. Thanks! -- Bhushan Shah http://bhush9.github.io IRC Nick : bshah on Freenode ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
On Tuesday, January 21, 2014 11:03:57 Bhushan Shah wrote: On Tue, Jan 21, 2014 at 1:19 AM, Àlex Fiestas afies...@kde.org wrote: In the plasma sprint we have done a session to plan what we are going to do with kde-workspace/kde-runtime repositories, here is the proposal we came with. We are going to create 2 new repos called plasma-desktop and plasma-workspace, we decided to use plasma as a prefix so in the future we can have more workspaces and desktops without being in the awkward situation of having one wrongly labeled as KDE while others are not (thinking on for example having Razorqt/lxde as part of KDE in the future). Current kde-workspace and kde- runtime will be kept for history reasons. I want to suggest something different, 1) Create two different groups named plasma-workspace and plasma-desktop like frameworks How is this granularity useful? To me, it sounds like way too much, too hard to move code around within the same domain, for example. We don't want to flood people with hundreds of repositories. The generic workspace vs. specific formfactor split is well in line with how we see people deploying Plasma, you install the framework, the generic workspace, and then a package for a specific formfactor. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Splitting kde-workspace and kde-runtime proposal
Hello! On Tue, Jan 21, 2014 at 1:19 AM, Àlex Fiestas afies...@kde.org wrote: In the plasma sprint we have done a session to plan what we are going to do with kde-workspace/kde-runtime repositories, here is the proposal we came with. We are going to create 2 new repos called plasma-desktop and plasma-workspace, we decided to use plasma as a prefix so in the future we can have more workspaces and desktops without being in the awkward situation of having one wrongly labeled as KDE while others are not (thinking on for example having Razorqt/lxde as part of KDE in the future). Current kde-workspace and kde- runtime will be kept for history reasons. I want to suggest something different, 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! -- Bhushan Shah http://bhush9.github.io IRC Nick : bshah on Freenode ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
