husted 02/05/27 20:48:01
Modified: xdocs/site vendors.xml roles.xml proposal.xml guides.xml
decisions.xml
Log:
Update vendor support page. Relink as "Third-Party Support".
Update language to use "Contributor" in place of "Developer" so as to
agree with vocabulary of ASF Contributor license.
Revision Changes Path
1.3 +104 -48 jakarta-site2/xdocs/site/vendors.xml
Index: vendors.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/vendors.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- vendors.xml 15 May 2002 18:48:39 -0000 1.2
+++ vendors.xml 28 May 2002 03:48:00 -0000 1.3
@@ -3,76 +3,132 @@
<properties>
<author email="[EMAIL PROTECTED]">Andrew C. Oliver</author>
- <title>Vendor Support for Jakarta software</title>
+ <author email="[EMAIL PROTECTED]">Ted Husted</author>
+ <title>Third-Party Support for Jakarta Products</title>
</properties>
<body>
-<section name="Vendor Support">
-
+<section name="Third-Party Support">
<p>
-Is your company thinking of taking "the plunge" into more affordable,
-higher quality opensource solutions? You're not alone. Are you
-worried about support? Volunteer answered mail lists aren't going
-to sell your boss? Well these companies can help you by supporting
-and/or providing complete solutions based on <a href="http://jakarta.apache.org";>
-Jakarta</a>.
+<b>This listing is provided as a reference only. No endorsements given
+or implied. If you would like to be added to this list, or removed, please
+contact <a
href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</a>.
+Pages linked must specifically cite support for one or more Jakarta products.
+</b>
</p>
-
<p>
-Being mentioned here is not an indication of official "endorsement"
-by the Apache Group, but is instead provided as a public service.
-If you would like to be added to this list, or removed, please contact
-<a href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</a>.
+Is your company thinking of taking "the plunge" into more affordable,
+high-quality, open source software solutions? You're not alone. Are you
+worried about support? Volunteer-answered mail lists aren't going
+to sell your boss? These companies may be able to help you by providing
+developer support or by providing complete solutions based on
+<a href="http://jakarta.apache.org";>Jakarta</a> products.
</p>
-
</section>
-<section name="Complete solution providers (alphabetical order)">
- <p>
- Complete solution providers analyze your businesses areas of needs or take
- on specific projects and provide end-to-end solutions including project
- management, analysis, and technical expertise.
- </p>
+<section name="Developer Support (alphabetical order)">
+<p>
+Developer Support providers focus on helping end-users or developers
+solve particular problems with a product, usually involving installation,
+configuration, or customization. These are often the same types of
+questions handled on the volunteer lists, but with a guaranteed, confidential
+response.
+</p>
<hr size="1" noshade="noshade" />
- <p>
- <ul>
- <li><a href="http://www.superlinksoftware.com";>SuperLink Software,
Inc.</a> -</li>
- <li>
- providing complete solutions based on Jakarta and <a
href="http://xml.apache.org";>XML</a> including dynamic Java/XML-based reporting
solutions outputting to Microsoft Excel and web applications.
- </li>
- <li>Raleigh, NC. (USA)</li>
- <li>acoliver at apache dot org</li>
+ <p>
+ <ul>
+ <li><b>company name/website</b>
+ <ul>
+ <li>brief description (<5x80 char lines)</li>
+ <li>City/State/Country</li>
+ <li>email contact</li>
</ul>
- </p>
+ </li>
+ </ul>
+ </p>
<hr size="1" noshade="noshade" />
<p>
<ul>
- <li>company name/website</li>
- <li>brief description (<5x80 char lines)</li>
- <li>City/State/Country</li>
- <li>email contact</li>
+ <li><a
href="http://www.multitask.com.au/default.html?page=mtSOS";><b>Supporting Open
Source</b></a>
+ <ul>
+ <li>We are providing support services to clients in a variety of Open Source
projects including various elements of the Apache Software Foundation's Jakarta
project: Struts, Ant, Tomcat, Latka, Maven, Log4J.</li>
+ <li>Sydney AU</li>
+ <li>info at multitask.com.au</li>
+ </ul>
+ </li>
</ul>
</p>
+<hr size="1" noshade="noshade" />
</section>
+<section name="Complete solution providers (alphabetical order)">
+<p>
+Complete Solution providers analyze your businesses areas of needs or take
+on specific projects and provide end-to-end solutions including project
+management, analysis, and technical expertise.
+</p>
+<hr size="1" noshade="noshade" />
+ <p>
+ <ul>
+ <li><b>company name/website</b>
+ <ul>
+ <li>brief description (<5x80 char lines)</li>
+ <li>City/State/Country</li>
+ <li>email contact</li>
+ </ul>
+ </li>
+ </ul>
+ </p>
+<p>
+<hr size="1" noshade="noshade" />
+<ul>
+ <li><a href="http://www.superlinksoftware.com";><b>SuperLink Software, Inc.</b></a>
+ <ul>
+ <li>
+ providing complete solutions based on Jakarta and <a
href="http://xml.apache.org";>XML</a> including dynamic Java/XML-based reporting
solutions outputting to Microsoft Excel and web applications.
+ </li>
+ <li>Raleigh NC US</li>
+ <li>acoliver at apache dot org</li>
+ </ul>
+ </li>
+</ul>
+</p>
+<hr size="1" noshade="noshade" />
+</section>
-<section name="Specialized solution providers (alphabetical order)">
- <p>
- Specialized solution providers focus on particular technical areas.
- For instance a Specialized solution provider specializing in Log4J would
- only provide services and consulting for projects directly related to
- Log4J.
- </p>
+<section name="Specialized Solution providers (alphabetical order)">
+<p>
+Specialized Solution providers focus on particular technical areas.
+For instance a Specialized solution provider specializing in Log4J would
+only provide services and consulting for projects directly related to
+Log4J.
+</p>
<hr size="1" noshade="noshade" />
- <p>
- <ul>
- <li>company name/website</li>
- <li>brief description (<5x80 char lines)</li>
- <li>City/State/Country</li>
- <li>email contact</li>
+ <p>
+ <ul>
+ <li><b>company name/website</b>
+ <ul>
+ <li>brief description (<5x80 char lines)</li>
+ <li>City/State/Country</li>
+ <li>email contact</li>
</ul>
- </p>
+ </li>
+ </ul>
+ </p>
+<hr size="1" noshade="noshade" />
+ <p>
+ <ul>
+ <li><a href="http://www.husted.com";><b>Husted dot Com</b></a>
+ <ul>
+ <li>Jakarta Struts Consulting</li>
+ <li>Fairport NY US</li>
+ <li>ted at husted.com</li>
+ </ul>
+ </li>
+ </ul>
+ </p>
+<hr size="1" noshade="noshade" />
</section>
</body>
1.7 +13 -13 jakarta-site2/xdocs/site/roles.xml
Index: roles.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/roles.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- roles.xml 15 Jan 2002 22:55:36 -0000 1.6
+++ roles.xml 28 May 2002 03:48:00 -0000 1.7
@@ -29,15 +29,15 @@
<p>
When a user starts to contribute code or documentation patches, they
- become a developer.
+ become a Contributor.
</p>
- <h2>Developers</h2>
+ <h2>Contributors</h2>
<p>
- Developers are the people who write code or documentation patches or
- contribute positively to the project in other ways. A developer's
- contribution is always recognized. In source code, all developers
+ Contributors are the people who write code or documentation patches or
+ contribute positively to the project in other ways. A volunteer's
+ contribution is always recognized. In source code, all volunteers
who contribute to a source file may add their name to the list of
authors for that file.
</p>
@@ -45,7 +45,7 @@
<h2>Committers</h2>
<p>
- Developers who give frequent and valuable contributions to a
+ Contributors who give frequent and valuable contributions to a
subproject of the Project can have their status promoted to that of
a "<em>Committer</em>" for that subproject. A Committer
has write access to the source code repository and gains voting
@@ -53,21 +53,21 @@
</p>
<p>
- In order for a Developer to become a Committer, another Committer
- can nominate that Developer or the Developer can ask for it.
+ In order for a Contributor to become a Committer, another Committer
+ can nominate that Contributor or the Contributor can ask for it.
</p>
<p>
- Once a Developer is nominated, all of the Committers for a subproject
+ Once a Contributor is nominated, all of the Committers for a subproject
will vote. If there are at least 3 positive votes and no negative
- votes, the Developer is converted into a Committer and given write
+ votes, the Contributor is converted into a Committer and given write
access to the source code repository for that subproject. This is an
- example offer letter that should be sent to the developer after
+ example offer letter that should be sent to the volunteer after
3 positive votes have been received:
</p>
<source><![CDATA[
-Dear Developer,
+Dear Contributor,
The Jakarta project would like to offer you commit privileges.
We have been impressed with your contributions up till now, and
@@ -175,7 +175,7 @@
At times, Committers may go inactive for a variety of reasons. A
Committer that has been inactive for 6 months or more may lose their
status as a Committer. Getting access back is as simple as
- re-requesting it on the projects developer mailing list.
+ re-requesting it on the project's Developer mailing list.
</p>
<p>
1.4 +22 -22 jakarta-site2/xdocs/site/proposal.xml
Index: proposal.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/proposal.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- proposal.xml 16 Apr 2001 09:08:51 -0000 1.3
+++ proposal.xml 28 May 2002 03:48:00 -0000 1.4
@@ -141,28 +141,28 @@
When a user starts to contribute code or documentation patches, they
become a developer.
</p>
-<h2><a name="roles/developers">Developers</a></h2>
+<h2><a name="roles/developers">Contributors</a></h2>
<p>
-Developers are the people who write code or documentation patches or
-contribute positively to the project in other ways. A developer's
-contribution is always recognized. In source code, all developers
+Contributors are the people who write code or documentation patches or
+contribute positively to the project in other ways. A volunteer's
+contribution is always recognized. In source code, all volunteers
who contribute to a source file may add their name to the list of
authors for that file.
</p>
<h2><a name="roles/committers">Committers</a></h2>
<p>
-Developers who give frequent and valuable contributions to a
+Contributors who give frequent and valuable contributions to a
subproject of the Project can have their status promoted to that of
a "<em>Committer</em>" for that subproject. A Committer
has write access to the source code repository and gains voting
rights allowing them to affect the future of the subproject.
</p>
<p>
-In order for a Developer to become a Committer, another Committer
-can nominate that Developer or the Developer can ask for it. Once a
-Developer is nominated, all of the Committers for a subproject will
+In order for a Contributor to become a Committer, another Committer
+can nominate that Contributor or the Contributor can ask for it. Once a
+Contributor is nominated, all of the Committers for a subproject will
vote. If there are at least <a href="#decisions/voting/other"> 3 positive votes and
no negative votes</a>,
-the Developer is converted into a Committer and given write access
+the Contributor is converted into a Committer and given write access
to the source code repository for that subproject. <font color="#800000">Before
receiving write access, a Committer must also affirm that they have read and
understood these guidelines, and agree to abide by
their terms, as they may be revised from time to time.</font>
</p>
@@ -258,7 +258,7 @@
<tr><td>
<blockquote>
<p>
-Developer lists are for the developers of the project. On these
+Developer lists are for the contributors to the project. On these
lists suggestions and comments for code changes are discussed and
action items are raised and voted on. For the developer community,
these lists are the very center of the project where all the
@@ -290,7 +290,7 @@
<tr><td>
<blockquote>
<p>
-All <a href="http://jakarta.apache.org/site/roles.html";>Developers</a> are
encouraged
+All <a href="http://jakarta.apache.org/site/roles.html";>Contributors</a> are
encouraged
to participate in decisions, but the decision itself is made by
those that have <a href="http://jakarta.apache.org/site/roles.html";>Committer</a>
status in the Project. In other words, the Project is a
@@ -316,23 +316,23 @@
<p>
Long term plans are simply announcements that group members are
working on particular issues related to the Project. These are not
-voted on, but Developers who do not agree with a particular plan, or
+voted on, but Committers who do not agree with a particular plan, or
think that an alternative plan would be better, are obligated to
inform the group of their feelings.
</p>
<h3><a name="decisions/items/stplans">Short Term Plan<font
color="#800000">s</font></a></h3>
<p>
-Short term plans are announcements that a developer is working on a
+Short term plans are announcements that a volunteer is working on a
particular set of documentation or code files with the implication
-that other developers should avoid them or try to coordinate their
+that other volunteers should avoid them or try to coordinate their
changes.
</p>
<h3><a name="decisions/items/plan">Release Plan</a></h3>
<p>
-A release plan is used to keep all Developers aware of when a
+A release plan is used to keep all volunteers aware of when a
release is desired, who will be the Release Manager, when the
repository will be frozen to create a release, and other assorted
-information to keep Developers from tripping over each other. Lazy
+information to keep volunteers from tripping over each other. Lazy
majority decides each issue in a release plan<font color="#800000">, or lazy
consensus if the issue involves a product change</font>.
</p>
<h3><a name="decisions/items/testing">Release Testing</a></h3>
@@ -369,7 +369,7 @@
not only stating their opinion, they are also agreeing to help do
the work.
</p>
-<p><font color="#800000">Any Developer or Committer ("member") may call
for an action-item vote on the <a href="#communication/dev"> Developer mailing
list</a>. It is preferred that a vote be preceded by a formal proposal
+<p><font color="#800000">Any Contributor or Committer ("member") may call
for an action-item vote on the <a href="#communication/dev"> Developer mailing
list</a>. It is preferred that a vote be preceded by a formal proposal
offered for discussion purposes. The message announcing a vote should contain a
Subject beginning with "[VOTE]", and a distinctive one-line
summary corresponding to the <a href="#decisions/items"> action item</a> for the
vote.</font></p>
<p>Each vote <font color="#800000">on an action item</font> can be made in one of
<strike> three</strike> <font color="#800000">four</font> flavors:</p>
@@ -427,7 +427,7 @@
Any <strike>Developer</strike> member may vote on any <strike> issue or</strike>
action item <font color="#800000">or related issue</font>. <strike> However, the
only <b> binding</b> <b> votes</b> are those cast by a Committer.</strike> <strike>
If the vote is
about a change to the source code or documentation and the primary
-author is a Developer and not a Commit<font color="#800000">t</font>er, the primary
author of what
+author is a Contributor and not a Commit<font color="#800000">t</font>er, the
primary author of what
is being changed may also cast a binding vote on that
issue</strike><strike>.</strike> <font color="#800000">When voting on an action item,
the subproject's Committers may also include the word "binding" next to
their vote, to simplify a tally
if it is needed.</font>All
binding vetos <b> must</b> <font color="#800000">also</font> contain an
explanation of why
@@ -571,11 +571,11 @@
file includes information about release plans, a summary of code
changes committed since the last release, a list of proposed changes
that are under discussion, brief notes about items that individual
-developers are working on or want discussion about, and anything
+volunteers are working on or want discussion about, and anything
else that may be useful to help the group track progress.
</p>
<p>
-The active status files are automatically posted to the developer
+The active status files are automatically posted to the Developer
mailing lists three times per week.
</p>
<h2><a name="source/branches">Branches</a></h2>
@@ -607,13 +607,13 @@
Related changes should be committed as a group, or very closely
together. Half complete projects should never be committed to the
main branch of a development repository. All code changes must be
-successfully compiled on the developer's platform before being
+successfully compiled on the contributor's platform before being
committed. <font color="#800000">This includes XML code that is used to build
documentation.</font>
</p>
<p>
The current source code tree for a subproject should be capable of
complete compilation at all times. However, it is sometimes
-impossible for a developer on one platform to avoid breaking some
+impossible for a contributor on one platform to avoid breaking some
other platform when a change is committed. If it is anticipated that
a given change will break the build on some other platform, the
committer must indicate that in the commit message.
1.8 +1 -1 jakarta-site2/xdocs/site/guides.xml
Index: guides.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/guides.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- guides.xml 1 Apr 2002 11:20:57 -0000 1.7
+++ guides.xml 28 May 2002 03:48:01 -0000 1.8
@@ -99,7 +99,7 @@
<h2>Moderator's Guide</h2>
<p>What mailing list moderators need to know.</p>
-<h2>Developer's Guide</h2>
+<h2>Contributor's Guide</h2>
<ul>
<li><a href="http://www.apache.org/foundation/licence-FAQ.html";>Apache License
and Distribution FAQ</a>
<ul>
1.3 +12 -11 jakarta-site2/xdocs/site/decisions.xml
Index: decisions.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/decisions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- decisions.xml 15 Mar 2001 06:54:39 -0000 1.2
+++ decisions.xml 28 May 2002 03:48:01 -0000 1.3
@@ -10,7 +10,7 @@
<section name="Decision Making">
<p>
- All <a href="./roles.html">Developers</a> are encouraged
+ All <a href="./roles.html">Contributors</a> are encouraged
to participate in decisions, but the decision itself is made by
those that have <a href="./roles.html">Committer</a>
status in the Project. In other words, the Project is a
@@ -18,11 +18,12 @@
</p>
<p>
- Any Developer may vote on any issue or action item. However, the
- only binding votes are those cast by a Committer. If the vote is
- about a change to the source code or documentation and the primary
- author is a Developer and not a Commiter, the primary author of what
- is being changed may also cast a binding vote on that issue.
+ Any subscriber to the list may vote on any issue or
+ action item. However, the only binding votes are those cast by a
+ Committer. If the vote is about a change to the source code or
+ documentation and the primary uthor is a Contributor and not a
+ Committer, the primary author of whatis being changed may also
+ cast a binding vote on that issue.
</p>
<p>
@@ -100,7 +101,7 @@
<p>
Long term plans are simply announcements that group members are
working on particular issues related to the Project. These are not
- voted on, but Developers who do not agree with a particular plan, or
+ voted on, but Committers who do not agree with a particular plan, or
think that an alternative plan would be better, are obligated to
inform the group of their feelings.
</p>
@@ -108,19 +109,19 @@
<h3>Short Term Plan</h3>
<p>
- Short term plans are announcements that a developer is working on a
+ Short term plans are announcements that a volunteer is working on a
particular set of documentation or code files with the implication
- that other developers should avoid them or try to coordinate their
+ that other volunteers should avoid them or try to coordinate their
changes.
</p>
<h3>Release Plan</h3>
<p>
- A release plan is used to keep all Developers aware of when a
+ A release plan is used to keep all volunteers aware of when a
release is desired, who will be the release manager, when the
repository will be frozen to create a release, and other assorted
- information to keep Developers from tripping over each other. Lazy
+ information to keep volunteers from tripping over each other. Lazy
majority decides each issue in a release plan.
</p>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
