Moving to git.kde.org open

[Niko Sams]

On Wed, Oct 6, 2010 at 10:41, Milian Wolff <mail at milianw.de> wrote:
> On Monday 04 October 2010 15:22:50 Andreas Pakulat wrote:
>> On 04.10.10 14:36:20, Aleix Pol wrote:
>> > On Sun, Oct 3, 2010 at 8:11 PM, Andreas Pakulat <apaku at gmx.de> wrote:
>> > > just FYI: This was posted on the planet:
>> > >
>> > > http://www.omat.nl/2010/10/03/git-kde-org-available/
>> > >
>> > > So moving is open for the kdevelop project now, just needs someone to
>> > > decide the project structure (if there should be changes done) and file
>> > > a request for the moving.
>> > >
>> > > Andreas
>> > >
>> > > --
>> > > Your lucky number has been disconnected.
>> > >
>> > > --
>> > > KDevelop-devel mailing list
>> > > KDevelop-devel at kdevelop.org
>> > > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>> >
>> > I think that we should move there definitely, but I think it would be
>> > better after 4.1 (which is pretty soon anyway).
>>
>> True, but note that in about 4 weeks kde-developers group on gitorious.org
>> will be deleted, so nobody except the kdevelop-devs will be able to push
>> there.
>
> +1 for after 4.1 which should happen before 4 weeks.
>
>> > What kind of project restructuring do you mean?
>>
>> Well, thats something to be disussed. projects.kde.org allows to have
>> arbitrarily nested projects, i.e. we could have kdevelop with quanta as
>> subproject and kdevelop-plugins. Or quanta and kdevelop as top-level
>> projects and each their own xxx-plugins subproject (to host those
>> not-yet-included but useful plugins). Or something totally different (or
>> the same as now)
>
> I'm - as the only current Quanta dev - vote for one big KDev* repo,
you mean KDev* project, right?

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
    ...

Niko