Because Koha's API and schema lack consistency, abstraction, and isolation of concerns, adding nearly anything substantial demands that those elements change in ways that affect other areas radically. The amount of resources required to rebase dozens of individual feature branches when half of them require meddling with the key internals in way that will affect others increases in a non-linear fashion with the passage of time.
I agree. Rather than forming comitees, Koha community has to deal with software engenering challenges. A dump (and informal) rule should impose to any entity adding to Koha a large new feature to do also substantial code rationalization and cleanup. (I don't say it's easy...)
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
