[TYPO3-dev] TYPO3xdev: SVN beta offering

[Andreas Otto]

Hi,

SF.net has accepted the application of TYPO3xdev to take part in the  
Subversion Beta Test.

Every developer who maintains a project on TYPO3xdev should send me the  
comments and suggestions how to proceed.

Please read the attached eMail from SF.net and the documents mentioned  
below.

Further information [1] can be found on the SF.net website.

[1]<https://sourceforge.net/docs/E09>


Cheers,
Andreas

----------  Forwarded Message  ----------

Subject: [Alexandria-svnbeta] SourceForge.net: Subversion beta launch
Date: Thursday 12 January 2006 21:45
From: Jacob Moorman <moorman at sourceforge.net>
To: alexandria-svnbeta at lists.sourceforge.net

Greetings,

The SourceForge.net Service Operations team is excited to announce the
readiness of our Subversion service beta.

You're receiving this message because you (and your project) have been
selected by SourceForge.net staff to participate in our Subversion
service beta.  We appreciate your interest in helping us improve
SourceForge.net.

This beta is scheduled to run between four and six weeks.  This service,
even though in beta, is fully supported by the SourceForge.net Service
Operations team.  We'll be working to address any problems you raise,
evaluate service performance, and prepare for launch of this service to
all projects.

Please read all of the instructions provided, and review as needed with
your team.  If you have questions, please contact us via the designated
support mechanism (see below).

This service is available to you immediately on the projects
you've previously identified.


Instructions on how to submit problems for support
--------------------------------------------------

Problems with the Subversion beta should be reported just like a problem
with any other SourceForge.net service.  Issues should be reported to
the Confidential Support Request Tracker for the alexandria project.

Reference: https://sourceforge.net/docs/E09#support


Updates on this service
-----------------------

Should updates to this service occur during the beta (as we work on
further enhancements and refinements, and address the defects you
report), a low volume of mail may be sent to this list by
SourceForge.net staff.  Please keep an eye out for this traffic.


What's included in the beta service offering?
---------------------------------------------

At time of beta launch, we provide the following:

* Developer Subversion access via HTTPS, auth is requested when you
   perform a write operation
* Anonymous Subversion access via HTTPS
* No sync delays between developer and anonymous Subversion access
* Web-based repository access via ViewVC
* Read-only rsync access to the repository to permit backups and
   remote mirroring
* Per-developer access control over repository access (ACL support to be
   added later) via the SourceForge.net permissions system
* Automated self-service migration of your SourceForge.net project CVS
   repository to Subversion
* A selected set of hook scripts, including commit email support
* Statistics tracking of Subversion repository activity


Who can access the Subversion services
--------------------------------------

Participation in our beta is limited to a specific set of projects.
When a project opts-in for Subversion access, it's important to
understand that you are also having your end-users join the beta
process.

Once enabled by the project, your project team and the community will
immediately have access to your project Subversion repository.

Developers will be able to commit (and perform other write operations)
if given proper permissions (see below).  As with our CVS service,
write access to your Subversion repository can only be granted to
project members.


Can we continue using CVS?
--------------------------

Subversion is offered in addition to CVS.  A project can opt to use CVS,
Subversion or both.  We highly recommend that projects elect to use
one or the other, to minimize end-user confusion.


How to turn on Subversion access
--------------------------------

Subversion access can be enabled on the Subversion page in the
SourceForge.net Project Admin pages. Check the 'Enable Subversion?'
check box and click on the Update button to enable it for your project.


How to provide Subversion permissions to your developers
--------------------------------------------------------

Developer access to Subversion is restricted using the same types of
permissions mechanisms used for CVS and shell service.  Under the
Members project admin page, click on the developer to set permissions
for.  Then, check the 'Allow access to Subversion repository (developer
access)' check box and click the 'Update Developer Permissions' button
to give Subversion write access to a project developer (un-check the box
to revoke SVN permissions).


Supported Subversion clients
----------------------------

The native Subversion client (command-line)
Reference: https://www.sf.net/docs/F06

TortoiseSVN
Reference: https://www.sf.net/docs/F07


How to migrate
--------------

An automated migration from a SourceForge.net CVS repository to the
SourceForge.net Subversion repository of the same project is available
simply by clicking a button in the project admin pages. Migration from
other sources (CVS repository tarball, SVN dump file) is to be requested
via Support Request. Refer to the import section of the Subversion
documentation for specific formatting details and concerns:

Reference: https://www.sf.net/docs/E09#import


Backup responsibilities
-----------------------

As with all other SourceForge.net services, it is the responsibility of
your project to backup project Subversion content.  Read-only rsync
access is provided, to allow for backups and remote mirroring.  Details
on how to make a full backup of your Subversion repository are provided
in our documentation.

Reference: https://www.sf.net/docs/E09#backup


Can I have my other projects put on Subversion as well?
-------------------------------------------------------

In short, no.  This is a closed beta offering, and its purpose is to
allow early access to a small number of projects to help work out the
kinks of this new powerful and complex service offering.  Once the beta
ends and the service is made live, your other projects will be able to
use Subversion at that time.


Thank you,

Jacob Moorman
Quality of Service Manager, SourceForge.net
moorman at sourceforge.net
moorman at vasoftware.com
--
**************************************************************************
This email may contain confidential and privileged material for the sole
use of the intended recipient.  Any review or distribution by others is
strictly prohibited. If you are not the intended recipient,
please contact the sender and delete all copies.
***************************************************************************

-------------------------------------------------------