<html><head><base href="x-msg://463/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">John, <div><div><br></div><div><div></div><blockquote type="cite"><div> * We expect the vendor to request two qualified, impartial</div><div> inspectors rather than the TWG itself to review the feature</div><div> submissions. (We acknowledge that the TWG itself does not</div><div> have the expertise to do the review, though some of its</div><div> members do.)</div></blockquote><div><br></div><div>Please forgive me if this topic has been discussed more thoroughly by the TWG in the past. OpenSFS might consider formulating this list of trusted inspectors on behalf of the community. Inspectors are volunteers from the community and are selected based on merit. To be an inspector, you submit information about:</div><div><br></div><div>- summary of overall Lustre and development experience</div><div>- overall years of Lustre experience</div><div>- years of experience per subsystem</div><div>- number of accepted commits to Lustre (per subsystem?)</div><div><br></div><div>Inspectors should also have some number of endorsements from the established group of inspectors.</div><div><br></div><div>All volunteers go into a public registry. OpenSFS establishes qualification criteria and then transparently selects a group of qualified volunteers. It doesn't matter what organization you work for but you must commit a certain number of inspection hours per month for OpenSFS community projects and chances are you'll be inspecting work </div><div><br></div><div>WhamClould already have a process refinement that requires two-level inspections, which OpenSFS might consider adopting.</div><div><br></div><div>Cheers,</div><div>Bojanic</div><div><br></div><div><div>On Apr 21, 2011, at 16:38 , John Carrier wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">Attached are the meeting minutes from todays TWG call where we started the discussion of what OpenSFS will require for release collateral and delivery of patches that result from our RFPs.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">Please post questions/comments to<span class="Apple-converted-space"> </span><a href="mailto:discuss@lists.opensfs.org" style="color: blue; text-decoration: underline; ">discuss@lists.opensfs.org</a><o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">Thanks,<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">--jc<o:p></o:p></div></div><span><2011-04-21 OpenSFS TWG minutes.txt></span>_______________________________________________<br>twg mailing list<br><a href="mailto:twg@lists.opensfs.org" style="color: blue; text-decoration: underline; ">twg@lists.opensfs.org</a><br><a href="http://lists.opensfs.org/listinfo.cgi/twg-opensfs.org" style="color: blue; text-decoration: underline; ">http://lists.opensfs.org/listinfo.cgi/twg-opensfs.org</a><br></div></blockquote></div><br></div></div></body></html>
<pre>______________________________________________________________________
This email may contain privileged or confidential information, which should only be used for the purpose for which it was sent by Xyratex. No further rights or licenses are granted to use such information. If you are not the intended recipient of this message, please notify the sender by return and delete it. You may not use, copy, disclose or rely on the information contained in it.
Internet email is susceptible to data corruption, interception and unauthorised amendment for which Xyratex does not accept liability. While we have taken reasonable precautions to ensure that this email is free of viruses, Xyratex does not accept liability for the presence of any computer viruses in this email, nor for any losses caused as a result of viruses.
Xyratex Technology Limited (03134912), Registered in England & Wales, Registered Office, Langstone Road, Havant, Hampshire, PO9 1SA.
The Xyratex group of companies also includes, Xyratex Ltd, registered in Bermuda, Xyratex International Inc, registered in California, Xyratex (Malaysia) Sdn Bhd registered in Malaysia, Xyratex Technology (Wuxi) Co Ltd registered in The People's Republic of China and Xyratex Japan Limited registered in Japan.
______________________________________________________________________