Quote:
Originally posted by Jack
ok.. this replys to really both this and the other thread. (website & gui)
If you all decide to use php, I'll be happy to help out. Since you will be having a forum, using that as a backend for templateing, db interaction, user accounts would reduce the work load a lot. However, it would then require all of the coders to be able to understand the workings of that type of system.
|
First off, here's the URL to what I've been playing around with so far:
http://freelancefirst.pitnews.org/forums/
As you can see, it's based around the Invision Power Board forum software. From my experience, it's not that bad for skinning(I've worked a little bit on this already) or writing mods for.
Also, I've been toying around with how to handle the version management system myself. Here's what I came up with:
-User A wants to use a file, so they check it out and download the current version.
-In the checkout tracking DB, the following is recorded(english language translation follows): "user A checked out file XXX.BSX version 1.5.2 on $date at $time"
-While User A has the file, user B wants to use the same file. When user B goes to download the file, they get a warning stating that user A is already working on that file, and asks them if they still want to download the file.
-If user B decides to download the file, the following is recorded in the checkout DB: "user B checked out file XXX.BSX version 1.5.2 on $date at $time"
-When User A or B checks back in their file with whatever modifications, a branch is created under the checked out version for EACH returned file.
-The project owner or project leader(owner=who requests it, leader=who accepted it) is responsible for deciding which branch, or a combination of the two, gets the 1.5.3 version identifier. The file(s) which do not recieve the new version number get tagged as "interim versions"(unless I can come up with a better name)
What do you think?