[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gforge-commits] gforge/docs/docbook/docbook/user_guide/project_functio
|
From: |
gsmet |
|
Subject: |
[Gforge-commits] gforge/docs/docbook/docbook/user_guide/project_functions cvs.xml, 1.1, 1.2 docman.xml, 1.1, 1.2 file_releases.xml, 1.1, 1.2 forums.xml, 1.1, 1.2 mailing_lists.xml, 1.1, 1.2 news.xml, 1.1, 1.2 project_admin.xml, 1.1, 1.2 project_summary.xml, 1.1, 1.2 task_manager.xml, 1.1, 1.2 tracker.xml, 1.1, 1.2 |
|
Date: |
Tue, 16 Mar 2004 12:50:23 -0600 |
Update of
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions
In directory db.perdue.net:/tmp/cvs-serv10055/user_guide/project_functions
Modified Files:
cvs.xml docman.xml file_releases.xml forums.xml
mailing_lists.xml news.xml project_admin.xml
project_summary.xml task_manager.xml tracker.xml
Log Message:
Fixed a lot of typos and updated some outdated information
Index: cvs.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/cvs.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- cvs.xml 2 Mar 2004 16:58:39 -0000 1.1
+++ cvs.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -4,6 +4,9 @@
The CVS button shows a page that contains information on how to
access the CVS repository. Use this information to configure your client for
CVS access.
</para>
<para>
+ This page also displays some statistics about the selected
project's CVS tree.
+ </para>
+ <para>
The Browse CVS Repository link opens the viewcvs web interface,
where you can view the CVS repository, view differences between revisions,
download versions of a file.
</para>
<note>
Index: docman.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/docman.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- docman.xml 2 Mar 2004 16:58:39 -0000 1.1
+++ docman.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -1,7 +1,7 @@
<section id="ug_project_docman">
<title>Document Manager</title>
<para>
- The Document Manager provided with Gforge gives you a simple
way to publish documents on the site.
+ The Document Manager provided with GForge gives you a simple
way to publish documents on the site.
</para>
<section>
<title>Submit new documentation</title>
@@ -12,7 +12,7 @@
<varlistentry>
<term>Document Title</term>
<listitem>
- <para>The document title refers to the
relatively brief title of th document</para>
+ <para>The document title refers to the
relatively brief title of the document</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -36,7 +36,7 @@
<varlistentry>
<term>Group that document belongs in</term>
<listitem>
- <para>You should select here the group
of the document.</para>
+ <para>You should select here the group
of the document. This feature is used to categorize documents.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -47,11 +47,11 @@
<section>
<title>Viewing existing docs</title>
<para>
- The viewing existing docs shows you a list of documents
published and approved for viewing; grouped by Document groups. You can click
on a document to view the entire content.
+ The View Documentation page shows you a list of
documents published and approved for viewing; grouped by Document groups. You
can click on a document to view the entire content.
</para>
</section>
<section>
- <title>Admin Doc</title>
+ <title>Admin</title>
<para>
Clicking on this will present you with a page showing
pending and active documents. In order to allow users to submit a document, you
must first set up the document groups for the project.
</para>
@@ -62,7 +62,7 @@
<varlistentry>
<term>Approve/publish pending submissions</term>
<listitem>
- <para>The Pendig Submissions list shows
the list of submissions that are waiting for your approval. Clicking on the
Document name, the Edit Document form will be displayed.</para>
+ <para>The Pending Submissions list
shows the list of submissions that are waiting for your approval. Clicking on
the document name, the Edit Document form will be displayed.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -73,7 +73,7 @@
<varlistentry>
<term>Active
Documents</term>
<listitem>
- <para>Active
Documents are displayed in the View Documentation list</para>
+ <para>Active
Documents are displayed in the View Documentation list.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -85,7 +85,7 @@
<varlistentry>
<term>Hidden
Documents</term>
<listitem>
- <para>Hidden
documents are not displayed</para>
+ <para>Hidden
documents are not displayed.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -97,7 +97,7 @@
<varlistentry>
<term>Private
Documents</term>
<listitem>
- <para>Private
documents are displayed only for members of the project</para>
+ <para>Private
documents are displayed only for members of the project.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -107,7 +107,7 @@
<term>Edit Document Groups</term>
<listitem>
<para>
- Clicking on this will present
you with a box and a button to add document groups, and it also shows the
document groups associated with this project. Submit as many document classes
as you wish - eg Howto, Release notes, FAQ, etc. These groups will be the
catagories the documents will fall into when users submit documents.
+ Clicking on this will present
you with a box and a button to add document groups, and it also shows the
document groups associated with this project. Submit as many document
categories as you wish - eg Howto, Release notes, FAQ, etc. These groups will
be the categories the documents will fall into when users submit documents.
</para>
</listitem>
</varlistentry>
@@ -119,7 +119,7 @@
When you select a document from one of the lists, a
form will be displayed. In this form you can change the Document Title, the
Short Description, the Language, the Document Group and the State.
</para>
<para>
- If the Document is a text file with .txt, .html or .htm
extension, a textbox appreas where you can edit the content of the document.
+ If the Document is a text file with .txt, .html or .htm
extension, a textbox appears where you can edit the content of the document.
</para>
<para>
If the Document is a binary document, you can upload a
new version of the document.
Index: file_releases.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/file_releases.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- file_releases.xml 2 Mar 2004 16:58:39 -0000 1.1
+++ file_releases.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -4,7 +4,7 @@
<section>
<title>Introduction</title>
<para>
- The File Releases System (FRS) is used to upload files
to the gforge site and to make these files available to the users in an easy
and efficient way.
+ The File Releases System (FRS) is used to upload files
to the GForge site and to make these files available to the users in an easy
and efficient way.
</para>
<para>
Files can be divided in different packages, and every
single package can be monitored by the users; these users will receive an email
every time a new file has been added to the package.
@@ -13,7 +13,7 @@
<section>
<title>Administration</title>
<para>
- The FRS system allows you to upload file to gforge and
make this file available to the public.
+ The FRS system allows you to upload file to GForge and
make this file available to the public.
</para>
<para>
You have to define a package before you can release a
file. A package should have a descriptive name for the project, e.g. gforge3.
@@ -49,7 +49,7 @@
<varlistentry>
<term>File Name</term>
<listitem>
- <para>Click the browse button to select
the file to upload. In some browsers you must select the file in the
file-upload dialogo and click OK. Double-clicking doesn't register the
file.</para>
+ <para>Click the browse button to select
the file to upload. In some browsers you must select the file in the
file-upload dialog and click OK. Double-clicking doesn't register the
file.</para>
<note>
<para>You can't upload file
that exceed the UploadFile Limit in php.ini.</para>
</note>
@@ -81,7 +81,7 @@
</varlistentry>
</variablelist>
<para>
- Click the Release File button. Your file will now
appire in the list of files in the File section.
+ Click the Release File button. Your file will now
appear in the list of files in the File section.
</para>
</section>
</section>
\ No newline at end of file
Index: forums.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/forums.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- forums.xml 2 Mar 2004 16:58:39 -0000 1.1
+++ forums.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -29,7 +29,7 @@
New forums can be created using the Admin section of
the forum. When a new forum is created, you must insert a name of the forum,
the description of the forum, select if the forum is public or private and if
anonymous posts are allowed on the forum.
</para>
<para>
- Public forums are visibile only to project members. If
Anonymous posts are enabled, everybody can post messages to the forum, even
users that are not logged it.
+ Public forums are visible only to project members. If
Anonymous posts are enabled, everybody can post messages to the forum, even
users that are not logged in.
</para>
<para>
You can also insert an email address where all posts
will be sent.
@@ -53,7 +53,7 @@
<varlistentry>
<term>Flat</term>
<listitem>
- <para>Similar to Nested, the messages
will be showed in cronological order.</para>
+ <para>Similar to Nested, the messages
will be showed in chronological order.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -76,7 +76,7 @@
<section>
<title>Available options</title>
<para>
- The forums of gforge have 2 very powerful options:
+ The forums of GForge have 2 very powerful options:
</para>
<variablelist>
<varlistentry>
@@ -89,7 +89,7 @@
<term>Monitor forum</term>
<listitem>
<para>You can select to monitor the
forum by clicking on the Monitor Forum button.</para>
- <para>If this option is enabled, every
post to the forum will be sent to you by email.This allows you to be informed
about new messages without beeing logged on to gforge. The name of the
monitored forum will appear in the users homepage in the section Monitored
Forums.</para>
+ <para>If this option is enabled, every
post to the forum will be sent to you by email.This allows you to be informed
about new messages without being logged on to gforge. The name of the monitored
forum will appear in the users homepage in the section Monitored Forums.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -97,7 +97,7 @@
<section>
<title>Forum admin</title>
<para>
- Clicking on the <guimenuitem>Forum Admin</guimenuitem>
link presents you with links to <guimenuitem>Add Forum, Delete
Message</guimenuitem> or <guimenuitem>Update Forum Info/Status</guimenuitem>.
+ Clicking on the <guimenuitem>Forum Admin</guimenuitem>
link presents you with links to <guimenuitem>Add Forum</guimenuitem>,
<guimenuitem>Delete Message</guimenuitem> or <guimenuitem>Update Forum
Info/Status</guimenuitem>.
</para>
<section>
<title>Add Forum</title>
@@ -121,7 +121,7 @@
<section>
<title>Searching</title>
<para>
- When using a forum, a voice
<guimenuitem>Forum</guimenuitem> will appear in the search combo box. Selecting
forum and inserting a text in the search box allows you to search through the
text data of the forum.
+ When using a forum, a voice
<guimenuitem>Forum</guimenuitem> will appear in the search combo box. Selecting
<guimenuitem>Forum</guimenuitem> and inserting a text in the search box allows
you to search through the text data of the forum.
</para>
</section>
</section>
\ No newline at end of file
Index: mailing_lists.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/mailing_lists.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- mailing_lists.xml 2 Mar 2004 16:58:40 -0000 1.1
+++ mailing_lists.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -4,21 +4,35 @@
This is where you will set up and administer the mailing lists
associated with the project.
</para>
<section>
- <title>Admin</title>
+ <title>Main page</title>
<para>
- This brings you to the Mail Admin page, where the
following options are available to you.
+ This page shows the list of available mailing lists.
</para>
- </section>
- <section>
- <title>Add Mailing List</title>
<para>
- Clicking here will allow you to create a new mailing
list. You can specify if it is to be made public (people who are not members of
the project can see and/or join it) or not. You can also add a description of
the list.
+ Clicking on List Name Archives will allow you to browse
the archives of the selected mailing list.
+ </para>
+ <para>
+ You can subscribe, unsubscribe or edit your preferences
for a specific mailing list by clicking the appropriate link.
</para>
</section>
<section>
- <title>Administrate/Update Lists</title>
+ <title>Admin</title>
<para>
- This allows you to change the description of the list,
the state of the list, and by clicking on <guimenuitem>Administrate this list
in GNU Mailman</guimenuitem> you can add members to the mailing list, set the
properties of the list, posting policies and so forth.
+ This brings you to the Mail Admin page, where the
following options are available to you.
</para>
+ <variablelist>
+ <varlistentry>
+ <term>Add Mailing List</term>
+ <listitem>
+ <para>Clicking here will allow you to
create a new mailing list. You can specify if it is to be made public (people
who are not members of the project can see and/or join it) or not. You can also
add a description of the list. You will receive an email with the
administration password of the list.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Administrate/Update Lists</term>
+ <listitem>
+ <para>This allows you to change the
description of the list, the state of the list, and by clicking on
<guimenuitem>Administrate this list in GNU Mailman</guimenuitem> you can add
members to the mailing list, set the properties of the list, posting policies
and so forth.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
</section>
\ No newline at end of file
Index: news.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/news.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- news.xml 2 Mar 2004 16:58:40 -0000 1.1
+++ news.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -1,22 +1,22 @@
<section id="ug_project_news">
<title>News</title>
<para>
- The news section allows you to insert news relative to your
project. News can be monitored similar to tracker items, forums. News will be
displayed on the project homepage and also on the site homepage, if the side
administrators approve the news.
+ The news section allows you to insert news relative to your
project. News can be monitored similar to tracker items, forums. News will be
displayed on the project homepage and also on the site homepage, if the site
administrators approve the news.
</para>
<para>
News are used generally to announce software releases or to
announce significant changes in the software or milestones.
</para>
<section>
<title>Inserting a news item</title>
- <para>You can insert a NewsByte by clicking on the Submit
link.</para>
+ <para>You can insert a news item by clicking on the Submit
link.</para>
<para>You can post news about your project if you are an admin
on your project.</para>
- <para>All posts for your project will appear instantly on your
project summary page. Posts that are of special interest to the community will
have to be approved by a member of the gforge news team before they will appear
on the gforge home page.</para>
+ <para>All posts for your project will appear instantly on your
project summary page. Posts that are of special interest to the community will
have to be approved by a member of the gforge news team before they will appear
on the GForge home page.</para>
<para>You may include URLs, but not HTML in your submissions.
URLs that start with http:// are made clickable.</para>
- <para>The NewsByte will go to the News Admin for approval for
publication.</para>
+ <para>The news item will go to the News Admin for approval for
publication.</para>
</section>
<section>
<title>Modifying/Approving a news item</title>
- <para>You can modify or/and approva a NewsByte by clicking on
the Admin Link.</para>
- <para>You can select the status of the News: Displayed or
Delete (the news will be deleted), you can insert the Subject (title) of the
newsByte and the details.</para>
+ <para>You can modify or/and approve a news by clicking on the
Admin Link.</para>
+ <para>You can select the status of the news: Displayed or
Deleted (the news will be deleted), you can insert the Subject (title) and the
details.</para>
</section>
</section>
\ No newline at end of file
Index: project_admin.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/project_admin.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- project_admin.xml 2 Mar 2004 16:58:40 -0000 1.1
+++ project_admin.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -12,7 +12,7 @@
The Project admin page is available by clicking on the
Admin tab.
</para>
<para>
- Clicking here will present you with links to Admin,
User Permissions, Edit Public Info, Project History, VHOSTS, Edit/Release
Files, Post Jobs, Edit Jobs, Edit MultiMedia Data, Database Admin and Stats.
The Project Admin page is only accessible to members of the project who have
been granted administrator privileges. By default, the person who registers the
project is given admin privileges. Other members can be granted admin rights by
the project administrator(s).
+ Clicking here will present you with links to Admin,
User Permissions, Edit Public Info, Project History, VHOSTS, Post Jobs, Edit
Jobs, Edit MultiMedia Data, Database Admin and Stats. The Project Admin page is
only accessible to members of the project who have been granted administrator
privileges. By default, the person who registers the project is given admin
privileges. Other members can be granted admin rights by the project
administrator(s).
</para>
</section>
<section>
@@ -34,7 +34,7 @@
In order for people to be able
to find the project, it must be classified in the Trove Map. This is basically
a set of categories in which like projects are grouped.
</para>
<para>
- Clicking on Edit Trove
Categorization presets a page which allows you to select the category(s) to
which the project belongs (select as many as possible).
+ Clicking on Edit Trove
Categorization presets a page which allows you to select the category(s) to
which the project belongs (select as many as needed).
</para>
<para>
Clicking Submit All Category
Changes will set the categorizations, and you will be returned to the Project
Admin page. You can change the trove categorizations during the lifetime of the
project by following the above steps, as the project moves through its life.
@@ -64,7 +64,7 @@
<section>
<title>Edit Public Info</title>
<para>
- This page enables the project admin to select the
information that is visible to members of the public and the project. It is
possible to select the utilities that are used, by the project, so that any
that are not desired are not presented on the web page. Specifically it is
possible to disable/enable:
+ This page enables the project admin to select the
information that is visible to the public and to the members of the project. It
is possible to select the utilities that are used by the project, so that any
that are not desired are not presented on the web page. Specifically it is
possible to disable/enable:
</para>
<itemizedlist>
<listitem><para>Mailing Lists</para></listitem>
@@ -149,4 +149,4 @@
</varlistentry>
</variablelist>
</section>
-</section>
+</section>
\ No newline at end of file
Index: project_summary.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/project_summary.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- project_summary.xml 2 Mar 2004 16:58:40 -0000 1.1
+++ project_summary.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -25,7 +25,7 @@
<varlistentry>
<term>Public areas</term>
<listitem>
- <para>For each Tool of Gforge, Summary
Information is displayed; e.g. Public Forums (1 message in 1 forums), Bugs (4
open, 12 total).</para>
+ <para>For each Tool of GForge, Summary
Information is displayed; e.g. Public Forums (1 message in 1 forum(s)), Bugs (4
open, 12 total).</para>
</listitem>
</varlistentry>
<varlistentry>
Index: task_manager.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/task_manager.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- task_manager.xml 2 Mar 2004 16:58:40 -0000 1.1
+++ task_manager.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -49,7 +49,7 @@
<varlistentry>
<term>Task Details</term>
<listitem>
- <para>You should insert here the most
detailed description possibile of the task.</para>
+ <para>You should insert here the most
detailed description possible of the task.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -106,7 +106,7 @@
</para>
<variablelist>
<varlistentry>
- <term>create new subprojects</term>
+ <term>Add a project</term>
<listitem>
<para>You can select if the subproject
is public (visibile to everyone) or not (visibile only to project
memebers).</para>
<para>This allows you to add a
subproject to a project, such as modules, documentation, etc.</para>
@@ -114,9 +114,9 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>update information</term>
+ <term>Update information</term>
<listitem>
- <para>Here you can select if the
project is public, private or deleted (visibile to nobody) and update the name
and description of the subjproject.</para>
+ <para>Here you can select if the
project is public, private or deleted (visible to nobody) and update the name
and description of the subproject.</para>
</listitem>
</varlistentry>
</variablelist>
Index: tracker.xml
===================================================================
RCS file:
/cvsroot/gforge/gforge/docs/docbook/docbook/user_guide/project_functions/tracker.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- tracker.xml 2 Mar 2004 16:58:39 -0000 1.1
+++ tracker.xml 16 Mar 2004 18:50:20 -0000 1.2
@@ -6,16 +6,16 @@
The Tracker is a generic system where you can store
items like bugs, feature requests, patch submissions, etc.
</para>
<para>
- In previous versions of the software, these items were
handled in separate software modules. Bugs, Enhancement Requests, Support
Requests and Patches handle the same type of data, so it was logical to create
an unique software module that can handle this types of data. New types of
trackers can be created when needed, e.g. Test Results, meeting minutes, etc.
+ In previous versions of the software, these items were
handled in separate software modules. Bugs, Enhancement Requests, Support
Requests and Patches handle the same type of data, so it was logical to create
an unique software module that can handle these types of data. New types of
trackers can be created when needed, e.g. Test Results, meeting minutes, etc.
</para>
<para>
You can use this system to track virtually any kind of
data, with each tracker having separate user, group, category, and permission
lists. You can also easily move items between trackers when needed.
</para>
<para>
- Trackers are referred to as <quote>Artifact
Types</quote> and individual pieces of data are <quote>Artifacts</quote>.
<quote>Bugs</quote> might be an Artifact Type, whiles a bug report would be an
Artifact. You can create as many Artifact Types as you want, but remember you
need to set up categories, groups, and permission for each type, which can get
time-consuming.
+ Trackers are referred to as <quote>Artifact
Types</quote> and individual pieces of data are <quote>Artifacts</quote>.
<quote>Bugs</quote> might be an Artifact Type, while a bug report would be an
Artifact. You can create as many Artifact Types as you want, but remember you
need to set up categories, groups, and permission for each type, which can get
time-consuming.
</para>
<para>
- When a project is created, gforge creates automatically
4 trackers:
+ When a project is created, GForge creates automatically
4 trackers:
</para>
<variablelist>
<varlistentry>
@@ -68,7 +68,7 @@
<varlistentry>
<term>Category</term>
<listitem>
- <para>The Category is generally used to
describe the function/module in which the bug appears. E.g for gforge, this
might be the items <quote>User Login</quote>, <quote>File releases</quote>,
<quote>Forums</quote>, <quote>Tracker</quote>, etc.</para>
+ <para>The Category is generally used to
describe the function/module in which the bug appears. E.g for GForge, this
might be the items <quote>User Login</quote>, <quote>File releases</quote>,
<quote>Forums</quote>, <quote>Tracker</quote>, etc.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -160,7 +160,7 @@
</varlistentry>
</variablelist>
<para>
- The Changelog on the bottom of the page shows in
cronological order the changes applied to the item. Also all followups can be
viewed.
+ The Changelog on the bottom of the page shows in
chronological order the changes applied to the item. Also all followups can be
viewed.
</para>
</section>
<section>
@@ -240,13 +240,13 @@
<varlistentry>
<term>Name</term>
<listitem>
- <para>The name
of the Tracker. This is the name displayed in the tracker list, e.g. Bug
Submittions.</para>
+ <para>The name
of the Tracker. This is the name displayed in the tracker list, e.g. Bug
Submissions.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Description</term>
<listitem>
- <para>The
descriptions of the Tracker. E.g. This is the tracker dedicated to the Bugs of
the project</para>
+ <para>The
description of the Tracker. E.g. This is the tracker dedicated to the Bugs of
the project</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -271,7 +271,7 @@
<varlistentry>
<term>Send email on new
submission to address</term>
<listitem>
- <para>All new
items be sent to the address inserted in the text box.</para>
+ <para>All new
items will be sent to the address inserted in the text box.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -293,13 +293,13 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>Free form text
for the <guimenuitem>submit new item</guimenuitem> page</term>
+ <term>Free form text
for the <guimenuitem>Submit new item</guimenuitem> page</term>
<listitem>
<para>This
allows you to put a specific introduction on the <guimenuitem>submit new
item</guimenuitem> page.</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>Free form text
for the <guimenuitem>browse items</guimenuitem> page</term>
+ <term>Free form text
for the <guimenuitem>Browse items</guimenuitem> page</term>
<listitem>
<para>This
allows you to put a specific introduction on the <guimenuitem>Browse
items</guimenuitem> page.</para>
</listitem>
@@ -330,7 +330,7 @@
When this function is enabled, a checkbox will appear
at the left side of each bug id. You can check one or more of the ids, select
one or more of the values in the Mass Update combo boxes and click Mass Update.
</para>
<para>
- All bugs will be modified with these new value(s). This
function is very useful if you need to change the same information for more
bugs; e.g. assigning 5 bugs to one developer or closing 10 bugs.
+ All selected bugs will be modified with these new
value(s). This function is very useful if you need to change the same
information for more bugs; e.g. assigning 5 bugs to one developer or closing 10
bugs.
</para>
</section>
<section>
@@ -374,7 +374,7 @@
<section>
<title>Searching for bugs</title>
<para>
- When using a tracker, a voice with the name of the
tracker will appear in the search combo box. The search will be done on the
description, summary, the username of the submitter and the username of the
assignee.
+ When using a tracker, a voice with the name of the
tracker will appear in the search combo box. The search will be done on the
description, the summary, the username of the submitter and the username of the
assignee.
</para>
</section>
</section>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gforge-commits] gforge/docs/docbook/docbook/user_guide/project_functions cvs.xml, 1.1, 1.2 docman.xml, 1.1, 1.2 file_releases.xml, 1.1, 1.2 forums.xml, 1.1, 1.2 mailing_lists.xml, 1.1, 1.2 news.xml, 1.1, 1.2 project_admin.xml, 1.1, 1.2 project_summary.xml, 1.1, 1.2 task_manager.xml, 1.1, 1.2 tracker.xml, 1.1, 1.2,
gsmet <=
- Prev by Date:
[Gforge-commits] gforge/docs/docbook/docbook/user_guide/user_functions index.xml, 1.1, 1.2
- Next by Date:
[Gforge-commits] gforge/common/search ExportProjectSearchQuery.class, 1.1, 1.2 ProjectSearchQuery.class, 1.1, 1.2 SkillSearchQuery.class, 1.1, 1.2
- Previous by thread:
[Gforge-commits] gforge/docs/docbook/docbook/user_guide/user_functions index.xml, 1.1, 1.2
- Next by thread:
[Gforge-commits] gforge/common/search ExportProjectSearchQuery.class, 1.1, 1.2 ProjectSearchQuery.class, 1.1, 1.2 SkillSearchQuery.class, 1.1, 1.2
- Index(es):