nicolaken 2003/10/07 08:51:55
Added: . forrest.properties index.html status.xml
structure.html
Log:
First pass at making the new website.
It generates correctly with Forrest, please give it a try;
suggestions are welcome :-)
Revision Changes Path
1.1 incubator/forrest.properties
Index: forrest.properties
===================================================================
##############
# Properties used by forrest.build.xml for building the website
##############
# Prints out a summary of Forrest settings for this project
#forrest.echo=true
# Specifies name of Forrest skin to use
project.skin=forrest-site
# Properties that must be set to override the default locations
#project.status=status.xml
#project.content-dir=src/documentation
#project.xdocs-dir=${project.content-dir}/content/xdocs
#project.skinconf=${project.content-dir}/skinconf.xml
# See http://xml.apache.org/forrest/validation.html
forrest.validate.xdocs.excludes=learn/glossary.xml,site.xml
1.1 incubator/index.html
Index: index.html
===================================================================
<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd";>
<html>
<head>
<title>Apache Incubator Project</title>
</head>
<body bgcolor="#ffffff">
<h1>Apache Incubator Project</h1>
<p>
<small><i>Last updated: $Date: 2003/10/07 15:51:55 $</i></small>
</p>
<!-- TODO
1. the licence
2. infrastructure
3. foundation structure
4. incubation flow (concept, proposal, setup, growth, graduation)
5. why the asf
-->
<h2>Status</h2>
<p>
This project is just ramping up, so there's nothing to see here
yet. Go on with your lives, citizens, and check back later.
</p>
<h2>Forming Resolution</h2>
<p>
Wait, there <i>is</i> one thing we can show: the resolution passed
by the Apache Board which formed this project.
</p>
<blockquote>
<p>
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with accepting new products into the
Foundation, providing guidance and support to help each new
product engender their own collaborative community, educating
new developers in the philosophy and guidelines for
collaborative development as defined by the members of the
Foundation, and proposing to the board the promotion of such
products to independent PMC status once their community has
reached maturity.
</p>
<p>
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Incubator PMC", be
and hereby is established pursuant to the Bylaws of the
Foundation; and be it further
</p>
<p>
RESOLVED, that the Apache Incubator PMC be and hereby is
responsible for the acceptance and oversight of new products
submitted or proposed to become part of the Foundation; and be
it further
</p>
<p>
RESOLVED, that the Apache Incubator PMC is responsible for
providing guidance and ensuring that subprojects under its
purview develop products according to the Foundation's
philosophy and guidelines for collaborative development; and be
it further
</p>
<p>
RESOLVED, that the Apache Incubator PMC is responsible for
regularly evaluating products under its purview and making the
determination in each case of whether the product should be
abandoned, continue to receive guidance and support, or
proposed to the board for promotion to full project status as
part of an existing or new Foundation PMC; and be it further
</p>
<p>
RESOLVED, that the office of "Vice President, Apache Incubator"
be and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Incubator PMC, and to have primary responsibility
for management of the subprojects within the scope and
responsibility of the Apache Incubator PMC; and be it further
</p>
<p>
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Incubator PMC:
</p>
<dl>
<dd>Aaron Bannert</dd>
<dd>Nicola Ken Barozzi</dd>
<dd>Ken Coar</dd>
<dd>Roy T. Fielding</dd>
<dd>B. W. Fitzpatrick</dd>
<dd>Jim Jagielski</dd>
<dd>Greg Stein</dd>
<dd>Sander Striker</dd>
</dl>
<p>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Jagielski be
and hereby is appointed to the office of Vice President, Apache
Incubator, to serve in accordance with and subject to the
direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be it
further
</p>
<p>
RESOLVED, that the initial Apache Incubator PMC be and hereby
is tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Incubator Project.
</p>
</blockquote>
<hr />
<div align="center">
<small>All portions copyright © 2002 by the Apache Software
Foundation.
All rights reserved.</small>
</div>
</body>
</html>
1.1 incubator/status.xml
Index: status.xml
===================================================================
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl"
href="./tools/antipede/resources/stylesheets/status.xsl"?>
<status>
<developers>
<person name="Nicola Ken Barozzi" id="nicolaken" email="[EMAIL
PROTECTED]"/>
<person name="Rodent of Unusual Size" id="coar" email="[EMAIL
PROTECTED]"/>
</developers>
<todo>
<actions priority="high">
<action context="docs" dev="incubator">
Add lots of content
</action>
</actions>
<!-- Add todo items. @context is an arbitrary string. Eg:
<actions priority="high">
<action context="code" dev="SN">
</action>
</actions>
<actions priority="medium">
<action context="docs" dev="open">
</action>
</actions>
-->
</todo>
<changes>
<!-- Add new releases here -->
<release version="0.1" date="2002">
<!-- Some action types have associated images. By default, images are
defined for 'add', 'fix', 'remove' and 'update'. If you add
src/documentation/resources/images/<foo>.jpg images, these will
automatically be used for entries of type <foo>. -->
<action dev="nicolaken" type="add" context="admin">
Added draft doc about developers become committers, and what to do.
</action>
<action dev="coar" type="add" context="admin">
Initial Import
</action>
<!-- Sample action:
<action dev="JB" type="fix" due-to="Joe Contributor"
due-to-email="[EMAIL PROTECTED]">
Fixed a bug in the Foo class.
</action> -->
</release>
</changes>
</status>
1.1 incubator/structure.html
Index: structure.html
===================================================================
<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd";>
<html>
<head>
<title>Apache Incubator: About the ASF Structure</title>
</head>
<body bgcolor="#ffffff">
<h1>Apache Incubator Project: Education</h1>
<p>
<small><i>Last updated: $Date: 2003/10/07 15:51:55 $</i></small>
</p>
<h2>About the Structure of the Apache Software Foundation</h2>
<p>
One of the functions of the Incubator project is to educate developers
new to the Apache Software Foundation in how it works, what the
pieces are, and how they fit together. This page is a rough-draft
first attempt at beginning the documentation of that.
</p>
<h3>The Apache Software Foundation (ASF) is a Corporation</h3>
<p>
Yes, the ASF is a membership-based corporation registered in Delaware,
United States. It is intended to be a registered non-profit charity,
and in fact was given 501(c)(3) status by the U.S. Internal Revenue
Service. However, even if something happens that changes that
status, the ASF is <b>still</b> a not-for-profit enterprise.
</p>
<p>
The ASF was incorporated to provide a legal entity which could shield
the developers working on its code. Along with being a corporation
come some boring niggly details, though:
</p>
<p>
The people who have the responsibilities of watching over the
Foundation's activities, and keeping them on track and out of
trouble, are the ASF's Board of Directors. The board consists
of nine individuals elected by the Foundation's membership
and invested by the membership with the authority to run
the Foundation and make tactical and strategic decisions concerning
it. (A lot of developers consider that boring and tedious.)
</p>
<p>
The membership of the ASF is composed of individuals, not companies. The
members have a legal stake in the ASF.
</p>
<p>
All software developed within the Foundation belongs to the ASF,
and therefore the members. The members own the code and the direction
of it and the Foundation. Committers get a shot at working on the code;
good committers become members and thus get a piece of the ownership of
the software and the direction. <b>Commit access is a privilege, not
a right, and is based on trust.</b>
</p>
<ul>
<li>projects</li>
<li>members: what they do, privileges, responsibilities,
how to get to be one</li>
<li>board: likewise</li>
<li>committers: likewise</li>
<li>officers: likewise</li>
<li>pmcs: likewise</li>
</ul>
<hr />
<p>
[gstein] Reminder: discuss legal liability for committers, PMC
members, ASF members, and officers and directors. Note the last
three are covered by section 12.1 of the Bylaws (but committers
and PMC members are not obviously discussed). Conversely to the
liability, discuss the indemnification and coverage the ASF
provides to these various parties. And does that cover people
outside the jurisdiction of Delaware law? How far?
</p>
<hr />
<p>
[gstein] Doing a dump of "why PMC Chairs are officers of the
corporation":
</p>
<pre>
From: Greg Stein <[EMAIL PROTECTED]>
Subject: officers and liability
Date: Tue, 29 Oct 2002 15:28:15 -0800
On Mon, Oct 28, 2002 at 03:33:19PM -0500, someone wrote:
> On Thursday, October 24, 2002, at 03:55 PM, Roy T. Fielding wrote:
> > On Thursday, October 24, 2002, at 12:07 AM, someone wrote:
> >> On Thursday, October 24, 2002, at 02:41 AM, Greg Stein wrote:
> >> ... the Bylaws, Veeps are definitely officers. ...
> >>
> >> It might be preferable then that PMC chairs not be VP.
> >
> > Absolutely not! That is the whole basis of letting PMCs manage
> > portions of the ASF code without technical interference from the
> > board/members.
>
> I certainly don't pretend to have any competence in corp. governance
> law. I assume Roy knows his stuff about this all. I'd love to be
> educated. How does the officer/non-officer status of a PMC chair have
> any effect on the board's level of technical oversight - I'd have
> assumed that was entirely a matter for the board to configure within
> the limits of their model of their responsibilities - legal and
> otherwise. I can't image that they gain much liability protection by
> making an officer the head of a PMC? This structure seems to only
> increases the number of parties personally at risk when the foundation
> is sued. I am probably missing something.
An officer of the corporation is, by definition, acting on behalf of the
corporation. So the oversight that the ASF requires is occurring (oversight
is not embodied in the Board, but the ASF as a whole; the Board is just the
main driver of corporate affairs).
And since the officer is acting on behalf of the corporation, there is no
personal liability -- standard corporate assumption of liability occurs. If
the officer was *not* acting in accordance with their stated role, then yes:
they would be personally liable.
Since the ASF is assuming liability, that is where our cash hoard comes in,
in case of problems.
Does that help to clear things up?
-------------------------------
From: "Roy T. Fielding" <[EMAIL PROTECTED]>
Subject: Re: officers and liability
Date: Tue, 29 Oct 2002 15:58:43 -0800
What Greg said, with the addition that officers and members are
further indemnified in accordance with our bylaws (meaning we also
take care of their legal expenses if sued do to their role's actions).
PMC chairs must be officers because the board can only delegate things
to employees or officers. It is impossible to delegate authority to
someone who has no authority.
[these musings are based on my recollection of discussions with Drew
when we set up the foundation]
....Roy
</pre>
<hr />
<div align="center">
<small>All portions copyright © 2002 by the Apache Software
Foundation.
All rights reserved.</small>
</div>
</body>
</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
