Re: Splitting kde-workspace and kde-runtime proposal

2014-01-27 Thread David Edmundson
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

Re: Splitting kde-workspace and kde-runtime proposal

2014-01-23 Thread andrea diamantini
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

Re: Splitting kde-workspace and kde-runtime proposal

2014-01-22 Thread David Hubner
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

Re: Re: Splitting kde-workspace and kde-runtime proposal

2014-01-22 Thread Martin Gräßlin
On Tuesday 21 January 2014 13:12:58 David Hubner 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

Re: Splitting kde-workspace and kde-runtime proposal

2014-01-21 Thread Sebastian Kügler
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.

Re: Splitting kde-workspace and kde-runtime proposal

2014-01-21 Thread Antonis Tsiapaliokas
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

Re: Splitting kde-workspace and kde-runtime proposal

2014-01-21 Thread Bhushan Shah
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

Re: Splitting kde-workspace and kde-runtime proposal

2014-01-21 Thread Bhushan Shah
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

Re: Splitting kde-workspace and kde-runtime proposal

2014-01-21 Thread Marco Martin
On Tuesday 21 January 2014 13:04:22 Sebastian Kügler wrote: 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

Splitting kde-workspace and kde-runtime proposal

2014-01-20 Thread Àlex Fiestas
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