Al, you're trying to make the relationship between the two entities something that just doesn't resemble reality.
YES, we've moved the .LRN-specific code base into our CVS tree.
YES, we're doing what we can to merge code to avoid duplication of error, code drift that would kill .LRN's ability to run on our core, etc etc.
But the .LRN configuration is still uniquely matched to the academic environment
And I just don't see the NEED to intermingle our identitities. Has Zope been hurt by the rise of the popular CMS application built upon it, Plone? Hardly. Just the opposite.
Branding .LRN as a vertical application built of OpenACS components with some "glue" helps legitimatize OpenACS as a development platform for the building of vertical applications.
We should, and I am quite sure will, maintain the distinction.
And you should take care with your posts, Socratic or otherwise. What if a University CIO, sitting on the fence regarding giving .LRN a fair hearing, Google's '.LRN" and hits your post on the front page of the search results. Now, that's stellar marketing - "should we disolve the .LRN consortium". If that's all they see, what the hell do you think THEY'LL think?
