<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 1, 2011, at 2:06 PM, Tom Davis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF"><div>On Jul 1, 2011, at 1:41 PM, Glyph Lefkowitz <<a href="mailto:glyph@twistedmatrix.com">glyph@twistedmatrix.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><br><div><div>On Jul 1, 2011, at 1:08 PM, chris wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">doing continuous development based on tools like<span class="Apple-converted-space"> </span><br>svn and trac is really painful and it's really difficult to motivate<span class="Apple-converted-space"> </span><br>yourself to work on a once rejected ticket</span></span></blockquote></div><br><div>Can you be more specific, please? What's painful?</div></div></blockquote><div><br></div><div>I always found it especially irritating to come back to a patch later. If I don't already have a patched checkout of Twisted, I need to figure out what revision I was at before (or to actually be safe, make a HEAD checkout), then reapply my patch, hoping it is still valid. </div><div><br></div><div>With a fork I can check it out any time, rebase to the current master (or branch I'm working on), having my changes reapplied for me. When I have made more changes I just push it up. No changes to tickets or switching keywords or watching Trac reject my patch file 10 times then clearing all my cookies or whatever.</div></div></blockquote><div><br></div><div>Wow, does that actually happen? The rejecting the patchfile, I mean. That's terrible.</div><div><br></div><div>In any case, that should not be important. You _should_ be able to use the DVCS of your choice to work on Twisted.[1] As I said in the previous message:</div><div><br></div><div><blockquote type="cite"><div bgcolor="#FFFFFF"><blockquote type="cite"><div><div>Plus, you can use the DVCS of your choice to actually author the patch.</div></div></blockquote></div></blockquote></div><div><br></div><div>Lots of people do submit patches using Git; I reviewed one earlier this week.</div><div><br></div><div>One thing I think this thread has inspired is a prompt move to make it clearer how to do this. It would be great if you could help out lvh in producing some good copy for the various workflow-documentation pages so that it's clear to people how to use their favorite VCS if they already have one; the SVN-based diff-and-ptach instructions that are already there are meant for users who may not be familiar with _any_ kind of version control. (Just to forestall any objections: this is a realistic audience, lots of Twisted contributors have been in secondary school when they started.)</div><br><blockquote type="cite"><div bgcolor="#FFFFFF"><div>I've always admired Twisted's standards and process; I think they have made it possible for such a huge project to maintain working order for so long. The tools could use an upgrade, though.</div></div></blockquote><div><br></div><div>Thanks for that :). And my earlier post notwithstanding, I agree. In fact, the tools <i>have</i> improved significantly, but many of them are things that contributors don't see (build system upgrades, release process improvements) but core developers, and therefore eventually users, do benefit from.</div><div><br></div><div>-glyph</div></div><div><br></div><div>[1]: Your choice, of course, should be Bazaar, as all other choices are wrong. But we can work around your Git habit ;-).</div><div><br></div></body></html>