Hello dear list. Sorry if this is not the correct list to ask this. Let me know if i could ask anywhere.
This afternoon i have been quite busy letting my mind go deep in the space, searching for other lifeforms, resolving JFK murder, somethings to do...and this is what bring me here. I'm thinking on a software idea, and would like to check with you, if you consider it a good/bad/wtf idea: Builiding a document content management system, for sharing resources(files, folders, etc), based on SVN. Consider the following SHARING table: resource=file/folder/whatever to share minor_rev=from which revision the sharing starts major_rev=to which revision the sharing ends With these scenario: file, 0, 0 share the first version(revision) of the document file, 14, 16 share file from revision 14 to 16 file, 14, * share the file from revision 14 to the latest file, *, 0 share the latest revision of the file only file, *, * share all the revision history for the file Of course, when the shared user log into the system, he must see a tree of folders and files. User can expand folders to see contents (also to see revisions, and that could be confusing if not well made) and can expand files to see diferent available versions of a file. I hope i have explained clearly. What do you think? Do i deserve Seppuku? Do you deserve to kill me for such an offense? There are plenty of CM systems on the Internet, and maybe there are some -based on svn- like this, but i havent seen any, and all i see are relational database based. Do you know any? There are also some considerations to make: Revisions in svn are for "svn tree", so a file can be the same between revisions. The file tree should only display version for the revisions were it change. Asking on freenode two alternatives were made: trigger on svn commit to store the info on DB (Altough seem efficient, is not like having a sharing CM based on BD, as many other system do?) try to (not very clear how) make a query to find in which revisions the file changed. Is this efficient? Maybe there is an API call to check this, or maybe this is a good reason to use CVS instead. Anyway, i truly thank for your time, patience and comments. Please, dont hesitate to critic and give some good arguments. Thanks again, hc.
