On Monday 23 December 2013 09:18:45 David Faure wrote:
> On Sunday 22 December 2013 15:07:55 Allen Winter wrote:
> > How about if we group all the current frameworks projects into a kdelibs
> > category?
> >
> > Eventually we'd have a category for plasma, kdepim, etc.
> >
> > the git urls wouldn'
On Sunday 22 December 2013 15:07:55 Allen Winter wrote:
> How about if we group all the current frameworks projects into a kdelibs
> category?
>
> Eventually we'd have a category for plasma, kdepim, etc.
>
> the git urls wouldn't change, only the logical grouping would in the
> projects database.
On Thursday, December 05, 2013 08:49:29 PM David Faure wrote:
> We're almost ready to split up kdelibs into a bunch of separate git modules,
> the upcoming "frameworks" in KF5.
>
> One question that came up is where these modules should end up in the
> projects.kde.org hierarchy.
>
> Currently
El Dissabte, 7 de desembre de 2013, a les 17:26:27, David Faure va escriure:
> On Saturday 07 December 2013 16:07:18 Albert Astals Cid wrote:
> > I am not objecting, but can I convince you guys to fix scripty and any
> > other script that will break by that new toplevel category?
>
> Yes we'll hav
On Saturday 07 December 2013 16:07:18 Albert Astals Cid wrote:
> I am not objecting, but can I convince you guys to fix scripty and any other
> script that will break by that new toplevel category?
Yes we'll have to fix translation support after the split, the Messages.sh are
also completely wron
El Dijous, 5 de desembre de 2013, a les 20:49:29, David Faure va escriure:
> We're almost ready to split up kdelibs into a bunch of separate git modules,
> the upcoming "frameworks" in KF5.
>
> One question that came up is where these modules should end up in the
> projects.kde.org hierarchy.
>
>
On Thursday, December 05, 2013 20:49:29 David Faure wrote:
[...]
> E.g. karchive will be in frameworks/karchive, in terms of projects.kde.org
> organization.
>
> Any objections?
>
> Seems clear to me, but Ben wanted to make sure before we proceed
I like that, would like to do the same kind of g
We're almost ready to split up kdelibs into a bunch of separate git modules,
the upcoming "frameworks" in KF5.
One question that came up is where these modules should end up in the
projects.kde.org hierarchy.
Currently we have the following toplevel "components" in kde_projects.xml:
