Framework: What you say?
Finally back from my month-long "sabbatical" and attempting to catch up with the dev list chatter.
Recently, I've noticed more than a few references to a Sakai "framework" - not a phrase I really understand in the Sakai context. Did I miss something? Every time I feel like I'm able to peel back a few more conceptual layers of the onion that is Sakai, I find seven new things that I've never heard of before. A lot of that is just due to the incredibly brilliant people we have working on Sakai (who don't always have time to write things down right away) and the collaborative nature of the work that leads to concepts being developed in ad-hoc ways (like during conference calls, or in hallway discussions during conferences).
However, in my RTFM research, I found that there is actually a confluence space for framework, which contains this nugget: "(Note that some documentation may refer to Kernel, rather than Framework, as the latter moniker was picked after we began exploring the concept.)" So Framework == kernel?
Except, looking a little deeper, I see from this confluence page that that's not quite the case, and that the "framework" concept seems to pre-date the whole "kernel" discussion. In fact, this all came to my attention in the first place because of Ian Boston's instructions for installing the ContentHostingService which say to deploy sakai "with framework."
At least I'm in good company:
"The current framework services are not very well defined (in my opinion)" -Aaron Zeckoski
"The current organization makes little or no sense to me." -Mark Norton
