| (16 intermediate revisions by 5 users not shown) | |||
| Line 2: | Line 2: | ||
** compromise? | ** compromise? | ||
-> every module in KDE gets a repo, every project in support/extragear | -> every module in KDE gets a repo, every project in support/extragear | ||
| − | gets a repo, koffice gets a repo | + | gets a repo, koffice gets a repo. '''This decision is now final and no longer up for discussion''' |
-> write a script to clone, update and build everything, like kde-svn | -> write a script to clone, update and build everything, like kde-svn | ||
| − | (TASK: Morice). | + | (TASK: Morice).= |
-> subprojects, like games or edu might choose to have a repo per app, | -> 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 | however, they will have to help out then. Otherwise, they get lumped | ||
together. Will have to ask the module maintainers (TASK: Chani will do | together. Will have to ask the module maintainers (TASK: Chani will do | ||
| − | the asking) | + | the asking) Resolution: EDU wants to stay together at least.l |
-> if a subproject wants to separate all their apps, someone will have to | -> if a subproject wants to separate all their apps, someone will have to | ||
help them (TASK) | help them (TASK) | ||
| − | ** who proposes to kde-core-devel | + | ** who proposes to kde-core-devel (TASK: Chani) |
** who checks with gitorious | ** who checks with gitorious | ||
* user accounts (gitorous accounts need to have a realname) | * user accounts (gitorous accounts need to have a realname) | ||
| − | ** get opt-in privacy agreement. TASK: eean. (coordinate with johann) | + | ** <strike>get opt-in privacy agreement. TASK: eean. (coordinate with johann)</strike>. Will not be possible: see http://lists.kde.org/?l=kde-scm-interest&m=125812257311133&w=2. |
** we need a simple method for people to say "make me a gitorious account". | ** we need a simple method for people to say "make me a gitorious account". | ||
| − | (wiki page?) This list warns about privacy issues: it is opt-in. | + | (wiki page?) This list warns about privacy issues: it is opt-in. TASK: |
| + | dario. | ||
** other users who have a gitorious account need to ask to be part of | ** other users who have a gitorious account need to ask to be part of | ||
kdedevelopers. | kdedevelopers. | ||
| Line 29: | Line 30: | ||
Finish documentation: TASK for Chani | Finish documentation: TASK for Chani | ||
** releasing | ** releasing | ||
| − | -> ask dirk, cyrille what do they need to create tarballs, | + | -> <strike>ask dirk, cyrille what do they need to create tarballs, |
| − | collect translations, tag multiple repos (TASK: boud, morice) | + | collect translations, tag multiple repos (TASK: boud, morice)</strike>. We asked the question, got no answer, so no help is needed. |
** building (kde-git-build, morice) | ** building (kde-git-build, morice) | ||
** pre/post commit hooks, write & coordinate with gitorious | ** pre/post commit hooks, write & coordinate with gitorious | ||
| Line 55: | Line 56: | ||
* perform tests: dario | * perform tests: dario | ||
* make a short list of people who can send new hooks to gitorious | * make a short list of people who can send new hooks to gitorious | ||
| − | + | -> ACL for creating tags: remains to be discussed: TODO | |
* documentation | * documentation | ||
** for anon users | ** for anon users | ||
** for developers | ** for developers | ||
| + | -> TASK: Chani and Dario | ||
* funding to pay gitorious | * funding to pay gitorious | ||
| + | -> TASK: <strike>ping KDE e.V. board about this (and Thiago). | ||
| + | (boud)</strike> | ||
| + | * note: we have to make sure what we get for the funding. | ||
| + | * service-level-agreement? | ||
| + | * convert svn mirrors to git mirrors: TODO | ||
* go through todo list to check what's open still and who can do that | * go through todo list to check what's open still and who can do that | ||
| + | -> conversion script: morice: ask Thiago for it! | ||
| + | -> externals: poke dfaure (TASK: jpwhiting) | ||
| + | -> email issue: in the next gitorious sprint (TASK: johan-s) | ||
* docs/ folders will need to be sync'd with svn? | * docs/ folders will need to be sync'd with svn? | ||
| + | -> for now, docs/manuals stay in svn. Moving to userbase or git can be done | ||
| + | later, it is not a blocker. Ask for input. | ||
| + | * <strike>get op on #kde-git: task for argonal</strike> | ||
| + | |||
| + | * AOB: | ||
| + | |||
| + | -> Chani: movetogit page has some false info about having individual | ||
| + | developer groups. | ||
| + | -> drf(Dario): | ||
KDE TechBase ** compromise?
-> every module in KDE gets a repo, every project in support/extragear
gets a repo, koffice gets a repo. This decision is now final and no longer up for discussion
-> write a script to clone, update and build everything, like kde-svn
(TASK: 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) Resolution: EDU wants to stay together at least.l
-> if a subproject wants to separate all their apps, someone will have to
help them (TASK)
** who proposes to kde-core-devel (TASK: Chani)
** who checks with gitorious
**get opt-in privacy agreement. TASK: eean. (coordinate with johann). Will not be possible: see http://lists.kde.org/?l=kde-scm-interest&m=125812257311133&w=2. ** we need a simple method for people to say "make me a gitorious account". (wiki page?) This list warns about privacy issues: it is opt-in. TASK: dario. ** other users who have a gitorious account need to ask to be part of kdedevelopers. ** we need a way to ensure everyone in thekde-developers group is on kde-cvs-announce@kde.org. (TASK: ask johann) ** we need to send an announcement to kde-cvs-announce@kde.org telling everyone how to request an account (and privacy info) (TASK: boud) ** our sysadmins need to have admin access to gitorious.
** translations
-> mostly good to go, could do with polish and documentation.
Finish documentation: TASK for Chani
** releasing
-> ask dirk, cyrille what do they need to create tarballs,
collect translations, tag multiple repos (TASK: boud, morice). We asked the question, got no answer, so no help is needed.
** building (kde-git-build, morice)
** pre/post commit hooks, write & coordinate with gitorious
*** post:
-> figure out which hooks we have right now (from
http://websvn.kde.org/trunk/kde-common/svn/hooks/)
* CIA
* BUG
* CCMAIL
* LICENSE
* EBN (Dario Freddi)
* etc.
-> check whether the list complete (boud, morice)
-> coordinate with harald sitter on writing them (morice)
-> get them to work with gitorious for all kde modules, they will run
on a kde server (morice, johan, dario)
*** pre:
-> ACL: only needed for web, top-level modules and konq certificates
* look into konq certificates (TASK: Mek, talk to sysadmin)
-> ask sysadmin what else pre-commit hooks are needed for (???)
* generated files?
* upload a complete list of what it checks: TASK for argonel
* figure out a way to call them from our site plugin: johan-s
* perform tests: dario
* make a short list of people who can send new hooks to gitorious
-> ACL for creating tags: remains to be discussed: TODO
** for anon users
** for developers
-> TASK: Chani and Dario
-> TASK:ping KDE e.V. board about this (and Thiago). (boud)* note: we have to make sure what we get for the funding. * service-level-agreement?
-> conversion script: morice: ask Thiago for it! -> externals: poke dfaure (TASK: jpwhiting) -> email issue: in the next gitorious sprint (TASK: johan-s)
-> for now, docs/manuals stay in svn. Moving to userbase or git can be done
later, it is not a blocker. Ask for input.
-> Chani: movetogit page has some false info about having individual
developer groups.
-> drf(Dario):
