[llvm-commits] CVS: llvm-www/Oversight.html

Fri Jan 7 14:21:44 PST 2005

Changes in directory llvm-www:

Oversight.html added (r1.1)
---
Log message:

Web page describing the oversight group.

---
Diffs of the changes:  (+107 -0)

Index: llvm-www/Oversight.html
diff -c /dev/null llvm-www/Oversight.html:1.1
*** /dev/null	Fri Jan  7 16:21:40 2005
--- llvm-www/Oversight.html	Fri Jan  7 16:21:29 2005
***************
*** 0 ****
--- 1,107 ----
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+ <html>
+   <head>
+     <title>LLVM Oversight Group Mission</title>
+   </head>
+ 
+   <body>
+     <h1>LLVM Oversight Group Mission</h1>
+ 
+     <h3>Introduction</h3>
+ 
+     The LLVM Oversight Group is a small group of LLVM developers that aim to
+     guide continued development, distribution, and community-building for
+     LLVM.  Our broad aim is to foster the wider adoption and growth of LLVM.
+     A key part of that is to encourage participation and contributions from
+     both UIUC and non-UIUC users.
+ 
+     <p>
+     We do <b>not</b> aim to create a bureaucracy.  On the contrary, we believe
+     that having a simple but organized process for overseeing LLVM should give
+     more confidence to potential users and contributors in the stability and
+     longevity of LLVM, and therefore encourage them to get involved.  Having a
+     well-understood process for major contributions should also encourage
+     developers to contribute their work and stay involved.
+     
+     <h3>Membership and Communication</h3>
+ 
+     The oversight group currently consists of Chris Lattner, Vikram Adve, Reid
+     Spencer and Misha Brukman. Our goal for the membership of this group is to
+     have Chris, Vikram and two or three other active LLVM developers,
+     including at least one from academia and one from industry.
+ 
+     <p>You can send e-mail to the group at
+     <a href="mailto:oversight at llvm.cs.uiuc.edu"><b><tt>
+ 	    oversight at llvm.cs.uiuc.edu</tt></b></a>.
+     This alias only reaches the oversight group, and messages can be kept
+     confidential on request.  Please use this alias for any feedback or
+     suggestions regarding LLVM policy issues outlined in the mission statement
+     below (rather than broadcasting them to <tt>llvmdev</tt>).
+ 
+     <h3>Mission</h3>
+ 
+     The primary goals of the LLVM oversight group are:
+     <ul>
+       <li> <b>Functionality and Stability in the Core Framework:</b>
+ 	<ul>
+ 	  <li> Adjudicate substantial changes to the core LLVM components,
+ 	    which essentially includes everything in <tt>llvm/lib/</tt>
+ 	    and the key llvm tools.</li>
+ 	  <li> Identify and prioritize improvements to the core.</li>
+ 	</ul></li>
+       <p><li> <b>Guidelines for who gets write-access to CVS:</b>
+ 	<ul>
+ 	  <li> The goal here is to encourage the most active contributors by
+ 	    giving them direct CVS write access.</li>
+ 	  <li> Our primary guiding principle here is that write access should
+ 	    be limited to persons who have a track record of responsible
+ 	    contributions, and are likely to remain active contributors
+ 	    for a long time (not for short-term projects).</li>
+ 	</ul> </li>
+       <p><li><b>Public Awareness:</b>
+ 	<ul>
+ 	  <li> Be <i>proactive</i> in finding opportunities to attract users
+ 	    and developers.</li>
+ 	  <li> Give/organize LLVM tutorials at conferences.</li>
+ 	  <li> Create publicity for new releases.</li>
+ 	</ul></li>
+       <p><li><b>Licensing and Copyright:</b>
+ 	<ul>
+ 	  <li> Oversee changes in LLVM licensing.</li>
+ 	  <li> Oversee LLVM copyright ownership issues.</li>
+ 	  <li> Attempt to ensure that we don't violate copyrights of other
+ 	  software used by or in LLVM, or infringe patents, especially
+ 	  unintentional violations due to contributed code.</li>
+ 	</ul></li>
+       <p><li><b>Release Management:</b>
+ 	<ul>
+ 	  <li> Collect feedback on what users would like to see in future releases.</li>
+ 	  <li> Provide a "best guess" page on what will be in the next release.</li>
+ 	  <li> Manage quarterly releases.</li>
+ 	</ul></li>
+       <p><li><b>Open Projects and Ongoing Projects:</b>
+ 	<ul>
+ 	  <li> Identify projects we would like to see happen.</li>
+ 	  <li> Maintain public information about these projects and priorities
+ 	    to guide interested developers.</li>
+ 	  <li> Maintain public information about ongoing major projects to
+ 	    avoid redundancy (and minimize a major source of conflict!).</li>
+ 	</ul>  </li>
+       <p><li><b>Dispute Resolution:</b>
+ 	<ul>
+ 	  <li>Resolve TECHNICAL disputes between parties that are unable
+ 	    to resolve the issues themselves.</li>
+ 	</ul></li>
+ 	<!--  <li> The goal is <i>not</i> to check each patch or check-in. -->
+     </ul>
+     
+ 
+ 
+     <hr>
+     <address><a href="mailto:vadve at cs.uiuc.edu">Vikram Adve</a></address>
+ <!-- Created: Fri Nov 19 10:19:25 CST 2004 -->
+ <!-- hhmts start -->
+ Last modified: Fri Jan  7 16:16:30 CST 2005
+ <!-- hhmts end -->
+   </body>
+ </html>