dotLRN FAQ

## The dotLRN FAQ

part of dotLRN

Last updated: $Date: 2003/01/22 14:23:38 $

Contents

- Basics
- State of dotLRN Development
- The OpenForce Role in dotLRN
- dotLRN and OpenACS
- Licensing
- Miscellaneous

Basics

Q: What is dotLRN?

dotLRN is a full-featured application for rapidly developing web-based learning communities, specifically in the context of Course Management. The dotLRN software relies on a development version of OpenACS v4.5 and includes data model, application logic, and templates to get you up and running very quickly.

Q: Is dotLRN usable?

dotLRN is currently in alpha state. The target audience at this time is mostly early adopters. No backwards-compatibility will be ensured until a beta version. That said, dotLRN is quite stable as is and can most certainly be used to determine near-term usability in a production environment.

Q: When will dotLRN ship?

dotLRN beta is planned for May 1st, 2002. dotLRN v1.0 is planned for August 1st, 2002.

Q: How can I contribute?

We are currently developing our contribution mechanisms.

If you are actively interested in helping us develop these mechanisms, please contact us at dotlrn@openforce.net.

Q: What about this dotLRN Governance discussion?

The discussion is still under way. MIT Sloan will be providing the framework for this in the very near future.

State of dotLRN Development

Q: So what version of OpenACS do I need to use?

dotLRN will work with:

- The latest development CVS sources (i.e. HEAD). Instructions to check out the latest development CVS sources are on the dotLRN installation page.

dotLRN will probably work with:

- A recent OpenACS nightly tarball But we don't test this, and all the warnings on the page apply

dotLRN will NOT work with:

- The OACS v4.5 beta CVS branch
- Any OACS v4.5 beta tarballs

When dotLRN is released as a complete tarball, we will specify exactly which OpenACS tarball or other package you'll be able to use.

Q: When will dotLRN be compatible with PostgreSQL?

PostgreSQL compatibility porting continues rapidly and will be completed in the coming weeks. A partial port is in the CVS tree, with more progress daily.

Q: Can I use ACS Classic 4.2/4.3?

Due to numerous fixes and enhancements made by the OpenACS developers, dotLRN will not work with ACS Classic. However, ACS Classic and OpenACS are similar enough so that code and skills based on one are very transferable to the other.

Q: Can I get a tarball of the dotLRN CVS?

Contact us at dotlrn@openforce.net if you are interested in a tarball.

The OpenForce Role in dotLRN

Q: What's the relationship between MIT Sloan and OpenForce?

MIT Sloan hired OpenForce to develop dotLRN to replace the aging SloanSpace v1, which itself was built on ACS v3.

Q: How will OpenForce work with other OpenACS developers?

OpenForce will continually provide anonymous CVS access to the dotLRN development tree. OpenForce will continue to provide architectural direction and goals for dotLRN. Over time, OpenForce will qualify and include new developers in the core development process. OpenForce expects to lead - but not monopolize - the dotLRN process. OpenForce will also provide a repository of dotLRN applications available for all to obtain existing dotLRN extensions and provide new ones to the community.

Q: Will OpenForce develop, support, and/or host dotLRN commercially?

Absolutely.

Q: Will OpenForce preclude me from providing my own services surrounding dotLRN?

Absolutely not.

Q: But Why? Aren't you crazy to throw away such clear business opportunity?

We are not in the business of selling packaged closed-source software. We believe that open-source software and a strong developer community provides plenty of opportunity for numerous commercial services. We intend to stick to the Open-Source track 100%. No tricks here.

dotLRN and OpenACS

Q: Is dotLRN a part of the OpenACS project?

dotLRN is not part of the OpenACS project, but it is an OpenACS application. This means that dotLRN will install on a vanilla OpenACS without additional modifications and through the regular, accepted OpenACS API. While dotLRN developers happen to also be core OpenACS developers, the dotLRN team is taking all possible measures to ensure that any modification suggested to the OpenACS core is approved by other OpenACS developers that do not have a direct stake in dotLRN.

Q: Will dotLRN be merged into OpenACS?

This is a question to be answered by the OpenACS community.

Licensing

Q: What are the terms of use for dotLRN?

dotLRN is distributed under the GNU General Public License version 2.

Miscellaneous

Q: How is dotLRN spelled and pronounced?

It's sometimes written as `.LRN`, but the spelling and capitalization `dotLRN` is preferred. hackers who type a lot usually write `dotlrn`. `dotLRN` is pronounced "daught-learn" We are currently accepting voice applications for the dotLRN MP3 pronounciation file.