[Twisted-Python] GitHub Twisted organization/repo
Hi, Are there any plans with the Twisted repo from GitHub? https://github.com/twisted/twisted Looks like it was not updated in a while. Garret Heaton is already doing a 15min mirroring of master/trunk https://github.com/powdahound/twisted Both repos have a couple of forks and it would be nice if all forks are from the same repo. I prefer and use GitHub code browsing since it is much faster than Twisted's official Trac code browsing. --------------- I now see that Tom Prince has already created git branches on GitHub for the ticket he is reviewing. Many thanks! I have already started creating git branches on GitHub for all my patched for Twisted. I found it much pleasant to send a "live patch" URL rather than a static attached diff file. Ex live diff: https://github.com/chevah/twisted/compare/chevah:master...chevah:5411-ftp-li... Append .diff to the url and you have a patch file: https://github.com/chevah/twisted/compare/chevah:master...chevah:5411-ftp-li... As a non-commiter for SVN this makes my life much more easier. Manually creating diff and attaching them to a slow Trac can cause a bit of frustration... but I always find to hard to follow a SVN branch that was created for at ticket and manually apply diffs on local copies. I find it very hard to work in parallel on more than 4 tickets and tracking diffs outside of SVN/GIT is not fun. I understand that moving from SVN to GIT is not easy and if core developers can create and share SVN branches there is no big inconvenience. For me, as a non-commiter, contributing to Twisted is not fun. Sorry for bothering you with my frustrations. I hope that you find the feedback useful, otherwise feel free to ignore it :) -- Adi Roiban
Adi Roiban <adi@roiban.ro> writes:
I now see that Tom Prince has already created git branches on GitHub for the ticket he is reviewing. Many thanks!
My repo is actually currently updated via a post-commit hook. Eventually, that will change to point at twisted/twisted on github, but I want to run it for a bit against an unofficial repo first.
One reason this is frowned on, is that the code then only exists in an external resource that may disappear or change without notice. That means that the work can be lost. There have been a number of code hosting sites that have disappeared, and that would take any contributions hosted only there with them. https://twistedmatrix.com/trac/report/16 has a bunch of old tickets that mostly with some code, that would potentially been lost.
I don't know if there is a desire to move to git. In any case, before any such migration can occur. Namely, updating all the hooks and tools to work with whatever vcs is being switched to. My impression is that, at least at one point, bzr was a more likely choice of distributed vcs to switch to. Tom
On 26 March 2013 18:11, Tom Prince <tom.prince@ualberta.net> wrote:
I understand this and I am not requesting to move the code to GitHub. I don't think that this is a god idea. I was only asking about GitHub mirrors. The main request for this thread was to have a single source repo mirror for Twisted in GitHub. Now there are at least 2. Now there are also 2 unrelated branches in GitHub for the same twisted, my original branch and Tom's mirror.
I am not requesting to move to Git. I was just expressing my frustration that attaching patch files to Trac is not fun, and working with read-only SVN is not fun, and following out-of-line review comments is not fun. -- Adi Roiban
On Mar 26, 2013, at 10:07 AM, Adi Roiban <adi@roiban.ro> wrote:
Demonstrably, all of these things are more fun than volunteering to maintain a functioning git mirror, since people do these things all the time, but do not do that ;). We'd love to have a single source github mirror. Can you provide assistance getting it set up, monitored and maintained? Thanks, -glyph
On 26 March 2013 21:48, Glyph <glyph@twistedmatrix.com> wrote:
Thanks Glyph, I am happy to help with that. I just wanted to know that there is interest in a single mirror and I will work from that. I will check with Garret Heaton and maybe with Tom Prince (if he is not too busy). -- Adi Roiban
Here's the simple script I'm running to sync the repo over to github.com/powdahound/twisted: https://gist.github.com/powdahound/5250837 Happy to transfer ownership of the repo to someone else if that ends up being helpful. Don't believe I have much to add in terms of repo-syncing knowledge, management, or monitoring. I'm honestly surprised this simple cron has been working as well as it has for so long. :)
Adi Roiban <adi@roiban.ro> writes:
I now see that Tom Prince has already created git branches on GitHub for the ticket he is reviewing. Many thanks!
My repo is actually currently updated via a post-commit hook. Eventually, that will change to point at twisted/twisted on github, but I want to run it for a bit against an unofficial repo first.
One reason this is frowned on, is that the code then only exists in an external resource that may disappear or change without notice. That means that the work can be lost. There have been a number of code hosting sites that have disappeared, and that would take any contributions hosted only there with them. https://twistedmatrix.com/trac/report/16 has a bunch of old tickets that mostly with some code, that would potentially been lost.
I don't know if there is a desire to move to git. In any case, before any such migration can occur. Namely, updating all the hooks and tools to work with whatever vcs is being switched to. My impression is that, at least at one point, bzr was a more likely choice of distributed vcs to switch to. Tom
On 26 March 2013 18:11, Tom Prince <tom.prince@ualberta.net> wrote:
I understand this and I am not requesting to move the code to GitHub. I don't think that this is a god idea. I was only asking about GitHub mirrors. The main request for this thread was to have a single source repo mirror for Twisted in GitHub. Now there are at least 2. Now there are also 2 unrelated branches in GitHub for the same twisted, my original branch and Tom's mirror.
I am not requesting to move to Git. I was just expressing my frustration that attaching patch files to Trac is not fun, and working with read-only SVN is not fun, and following out-of-line review comments is not fun. -- Adi Roiban
On Mar 26, 2013, at 10:07 AM, Adi Roiban <adi@roiban.ro> wrote:
Demonstrably, all of these things are more fun than volunteering to maintain a functioning git mirror, since people do these things all the time, but do not do that ;). We'd love to have a single source github mirror. Can you provide assistance getting it set up, monitored and maintained? Thanks, -glyph
On 26 March 2013 21:48, Glyph <glyph@twistedmatrix.com> wrote:
Thanks Glyph, I am happy to help with that. I just wanted to know that there is interest in a single mirror and I will work from that. I will check with Garret Heaton and maybe with Tom Prince (if he is not too busy). -- Adi Roiban
Here's the simple script I'm running to sync the repo over to github.com/powdahound/twisted: https://gist.github.com/powdahound/5250837 Happy to transfer ownership of the repo to someone else if that ends up being helpful. Don't believe I have much to add in terms of repo-syncing knowledge, management, or monitoring. I'm honestly surprised this simple cron has been working as well as it has for so long. :)
participants (4)
-
Adi Roiban -
Garret Heaton -
Glyph -
Tom Prince