Re:Open source and the ability to modify code
by cromulent on Friday March 01, 2013 @10:15AM
(#5304596)
So, where you intend to fork and maintain, then fork and maintain.
If you do not intend to fork and maintain, then do not fork and maintain.
Is that what you are saying?
Re:Open source and the ability to modify code
by NickLarsen on Friday March 01, 2013 @10:21AM
(#5304628)
Yes, with a strong bias to not forking and maintaining. Stale project, well you gotta fork and maintain. Active project, avoid forking with the intention of using a custom build in your system.
Nick - it's just different levels. One can say the same thing about future versions of libraries not maintaining backward compatibility, and breaking APIs that applications depend on. So does this mean you should never download upgrades of libraries that your apps depend on?
The way I see it there are there levels in a good stack:
1. CORE 2. MODULES 3. APPS
Ideally, the thing should be extensible enough that the module writers can respond to changes in the core but keep their own API backward compatible. There are fewer modules than apps, and there is only one core.
So I think the whole argument isn't black and white, it's a matter of degree! Things have to get done, and sometimes things change. That's the only constant, you know :)
It should be noted that the situation where you intend to fork and maintain the project, this does not apply, and by all means make your changes. In the case where you intend to update, this pattern will help you avoid the pain.