Creating the Mambo Foundation The idea of using a nonprofit organization to direct Mambo, while keeping it separate from Miro International, started in April. In discussions, the idea sounded good to core developers Brian Teeman and Andrew Eddie. Reportedly, they decided something like the Mambo Foundation was very useful and could help keep CEO Peter Lamount involved with his project. To create the structure of the foundation, Miro held a meeting for the MSC (Mambo Steering Committee) in Australia. Brian Teeman and Andrew Eddie flew themselves there so that they could contribute. The MSC formed an agreement that Miro would file a letter of intent to transfer copyrights and trademarks to the foundation. It was also understood that the foundation would do fund raising activities to help support Mambo. It was still undetermined if Miro would have any direction in governing Mambo's development, so the matter was left open ended. Andrew Eddie backed the idea of Miro becoming more involved in Mambo. He described Mambo as rising steady in popularity, but it was reaching a plateau of users (mostly hobbyists and open source activists). He said in an interview:
He also viewed the foundation as a very positive thing. In providing direction for the project, it would keep developers from changing things users wanted to remain and to provide better focus in the development, instead of constantly changing APIs and interface tweaks. He believed Miro was not trying to pull Mambo back “into the fold,” and he emphasized Mambo’s involvement:
In short, the Core Development Team originally saw a lot of promise in Mambo Foundation. They had been fully involved in drafting the foundation documents. As Miro proceeded through the legal process to form the nonprofit, developers assumed that the foundation documents they agreed on remained unchanged.
blog comments powered by Disqus |