JoomlaLeaks

Leaks, Drips, and Spills

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

 

tunnel vision n (ca. 1942) 1: constriction of the visual field resulting in loss of peripheral vision; 2: extreme narrowness of viewpoint: narrowmindness; also : single-minded concentration on one objective – tunnel visioned adj

  Webster’s Collegiate Dictionary, 1996

Some leaders perceive they can, by force of will, ensure the intended consequences of their actions – even in the face of mounting evidence that the outside forces (e.g. competitors, regulators, economic conditions, customers, or community) are not reacting to their expectations “correctly.” Greek tragedians referred to this failing as “hubris” – the overwhelming pride that blinds the tragic hero to the consequences of his/her actions. The audience can clearly foresee the inevitable fall from a great height, but the tragic hero is blind to all but his own intentions.

 If you have not yet had the opportunity, I suggest you read Paul Orwig's latest communication in the Joomla Leadership Google Group.

Published in Joomla

I am still trying to figure out how the board of OSM went from wanting to install numerous "liaison's" or committee chairs between the board members and the various committees or teams that the newly installed president of OSM seemed to want back in April of 2010 to the current proposal of incorporating all Joomla! leadership groups within the overarching reach of the OSM structure. Back in April of 2010, Elin Waring attempted to explain that the Core team didn't want to be on committees. They wanted OSM to deal with the business aspects.

Board Meeting Minutes 4/19/2010

2. Liaisons and committees, brainstorming session (Ryan Ozimek)

Elin explains history how Core team each was on a Committee. They now prefer that we deal with OSM business.

Published in Joomla

I find it a little more then curious that the President of OSM has not taken part in any of the discussions surrounding the proposed restructuring of the Joomla! Leadership with the Board of OSM being over all Joomla! teams. In fact, as I pointed out in the blog Where's Waldo (err.. Ryan Ozimek)?, Mr. Ozimek has only really been visible in his world-wide travels. The President of the Board has certain responsibilities including:

  • Execute the will of the board
  • Provide leadership to the board
  • Develop a vision for the board
  • Be the communicator or spokesperson for the board
  • Manage the effective use of meetings (regular and committee meetings)
Published in Joomla
Friday, 25 November 2011 14:36

Joomla! Leadership - Bait and Switch

 
 
 
 
In lawmaking, "caption bills" that propose minor changes in law with simplistic titles (the bait) are introduced to the legislature with the ultimate objective of substantially changing the wording (the switch) at a later date in order to try to smooth the passage of a controversial or major amendment. Rule changes are also proposed (the bait) to meet legal requirements for public notice and mandated public hearings, then different rules are proposed at a final meeting (the switch), thus bypassing the objective of public notice and public discussion on the actual rules voted upon. While legal, the political objective is to get legislation or rules passed without anticipated negative community review.
  From Wikipedia - "Bait and Switch"
Published in Joomla
Thursday, 17 November 2011 11:27

It's Probably Not Really A Conspiracy But ...

... it might as well be!

Yesterday, Paul Orwig posted to the Google Joomla Leadership Group that the OSM board had suggested that he extend his solicitation to the leadership seeking their opinion on whether they go forward with the proposed structural changes to the Joomla! Project. The original post was made October 30 and there had only been one reply and that was from Brad Baker who didn't necessarily see the proposed changes as a solution to the issues raised but said "Still, I am happy to support the majority". Which is, of course, one of the problems I see with the Joomla Leadership as a whole. (See Groupthink blog.)

Unfortunately, Paul Orwig is not only a member of OSM, he is also its Treasurer - one of the now four officer positions of the board. He is also a member of the Community Leadership Team (CLT). That definitely puts him up there as one of the leaders within Joomla.

Published in Joomla

On October 18, 2011, Paul Orwig who had originally started a discussion group on September 29, 2011 about Proposed leadership structure changes & request for community feedback posted in the Google Joomla Leadership public group that he was thinking of closing discussion on the proposal even though he committed originally to leave discussion open until October 27, 2011. Immediately, more discussion ensued. At the time he was proposing to shut down discussion there were 157 posts. As of today, Friday, October 21, 2011 at 1:17 pm CDT, there are 186 posts. Interestingly enough those 186 posts were placed by only 23 individuals. And, of those 23 individuals, only 16 are not members of the OSM Board, the Community Leadership Team, or the Production Leadership Team. Besides the obvious observation that very few of the community have weighed in with their opinions, very few of the various leadership team members have weighed in with theirs either.

Published in Joomla

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.

Published in Joomla
Page 2 of 2