<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [openfabrics-ewg] Getting EWG off to a rapid and positive start</TITLE>
</HEAD>
<BODY>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">Bryan</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">,</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">Thanks for leading the discussion. </FONT> <FONT SIZE=2 FACE="Arial">I have tried to address some of the questions in the proposal below.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">All, </FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">Here is a strawman proposal for the EWG</FONT> <FONT SIZE=2 FACE="Arial">Distribution</FONT> <FONT SIZE=2 FACE="Arial">process</FONT><FONT SIZE=2 FACE="Arial">. I would like to call a meeting of the EWG members on Monday between at 11:30 AM PST (this time works for the folks in Israel)</FONT><FONT SIZE=2 FACE="Arial">. PLEASE CONFIRM</FONT><FONT SIZE=2 FACE="Arial">:</FONT></P>
<P ALIGN=LEFT><B><FONT SIZE=2 FACE="Arial">KEY PEOPLE in the process:</FONT></B></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">1.</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">The EWG needs a CHAIR, per Open Fabrics Bylaws who needs to be approved by the BOD. The Chair is a liaison between the EWG and the BOD.</FONT><FONT SIZE=2 FACE="Arial"> Will communicate the existence and purpose of the EWG to OpenFabrics-General.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">2.</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">RELEASE COORDINATOR who drives the upcoming release. </FONT> <FONT SIZE=2 FACE="Arial">Drives</FONT><FONT SIZE=2 FACE="Arial"> decisions</FONT> <FONT SIZE=2 FACE="Arial">collaboratively to</FONT><FONT SIZE=2 FACE="Arial"> enable stable</FONT><FONT SIZE=2 FACE="Arial">, supportable</FONT><FONT SIZE=2 FACE="Arial"> release</FONT> <FONT SIZE=2 FACE="Arial">of EWG Distribution</FONT> <FONT SIZE=2 FACE="Arial">on schedule.</FONT><FONT SIZE=2 FACE="Arial"> Defines</FONT><FONT SIZE=2 FACE="Arial">:</FONT> <FONT SIZE=2 FACE="Arial">Which software components are included?</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">Which hardware components are intended to work?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">3. Open Fabrics Release Committee Lead - the OFR LEAD (what Bryan from P</FONT><FONT SIZE=2 FACE="Arial">athScale</FONT><FONT SIZE=2 FACE="Arial"> is today)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">4. TEST LEADS from each Company</FONT><FONT SIZE=2 FACE="Arial">. Decides:</FONT> <FONT SIZE=2 FACE="Arial">Which distros are targeted?</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">What is the test matrix?</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">What documentation will be written up for customers?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">5. MAINTAINERS and backups (B-MAINTAINER) for each component in EWG</FONT><FONT SIZE=2 FACE="Arial">: Calls dedicated technical meetings to ensure delivery, code</FONT><FONT SIZE=2 FACE="Arial">/feature</FONT><FONT SIZE=2 FACE="Arial"> completeness.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial"> </FONT></P>
<P ALIGN=LEFT><B><FONT SIZE=2 FACE="Arial">Suggested schedules:</FONT></B><B></B><B></B></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">EWG Distribution 1.0 - sync with OFR Release 1.0 date of May 8.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">EWG Distribution 1.1 - Sept (4 months delta</FONT><FONT SIZE=2 FACE="Arial"> between releases</FONT><FONT SIZE=2 FACE="Arial">)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial"> </FONT></P>
<P ALIGN=LEFT><B><FONT SIZE=2 FACE="Arial">Proposal</FONT></B><B></B><B><FONT SIZE=2 FACE="Arial"> for electing the KEY PEOPLE:</FONT></B></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">1. CHAIR is elected on a rotating basis - changing every 4 months with EWG release completions. Represented by system companies - Cisco, Voltaire, SilverStorm. In alphabetical order. So, starts with Cisco as the CHAIR. Storage vendors like LSI if they meet the criteria to a EWG member can be eligible to be CHAIR as well. First proposed rotation is after EWG Distribution 1.1 (May 8 being too close)</FONT><FONT SIZE=2 FACE="Arial">. If that is a problem, it could be Matt</FONT> <FONT SIZE=2 FACE="Arial">representing</FONT><FONT SIZE=2 FACE="Arial"> a neutral party.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">2. RELEASE COORDINATOR is elected from either Mellanox or PathScale on a rotating basis - changing every 4 months with EWG release completions. </FONT> <FONT SIZE=2 FACE="Arial">Change will be decided when the time comes based on voting</FONT><FONT SIZE=2 FACE="Arial"> or</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">recent past</FONT> <FONT SIZE=2 FACE="Arial">effectiveness etc</FONT><FONT SIZE=2 FACE="Arial">.</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">T</FONT><FONT SIZE=2 FACE="Arial">his person must be</FONT> <FONT SIZE=2 FACE="Arial">commercially</FONT> <FONT SIZE=2 FACE="Arial">neutral to the system companies who compete in the end user space. At any time Mellanox or PathScale will be the RELEASE COORDINATOR or OFR LEAD</FONT><FONT SIZE=2 FACE="Arial">, not both</FONT><FONT SIZE=2 FACE="Arial">. Currently Pathscale is OFR LEAD. So Mellanox will be RELEASE COORDINATOR. First p</FONT><FONT SIZE=2 FACE="Arial">ossible</FONT><FONT SIZE=2 FACE="Arial"> rotation</FONT><FONT SIZE=2 FACE="Arial"> (based on voting, effectiveness etc.)</FONT><FONT SIZE=2 FACE="Arial"> is after EWG Distribution 1.1 (May 8 being too close)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">3. OFR LEAD is elected from either Mellanox or PathScale on a rotating basis - changing every 4 months with EWG release completions.</FONT> <FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">Change will be decided when the time comes based on voting</FONT><FONT SIZE=2 FACE="Arial"> or</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">recent past</FONT> <FONT SIZE=2 FACE="Arial">effectiveness etc</FONT><FONT SIZE=2 FACE="Arial">.</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">T</FONT><FONT SIZE=2 FACE="Arial">his person must be</FONT> <FONT SIZE=2 FACE="Arial">commercially</FONT> <FONT SIZE=2 FACE="Arial">neutral to the system companies who compete in the end user space</FONT><FONT SIZE=2 FACE="Arial">. </FONT> <FONT SIZE=2 FACE="Arial">At any time Mellanox or PathScale will be the RELEASE COORDINATOR or OFR LEAD</FONT><FONT SIZE=2 FACE="Arial">, not both</FONT><FONT SIZE=2 FACE="Arial">. Currently Pathscale is OFR LEAD. So Mellanox will be RELEASE COORDINATOR. First p</FONT><FONT SIZE=2 FACE="Arial">ossible</FONT><FONT SIZE=2 FACE="Arial"> rotation</FONT><FONT SIZE=2 FACE="Arial"> (based on voting, effectiveness etc.)</FONT><FONT SIZE=2 FACE="Arial"> is after EWG Distribution 1.1 (May 8 being too close)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">4. TEST LEADS - elected by individual companies. Scott from Cisco, Bob from SST, Moni from V, Amit from M</FONT><FONT SIZE=2 FACE="Arial">ellanox</FONT><FONT SIZE=2 FACE="Arial">, Betsy from P</FONT><FONT SIZE=2 FACE="Arial">athscale</FONT><FONT SIZE=2 FACE="Arial">. </FONT> </P>
<BR>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">5. MAINTAINERS (B-MAINTAINERS): Selected based on who is currently maintaining. MAINTAINER selects B-MAINTAINER based on technical expertise, past contributions. Here are MAINTAINERS and suggestions for B-MAINTAINERS:</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">MTHCA - Roland (Michael Tsirkin)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o</FONT> <FONT SIZE=2 FACE="Arial">IPATH</FONT><FONT SIZE=2 FACE="Arial"> - Roland (</FONT><FONT SIZE=2 FACE="Courier New">Bryan</FONT><FONT SIZE=2 FACE="Arial">)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o Core - Roland (</FONT><FONT SIZE=2 FACE="Courier New">Bryan</FONT><FONT SIZE=2 FACE="Arial">) </FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o IPoIB - Roland (Eli Cohen)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o SDP - Michael Tsirkin (?)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o SRP - Roland (Vu)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o iSER - Moni (?)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o RDS - Todd (</FONT><FONT SIZE=2 FACE="Arial">?</FONT><FONT SIZE=2 FACE="Arial">)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o MVAPICH -</FONT><FONT SIZE=2 FACE="Arial"> ?? (ideally would like companies with vested interest to productize MVAPICH)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o Open MPI -</FONT> <FONT SIZE=2 FACE="Arial">?? (ideally would like companies with vested interest to productize</FONT> <FONT SIZE=2 FACE="Arial">Open MPI</FONT><FONT SIZE=2 FACE="Arial">)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o OSM -</FONT> <FONT SIZE=2 FACE="Arial">Eitan (Hal)</FONT><FONT SIZE=2 FACE="Arial"> </FONT> <FONT SIZE=2 FACE="Arial">(ideally would like companies with vested interest to productize</FONT> <FONT SIZE=2 FACE="Arial">OSM</FONT><FONT SIZE=2 FACE="Arial">)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o Diagnostic Tools -</FONT> <FONT SIZE=2 FACE="Arial">Eitan</FONT> <FONT SIZE=2 FACE="Arial">(</FONT><FONT SIZE=2 FACE="Arial">Hal</FONT><FONT SIZE=2 FACE="Arial">)</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial"> </FONT></P>
<P ALIGN=LEFT><B><FONT SIZE=2 FACE="Arial">RELEASE</FONT></B><B></B><B><FONT SIZE=2 FACE="Arial"> COMPONENT</FONT></B><B></B><B><FONT SIZE=2 FACE="Arial"> CATEGORIES</FONT></B><B></B><B><FONT SIZE=2 FACE="Arial">:</FONT></B></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">They fall under 3 categories:</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o BASE COMPONENTS: IPoIB, SDP, SRP, iSER, RDS, Open MPI,</FONT> <FONT SIZE=2 FACE="Arial">iPath,</FONT> <FONT SIZE=2 FACE="Arial">MTHCA</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o Depending on vendors desire</FONT><FONT SIZE=2 FACE="Arial">/ability</FONT><FONT SIZE=2 FACE="Arial"> to qualify and support BASE COMPONENTS - some may be released and supported by vendors as TECH PREVIEW only. E.g., iSER could be TECH PREVIEW for Cisco. </FONT> <FONT SIZE=2 FACE="Arial">SRP could be TECH PREVIEW for Voltaire.</FONT><FONT SIZE=2 FACE="Arial"> RDS could be TECH PREVIEW for all etc. The goal is to get TECH PREVIEW components graduate to supported BASE COMPONENTS in the EWG</FONT> <FONT SIZE=2 FACE="Arial">Distribution</FONT> <FONT SIZE=2 FACE="Arial">1.1</FONT><FONT SIZE=2 FACE="Arial"> scheduled for September.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">o ADD-ON -</FONT> <FONT SIZE=2 FACE="Arial">These will be added in</FONT> <FONT SIZE=2 FACE="Arial">Vendor specific</FONT> <FONT SIZE=2 FACE="Arial">distributions as</FONT> <FONT SIZE=2 FACE="Arial">add-ons</FONT> <FONT SIZE=2 FACE="Arial">on top of (and not replacing</FONT><FONT SIZE=2 FACE="Arial">)</FONT><FONT SIZE=2 FACE="Arial"> BASE COMPONENTS.</FONT><FONT SIZE=2 FACE="Arial"> OSM, Proprietary SM, Proprietary MPI</FONT><FONT SIZE=2 FACE="Arial">, other value added management and tools</FONT><FONT SIZE=2 FACE="Arial"> etc</FONT><FONT SIZE=2 FACE="Arial"> fall in this category</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial"> </FONT></P>
<P ALIGN=LEFT><B><FONT SIZE=2 FACE="Arial">EWG DISTRIBUTION MANAGEMENT</FONT></B><B></B><B><FONT SIZE=2 FACE="Arial"> + SYNCH WIT</FONT></B><B></B><B><FONT SIZE=2 FACE="Arial">H</FONT></B><B></B><B><FONT SIZE=2 FACE="Arial"> OFR RC BRANCH</FONT></B><B></B><B></B></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">Copy</FONT><FONT SIZE=2 FACE="Arial"> a specific trunk</FONT><FONT SIZE=2 FACE="Arial">/branch</FONT><FONT SIZE=2 FACE="Arial"> version to</FONT> <FONT SIZE=2 FACE="Arial">EWG</FONT><FONT SIZE=2 FACE="Arial"> area you can call this a tag. The main idea of a tag is that you do not commit changes to the tagged area.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">In addition</FONT> <FONT SIZE=2 FACE="Arial">there is a</FONT><FONT SIZE=2 FACE="Arial"> directory called patches where</FONT> <FONT SIZE=2 FACE="Arial">EWG places</FONT><FONT SIZE=2 FACE="Arial"> the fixes wanted that were not in the trunk</FONT><FONT SIZE=2 FACE="Arial">/branch</FONT><FONT SIZE=2 FACE="Arial">.</FONT><FONT SIZE=2 FACE="Arial"> The</FONT> <FONT SIZE=2 FACE="Arial">OFR LEAD</FONT><FONT SIZE=2 FACE="Arial"> folds those into the OFR-RC</FONT> <FONT SIZE=2 FACE="Arial">branch</FONT><FONT SIZE=2 FACE="Arial"> immediately.</FONT> <FONT SIZE=2 FACE="Arial"> Coordinated with RELEASE COORDINATOR as necessary.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">Continue</FONT><FONT SIZE=2 FACE="Arial"> copy of trunk</FONT><FONT SIZE=2 FACE="Arial">/branch</FONT><FONT SIZE=2 FACE="Arial"> to the tag few times till</FONT> <FONT SIZE=2 FACE="Arial">EWG gets</FONT><FONT SIZE=2 FACE="Arial"> to the point</FONT> <FONT SIZE=2 FACE="Arial">it wants to freeze code</FONT><FONT SIZE=2 FACE="Arial">. From this point</FONT><FONT SIZE=2 FACE="Arial"> (regression test phase)</FONT><FONT SIZE=2 FACE="Arial"></FONT> <FONT SIZE=2 FACE="Arial">EWG</FONT><FONT SIZE=2 FACE="Arial"> only add</FONT><FONT SIZE=2 FACE="Arial">s</FONT><FONT SIZE=2 FACE="Arial"> patches (some</FONT> <FONT SIZE=2 FACE="Arial">can be EWG</FONT><FONT SIZE=2 FACE="Arial"> fixes and some from the trunk</FONT><FONT SIZE=2 FACE="Arial">/branch</FONT><FONT SIZE=2 FACE="Arial">).</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Arial">We need a discussion on the contents of</FONT> <FONT SIZE=2 FACE="Arial">the</FONT> <FONT SIZE=2 FACE="Arial">OFR rc1</FONT> <FONT SIZE=2 FACE="Arial">branch</FONT> <FONT SIZE=2 FACE="Arial">- whether it meets the need of end users defined by the EWG and if that needs to be updated (as rc2) based on feedback from EWG</FONT><FONT SIZE=2 FACE="Arial">.</FONT></P>
<BR>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">Thanks</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">Sujal</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">-----Original Message-----<BR>
From: Bryan O'Sullivan [<A HREF="mailto:bos@pathscale.com">mailto:bos@pathscale.com</A>]<BR>
Sent: Thursday, March 16, 2006 9:36 AM<BR>
To: Openfabrics-ewg@openib.org<BR>
Subject: [openfabrics-ewg] Getting EWG off to a rapid and positive start</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">Hello -</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">I'll be PathScale's engineering and testing representative on the EWG.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">I would suggest that we start by clarifying the goals of the EWG</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">process, so that everyone is in sync.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">My principal interest is in ensuring that there is no duplicated or</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">wasted effort between the 1.0 process and the EWG process, and that each</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">can proceed at its own appropriate pace with maximal cooperation between</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">the two.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">What I believe is a good way to achieve this is as follows.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">Somebody needs to articulate the goals of the EWG process, and the</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">timeline in which it will take place. Here are some suggestions I have.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * The existence of EWG should be made public on openib-general,</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> and it must be made clear that there is cooperation, not</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> duplication, between the 1.0 and EWG processes.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * Which software components are included?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * Which hardware components are intended to work?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * Which distros are targeted?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * What is the test matrix?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * What documentation will be written up for customers?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * How long is the support window?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> * What's the policy with respect to switching to the official 1.0</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"> and subsequent releases?</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">To get the testing and defect fixing balls rolling as quickly as</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">possible, EWG contributors ought to use the 1.0 release candidate tree</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">at <A HREF="https://openib.org/svn/gen2/branches/1.0/" TARGET="_blank">https://openib.org/svn/gen2/branches/1.0/</A> as its initial basis for</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">source code to build and test. You can download source tarballs and</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">some RPM packages from <A HREF="http://openib.red-bean.com/" TARGET="_blank">http://openib.red-bean.com/</A></FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">It's fine with me if EWG branches from 1.0 so that it can proceed at its</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">own pace. However, if this happens, there must be frequent merges</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">between the two trees, because clearly everything that happens in one</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">branch ought to be beneficial to the other.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">The mechanism that EWG uses to track defects should be OpenIB Bugzilla.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">I believe it's already configured in an appropriate manner. If not, I</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">will be happy to make any needed changes, or ask our colleagues at</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">Sandia to help out.</FONT></P>
<P ALIGN=LEFT> <FONT SIZE=2 FACE="Courier New"><b</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">_______________________________________________</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">openfabrics-ewg mailing list</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New">openfabrics-ewg@openib.org</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Courier New"><A HREF="http://openib.org/mailman/listinfo/openfabrics-ewg" TARGET="_blank">http://openib.org/mailman/listinfo/openfabrics-ewg</A></FONT></P>
</BODY>
</HTML>