vtiger

jeffk · Joined: 07 Dec 2004 Posts: 96

I've been vocal in advocating that vtiger's SCM (sourceforge CVS) and tracker (sourceforge) are holding the project back. I now have an easy example of 'how good it could be' with the right tools, for your browsing convenience.

Plone (zope/python CMS) has been on subversion for a long time now, and the benefits of that are clear to me as a Plone user. Well, they recently started using trac, an extraordinary free tool that integrates Wiki, Issue tracking, Timelines and subversion source and changeset browsing in one integrated package.

http://trac.plone.org/plone/roadmap

http://trac.plone.org/plone/timeline

(the most active source branch is '2.1')
http://trac.plone.org/plone/browser/CMFPlone/branches/2.1
(be sure to browse some 'changesets' to see easily understood diffs)

http://trac.plone.org/plone/report (ticket reports)

The proof is there for all of us to see, this kind of toolchain would be *the* difference maker for what the vtiger team wants to achieve.

I think vtiger should drop everything they're doing for a few days, migrate vtigercrm to subversion with cvs2svn, install trac and pick up the new and improved process a week later with a reinvigorated community.

indigoleopard · Joined: 21 Aug 2004 Posts: 2111 Location: india,chennai

Hi Jeff!

Indeed, we would love to do it, but as you know we are nearing Alpha and we will not be able to take it up. Moreover, there are no resources to spare. Remember, we are just 9 guys here.

Moreover, the entire combo is new to us.

May I ask you to take the initiative and do some testing on the same please?

Richie

jeffk · Joined: 07 Dec 2004 Posts: 96

Update: I have successfully run the conversion script cvs2svn on a nightly tarball of the vtigercrm repository. I have a working subversion repository with all of the cvs modules (vtiger_crm, outlookplugin, customerportal, etc.), and all tags, all branches, and all revisions with commit information intact. For example:
Code: $ svn log file:///svn/vtigercrm/trunk/vtiger_crm/index.php | head -n 30
------------------------------------------------------------------------
r2656 | mangai | 2005-12-16 01:44:42 -0500 (Fri, 16 Dec 2005) | 2 lines

changes made to split Orders module into SalesOrder and PurchaseOrder

------------------------------------------------------------------------
r2601 | mickie | 2005-12-13 03:05:47 -0500 (Tue, 13 Dec 2005) | 2 lines

* Added action COnvertAsFAQ in ereg

------------------------------------------------------------------------
r2577 | mangai | 2005-12-08 04:34:28 -0500 (Thu, 08 Dec 2005) | 2 lines

vtiger logger has been changed to default php logger

------------------------------------------------------------------------
r2514 | saraj | 2005-11-29 14:17:43 -0500 (Tue, 29 Nov 2005) | 2 lines

* Arbitrary File uplad Vulnerability fix added
I will now investigate setting up trac.

I am working up a list of procedures that vtiger could use to convert to a subversion repository hosted on their own server, or hosted at berlios, tigris, etc.

My objective to have investigated converstion-related issues in time for the core team to take a good hard look at migrating to subversion as soon as possible after the vtigercrm-5.0.0-alpha1 and vtigercrm-4.2.3 releases.

The team should have a look at the earlier post's urls showing what benefit plone is receiving from subversion and trac, so that they can make an informed decision at the appropriate time.

jeffk · Joined: 07 Dec 2004 Posts: 96

indigoleopard wrote: we are just 9 guys here.
You won't be just 9 guys if you have a slick community-collaboration environment like trac and subversion. It's a resource multiplier, and better suited to taking on additional people with commit priviledges, since subversion makes it so much easier to clean up after repository mistakes and merge/maintain long-lived branches.

mikecrowe · Joined: 04 Jan 2005 Posts: 499

Richie,

I setup trac and SVN in about 30 minutes. I was amazed.

In moving my stuff from directories into SVN, I'm starting to see the light.

I agree let's wait until after alpha. But that should be the first step for beta. I really like the trac issue and milestone features. If you are interested, I'll open my private site I use up so you can see.

jeffk · Joined: 07 Dec 2004 Posts: 96

mikecrowe wrote: I setup trac and SVN in about 30 minutes. I was amazed.
That's great to hear. I used cvs2svn-1.3.0 to convert the nightly repository tarball:
Code: http://cvs.sourceforge.net/cvstarballs/vtigercrm-cvsroot.tar.bz2
The one necessary trick is to unpack it and rm -rf the CVSROOT directory (unnecessary cvs infrastructure files). I'm told by people on the cvs2svn mailing list that CVSROOT contains no versioning information of interest to subversion.
Code: cvs2svn -s /svn/vtigercrm /svn/vtigercrmcvsrepos
I use subversion-1.3.0_rc4, but any subversion after 1.2 should default to the fstype=fsfs, which is an important improvement over the old BerkeleyDB default.

http://cvs2svn.tigris.org/

indigoleopard · Joined: 21 Aug 2004 Posts: 2111 Location: india,chennai

Hi Mike/Jeff!

I agree with you that we must move on to the latest tools around. Mike, if you have time and if you can get Jeff on board, could you please play around and see what all we can do with the tools?

Time we got Jeff on board. He is harassing too much now. :D :D !

Richie

mikecrowe · Joined: 04 Jan 2005 Posts: 499

Agree'd about bringing jeff on board. Punishment for vocality! :D