<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span>Guidelines for this would be nice to have.</span></div><div><br><span></span></div><div><span>I'd say definite changes that should go through a reviewed pull request:</span></div><div><br><span></span></div><div><span>* changes from non-phobos developers (obviously)</span></div><div><span>* changes to files that you do not "own" (even if trivial). For example, if I were to find a bug in std.parallelism, I shouldn't commit, I should generate a pull request for review.<br></span></div><div><span>* changes that alter the design of a module.</span></div><div><span>* new code (including adding classes/structs/functions to an existing module)<br></span></div><div><span><br></span></div><div><span>I think everything else is OK to commit directly instead of generating a pull request, including bug fixes (as long as they are not
fixed by doing one of the above).<br></span></div><div><br></div><div>What do you think? A list like this (and actually, our entire process should be documented, including how to get included as a phobos developer) should be posted to the web site.</div><div><br></div><div>-Steve<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> David Simcha <dsimcha@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Discuss the phobos library for D <phobos@puremagic.com><br><b><span style="font-weight: bold;">Sent:</span></b> Sunday, May 1, 2011 11:29 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [phobos]
[D-Programming-Language/phobos] a15e68: Accidentally committed with a bunch of debugging c...<br></font><br>On 5/1/2011 10:51 PM, Andrei Alexandrescu wrote:<br>> David -- you may want to make updates through the pull request system. That gives you the opportunity of having one extra pair of eyes look over the code.<br>> <br>> Ideally there should be at least two people involved in a change. Unfortunately, it looks like the second person is me rather often.<br>> <br><br>I understand the idea that significant commits should be reviewed, but where do we draw the line? Reviewing even the most trivial commits seems unnecessarily bureaucratic to me. In the case of the initial commit, std.parallelism had already been in review for weeks. (To play Devil's Advocate, though, the changes to the make file might have been worth reviewing.)<br>_______________________________________________<br>phobos mailing list<br><a
ymailto="mailto:phobos@puremagic.com" href="mailto:phobos@puremagic.com">phobos@puremagic.com</a><br><a href="http://lists.puremagic.com/mailman/listinfo/phobos" target="_blank">http://lists.puremagic.com/mailman/listinfo/phobos</a><br><br><br></div></div></blockquote></div></div></body></html>