Ian Monroe wrote: >* Scripty. Its somewhat of a mystery where it is and how this thing >works. :) So it just needs to clone the central git repo, and perhaps >use a stable branch in the future. It should commit the translation >files back into SVN like it does currently, and make the commits with >.desktop files available somewhere. >*svn externs. We currently have a couple: one is Plasma (which we'll >remove once we depend on KDE 4.3 I think) and the other is a library >written by an Amarok dev that could probably be converted into a git >repo as well. It'd be nice to at least record the history of svn >externs.
SVN externs are not a problem. They just die. Get rid of them right now,
on SVN (they are hurting you now because you're using git-svn). SVN and
Git users will thank you.
>*Other problems that I don't know about.
Other problems that come to mind:
* infra-structure (must convince sysadmins to host and maintain
git.kde.org)
* how to create personal or group repositories. Should we use Gitorious
or GitHub?
* the unresolved issue of accountability
* who will have push rights? To which branches? Who can create branches?
Which branches/repos will allow force-pushes?
* SSH accounts for the Git server
(every single KDE contributor using HTTPS must mail an SSH key)
* the general layout of the server hierarchy (Amarok may be the first,
but we hope it's not the last, so we need some future-proofing)
* should we use supermodule/supermodule? Should we use repo?
* should we use a patch-submission-and-review system? (probably not)
And most importantly:
* who is going to do all this work?
I'm not volunteering.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
