Dennis E. Hamilton wrote on Sat, Jul 16, 2011 at 11:43:13 -0700: > One place where Apache is pretty strict has to do with toolcraft and > the tools that must be used (e.g., the CMS for web sites and > Subversion for practically everything). These tools are used across > Apache for non-technical as well as technical reasons. They fit into > the visibility of everything that happens (the Subversion commit > messages include diffs) and the reversibility of anything that is > found to be undesirable or incorrect.
No one "must" use the CMS. There are some technical requirements that project Web sites must satisfy (eg: no dynamic code, scripts, etc may run on the Web server serving the sites), but the CMS isn't one of them. (Subversion, for example, uses svnpubsub but does not use the CMS.) As to Subversion: the most often requested alternative is Git, and people have begun work on making that a possibility within the requirements of Apache --- ref, grep the INFRA Jira issue tracker for "Git" open issues --- but that work has not finished, therefore native Git hosting is not presently an option. > The other area where Apache is rigorous has to do with IP and ensuring > that Apache-provided code is clean and under the Apache license.
