Hi, my vast array of spybot detected I was needed in this discussion (joking, I am just member of the list). So yes, I was previously interested in switching to git. I have several branches myself already using git, but it is not a migration, nothing like one.<br>
<br>So point by point (read previous email):<br>#1:<br>Umbrello can still be part of KDESDK and be in a separate repository, just like Kate. Git does not really handle subprojects in repositories, so it is the only way to go. I don't think we can keep sharing the same repositories as KDESDK. No other KDE project did when migrating.<br>
<br>#2:<br>Yes, it need to be done<br><br>#3:<br>I think we need to move it. We can ask on #kde-sysadmin for a better opinion,<br><br>#4:<br>All of them, but keep the log of master while integrating the other one as a single block of the git and make them ready for a "git merge master" (when possible/applicable). Like that it would be possible to start cherry-picking commits or merging different branches. I think using trunk as the master is the best idea to keep the best possible commit log.<br>
<br>#5-6:<br>Guys on #kde-sysadmin probably know better they did a lot of project migration.<br><br>#7:<br>I have started a migration some months ago, but gave up after having some problems. I code on many projects, but not at once, so until I come back to Umbrello, I can't put much time on this. I work almost full time as a IT consultant and got full time at school at once, so I have limited time, I can only work on one project at once. Right now I have pressure from my users to work on something else, so until it is done Umbrello will have to wait. I still think my code is useful for the project and deserve to be merged for what it add. But not right now and not for the next ~2 month.<br>
<br>#8:<br>We should use KDE identity service and let anybody with a KDE account work on the project. It is what is so great about KDE, we are one community, not a bunch of loosely related ones. I don't see any reasons why this should change. As for repo maintainer, it can be decided later. SVN never really required one. While having a "master integrator" in git is useful, it is not mandatory.<br>
<br>#9:<br>Yes, but not at this time. Everything else can wait until the transition is done. We need to see the branching model we will use (one branch per bug/feature or 1 branch per dev (personal playground model)?)<br>
<br><div class="gmail_quote">On 17 January 2012 18:03, Ralf Habacker <span dir="ltr"><<a href="mailto:ralf.habacker@googlemail.com">ralf.habacker@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Am 13.01.2012 00:11, schrieb Andi Fischer:<br>
> Am 12.01.2012 23:34, schrieb Ralf Habacker:<br>
>> Are there any plans to migrate to git for easier branch and merge<br>
>> management ?<br>
>><br>
>> Regards<br>
>> Ralf<br>
> Not yet. That would be very cool.<br>
><br>
> To do that the following has to be done: (see also<br>
> <a href="http://techbase.kde.org/Projects/MovetoGit" target="_blank">http://techbase.kde.org/Projects/MovetoGit</a>)<br>
> - write some importing rules<br>
> - buy a big hard drive<br>
Here are a few notes and questions:<br>
<br>
1. umbrello is currently a part of the kdesdk package. Should this be<br>
the prefered way in he future or should umbrello goes into a separate<br>
git repository?<br>
2. a separate repo means to convert umbrello to a standalone cmake package.<br>
3. umbrello doc is not a part of the recent umbrello subdir - how to<br>
proceed ? let it still be in kdesdk or move to umbrello source ?<br>
4. umbrello uses several branches - which one need to be migrated and<br>
which one could be dropped ?<br>
5. The main documentation for a migration into a kde git repository<br>
could be found on <a href="http://techbase.kde.org/Projects/MoveToGit/StepsToMove" target="_blank">http://techbase.kde.org/Projects/MoveToGit/StepsToMove</a><br>
- there is a detailed plan<br>
6 In this doc there is no hint about how to migrate the translation<br>
service<br>
7. Who will do the migration - Jonathan mentioned that Emmanueel Lepage<br>
Vallee (Elv13) who pops up on IRC occationally has been interested in<br>
doing this in the past, he needs to be contacted<br>
8. Who should have write access to this repo - who should be the<br>
maintainer of the repository ?<br>
9. Are there any missing topics ?<br>
<br>
Regards<br>
Ralf<br>
<br>
<br>
------------------------------------------------------------------------------<br>
Keep Your Developer Skills Current with LearnDevNow!<br>
The most comprehensive online learning library for Microsoft developers<br>
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,<br>
Metro Style Apps, more. Free future releases when you subscribe now!<br>
<a href="http://p.sf.net/sfu/learndevnow-d2d" target="_blank">http://p.sf.net/sfu/learndevnow-d2d</a><br>
_______________________________________________<br>
Uml-devel mailing list<br>
<a href="mailto:umbrello-devel@kde.org">Uml-devel@lists.sourceforge.net</a><br>
<a href="https://mail.kde.org/mailman/listinfo/umbrello-devel" target="_blank">https://mail.kde.org/mailman/listinfo/umbrello-devel</a><br>
</blockquote></div><br>