On Wed, Nov 10, 2010 at 1:10 PM, Galen Charlton <[email protected]> wrote:
> -1 for moving etc to a separate Git project. The default > configuration files are an integral part of Koha. For variant > configurations such as a Plack or nginx config, it would be clearer to > have relevant files in subdirectories or identified by file name > instead of putting them in branches. That way, somebody installing > Koha for the first time would see (say) both an etc/koha-apache.conf > and an etc/koha-nginx.conf; i.e., all of the options would be directly > in front of them. Furthermore, often changes made to files in etc are > dependent on changes made to code or templates; separating etc and the > rest of Koha into submodules would make it harder to prepare patches > and manage topic branches. > > I'm with Galen here. > 0 for moving the PO files to a separate Git project. The size of the > repository doesn't really strike me as a big deal; the Git protocol is > pretty efficient. That said, while I don't see a great deal of > benefit to splitting the translations off into a separate repository, > I don't see much harm either. > If setting up the PO files as a separate project allows one PO repo to be "submoduled" to several Koha repos then I can see how this might benefit a multi-koha server. As it is, we don't implement any language other than English, so it really does not matter to me one way or the other. Kind Regards, Chris
_______________________________________________ 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/
