Re: Loosening Quotient review requirements
Glyph Lefkowitz <[email protected]> Mon, 4 Jan 2010 15:52:46 -0500
| Newsgroups | gmane.comp.python.quotient.dev |
|---|---|
| Message-ID | <[email protected]> |
--===============1253411678== Content-Type: multipart/alternative; boundary=Apple-Mail-1-863325455 --Apple-Mail-1-863325455 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Jan 4, 2010, at 3:40 PM, [email protected] wrote: > The development process for all the rest of the Divmod projects would=20= > remain the same (at least for now). I would do self-reviews and=20 > continue to seek out a high level of quality in the code. >=20 > This would only apply to me, since I seem to be the only developer. = If=20 > someone else shows up, then the problem goes away and we can resume=20 > reviews. >=20 > The alternative isn't very different. There are things in Quotient I=20= > really want to fix; if reviews remain required and no reviewers are=20 > available, then I'll end up with a de facto fork of Quotient, also = with=20 > no independent code review. It would be simpler if I could avoid such = a=20 > fork. Please go ahead and self-review. I can't imagine what the utility of = creating such a fork would be :). I still need to get my IP approval squared away at work before I can get = back to contributing, but even when I do, it's unlikely that I'd be able = to keep up with your changes to Quotient. I'm looking forward to using it again one day though :). --Apple-Mail-1-863325455 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; = "><div><div>On Jan 4, 2010, at 3:40 PM, <a = href=3D"mailto:[email protected]">[email protected]</a> = wrote:</div><br class=3D"Apple-interchange-newline"><blockquote = type=3D"cite"><div>The development process for all the rest of the = Divmod projects would <br>remain the same (at least for now). I = would do self-reviews and <br>continue to seek out a high level of = quality in the code.<br><br>This would only apply to me, since I seem to = be the only developer. If <br>someone else shows up, then the = problem goes away and we can resume <br>reviews.<br><br>The alternative = isn't very different. There are things in Quotient I <br>really = want to fix; if reviews remain required and no reviewers are = <br>available, then I'll end up with a de facto fork of Quotient, also = with <br>no independent code review. It would be simpler if I = could avoid such a <br>fork.<font class=3D"Apple-style-span" = color=3D"#000000"><font class=3D"Apple-style-span" = color=3D"#144FAE"><br></font></font></div></blockquote><br></div><div>Plea= se go ahead and self-review. I can't imagine what the utility of = creating such a fork would be :).</div><div><br></div><div>I still need = to get my IP approval squared away at work before I can get back to = contributing, but even when I do, it's unlikely that I'd be able to keep = up with your changes to Quotient.</div><div><br></div><div>I'm looking = forward to using it again one day though = :).</div><div><br></div></body></html>= --Apple-Mail-1-863325455-- --===============1253411678== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline