...
This leads to several important Sakai Foundation roles in the Sakai project that have no direct analogues in the Apache project.
Sakai
...
The primary purpose of the Sakai Foundation Chief Architect is to insure the long-term technical coherence of all the Sakai software. The Chief Architect works with the framework projects(s) and many other projects to insure that Sakai continues to "fit together" in the long term.
The Chief Architect publishes guiding documents and technical roadmaps to guide Sakai developers. Roadmaps are not precise project plans, but instead a way to ensure that cross-project technical directions are well-communicated to all projects to best allow each project to be able to react to cross-project technical issues in a timely manner.
While the Chief Architect has broad responsibilities to communicate and interact across projects, she has no particular direct authority over any of the projects. Like any other member of the community, the Chief Architect must work cooperatively with the PMC for each project.
The Chief Architect may be called in to help resolve disputes between projects, but in this role, she is only offering her guidance and acting as a facilitator to help the conversation between the projects move forward.
Since the Sakai Framework projects have significant impact across all of the Sakai applications, typically the Chief Architect will work closely with the lead committer(s) in the core service/framework project(s).
The Chief Architect is not automatically granted committer status in any Sakai project. Like any committer, the Chief Architect must earn their committer status by their contribution and commitment to the particular project. The Chief Architect also has no particular say in the makeup of the commit list in any project.
The Chief Architect is responsible for producing a report each quarter that summarizes her activity and provides a forward-looking architecture roadmap. The roadmap is expected to be at a high level and lets the community know the likely directions in the next 6-24 months in terms of architecture. This report is targeted at the developer community and published broadly.
There is no analogue in the Apache project for the Chief Architect role. The Chief Architect role is one of orchestration across projects. By focusing the Chief Architect role on communication and not granting any particular authority to the Chief Architect the role is designed to enhance and support the Apache-style PMC structure used in Sakai.
Sakai Project Coordinator
The primary goal of the Sakai Foundation Project Coordinator is to track community activity across projects and help different activities work best with each other and work best with the community. The PC is expected to be a single point of contact about "who is doing what" in the Sakai community.
...