<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 14, 2013 at 10:02 AM, Dean Inglis <span dir="ltr"><<a href="mailto:inglis.dl@gmail.com" target="_blank">inglis.dl@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div>
Hi<br></div>I am fairly new to using the gerrit review process to address a bug fix <br>but am not a member of VTK-core group and have some questions:<br><br></div>
when sharing a topic:<br>- who from the group should I assign to my topic ? (it might be useful to know <br></div><div> from Wiki/VTK/Git/Develop what areas of VTK those members are involved with)<br></div></div></div></div>
</div></div></div></div></blockquote><div><br></div><div>Use git log --follow on the files you touch. The most recent couple of authors are likely the best reviewers.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div><div><div><div></div>- do I need to contact a group member first and ask their permission before<br>
</div> assignment ?<br></div></div></div></div></div></div></blockquote><div><br></div><div>No!!!! Please do jump right in.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div><div></div>- how many members should I assign to ?<br></div></div></div></div></div></blockquote><div><br></div><div>Two two three seems to work well in my experience.</div><div>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div></div>in general:<br>
- is there a reasonable time expectation for topic reviews to be completed or <br></div> responded to ? (it might be useful if topics were categorized with time to review/completion<br>
</div><div> stats were available)<br></div></div></div></blockquote><div><br></div><div>Not really. Depends on people's workload and style. If no one responds in a week or two, bug the developer mailing list.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div></div>- are bug fixes automatically incorporated into earlier branches / tags ?<br>
<br></div></div></blockquote><div><br></div><div>No. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div></div>thnx,<br>Dean<br></div>
<br></blockquote><div><br></div><div>Note: lots of this type of how to contribute type knowledge can be found in the VTK Software Process document, which you can find here:</div><div><a href="https://docs.google.com/a/kitware.com/document/d/1nzinw-dR5JQRNi_gb8qwLL5PnkGMK2FETlQGLr10tZw/view" target="_blank">https://docs.google.com/a/kitware.com/document/d/1nzinw-dR5JQRNi_gb8qwLL5PnkGMK2FETlQGLr10tZw/view</a></div>
<div>The VTK web pages are being updated as we speak to make it more visible.</div><div> <br></div><div><br></div><div>Thanks Dean!</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br></blockquote></div></div></div>