[Vtigercrm-developers] caching user privileges
John Crisp
john at reetspetit.net
Fri Feb 10 09:19:54 PST 2012
> changes into trunk as possible. I have submitted less than ten
> patches out of the roughly one thousand internal Bugzilla tickets we
> fixed last year, but have had zero patches accepted. This is
> seriously throttling on my enthusiasm towards submitting additional
> patches.
My point earlier. I still cannot understand why more patches offered are
not accepted. Surely that is the whole point of 'Community' involvement
? I personally noticed dozens of spelling mistakes (I'm no coder, but
figure every little helps), but didn't report them as I thought they
probably wouldn't get accepted. What's the point ?
The irony is that many OS projects cry out for help, and here it is
thrown at them and frequently ignored. Some odd reasoning going on
somewhere.
>
> So how do we fix this situation? First off, a centralized source
> control model means that the onus is on vtiger to do this work
> gratis. They're a business, they have to keep the lights on, and if
> that means they prioritize their On Demand offering over the community
> edition, then it's unfortunate, but can we really fault them? I'm
> thinking out loud here, but what if they mirrored their On Demand svn
> repository on GitHub, then we created a community fork off of that?
Agreed, a business has to make money first & foremost. However, I'm not
so sure that they want to give away what they consider as their bread
and butter, and in many respects I can't blame them for that.
Interesting suggestions for sure though. I think getting bugs fixed and
incorporated is the priority. If you don't run the svn copy, trying to
find and apply patches is a nightmare. For many users that may leave
them wide open to any bugs discovered if they do not check the trac etc.
My 2 cents FWIW :-)
B. Rgds
John
More information about the vtigercrm-developers
mailing list