Difference between revisions of "Projects/MovetoGit/Meeting1111"

Revision as of 20:13, 11 November 2009

• project layout

 ** 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 
          (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)
       -> 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

• user accounts (gitorous accounts need to have a realname)

 ** get opt-in privacy agreement. TASK: eean. (coordinate with johann)
 ** 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.
 ** 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.

• scripts for

 ** translations
 ** releasing
 ** building
 ** pre/post commit hooks, write & coordinate with gitorious

• documentation

 ** for anon users
 ** for developers

• funding to pay gitorious
• go through todo list to check what's open still and who can do that
• docs/ folders will need to be sync'd with svn?