From triplesoup-commits-return-11-apmail-incubator-triplesoup-commits-archive=incubator.apache.org@incubator.apache.org Sun Feb 18 18:16:34 2007
Return-Path:
Delivered-To: apmail-incubator-triplesoup-commits-archive@locus.apache.org
Received: (qmail 46059 invoked from network); 18 Feb 2007 18:16:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
by minotaur.apache.org with SMTP; 18 Feb 2007 18:16:33 -0000
Received: (qmail 5354 invoked by uid 500); 18 Feb 2007 18:16:41 -0000
Delivered-To: apmail-incubator-triplesoup-commits-archive@incubator.apache.org
Received: (qmail 5315 invoked by uid 500); 18 Feb 2007 18:16:41 -0000
Mailing-List: contact triplesoup-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: triplesoup-dev@incubator.apache.org
Delivered-To: mailing list triplesoup-commits@incubator.apache.org
Received: (qmail 5306 invoked by uid 99); 18 Feb 2007 18:16:41 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Feb 2007 10:16:41 -0800
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3)
by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Feb 2007 10:16:31 -0800
Received: by eris.apache.org (Postfix, from userid 65534)
id B620B1A981D; Sun, 18 Feb 2007 10:16:11 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r508926 [2/2] - in /incubator/triplesoup/site: ./ docs/
docs/images/ lib/ xdocs/ xdocs/images/ xdocs/stylesheets/
Date: Sun, 18 Feb 2007 18:16:11 -0000
To: triplesoup-commits@incubator.apache.org
From: leosimons@apache.org
X-Mailer: svnmailer-1.1.0
Message-Id: <20070218181611.B620B1A981D@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
Copied: incubator/triplesoup/site/xdocs/mailing.xml (from r508922, harmony/standard/site/xdocs/mailing.xml)
URL: http://svn.apache.org/viewvc/incubator/triplesoup/site/xdocs/mailing.xml?view=diff&rev=508926&p1=harmony/standard/site/xdocs/mailing.xml&r1=508922&p2=incubator/triplesoup/site/xdocs/mailing.xml&r2=508926
==============================================================================
--- harmony/standard/site/xdocs/mailing.xml (original)
+++ incubator/triplesoup/site/xdocs/mailing.xml Sun Feb 18 10:16:09 2007
@@ -20,15 +20,15 @@
- Apache Harmony Mailing Lists
- Harmony Documentation Team
+ Apache TripleSoup - Mailing Lists
+ TripleSoup Documentation Team
-
+
-Apache Harmony mailing lists operate under the following terms :
+Apache TripleSoup mailing lists operate under the following terms :
@@ -73,117 +73,40 @@
-There are currently three publicly available mailing lists for Harmony :
+There are currently the following publicly available mailing lists for TripleSoup :
The developer mailing list is used by the developers to discuss
-plans, make decisions, vote on technical issues, etc. This
-list has a higher volume, though some conversations take place on
- IRC as
-well.
+plans, make decisions, vote on technical issues, etc.
- Please note that at this time, we are keeping all developer traffic on one list,
- for classlibrary, virtual machine, doc, site and tool development, in order to
- help build one homogeneous community. It is expected that at some point in the
- near future, we'll be splitting off into technical domains.
-
-
- In order to help people sort and make sense of the traffic, please prefix your
- subject line with an appropriate token :
-
-
-
- [general] - for things of general interest
-
-
- [announce] - announcements
-
-
- [legal] - discussion about legal issues
-
-
- [classlib][module] - for classlibrary-related
- issues (and you can optionally specify the specific module)
-
-
- [drlvm][module] - for DRLVM-related
- issues (and you can optionally specify the specific module)
-
-
- [jchevm][module] - for jchevm-related
- issues (and you can optionally specify the specific module)
-
-
- [bootvm][module] - for bootvm-related
- issues (and you can optionally specify the specific module)
-
-
- [doc] - for documentation-related issues
-
-
- [tools] - for tools-related issues
-
-
- [testing] or [qa] - for tools-related issues
-
-
-
-
- Simply add the token to the start of your subject line. For example :
-
-
-
This list receives notifications (with diffs) every time a change is
-committed to the Harmony source tree. It also receives change notices
-for changes to the Harmony Wiki and whenever issues are added to or
+committed to the TripleSoup source tree. It also receives change notices
+for changes to the TripleSoup Wiki and whenever issues are added to or
updated in our
-JIRA issue tracking system.
Copied: incubator/triplesoup/site/xdocs/svn.xml (from r508924, harmony/standard/site/xdocs/svn.xml)
URL: http://svn.apache.org/viewvc/incubator/triplesoup/site/xdocs/svn.xml?view=diff&rev=508926&p1=harmony/standard/site/xdocs/svn.xml&r1=508924&p2=incubator/triplesoup/site/xdocs/svn.xml&r2=508926
==============================================================================
--- harmony/standard/site/xdocs/svn.xml (original)
+++ incubator/triplesoup/site/xdocs/svn.xml Sun Feb 18 10:16:09 2007
@@ -21,16 +21,16 @@
- Apache Harmony
- Harmony Documentation Team
+ Apache TripleSoup
+ TripleSoup Documentation Team
-
+
-The Harmony project uses the
+The TripleSoup project uses the
Subversion version control
system. If you're new to Subversion, you can check out the
online book about Subversion.
@@ -43,7 +43,7 @@
Anyone can check code out of Subversion. You only need to specify a
username and password in order to update the Subversion repository, and only
-Harmony committers have the permissions to do that. We run Subversion
+TripleSoup committers have the permissions to do that. We run Subversion
over standard HTTPS, so hopefully you won't have problems with intervening
firewalls.
-Any Harmony committer should have a shell account on
+Any TripleSoup committer should have a shell account on
svn.apache.org. Before you can commit, you'll need to set a
Subversion password for yourself. To do that, log in to
svn.apache.org and run the command svnpasswd.