<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 Jun 5, 2013, at 12:37 AM, Adi Roiban <<a href="mailto:adi@roiban.ro">adi@roiban.ro</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 5 June 2013 09:29, Glyph <<a href="mailto:glyph@twistedmatrix.com">glyph@twistedmatrix.com</a>> wrote:<br>[snip]<br><br><blockquote type="cite">So, please, go on contributing patches to Twisted; I thank you for your<br>contribution and I thank you doubly for your patience.<br></blockquote><br>From my point of view, the fact that reviews take so long is one<br>reason why committing patches to Twisted is not fun. So I think that<br>you are right to focus on solving the review issues.<br><br>I have contributed a few patches to twisted.protocols.ftp and I think<br>that one of the reason why it took so long to review the code, is due<br>to the fact that no core developer really cares about FTP<br>implementation.<br>I know that everybody want Twisted to be big and great, but there are<br>limited resources that needs to be managed.<br></div></blockquote><div dir="auto"><br></div><div dir="auto">Would you be interested in contributing to those resources by doing some reviews yourself? :)</div><div dir="auto"><br></div><div dir="auto">As a non-committer, you can do reviews of fixes contributed by committers (like me, exarkun, dreid, radix, therve...). It's up to the committer to decide whether your review was thorough enough, so it's their fault if you didn't do a good enough job :). If you clear those tickets out of the queue, it gives committers more time to review tickets from external contributors.</div><br><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">This is not a complain :), but what I wanted to say is that maybe it<br>is better for Twisted to be a thinner library, and "downgrade" some of<br>the code to independent projects.</div></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">In this way, core developers will have more time to review more<br>important core features, rather than looking at my minor fixes for FTP<br>and later maintaining that code.<br></div></blockquote><br></div><div>There are, possibly, some features that Twisted could shed. But, based on my experience, I don't think that this is a major issue. A big reason that we need code review is to introduce external contributors to our coding practices so that they can work up to making more significant changes; in that sense, most reviews are similar unless they're really big.</div><div><br></div><div>Also, one of the main advantages of Twisted is that it's a feature-rich suite of protocols which work together. It's nice to have common documentation and testing standards applied to all of them. (One day, after they've been maintained for another 10 years or so, maybe that'll even mean they all have good documentation and tests! :-)).</div><div><br></div><div>-glyph</div><div><br></div></body></html>