> > > -you won't be part of commit-filter, you won't be able to use BUG: or > > CCMAIL: or any of those hooks until they're done. > > This is a bummer, but we knew that going in, yes. > > BTW, something I forgot to mention: Eli 'argonel' > MacKenzie whom you might know from #kde-git and who > has been present at the last few meetings about the > git transition is a core developer at Konversation, > so we've been trying to involve ourselves in the > transition work already. > > I've also done things like work a tiny bit on the > CIA post-commit hook for SVN in the past, so I might > be able to make myself useful on these kinds of > things somehow.
yay :) > > > -if you've got a docbook folder, remember to separate it out and leave it > > somewhere in svn for the translators. > > Our handbook is in extragear/network/docs right now; I > had figured we'd leave it there, and whenever we announce > a string and documention freeze on kde-i18n-doc we mention > where the docs are. Sound good? Albert? ah, so you're in the same boat as amarok there. mmkay. > > > there are also social consequences - I think it'll create more pressure > > to move to git before it's ready, and there'll be less pressure to > > actually resolve that todolist. it also feels less "KDE" right now - we > > don't have a kde page on gitorious or anything... or am I putting the > > cart before the horse on that one? :) > > Yes, the social consequences are perhaps the most worry- > ing. > > However, my take on this is this: Konversation is one of > the oldest and most stable KDE Extragear projects around. > Konversation has been around for 6 1/2 years now, and our > mission has always been to be a KDE app and a champion > for the KDE platform first and foremost. Having more > "good old KDE stuff" on Gitorious can perhaps help in ma- > king sure we successfully import our culture there. I > would hate to see this as cutting any ties with KDE, I > see it more as extending KDE to a new place. Our spiri- > tual home will always be KDE, not Gitorious ;-). :) good to hear. perhaps that approach *can* work... > > > so... if you think the move is worth it in spite of that, I won't try to > > stop you. however, I really think it would be better for all of us if you > > put pressure on (or volunteered to help with) fixing the technical issues > > *first*. > > > > > > all I ask is that you consider all the consequences before making a > > decision. > > Well, it's definitely not like "we need to be on Gito- > rious by Monday!" We have a strong interest in not drag- > ging things out until the end of time, but we also don't > want to jump in over-hurriedly. This why I opened this > thread on the tagging problem: We started to look into > the consequences of moving now, and that was one of the > problems we identified and that we wanted to talk about > first. ahh. well, fwiw I plan to take a stab at organizing documentation again on december 16th. as for tagging... iirc it's a matter of balancing the need to do the occasional force-push vs. not wanting accidental forces to mess things up (er, *can* you force push by accident?). I think having force ability was compared to running as root. I don't think we want everyone with commit access (people who've only committed a few things, people who are no longer around) to have that level of access freely, but I hope we can minimize the effort required to get it when needed. btw, are you setting reply-to or something? twice I almost emailed you instead of the list? :) -- This message brought to you by eevil bananas and the number 3. www.chani3.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
