The situation here should be much the same as before. People using scripts like kdesvnbuild will be able to download and update kde as before. The scripts themselves however will need to be modified to address any new organisation.

gitolite

git

projects can keep their interdependencies, module-wide libraries and so on

less server space

split:

moving a project (eg. to unmaintained) moves its whole history

user workflow

modules:

keeps a sense of community by having a whole module kept together

increases passive testing of trunk (more people to notice if the build's broken)

lower barrier to hacking on other projects in the module

easier to refactor a module [rare]

less downloading & disk space for those who want entire modules

split:

less downloading & disk space for people who only want a small part of a module

easier to get started on one little app?

easier to avoid being exposed to unstable versions of other projects [I think that's a bit selfish though]

comments:

kdesrc-build, build-tool and mr make it easy to handle large numbers of repos, although there's still room for improvement on userfriendliness.

releases

modules:

closer to what we have with svn??

split:

Social Workflows

This section tries to put together some personas for the way developers works. We will then try to ensure that the desired workflows are supported as well as can be achieved in the new setup.

the focused developer (e.g. "I work on Kate. Just Kate.")

the fast paced application development team (e.g. "We release a new version of Amarok every 6 weeks.")

hybrid SC-but-also-individual-releases-with-focus-on-specific-targets (e.g. "Marble is part of the KDE Edu module, but also is targetting smart phones in an agressive manner.")

fast paced development driven by external requirements (e.g. "KDE PIM is in practice primarily developed according to the needs and schedules of paying clients.")

tight knit community that co-maintains a set of components/applications (e.g. "All applications in KDE Games are worked on communally by whomever is currently active in the KDE Games team at the time.")

set of components that share local libraries and only make sense when released together (e.g. "kdebase-workspace hosts several local, non-BIC libraries shared between KDM, KWin, Plasma-* shells and contains all the base plugins required for a reasonably functioning KDE Workspace.")

downstream kde packagers

KDE bleeding edge users/testers

The situation here should be much the same as before. People using scripts like kdesvnbuild will be able to download and update kde as before. The scripts themselves however will need to be modified to address any new organisation.