First of all I think the portion of the title "
viewing from a distance" should be taken as a note that I have not been involved in the internal decision making process of the Joomla people site that has recently gone into beta mode. I am not even aware if there was a formal process in place.
However, it has become obvious to me and to others that matters of such concern should have been thought-out better from the start instead of creating a situation that invites confusion and arguments. Not that there is anything wrong with arguing in a civilized tone as such discussions can prove very productive.
It appears (once again pointing out that this is the view I have from were I stand) that a new effort has gone public with the following view from a distance characteristics listed as they seemed to occur:
- discussion in google group about starting a community site
- public announcement of technical solution decision asking for community involvement in the form of an RFC (?)
- beta launch of people.joomla.org site
- thread discussions to decide (?) what rules and boundaries should govern the live beta site
- thread locked without any message to community
What's wrong in this order?
Well, I would assume that in a logical project management order something like this should happen:
- Proposal document prepared that contains basic idea of project, project goals - mission statement (how to assess if final outcome is successful?), proposed approach
- RFP issued - doesn't have to be public just has to be present. The RFP documents should contain (an internal?) evaluation process/criteria from the start, so everyone on the decision making team can use later on. Would even be good to have a risk assessment document for things that could go wrong.
- RFP shared with organization(s) that for whatever reason are deemed as suitable to undertake the project
- Evaluation process (based on previously set criteria evaluation guidelines)
- Announcement of award (doesn't have to be public) - project management tasks (requirements document, development, testing, deployment, go live, maintenance phase, etc)
It appears that the people site effort had no apparent mission statement or at least no public mission statement. If such a statement existed, then the rules and boundaries discussion would have been easy to work out. At the moment the process is backwards. Managing a community is very different from moderating a forum. Its like the game of life - where the player just places the seeds in the beginning and lets the cells interact. It is impossible to foresee the situation in the future.
Of course these thoughts are my own personal observations that for some reason I feel cannot be posted on the Joomla forums (that's another issue - so I am glad this site exists).
I see some mistakes in this process and since I know that ATAAW is considering a new "community" site perhaps others in the ATAAW team see them also. In order to learn from mistakes one must first accept and acknowledge their existence.
Thanks for reading ...
You need to be a member of All Together, As A Whole to add comments!
Join All Together, As A Whole