On Sun, Mar 04, 2007 at 03:29:01PM +0000, Kake L Pugh wrote:
On Sat 03 Mar 2007, IvorW ivorw-openguides@xemaps.com wrote:
Ideally we _should_ all be sharing our code changes with the rest of the OpenGuides community. Unfortunately, there are some extremely forked code bases out in the big wide world, which is making upgrades difficult for some.
It might be worth starting a discussion on why people needed to fork in the first place.
I have some patches to which each of these apply.
Was it primarily because you expected to get around to packaging up your changes and sending in patches, but didn't?
* memcached integration falls into this category.
Or because you wanted to do something that wasn't appropriate for the main distro, but couldn't work out how to do it separately and integrate it into your Guide unobtrusively?
* Geocoder.us lookups fall into this category. * My particular brand of spam catching falls into this category. "couldn't" is relative -- I might have been able to, but didn't have the time to.
Or because your patches were difficult to integrate into the distro for some reason?
* http://dev.openguides.org/ticket/11 -- posted a patch with a 'running start', never got looked at with feedback on how I should change it.
My problem is I know very little perl, so I don't trust what I write, and I don't get a feeling that I'm getting a lot of feedback on what I should be doing to get code back to trunk. I have at least a couple outstanding minor patches in the OG trac that I don't know the status of or what I should do with.
Regards,