[Kde-scm-interest] Project layout on gitorious

[Ian Monroe]

2010/3/28 Cornelius Schumacher <schumacher at kde.org>:
> On Sunday 28 March 2010 Thomas Zander wrote:
>>
>> $ git clone git://gitorious.org/svn2git/kde-ruleset.git
>> $ grep 'create repository' kde-ruleset/*
>>
>> Each of those lines will be its own project with one or more repositories.
>
> Attached is the slighthly edited output of this commands. In this form it
> doesn't really make sense. This would be an insane number of projects,
> especially for extragear I doubt that every single application needs its own
> project.
>
> If we take the directory as project and the name as repo it makes more sense,
> but there are still quite some inconsistencies:
>
> * Kate and KDevelop have plugins as top-level project names. I guess they
> should be repos in the respective main projects.
> * Extragear would be a huge project. This might make sense, but maybe it also
> would be desirable to group them by topic.
> * The current main SVN modules which represent what we officially release
> would be in the KDE project, each module one repo. This sounds good, but the
> all uppercase spelling of "KDE" is inconsistent with the spelling of the other
> projects.
> * kdesupport could also be split up in a number of projects. This might better
> reflect who is working on it and how.
>
> With the separate definition of what makes up KDE, which was suggested by Ian
> in the other mail, it wouldn't really matter how projects are laid out, but an
> inconsistent structure would still confuse people, as this is the organization
> which is reflected in the gitorious web interface, so I think it's worth to
> get this right.

As far as I know, the 'layout' on Gitorious will be entirely flat. So
I don't really understand what you're talking about.

Ian