Author: spadkins
Date: Tue Apr 2 13:09:31 2013
New Revision: 15619
Modified:
p5ee/trunk/README
Log:
final planned commit. the source code repository is moved to code.google.com.
Modified: p5ee/trunk/README
==============================================================================
--- p5ee/trunk/README (original)
+++ p5ee/trunk/README Tue Apr 2 13:09:31 2013
@@ -1,139 +1,9 @@
-Perl 5 Enterprise Environment (P5EE) CVS
-========================================
+This source code repository has been moved from svn.perl.org to code.google.com.
-The cvs for the P5EE code is hosted at cvs.perl.org.
+ https://code.google.com/p/app-context-framework/
-Mailinglist
-===========
-
-All commits gets mailed to the cvs-p5ee mailinglist. Be sure to subscribe
-to cvs-p5ee-subscribe@perl.org if you are interested in what's going on.
-
-Anonymous CVS access
-====================
-
- cvs -d :pserver:anonymous@cvs.perl.org:/cvs/public login
- [press enter at the password prompt]
- cvs -d :pserver:anonymous@cvs.perl.org:/cvs/public co p5ee
-
-
-Web interface to the CVS repository
-===================================
-
-Available at http://cvs.perl.org/cvsweb/p5ee/.
-
-Directory Organization
-======================
-
-There are two top level directories which correspond to Perl namespaces:
-
-P5EEx
------
-
-The P5EEx (P5EE-eXperimental) namespace is for supporting prototyping
-and experimentation. The goal is to allow for people to prove
-their ideas with code, and provide a forum for a meritocracy to
-emerge without polluting the P5EE namespace
-
-P5EE
-----
-
-The P5EE namespace will be reserved for things which have been
-proven in the P5EEx namespace and are promoted through some sort
-of vote.
-
-
-Under the P5EEx, we have a set of code names for different experimental
-versions. We have choosen colors exactly because they imply nothing
-about the relative merits of the different experimental areas
-(i.e. P5EEx::Blue vs. P5EEx::Green).
-
-Each experimental area (i.e. P5EEx::Blue) would contain code which is
-proposed for promotion to the P5EE namespace. For example
-
- Experimental Module Proposed Module (implied)
- P5EEx/Blue/README README
- P5EEx/Blue/P5EE.pm P5EE.pm
- P5EEx/Blue/P5EE/Context.pm P5EE/Context.pm
- P5EEx/Blue/P5EE/Config.pm P5EE/Config.pm
- P5EEx/Blue/P5EE/Config/XML.pm P5EE/Config/XML.pm
-
-
-Each experimental module set should be independently submittable to
-CPAN, although I don't think it necessary for anyone at this time
-to rush out and submit P5EEx code to CPAN. i.e.
-
- P5EEx-Blue-0.05.tar.gz
-
-Our goal is to experiment, prove the value of code, promote it to
-P5EE, and publish
-
- P5EE-1.00.tar.gz
-
-on CPAN.
-
-
-For registered developers
-=========================
-
-First, if you don't already have it get a perl.org account at
-http://dev.perl.org/auth/account. Then send an email to richter@ecos.de
-to enable CVS access for your account.
-After you have had CVS access enabled on your account, please allow up to
-30 minutes before all systems are syncronized.
-
-Checkout a local copy of the p5ee module
-
-Where LOGIN is your perl.org login name, do a
-
- cvs -d :pserver:LOGIN@cvs.perl.org:/cvs/public login
- [enter your perl.org password]
- cvs -d :pserver:LOGIN@cvs.perl.org:/cvs/public co p5ee
- cd p5ee
-
-Keep your copy updated
-
- cvs update -dP
-
-Commit some changes
-
- cvs commit filename [filename]
-
-Do a diff
-
- cvs diff [filename]
-
-Add a file
-
- cvs add [filename]
-
-Other tips
-I like the "-u -d" options to diff, so I have
-
- diff -u -d
-
-in my ~/.cvsrc.
-
-Snapshots
-=========
-
-If you cannot access the CVS server, for whatever reason, firewall or just
-company policy, you can access CVS snapshots, created every 6 hours.
-
-http://cvs.perl.org/snapshots/
-
-CVS Tutorials
-=============
-
-The CVS Book at http://cvsbook.red-bean.com/cvsbook.html
-
-Problems, Comments, Feedback about the P5EE cvs
-===============================================
-
-Send any of them to Gerald Richter <richter@ecos.de>.
-
-
-$Id$
+You can check out the source code with
+ svn checkout http://app-context-framework.googlecode.com/svn/trunk/ app-context-framework
Date: Tue Apr 2 13:09:31 2013
New Revision: 15619
Modified:
p5ee/trunk/README
Log:
final planned commit. the source code repository is moved to code.google.com.
Modified: p5ee/trunk/README
==============================================================================
--- p5ee/trunk/README (original)
+++ p5ee/trunk/README Tue Apr 2 13:09:31 2013
@@ -1,139 +1,9 @@
-Perl 5 Enterprise Environment (P5EE) CVS
-========================================
+This source code repository has been moved from svn.perl.org to code.google.com.
-The cvs for the P5EE code is hosted at cvs.perl.org.
+ https://code.google.com/p/app-context-framework/
-Mailinglist
-===========
-
-All commits gets mailed to the cvs-p5ee mailinglist. Be sure to subscribe
-to cvs-p5ee-subscribe@perl.org if you are interested in what's going on.
-
-Anonymous CVS access
-====================
-
- cvs -d :pserver:anonymous@cvs.perl.org:/cvs/public login
- [press enter at the password prompt]
- cvs -d :pserver:anonymous@cvs.perl.org:/cvs/public co p5ee
-
-
-Web interface to the CVS repository
-===================================
-
-Available at http://cvs.perl.org/cvsweb/p5ee/.
-
-Directory Organization
-======================
-
-There are two top level directories which correspond to Perl namespaces:
-
-P5EEx
------
-
-The P5EEx (P5EE-eXperimental) namespace is for supporting prototyping
-and experimentation. The goal is to allow for people to prove
-their ideas with code, and provide a forum for a meritocracy to
-emerge without polluting the P5EE namespace
-
-P5EE
-----
-
-The P5EE namespace will be reserved for things which have been
-proven in the P5EEx namespace and are promoted through some sort
-of vote.
-
-
-Under the P5EEx, we have a set of code names for different experimental
-versions. We have choosen colors exactly because they imply nothing
-about the relative merits of the different experimental areas
-(i.e. P5EEx::Blue vs. P5EEx::Green).
-
-Each experimental area (i.e. P5EEx::Blue) would contain code which is
-proposed for promotion to the P5EE namespace. For example
-
- Experimental Module Proposed Module (implied)
- P5EEx/Blue/README README
- P5EEx/Blue/P5EE.pm P5EE.pm
- P5EEx/Blue/P5EE/Context.pm P5EE/Context.pm
- P5EEx/Blue/P5EE/Config.pm P5EE/Config.pm
- P5EEx/Blue/P5EE/Config/XML.pm P5EE/Config/XML.pm
-
-
-Each experimental module set should be independently submittable to
-CPAN, although I don't think it necessary for anyone at this time
-to rush out and submit P5EEx code to CPAN. i.e.
-
- P5EEx-Blue-0.05.tar.gz
-
-Our goal is to experiment, prove the value of code, promote it to
-P5EE, and publish
-
- P5EE-1.00.tar.gz
-
-on CPAN.
-
-
-For registered developers
-=========================
-
-First, if you don't already have it get a perl.org account at
-http://dev.perl.org/auth/account. Then send an email to richter@ecos.de
-to enable CVS access for your account.
-After you have had CVS access enabled on your account, please allow up to
-30 minutes before all systems are syncronized.
-
-Checkout a local copy of the p5ee module
-
-Where LOGIN is your perl.org login name, do a
-
- cvs -d :pserver:LOGIN@cvs.perl.org:/cvs/public login
- [enter your perl.org password]
- cvs -d :pserver:LOGIN@cvs.perl.org:/cvs/public co p5ee
- cd p5ee
-
-Keep your copy updated
-
- cvs update -dP
-
-Commit some changes
-
- cvs commit filename [filename]
-
-Do a diff
-
- cvs diff [filename]
-
-Add a file
-
- cvs add [filename]
-
-Other tips
-I like the "-u -d" options to diff, so I have
-
- diff -u -d
-
-in my ~/.cvsrc.
-
-Snapshots
-=========
-
-If you cannot access the CVS server, for whatever reason, firewall or just
-company policy, you can access CVS snapshots, created every 6 hours.
-
-http://cvs.perl.org/snapshots/
-
-CVS Tutorials
-=============
-
-The CVS Book at http://cvsbook.red-bean.com/cvsbook.html
-
-Problems, Comments, Feedback about the P5EE cvs
-===============================================
-
-Send any of them to Gerald Richter <richter@ecos.de>.
-
-
-$Id$
+You can check out the source code with
+ svn checkout http://app-context-framework.googlecode.com/svn/trunk/ app-context-framework
