RFC: remove qt-copy

Gary Greene greeneg at tolharadys.net
Mon May 25 22:07:37 BST 2009


On Monday 25 May 2009 01:54:53 pm Aaron J. Seigo wrote:
> hi all ...
>
> since it's finally come up on the kde-commit list, i'd like to make a
> "formal" proposal regarding qt-copy, namely:
>
> Proposal
> -------------
> * Use http://qt.gitorious.org/+kde-developers/qt/kde-qt instead of qt-copy
> * Remove qt-copy from our svn repository after a post-announcement grace
> period (so that we don't pull the rug out from under people)
>
> Details and Benefits
> ----------------------------
> Any KDE developer can be added to the kde-developers team and thereby have
> commit access, just as we do now.
>
> Keeping kde-qt up to date with Qt upstream can be done via gitorious, which
> should make it easier for us.
>
> It fits directly into the Qt Software development team's daily workflow
> meaning that the odds of our patches getting upstreamed increases.
>
> It removes a bit more burden on our svn server and we can probably stop
> with things like the apply-patches stuff. Less overhead and time == good,
> and people won't have to know about apply-patches to make it all work.
>
>
> Downsides
> ----------------
> It means using git, not something everyone is comfortable with. This is
> nearly a moot point, however, as that move seems inevitable; while there
> isn't unanimity on the topic (and I doubt that's realistically achievable;
> it's a little like whitespace conventions ;) there as an apparent general
> consensus on the matter.
>
> It means checking out and building Qt again.
>
>
> Implementation
> ---------------------
> Someone will need to make sure that all of our patches are already in
> kde-qt if they aren't already.
>
> Someone will need to update any articles on Techbase that refer to qt-copy
> and provide a step-by-step on how to use kde-qt. This might be a nice
> exercise in starting to put together a "Using KDE's git repositories"
> information we'll need in the future anyways (assuming that the KDE git
> transition does actually occur)
>
> Someone will need to provide a formal announcement so everyone has a heads
> up along with pointers to the above instructions.
>
> Someone will need to actually remove qt-copy from svn after the grace
> period following the announcement (1 week? 2? 3?).
>
>
> Thoughts? Opinions?

While personally, I dislike distributed SCMs, I do see this as the best move 
since having a more "upstream" home for the core library we depend on is a 
good thing, and lowers the work load of packagers and developers both.

-- 
Gary L. Greene, Jr.
Sent from: peorth.tolharadys.net
 14:05:20 up 21 days,  6:31,  4 users,  load average: 0.58, 0.56, 0.51
==========================================================================
Developer and Project Lead for the AltimatOS open source project
Volunteer Developer for the KDE open source project
See http://www.altimatos.com/ and http://www.kde.org/ for more information
==========================================================================

Please avoid sending me Word or PowerPoint attachments.




More information about the kde-core-devel mailing list