On his blog, Dave Neary has written up
the notes from a talk he gave at the Desktop Summit on the costs of working with community to get code upstream vs. the costs of not working with the community. The article (and talk) have several real-life examples of those costs. "To avoid missing out on this work, it's recommended to merge regularly changes from upstream into your local copy of the upstream package. But this merge is typically not free — and the bigger your changes, the more likely it is you will find significant conflicts between upstream and your local copy. There is also an additional, often-forgotten overhead involved with regression testing and validation post-merge. Every time I upgrade a component to a new version, I need to verify that it hasn't broken anything, either because of changed behaviour at integration points I'm using or simply because some regressions were introduced when fixing other issues.
to post comments)