You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@stdcxx.apache.org by se...@apache.org on 2011/02/14 02:05:51 UTC

svn commit: r1070350 - /stdcxx/site/status/2011-02.txt

Author: sebor
Date: Mon Feb 14 01:05:51 2011
New Revision: 1070350

URL: http://svn.apache.org/viewvc?rev=1070350&view=rev
Log:
2011-02-13  Martin Sebor  <se...@apache.org>

	* status/stdcxx-status/2010-11.txt: Updated/modified board report
	for February 2011.

Modified:
    stdcxx/site/status/2011-02.txt

Modified: stdcxx/site/status/2011-02.txt
URL: http://svn.apache.org/viewvc/stdcxx/site/status/2011-02.txt?rev=1070350&r1=1070349&r2=1070350&view=diff
==============================================================================
--- stdcxx/site/status/2011-02.txt (original)
+++ stdcxx/site/status/2011-02.txt Mon Feb 14 01:05:51 2011
@@ -18,11 +18,11 @@ Notable changes since previous report (N
   already submitted some patches or expressed serious interest in
   contributing going forward.
 
-  Another alternative is to move stdcxx to a repository outside of
-  ASF such as SourceForge or similar where interested developers
-  could start committing changes on their own right away, without
-  going through the "training" process. This seems to the preferred
-  solution among at least some of the interested users.
+  Another alternative is to move stdcxx to a repository outside
+  of ASF such as SPI (http://www.spi-inc.org/) where interested
+  developers could start committing changes on their own right away,
+  without going through the "training" process. This seems to the
+  preferred solution among at least some of the interested users.
 
   Are there any other options?