On Tuesday, January 15, 2013 13:37:09 Martin Gräßlin wrote:
> IMHO it should all be in workspace on pko. If we drop out of the SC (and
> given some comments on the threads, that seems to be common agreement) we
> don't need extragear anymore for workspace stuff.
i honestly think this would be the
here are my current thoughts on these questions:
On Monday, January 14, 2013 17:51:50 Aaron J. Seigo wrote:
> * where should the repositories live?
i'd like to see a single Workspaces category on projects.kde.org. the current
kde-workspace repo would be moved to it, and we'd add in all the other
On Monday 14 January 2013 17:51:50 Aaron J. Seigo wrote:
> * where should the repositories live?
> * 1 place, such as a single "workspaces" topic on projects.kde.org
> * scattered: some in kde-workspaces and some in extragear/base (and
> elsewhere)
> * ??
IMHO it should all be in
> * where should the repositories live?
Each project should be in his own repo but in a way that makes compile it easy
(./kdesrc-build kde-workspace, done).
> * what should the devel strategy of these repositories be?
> * what should the release cycle of these repositories be?
Whatever fits best
On Monday, January 14, 2013 20:54:56 Marco Martin wrote:
> On Monday 14 January 2013, Aaron J. Seigo wrote:
> > the question we have is:
> > how do we want to bring these various repositories together
> > into a coherent, usable result?
>
> most of them are projects of quite different, so
On Monday 14 January 2013, Aaron J. Seigo wrote:
> hi..
>
> as Alex noted in an email in the "reflecting on 4.10" thread, we have
> several current and upcoming git repos that are topically part of the
> workspaces. such repositories include:
>
> * bluedevil
> * networkmanagement
> * kscreen (it'
hi..
as Alex noted in an email in the "reflecting on 4.10" thread, we have several
current and upcoming git repos that are topically part of the workspaces. such
repositories include:
* bluedevil
* networkmanagement
* kscreen (it's dependency, libkscreen, is probably a Frameworks topic, not
wo