<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Mar 16, 2014, at 12:31 AM, Jonathan Ballet <<a href="mailto:jon@multani.info">jon@multani.info</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Glyph,<br><br>On Thu, Mar 13, 2014 at 12:35:17PM -0700, Glyph Lefkowitz wrote:</blockquote><br><blockquote type="cite"><blockquote type="cite">If someone would like to turn this list into a wiki page under <<a href="https://twistedmatrix.com/trac/wiki/Infrastructure">https://twistedmatrix.com/trac/wiki/Infrastructure</a>> that would be great, so it could be updated with anything I've forgotten. Right now there's the beginnings of a SwitchToBazaar which should probably be deleted, since we're not going to do that.<br></blockquote><br>I don't have edit permissions on the wiki, so I took the list of stuff<br>you mentionned here and made a wiki page joined to this email.<br></blockquote><div><br></div><div>What's your username? The only reason we even have edit permissions is to prevent spamming, anyone may ask for edit permission at any time :-).</div><br><blockquote type="cite">Compared to the SwitchToBazar page, here are the things which are<br>missing from your email - I don't know how relevant they are though:<br><br> * mailer post-commit hook<br></blockquote><div><br></div><div>Yeah, we probably need this. It seems like this ought to be pretty trivial to set up in git though :-).</div><br><blockquote type="cite"> * the release scripts<br></blockquote><div><br></div><div>Oh, good point. These rely fairly lightly on svn, but the dependency is there.</div><div><br></div><div>This would be a good place to start. Unfortunately, since tagging works differently in svn and git, I don't think we can simply start doing the release out of git without a repository to push to. If I'm wrong about this, so much the better, and we could actually start having release managers use git if they like :). Regardless, all the code to do so could be tested and landed as a normal development task with no administrative blockers, so this might be a good place for someone interested in moving the process along to start.</div><br><blockquote type="cite"> * the developer documentation (I guess that should be done)<br></blockquote><div><br></div><div>The developer documentation is already so bad (as Adi Roiban has pointed out) that it wouldn't make sense to block migrating to git on a comprehensive upgrade.</div><br><blockquote type="cite"> * figure the version number from Git instead of Subversion<br></blockquote><div><br></div><div>This would be an even more straightforward patch to Twisted, in twisted.python.versions.</div><br><blockquote type="cite"> * decide what to do with Combinator<br></blockquote><div><br></div><div>I think Combinator is an evolutionary dead end at this point. Tools like virtualenv, virtualenvwrapper, pyenv, </div><br><blockquote type="cite">There might be still some editing to do but that could be a start.<br></blockquote><br></div><div>I've deleted the SwitchToBazaar page and, for now, uploaded your proposal at <<a href="https://twistedmatrix.com/trac/wiki/Infrastructure/SwitchToGit">https://twistedmatrix.com/trac/wiki/Infrastructure/SwitchToGit</a>>. Hopefully someone (maybe me) can give you edit permission as soon as you announce your username :).</div><div><br></div><div>Thanks for your contribution,</div><div><br></div><div>-glyph</div><div><br></div></body></html>