[Vtigercrm-developers] SVN access

Mike Crowe mike at mikeandkellycrowe.com
Sat Feb 4 06:08:37 PST 2006


I will have to get the vtiger guys to do that.  I only have the access 
to the machine now, not the DNS records.

Sergio, join us in #vtiger



Sergio A. Kessler wrote:
> mike, how about pointing devel.vtigerforge.com to vtiger.fosslabs.com ?
>
> and forge.vtigerforge.com to the actual gforge ?
>
> then devel.vtigerforge.com will be the place for the vtiger core
> products (v5.0, v4.2.x, etc)
> and forge.vtigerforge.com for all the satellite projects...
>
> /sak
>
> On 2/3/06, Mike Crowe <mike at mikeandkellycrowe.com> wrote:
>   
>> I'm going to throw a little cold water on this and ask for some patience:
>>
>> IMHO, Here's what I want:
>>
>> There should be 1 site, vtigerforge.com
>> vtiger.vtigerforge.com should be the main trac site for vtiger
>> repository and issues.
>> vtiger projects we create should be in SVN, handled by gforge.
>>
>> When Fathi completes his gforge setup, I plan on giving him access to
>> vtigerforge.com.  He will move databases and all to that site so that
>> vtigerforge.com yields gforge instead of the current novellforge.
>>
>> Would you be willing to do the same?  I'd like to see the main SVN and
>> trac for vtiger on the forge machine.  Are you willing to migrate this?
>>
>> Mike
>>
>> Matthew Brichacek wrote:
>>
>>     
>>>> svn and trac are being handled by you.
>>>>
>>>>
>>>>         
>>> And jeffk, he seems to have more knowledge in svn management than me so
>>> we should ping him on things until we are all as comfortable.
>>>
>>>
>>>
>>>       
>>>> gforge by Fathi
>>>>
>>>>
>>>>         
>>> Yes, I've contacted him off-list to find out what shell permissions he
>>> needs and anything else I can help him with.
>>>
>>>
>>>
>>>       
>>>> Mike too has a forge.
>>>>
>>>>
>>>>         
>>> I was under the impression that we would turn off mikes forge when
>>> gforge was up.
>>>
>>>
>>>
>>>       
>>>> What to do with it and who is handling that stuff?
>>>>
>>>>
>>>>
>>>>         
>>> I'll keep an eye on the forge/trac/svn happenings and make sure anything
>>> is posted here to the list.
>>>
>>>
>>>
>>>
>>>       
>>>> Now, we are working on porting the cvs stuff to svn.
>>>> That would basically mean that we stop cvs cins into sf.net totally
>>>> effective immediately.
>>>>
>>>>
>>>>         
>>> This would be great!  The whole project can reap the benefits of
>>> subversion/trac if you abandon SF for now.  Maybe re-visit SF after
>>> subversion is in wider use with their system, provided developers aren't
>>> madly in love with Trac by then.
>>>
>>>
>>>
>>>       
>>>> I get the bigger picture but have no implementation
>>>> knowledge. Willing to learn. Guidance needed.
>>>>
>>>>
>>>>         
>>> No problem.  Start with the svn book that jeffk posted.  Subversion is
>>> very easy to work with and once you've figured out your most used
>>> commands you'll be amazed at how smooth it is (I was).
>>> http://svnbook.red-bean.com/en/1.1/index.html
>>>
>>> Maybe jeffk or someone else can give us an IRC demo of how to branch and
>>> merge in a way that would be most beneficial to the developers.
>>>
>>> I have http check outs and http authenticated maintenance enabled for
>>> subversion.  I'll work on https after we get the user->branch mapping
>>> done.  What I need from you is a list of current users on the SF CVS
>>> tree and what branches they are allowed to access.  I will re-create
>>> this in svn and then we can let everyone loose.
>>>
>>> Still to be done:
>>> A password changing page for users of trac/svn to be able to change
>>> their passwords.  I can build this or anyone else can, it's just an
>>> htpasswd file.  Https access for developer check-ins to the system.
>>> Gforge installation, I am in contact with Fathi off-list to gather his
>>> requirements.
>>>
>>> Install xchat (windows or linux) and point it to
>>> vtiger.fosslabs.com:6667 and '/join #devel'.  You can use this to
>>> communicate with the entire team in real time and this way you can open
>>> those hallway meetings up to the rest of us.  We can work on a logging
>>> and publishing scheme so the data is archived and available for
>>> reference later.  This is a very handy tool, user coaching, IRC demos
>>> and other things can happen in here that are great for reference later
>>> and may get lost in a large mailing list.  I cruise the linux-vserver
>>> IRC logs all the time.  They have a few developers on there that mentor
>>> other devs on kernel stuff and its a great place to pick up these
>>> conversions exactly the way they happened, off the cuff remarks and
>>> all :).
>>>
>>> Matt
>>>
>>> _______________________________________________
>>> vtigercrm-developers mailing list
>>> vtigercrm-developers at lists.vtigercrm.com
>>> http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
>>>
>>>
>>>       
>> _______________________________________________
>> vtigercrm-developers mailing list
>> vtigercrm-developers at lists.vtigercrm.com
>> http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
>>
>>     
>
> _______________________________________________
> vtigercrm-developers mailing list
> vtigercrm-developers at lists.vtigercrm.com
> http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
>   




More information about the vtigercrm-developers mailing list