These are issues that the Technical Advisory Board will have to wrestle with, and sure, I have no problem with their being some level of transparency in the planning and in fact I welcome suggestions.
Ben is on vacation and until he returns we can't determine who from Open Force will be on the Technical Advisory Board. The TAB hasn't really done anything yet, partly because of Ben's being gone and partly because I've been extremely busy these past two weeks.
We can't really release an official version of dotLRN until there's an official release of OpenACS 4 for it run on. Thus the importance of driving OpenACS 4.6 out the door. This also means we have a little breathing space for planning the first release of dotLRN.
