| Line 3: | Line 3: | ||
-> every module in KDE gets a repo, every project in support/extragear gets a repo, koffice gets a repo | -> every module in KDE gets a repo, every project in support/extragear gets a repo, koffice gets a repo | ||
-> write a script to clone, update and build everything, like kde-svn (morice). | -> write a script to clone, update and build everything, like kde-svn (morice). | ||
| − | -> subprojects, like games or edu might choose to have a repo per app, however, they will have to help out then. Otherwise, they get lumped together. Will have to ask the module maintainers (TASK) | + | -> subprojects, like games or edu might choose to have a repo per app, however, they will have to help out then. Otherwise, they get lumped together. Will have to ask the module maintainers (TASK: Chani will do the asking) |
-> if a subproject wants to separate all their apps, someone will have to help them (TASK) | -> if a subproject wants to separate all their apps, someone will have to help them (TASK) | ||
** who proposes to kde-core-devel | ** who proposes to kde-core-devel | ||
KDE TechBase ** compromise?
-> every module in KDE gets a repo, every project in support/extragear gets a repo, koffice gets a repo
-> write a script to clone, update and build everything, like kde-svn (morice).
-> subprojects, like games or edu might choose to have a repo per app, however, they will have to help out then. Otherwise, they get lumped together. Will have to ask the module maintainers (TASK: Chani will do the asking)
-> if a subproject wants to separate all their apps, someone will have to help them (TASK)
** who proposes to kde-core-devel
** who checks with gitorious
** translations ** releasing ** building ** pre/post commit hooks, write & coordinate with gitorious
** for anon users ** for developers
