Moving to git.kde.org open
aleixpol at kde.org
Mon Oct 18 21:27:24 UTC 2010
On Mon, Oct 18, 2010 at 10:56 PM, Milian Wolff <mail at milianw.de> wrote:
> On Wednesday 06 October 2010 10:51:49 Niko Sams wrote:
> > I think we should keep a similar layout as we have now, maybe the plugins
> > better structured as that is now possible afaik:
> > kdevelop "module"
> > kdevplatform
> > kdevelop
> > quanta
> > plugins
> > php
> > php-docs
> > ...
> After a discussion on IRC it was made clear that we don't have a choice but
> switch over to git.kde.org as otherwise the sysadmins would consider us
> KDE" and delete e.g. kdevelop from bugs.kde.org. Anyways, I think we all
> that we are KDE and that we do want to help avoid the fragmentization, so
> agree on the structure. Sho said we'd "certainly" have two weeks of time
> I'd personally be willing to do the setup and talk with the admins
> to get it all done.
> Anyways. back to our structure.
> Two things I needed to learn today:
> - projects can be arbitrarily nested in redmine
> - the git clone urls won't be nested
> So taking into account I propose this structure, with the git url id in
> kdevelop "module"
> kdevplatform (kdevplatform.git)
> kdevelop (kdevelop.git)
> quanta (quanta.git)
> php (kdev-php.git)
> php-docs (kdev-php-docs.git)
> qmake (kdev-qmake.git)
> Sho said that this structure would be possible and I quite like it as it
> everything kdev related in one tree.
> So, any opposition? Better suggestions?
> Milian Wolff
> mail at milianw.de
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
I'm fine with it, it's mostly the same as nikos's anyway, with the
difference of extra's.
Just to note it, using this structure would deprecate playground in favour
of experimental, it's fine with me but it still requires some rule to get
them all there. Also we should consider naming it playground for better
coherence. What are other projects doing with their playground stuff?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel