Author: crossley
Date: Sat Sep 13 22:46:04 2008
New Revision: 695118
URL: http://svn.apache.org/viewvc?rev=695118&view=rev
Log:
The term "project roles" is better as "project tasks".
Added:
forrest/trunk/site-author/content/xdocs/tasks.xml
- copied, changed from r695097,
forrest/trunk/site-author/content/xdocs/roles.xml
Removed:
forrest/trunk/site-author/content/xdocs/roles.xml
Modified:
forrest/trunk/site-author/content/.htaccess
forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml
forrest/trunk/site-author/content/xdocs/site.xml
forrest/trunk/site-author/status.xml
Modified: forrest/trunk/site-author/content/.htaccess
URL:
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/.htaccess?rev=695118&r1=695117&r2=695118&view=diff
==============================================================================
--- forrest/trunk/site-author/content/.htaccess (original)
+++ forrest/trunk/site-author/content/.htaccess Sat Sep 13 22:46:04 2008
@@ -34,6 +34,7 @@
Redirect /howto http://forrest.apache.org/docs_0_80/howto
# Some moved documents
+RedirectMatch ^/roles(.*) http://forrest.apache.org/tasks$1
# handle all DTDs etc.
<Files ~ "\.(dtd|mod)$">
Modified:
forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml?rev=695118&r1=695117&r2=695118&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml
(original)
+++ forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml
Sat Sep 13 22:46:04 2008
@@ -40,8 +40,8 @@
website.
</p>
<p>
- See other notes for the Documentation Coordinator
- <a href="site:roles">role</a>.
+ See other notes for the Documentation Coordination
+ <a href="site:tasks">tasks</a>.
</p>
</section>
<section id="forrestbot-local">
Modified: forrest/trunk/site-author/content/xdocs/site.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/site.xml?rev=695118&r1=695117&r2=695118&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/site.xml (original)
+++ forrest/trunk/site-author/content/xdocs/site.xml Sat Sep 13 22:46:04 2008
@@ -62,7 +62,7 @@
<actions href="#actions"/>
</guidelines>
<committed label="Being committed" href="committed.html"
description="Notes about contribution"/>
- <roles label="Project roles" href="roles.html" description="Tasks to
keep the project flowing"/>
+ <tasks label="Project tasks" href="tasks.html" description="Tasks to
keep the project flowing"/>
</project>
</getting-involved>
<infrastructure label="Resources and Infrastructure" tab="project"
Copied: forrest/trunk/site-author/content/xdocs/tasks.xml (from r695097,
forrest/trunk/site-author/content/xdocs/roles.xml)
URL:
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/tasks.xml?p2=forrest/trunk/site-author/content/xdocs/tasks.xml&p1=forrest/trunk/site-author/content/xdocs/roles.xml&r1=695097&r2=695118&rev=695118&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/roles.xml (original)
+++ forrest/trunk/site-author/content/xdocs/tasks.xml Sat Sep 13 22:46:04 2008
@@ -19,7 +19,7 @@
"http://forrest.apache.org/dtd/document-v20.dtd";>
<document>
<header>
- <title>Project roles</title>
+ <title>Project tasks</title>
</header>
<body>
<section id="overview">
@@ -27,13 +27,13 @@
<p>
There are many tasks that need to be done to keep the project flowing.
With the tasks being well-defined, the hope is that various people will
- be able to assist to carry out the role and so not rely on a couple of
+ be able to assist to carry out the tasks and so not rely on a couple of
individuals to do all the work.
</p>
<p>
There are no roles for "leadership" of technical areas. We don't have
the concept of leadership at the ASF. Rather these are "functional
- roles".
+ tasks".
</p>
<p>
This is not intended to put pressure on people to force them to do work
@@ -42,34 +42,34 @@
healthy project.
</p>
<p>
- Most roles have minimal tasks and are not too onerous. For example, for
- the "Documentation Coordinator", the only job might be to publish the
+ Most tasks are not too onerous. For example, for
+ the "Documentation Coordination", the only job might be to publish the
documentation every Friday. Sure it can be done at other times and
other
people can do it too, but at least it gets done once per week.
</p>
<p>
- Having a person doing a role does not mean that everyone can leave it
to
+ Having a person doing a task does not mean that everyone can leave it
to
them and rely on them. Anyone else can dive in and do the job (for
example, publish the docs twice per week). The more people who are
- familiar with the role, the better. Perhaps the person who is primarily
- doing that role will notice that there can be improvements to how they
+ familiar with the task, the better. Perhaps the person who is primarily
+ doing that task will notice that there can be improvements to how they
are doing it.
</p>
<p>
- If a person is dissatisfied with the way a particular role is being
done
+ If a person is dissatisfied with the way a particular task is being
done
then find a way to offer constructive criticism, perhaps by assisting
or
- by enhancing the role documentation.
+ by enhancing the task documentation.
</p>
<p>
- Most of the roles (except of course the Developer role) can only be
+ Most of the tasks (except of course the Developer role) can only be
carried out by PMC members because commit access is required.
</p>
</section>
- <section id="roles">
- <title>The roles</title>
+ <section id="tasks">
+ <title>The tasks</title>
<p>
- These are the main roles, including the obvious ones. There are
probably
- other roles that need to be defined also. Each role should have some
+ These are the main tasks, including the obvious ones. There are
probably
+ other tasks that need to be defined also. Each task should have some
continually enhanced documentation about it, so that any person can do
the tasks.
</p>
@@ -99,8 +99,8 @@
as possible.
</p>
</section>
- <section id="forrest-friday-coordinator">
- <title>ForrestFriday Coordinator</title>
+ <section id="forrest-friday-coordination">
+ <title>ForrestFriday Coordination</title>
<p>
The tasks are defined in
<a href="site:forrest-friday">ForrestFriday</a>.
@@ -114,12 +114,12 @@
Ensure that the session is summarised.
</p>
<p>
- This role can possibly be done by someone who is not a committer.
+ This task can possibly be done by someone who is not a committer.
However, a logfile and summary need to be committed to SVN.
</p>
</section>
- <section id="issue-tracker-coordinator">
- <title>Issue Tracker Coordinator</title>
+ <section id="issue-tracker-coordination">
+ <title>Issue Tracker Coordination</title>
<p>
Add new Components, e.g. for each new plugin.
</p>
@@ -144,8 +144,8 @@
are scheduled for the upcoming release.
</p>
</section>
- <section id="documentation-coordinator">
- <title>Documentation Coordinator</title>
+ <section id="documentation-coordination">
+ <title>Documentation Coordination</title>
<p>
Publish the documentation at least once per week.
</p>
@@ -156,7 +156,7 @@
regularly generated from it.
</p>
<p>
- This role is not actually about doing the documentation. That should
+ This task is not actually about doing the documentation. That should
be up to everyone.
</p>
<p>
@@ -165,8 +165,8 @@
documentation</a>.
</p>
</section>
- <section id="subversion-monitor">
- <title>Subversion Monitor</title>
+ <section id="subversion-monitoring">
+ <title>Subversion Monitoring</title>
<p>
Ensure that svn:eol-style settings are "native" for all text files.
</p>
@@ -185,8 +185,8 @@
SVN in the "tools" directory.
</p>
</section>
- <section id="legal-monitor">
- <title>Legal Monitor</title>
+ <section id="legal-monitoring">
+ <title>Legal Monitoring</title>
<p>
Regularly run a script which verifies and inserts missing license
headers to source files.
@@ -209,7 +209,7 @@
<section id="developer">
<title>Developer</title>
<p>
- The above roles are only for PMC Members. How can the Developers be
+ The above tasks are only for PMC Members. How can the Developers be
involved? That is easy: do the Developer Role.
</p>
<p>
Modified: forrest/trunk/site-author/status.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/site-author/status.xml?rev=695118&r1=695117&r2=695118&view=diff
==============================================================================
--- forrest/trunk/site-author/status.xml (original)
+++ forrest/trunk/site-author/status.xml Sat Sep 13 22:46:04 2008
@@ -453,7 +453,7 @@
</action>
<action context="docs" type="add" dev="DC">
Add document about project
- <link href="site:roles">roles</link>.
+ <link href="site:tasks">tasks</link>.
</action>
<action context="code" type="update" dev="DC" fixes-bug="FOR-824"
due-to="Steve Masover">
Howto-v20 now properly handles a/@class=fork etc. attribute to enable
