- We now have a sort of organisation chart for the Sakai Foundation, which is good (this says that the Foundation is maturing). The Requirements process is one part of the Foundation, where users have their influence. Software coordination (including QA) and community communication are the other two parts of the Foundation organisation.
- Adoption of Sakai is still growing.
- There are some working principles, such as Public discourse as much as possible, meritocracy, distributed decision making. The essential principle is that there are no 'bosses' who make the decisions. There are project coordinators (and not managers!), which concept is stolen from the Apache Foundation.
- Because of the Requirements process (Mark Norton is coordinator), we don't have to burden the developers with these kind of stuff. They can develop!
- There is a community requirements summary for every release, so that there is a short document for everyone to read.
- Quality Assurance (coordinator is Megan May) is making more waves. QA makes the final call for a releases. QA broadens the community involvement, because not only nerdy people are involved here.
- Anthony Whyte is the coördinator for community communication.
- The only thing we are non-transparent about, is security. This is only communicated to people we know (which is also copied from the Apache Foundation) before we inform the public.
- Communication should be better :-). We are going to redesign the website and all that stuff that is behind it (seamlessly integrate confluence, jira and collab). One improvement that Chuck kept repeating: we need a document library. I cannot agree more.
- One important document in this document library should be a Roadmap.
woensdag, december 06, 2006
We have got a structure!
Charles Severance just started his overview of the Sakai Foundation. His main message was that we are not sprinting anymore, we are at a slower pace, but with much more quality and much more people involved. There were some other interesting messages from his talk: