[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

browser interface thoughts....

From: bruce <bedouglas_at_earthlink.net>
Date: 2005-04-14 04:18:21 CEST

hi...

i've been trying to deal with Gforge/ViewCVS and realize that there needs to
be some additional functionality. if you're going to integrate with SVN,
there should be a way of creating projects, and specifying the project
structure so the repository gets built correctly for the project.

Gforge appears reasonable for managing the project, but I haven't seen any
tool/app that allows one to do the project/repository creation part...

i envision an app that allows you to:

allow user to specify/create projects
 -this sets up the project structure
 -determines if an existing project already exists
 -checks to see if enough disk space is available
  (while there could be enough space initially,
   this could change. over time, should allow the
   project to be created on disk array)

(The idea is to allow a user to specify the project
 layout/dir structure for the repository/workspace)
---------------------------------------------
project/directory specification/creation process
-app allows the user to enter project name
 -app allows user to create directory structure
 -allow user to move/rename/modify/delete/add directories
 -allow user to provide comments for directories
 -allow user to specify status of project creation
   -in process
   -ready to be authorized/pending authorization
 -initially only allow a single user to create the project
  structure. (over time, allow multiple users/groups to
  create the project/dir structure)

(the idea is to allow the admin to authorize the project
 and for the app to create the requisite repository/workspace
 structure)
---------------------------------------------
allow admin to authorize project creation
 -this creates the underlying project structure on the hard-drive
 -this also creates the SVN repository
 -this also does an import into the SVN repository
 -this also deletes the initial project dir structure
 -this also does a SVN co' to create the project workspace
 -notifies the initial user/owner of the project creation
 -updates the database of the SVN/project actions

for completed project structures
---------------------------------------------
allow authorized members of the project to be able to:
 -access the project dirs/files
 -download/upload the files
 -checkout-check-in files from repository
 -keep track of which files are out, and who's
  checked them out
 -display this information for the file in the
  project (status/checked-in/out, who has it, etc..)
 -app should handle all underlying interaction
  with SVN repositories

this kind of approach appears to go beyond the ViewCVS
in that a user can actually create different project
structures.

a major issue that i'm grappling with though, is if
user A checks out a file (foo), in the project
repository, and user B checks out the same file (foo)
in the project repository, how does SVN handle this condition...

or, should i just not allow multiple people to check out
the same file at the same time from the repository...

these are some thoughts, feel free to comment/add more. give the
pros/cons/etc...

thanks

bruce
bedouglas@earthlink.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 14 04:19:54 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.