[Vtigercrm-developers] Calling all private 4.x development owners

[Ales Petric]

Ok

As private developer owner of 4.2.x I would like to be involved 
'actively' in planning, maintaining and updating
the 4.2.x.

With what can I contribute:
1- I can bug fix (ticket solve)
2- I can suggest & plan with others what's to be in next release (4.2.X) 
and help with coding to achieve that
3- I can define groups for managing individual modules (maintainers) 
that will togather with other involved in 4.2.x deceide what's needed to 
build as add-on
4- I can do the functional analyse of current 4.2.x and publish .pdf, 
like system & user help (for developers and others related)
5- I can built three of functionality, like dir structure (for UseCase, 
TestCase and other related)
6- I can define which ticket/issue goes with X module or X functionality 
(for quick issue solving and other related)
7- I can help sync with other anonymous/private developers what was 
solved/debugged and help to merge existing code into next to be released
8 .. and many other stuff that I had have already done and not 
published...I can decode that for other users...

What do I need:
1- Account with permissions to do something, I don't want to be 
anonymous updater.

Now it's 8 vs 1 :(

I it would be great to be involved with when to release and what's 
included in next 4.2.x.

Ales

Nolan Andres wrote:
> As one of the mentioned 4.2 developers mostly lurking on this list...
>
> Like others have mentioned, I've got 2 classes of modifications: 
>
> 1. those _I think_ others may be interested in
> 2. those _I think_ others will not be interested in
>
> What I want to know is...is what _I think_ in any way connected with
> reality? 
>
> More to the point...
>
> How do I know whether or not I *should* submit a given patch to the
> current tree for 4.2.5? In my previous (though admittedly minimal)
> exploration, I got the sense that 4.2.x was essentially "feature frozen"
> and that bug/security fixes and deployment/installation/maintenance
> stuff were fair game.
>
> For myself (and others like me), is 4.2 open for new features? If so,
> should we just continue to take it on ourselves to self-select those
> things _we think_ are more universal in nature? Should we try the
> shotgun approach (submit everything to 'Code Contributions' and see what
> gets picked up)? Is there a "proper place" to provide a list of changes
> we've made and give others the opportunity to speak for/against
> including them (or give a 'vTiger Linus' the opportunity to
> accept/reject them)? 
>
> I think once I have a clear idea of how best to contribute, particularly
> to 4.2, I'll be more able to do so effectively.
>
> By the way, I think Matt's v5 architecture ideas are great, but they do
> muddy the waters for me a bit. Seeing those ideas, I have hope that
> something along those lines may be implemented, but it also makes me
> question *when* the right time will be to port some of my changes and
> additions to v5...I'd rather just do it once. 
>
> peace,
> nokes
>
>
>
> On Thu, 2006-07-13 at 03:46 -0700, Richie wrote:
>   
>> Hi!
>> This is a call to all the 4.x private development owners.
>>
>> Many of you would have been working on your own version of vtiger as you would have 
>> customized it to your own needs. This is a call for those guys.
>>
>> The intent is to aggregate most of the common features that you have built and have them
>>  integrated into the vtiger core codebase. The integration might happen in the 4.2.x branch
>>  or even in the 5.x branch as needed by the community.
>>
>> Pros:
>>
>> By doing the above, you will be able to be in sync with the latest and greatest developments
>>  happening on vtiger. I understand that the current vtigercrm-5.x code base is not that easy a 
>> read as one would think of but we are working on it. Yesterday we had comments about the
>>  code not being properly commented, we are working on that right now even as I type this post. 
>> So, the idea I am conveying is that we are not perfect but are listening to the comments and 
>> taking actions too. Hence, please do keep the faith.
>>
>> Cons:
>>
>> By maintaining your own code bases, you lose out on the community benefits like
>>  identifying bugs, feature integration, new ideas, etc.
>>
>> We welcome your contributions. 
>>
>> Yes, there was a time in the past when I was decidedly introvert and the project suffered. I realise 
>> the folly. Let us get on with it and make vtiger a success. 
>> I have learnt from my past mistakes. Join the team, come on board.
>>
>> Richie
>> _______________________________________________
>> Get started with creating presentations online - http://zohoshow.com?vt 
>>     
>
> _______________________________________________
> Get started with creating presentations online - http://zohoshow.com?vt 
>
> __________ NOD32 1.1661 (20060714) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20060717/f0af863c/attachment-0003.html