Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Dec 2011 22:51:12 +0000
From:      Frank Shute <frank@shute.org.uk>
To:        ss griffon <ssgriffonuser@gmail.com>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Revision control advice
Message-ID:  <20111222225112.GA58727@orange.esperance-linux.co.uk>
In-Reply-To: <CAFYJ9ehcvoP%2BS%2BtacD2g8CZ-UmBHrNx9FSBXMyUUM7M26dbiXw@mail.gmail.com>
References:  <alpine.BSF.2.00.1112212011490.44046@tripel.monochrome.org> <4EF29AD7.5040807@herveybayaustralia.com.au> <CAFYJ9ehcvoP%2BS%2BtacD2g8CZ-UmBHrNx9FSBXMyUUM7M26dbiXw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 21, 2011 at 08:24:01PM -0700, ss griffon wrote:
>
> On Wed, Dec 21, 2011 at 7:49 PM, Da Rock
> <freebsd-questions@herveybayaustralia.com.au> wrote:
> > On 12/22/11 11:37, Chris Hill wrote:
> >>
> >> Hello list,
> >>
> >> I apologize for this posting being not-much-on-topic, but my other
> >> resources have come to naught and I think you folks may have some expe=
rience
> >> in this area.
> >>
> >> I'm looking to set up some sort of revision control system at work. Si=
mple
> >> enough, except that our situation is approximately the reverse of what=
 most
> >> revision control systems are designed for.
> >>
> >> Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of
> >> small, rapid-fire projects that are created at the rate of 3 to 20 per
> >> month. They last a few days or a few months and are (usually) not deve=
loped
> >> afterward. Each project has one to three developers working on it, som=
etimes
> >> simultaneously. Usually it's one guy per project.
> >>
> >> Since my programmers are not necessarily UNIX-savvy, I'd like to deplo=
y a
> >> web interface for them which will allow them to create new repositories
> >> (projects) as well as the normal checkin, checkout, etc. I want to set=
 this
> >> up once, and from there on have the programmers deal with managing the=
ir own
> >> repos. And heaven forfend exposing them to the horrors of the shell.
> >>
> >> I've built a test server (9.0-RC3, amd64) for experimenting with this
> >> stuff. So far I've installed and played with:
> >> =A0- fossil. I like the simplicity and light weight, but it doesn't se=
em to
> >> allow creation of new repos at all (let alone multiple ones) from the =
web
> >> interface, and the documentation is meager. I've pretty much given up =
on it.
> >> =A0- subversion, which looks like the heavy hitter of RCSs, but it's n=
ot at
> >> all clear to me how to handle the multiple-project scenario. Still wor=
king
> >> on it.
> >> =A0- git looks promising, but I have not installed it yet.
> >>
> >> If anyone can point me to a tool that might be suitable, I would be mo=
st
> >> grateful.
> >
> > I'd suggest subversion. It allows individual files to be versioned, you=
 can
> > setup a webdav interface, and there are other tools that can help maint=
ain
> > it.
> >
> > Forget the individual repositories. Setup a single repository and have
> > directories for each project. in each directory you can then setup trun=
k,
> > branches, whatever, as per best practices in the Book.
> >
> > Designate a person or two to administer, and use directory level auth, =
or
> > another alternative I haven't thought of.
> >
> > My 2c's anyway. HTH
> >
>=20
> Yeah I would second what Mr Rock says.  Set up a single repo where
> folders can be used for projects.  Since svn lets you checkout sub
> folders of a repo, each developer can check out the folder that
> corresponds to their project.  Also, Tortoise svn is a very nice
> graphical utility that will allow your developers to manage there svn
> folders without even needing a web interface (most non unix people
> that I know like tortoise), so there is less maintenance for you :)
> Finally, kudos to moving towards using version control, its an
> important step for a software company.

I'll 3rd the choice of Subversion. It's quite easy to setup and use.

There's also the book online:

http://svnbook.red-bean.com/en/1.7/index.html

for you to read at your pleasure and which you can also point your users to.


Regards,

--=20

 Frank

 Contact info: http://www.shute.org.uk/misc/contact.html



--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)

iEYEARECAAYFAk7ztF8ACgkQHduKvUAgeK5RwQCg2P4ipWnazV+w4q61ZaU5yKp+
cfgAn13uOr+yBzkWuZF0dAh2+k85YZEt
=/Ud0
-----END PGP SIGNATURE-----

--1yeeQ81UyVL57Vl7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111222225112.GA58727>