In the past month the Product Council has, for the first time, turned its attention to Sakai 3. It wasn't too long ago, in fact, that Sakai 3 first entered incubation from R&D. The Sakai 2 tools that the Product Council reviewed back in November and December emphasized the release gatekeeping role of the Council, which may have been a necessary start, but also perhaps a misleading one.
My focus is shifting ever more toward community-based activities that inform and shape Sakai 3. Again, I think Sakai 3 represents for us not just a new codebase and user experience, but also new ways in which the community comes together to produce the product.
This has been some time in coming, but Sakai 3 as a whole is now in incubation. It wasn't too long ago that "Sakai 3" stood as a category within which other projects were being incubated (e.g. K2, Groups), but we've come to the realization that although this compartmentalization may have made it easier to think about the issues piecemeal, it wouldn't be helpful for producing the earliest iterations of a product that needs to hang together.