JoomlaLeaks

Leaks, Drips, and Spills

All petitions expired
Petitions described below hosted on change.org have been closed.

 

09 Oct 2011
Written by
Rate this item
(5 votes)

Alice Grevet, a board member and Assistant Secretary of the Open Source Matters, Inc. board, writes a monthly article in the Joomla! Community Magazine title "Open Source Matters Report" for the month of that issue. It amazingly has absolutely nothing to do with OSM and everything to do with the other leadership teams within Joomla. Some people believe in conspiracy theories like John F. Kennedy's assassination, Roswell New Mexico's aliens, Princess Diana, and so on. If I was a believer in these conspiracy theories, I might want to believe that the OSM board has been preparing the way for some time to have all the other leadership teams reporting directly to the board. After all, why would OSM be reporting on their activities as if those activities were their own? Makes you think about this proposed organizational change doesn't it? After all, even Mel Gibson was eventually proved correct.

 

08 Oct 2011
Written by
Rate this item
(5 votes)

If you haven't read this blog by Paul Orwig written on September 29, 2011, you should. But what you should do next is read the input at JPeople and perhaps you will realize that it appears that a very few - mostly Joomla leadership is proposing major changes in how the Joomla project will be organized in the future. You will also note thet very, very few of the Joomla Community are participating in the discussion possibly again because there continues to be veiled and not so veiled implications that certain people have said enough. Doesn't encourage participation.

Currently the role of OSM is to support the developers who code Joomla. If the few who think defining a business structure and bringing the developers under the authority of the OSM Board of Directors (no matter what they might rename OSM to) will encourage the developers to code, they really haven't been living in the Open Source world. Right now there are limits to what the board can do. The developers in the Community Oversight Team can remove board members or add them at will. Kind of makes sure that OSM remains responsive to developers don't you think? Under discussion is a much simpler structure with OSM at the top operating without any oversight.