PHP Programming Language - Cultural View

PHP Programming Language - Cultural View PHP Programming Language - Cultural View

culturalview.com
from culturalview.com More from this publisher
10.02.2013 Views

Mambo (software) 116 • Mambo Open Source 4.0 is released. • 2003: Early in 2003, Miro hands off the responsibility of the code fully to the Open Source project Development Team. • Miro concentrates on its commercial products and Mambo Open Source builds momentum under the leadership of Robert Castley. • Miro released Mambo CMS, a commercial version of Mambo Open Source. Miro claims that Mambo CMS does not contain any source added to Mambo after it was made open source. [6] • Miro Construct Pty Ltd goes into voluntary liquidation in February 2003 and in August, Miro International Pty Ltd is formed. [7] Source code for Mambo Open Source shows copyright 2000 - 2003 Miro Construct Pty Ltd. • Mambo Open Source 4.5 released in December 2003. By this time, almost all of the original Miro code had disappeared during refactoring. • 2004: mamboforge.net starts in March, 2004. • Linux Format awards Mambo “Best Free Software Project” of the Year. [8] • Linux User and Developer names it “Best Linux or Open Source Software”. [9] • In late 2004, Mambo was targeted by legal threats concerning the intellectual property rights to certain pieces of code contained in the core. The problem was severe and cost money, man hours, and eventually the loss of some key community leaders. Miro came to the aid of Mambo, offering legal and corporate resources to protect the development team and preserve the program. [10] • Robert Castley resigns as Project Director and in November, Andrew Eddie takes on the role. [11] • December 2004: the Mambo Steering Committee was established with representatives from both Miro and the Mambo development team. This committee was designed to govern the Mambo project. [12] • January 2005: Andrew Eddie announces a joint venture between Mambo and Miro International Pty Ltd, with Miro proposing to offer financial support for the open source project, plus training, commercial support services, and developer certification. [13] • February 2005: Discussions begin over the formation of a non-profit foundation for the Mambo project. • March 2005: The name "Mambo Open Source" (which was commonly referred to as MOS) was changed to just "Mambo", causing concern in the community over apparent confusion this would cause between the open source, community-developed CMS and Miro's commercial offering, "Mambo CMS". [14] • April 2005: The commercial Mambo CMS is renamed "Jango". [15] • “Best Open Source Solution” and “Best of Show - Total Industry Solution” at LinuxWorld Boston. [16] • “Best Open Source Solution” at LinuxWorld San Francisco. [17] • July 2005: mambo-foundation.org domain is established. • August 2005: Mambo Foundation, Inc is legally constituted on 8 August 2005. Miro CEO Peter Lamont appoints himself President of the Board of the new Foundation. [18] • 12 August: Robert Castley, who is an inaugural member of the Mambo Foundation Board of Regents, states: "The Foundation allows for everything to be placed outside of Miro incl. Domain Names, hosting etc. " and goes on to say that with him, the original founder of Mambo Open Source, and Andrew Eddie both being on the Board of the Mambo Foundation, Mambo would continue as a successful, open source project. He concluded his statement with,"So there you have it: two very key people in the overall success of Mambo are at the helm. Trust me, Mambo is in very, very safe hands!" • A few days later, the entire team of core programmers publicly announced they had abandoned Mambo and shortly after this, Robert Castley steps down from the Board of Regents. [19]

Mambo (software) 117 • The former core development team members regroup under the name "Open Source Matters" and the open source community at mamboserver.com fractures over allegations that the Mambo Foundation was formed without community input and with insufficient developer control. People express suspicion over the level of involvement by Miro International. By the end of August, the new project is named Joomla! and most of the former Mambo community has relocated to Open Source Matters. By the end of September, Open Source Matters Inc is a duly constituted non-profit corporation registered in New York. [20] • Joomla! positions itself as a "rebranding of Mambo" and releases its first fork of Mambo as Joomla 1.0 in September, 2005. The two code-bases are almost identical at this stage. • Mambo forms a new core development team with Martin Brampton appointed as Core Development Team leader. [21] [22] • Miro assigns all rights in the copyright of Mambo to the Mambo Foundation. • December 2005: Miro International Pty Ltd is voluntarily deregistered as a company from 31 December 2005. [23] • January 2006: The rights to Miro International Pty Ltd are sold by Peter Lamont and a new business entity called Miro Software Solutions is created. Miro Software Solutions continues to develop Jango and other proprietary software under new ownership. [24] • March 2006: Mambo named "Best Open Source Software Solution" at LinuxWorld Australia. • April 2006: Core developer team leader, Martin Brampton, resigns and leaves the project. Chad Auld takes over the role as Core Developer Team leader. [25] • July 2006: The Mambo Foundation websites become independent from Mambo Communities Pty Ltd. [26] • Following elections, the new Board of the Mambo Foundation takes office. The Mambo Foundation is now completely independent of any corporate interest. [27] • April 2007: Mambo 4.6.2 is released. This is a maintenance release for the 4.6.x branch and enables localisation of Mambo. [28] • January 2008: Mambo 4.5.6 is released. This is the final release of the Mambo 4.5 branch. [29] • February 2008: Chad Auld leaves the project. [30] • March 2008: John Messingham becomes Project Leader. Ozgur Cem Sen becomes core development team leader. [31] Ozgur Cem Sen leaves the project shortly thereafter. Andrés Felipe Vargas Valencia is elected Team Leader. • April 2008: Four former Mambo core developers fork Mambo and form MiaCMS. Who forked Mambo as they felt that Mambos policies, processes, and priorities of the official Mambo Foundation were having a negative impact on the code and the community. [32] • May 2008: Mambo 4.6.4 is released. Codename 'Sunrise', Mambo 4.6.4 is a security and maintenance release that fixes a number of serious security vulnerabilities. [33] • June 2008: Mambo 4.6.5 is released. Codename 'Jupiter', Mambo 4.6.5 is a security release that fixes a number of serious security vulnerabilities. [34] • September 2008: Mambo announces end of life for supporting PHP 4. All future releases will require PHP 5.2 or higher. [35]

Mambo (software) 117<br />

• The former core development team members regroup under the name "Open Source Matters" and the open source<br />

community at mamboserver.com fractures over allegations that the Mambo Foundation was formed without<br />

community input and with insufficient developer control. People express suspicion over the level of involvement<br />

by Miro International. By the end of August, the new project is named Joomla! and most of the former Mambo<br />

community has relocated to Open Source Matters. By the end of September, Open Source Matters Inc is a duly<br />

constituted non-profit corporation registered in New York. [20]<br />

• Joomla! positions itself as a "rebranding of Mambo" and releases its first fork of Mambo as Joomla 1.0 in<br />

September, 2005. The two code-bases are almost identical at this stage.<br />

• Mambo forms a new core development team with Martin Brampton appointed as Core Development Team leader.<br />

[21] [22]<br />

• Miro assigns all rights in the copyright of Mambo to the Mambo Foundation.<br />

• December 2005: Miro International Pty Ltd is voluntarily deregistered as a company from 31 December 2005. [23]<br />

• January 2006: The rights to Miro International Pty Ltd are sold by Peter Lamont and a new business entity called<br />

Miro Software Solutions is created. Miro Software Solutions continues to develop Jango and other proprietary<br />

software under new ownership. [24]<br />

• March 2006: Mambo named "Best Open Source Software Solution" at LinuxWorld Australia.<br />

• April 2006: Core developer team leader, Martin Brampton, resigns and leaves the project. Chad Auld takes over<br />

the role as Core Developer Team leader. [25]<br />

• July 2006: The Mambo Foundation websites become independent from Mambo Communities Pty Ltd. [26]<br />

• Following elections, the new Board of the Mambo Foundation takes office. The Mambo Foundation is now<br />

completely independent of any corporate interest. [27]<br />

• April 2007: Mambo 4.6.2 is released. This is a maintenance release for the 4.6.x branch and enables localisation<br />

of Mambo. [28]<br />

• January 2008: Mambo 4.5.6 is released. This is the final release of the Mambo 4.5 branch. [29]<br />

• February 2008: Chad Auld leaves the project. [30]<br />

• March 2008: John Messingham becomes Project Leader. Ozgur Cem Sen becomes core development team<br />

leader. [31] Ozgur Cem Sen leaves the project shortly thereafter. Andrés Felipe Vargas Valencia is elected Team<br />

Leader.<br />

• April 2008: Four former Mambo core developers fork Mambo and form MiaCMS. Who forked Mambo as they<br />

felt that Mambos policies, processes, and priorities of the official Mambo Foundation were having a negative<br />

impact on the code and the community. [32]<br />

• May 2008: Mambo 4.6.4 is released. Codename 'Sunrise', Mambo 4.6.4 is a security and maintenance release that<br />

fixes a number of serious security vulnerabilities. [33]<br />

• June 2008: Mambo 4.6.5 is released. Codename 'Jupiter', Mambo 4.6.5 is a security release that fixes a number of<br />

serious security vulnerabilities. [34]<br />

• September 2008: Mambo announces end of life for supporting <strong>PHP</strong> 4. All future releases will require <strong>PHP</strong> 5.2 or<br />

higher. [35]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!