I haven't heard anything about this, but if you hear more please let me know.
The cynical view: http://www.moodleus.org/blog/?p=44
A look at the sales hype: http://blogs.csuchico.edu/tlp/?p=89
We have WebCT-Bb, [plus a home grown product, Interact] but start next week with a Moodle trial. Whatever the destiny (>Bb NG or >Moodle) there is huge change coming up for us. My impression is Bb NG is a HUGE shift.
Here, the change from WebCT4 > Bb 6 did not realise the expected gains in functionality and ease of use and pedagogical support.
The trial is going well: BUT in the real world of research, papers, winter flu and families, many trialists seem to have disappeared off the face of the earth (as far as the trial is concerned) and I KNOW their courses are not ready. Next week the tsunami will hit I am sure: 43 support calls!! ?? It will be fun.
I hear all sorts of rumours on how much the Bb presentations are mockups or real, and how much coding is done. In the world of S/W you can mistake a clear view of what you want with closeness of the goal. I'd look for a public (even if evolving) roadmap. I do not know if they will give one. I am a minion. I support Bb users, do Bb workshops, but am not allowed into the official Bb forums, wiki or anything. I do not get to go to the closed meetings.
We have been promised somethng to look at in Sepember.
A colleague e-mailed me. "One LMS to unite them, one LMS to rule . . . "
Enough ramble. - Derek
We ran both Moodle and Blackboard with the same user name and password (though not file sharing or sso) for 3 years. A big thing students and faculty kept asking was to choose one system and stick with it. Sharing files and SSO aren't the big problems, in my experience - a much larger problem is learning two or more different interfaces. Some users (who tend to gravitate toward technical positions and be early adopters) have little problem learning how systems work, and similar systems with different interfaces are not a big problem for this kind of technology user.
For a (perhaps much larger) group of users, they memorize colors, icons, and the position of buttons when learning an application. Even minor changes in interface cause a great deal of problems for this group. In my experience using and integrating different systems, the more similar two systems are in function - the harder it is for non-technical users to learn how to operate them. In other words, it's easy enough to understand why a bank software system functions differently from a wiki, but harder if the bank had it's own wiki, but was also integrated with a different wiki, and sometimes you used one and in other places, you used the other. This kind of thing gets very tough, especially for students who may take courses in several different systems.
Chuck Severance, former Executive Director of the Sakai Foundation, has been hired by IMS to lead this; he is running a Google Summer of Code project to get some LTI consumers and producers built:
I've actually asked him who's involved from the Moodle community (since AU may be able to help with this work), but I suspect he's still recovering from last week's Paris Sakai conference.
I don't know if this is what Bb refer to. My guess is more that it's more just about accessing files uploaded into Moodle, perhaps something like our Repository API.
I've been following this thread and I thought I would jump in to clear up some confusion. There are two technologies being developed as a part of Project NG, our multi-release, multi-year vision of the future. These are the LTI interface and the Learning Environment Connector. The LTI interface allows remote tools to publish and connect to Blackboard courses. We are working with the IMS and hope that this interface will be a reusable standard so that people who develop tools can plug them into any compliant CMS/VLE. The Learning Environment Connector will connect Bb services/modules with courses which are not hosted in the Bb CMS/VLE. This technology will allow other Bb modules such as Outcomes, Community, Content, Transaction, and Connect to interoperate with other course management systems. A bi-directional flow of data is envisioned between Blackboard modules and the remote CMS/VLE. This technology has already been used to connect Campus Edition 4.1 to Blackboard 8. I am doing a session on the Connector at the DevCon portion of BbWorld next week; and will post further updates to the Blackboard blog (http://www.educateinnovate.com/) as we are able to make more details public.
I have not seen any information on the Moodle connector yet
We've just announced more details on our work to integrate Blackboard and Moodle. We're partnering with Iowa State to create this integration. We are currently in testing for this solution and we expect to release the connector components (a Blackboard Building Block, and Moodle Block) as open source via the OSCELOT project space. Detailed documentation on the connector APIs will be available on www.edugarage.com after we make the connector generally available. I will follow up here as more information is released.
Folks attending the Educause conference can join me at the Blackboard booth Tuesday October 28 at 5:20, or Wednesday October 29 at noon where I will be presenting on the topic of Blackboard's new open initiatives. If you are at Educause you may also want to attend our panel discussion on the emergence of open and interoperable technologies in higher education. This event will be held on Thursday from 11:45-12:35 in Room W223. This discussion will be lead by Scott Jaschik, Editor Inside Higher Ed. Panelists include Serge Goldstein, Associate CIO and Director of Academic Services, Princeton University, Charles Severance Former Executive Director, Sakai Foundation and Chief Architect, Sakai Project, Michael Morrison, Manager of Academic Applications, Syracuse University, and Michael Chasen CEO, Blackboard Inc.