Index: openacs-4/packages/dotlrndoc/www/doc/dotlrn-faq.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrndoc/www/doc/dotlrn-faq.adp,v diff -u -r1.4 -r1.5 --- openacs-4/packages/dotlrndoc/www/doc/dotlrn-faq.adp 12 Apr 2002 18:01:31 -0000 1.4 +++ openacs-4/packages/dotlrndoc/www/doc/dotlrn-faq.adp 28 Apr 2002 20:09:47 -0000 1.5 @@ -1,196 +1,224 @@ -<%= [dotlrn_header "dotLRN FAQ"] %> -
- -

The dotLRN FAQ

- -

part of dotLRN - -

Contents - -

- - -

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 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 OpenACS v4.5. Currently, dotLRN requires - some fixes to OpenACS that are not part of beta1 (but which - will be part of a later beta), so you'll need to download the - latest OpenACS CVS.

When dotLRN is - released as a complete tarball, we will specify exactly which - OpenACS tarball you'll need to use. - -

Q: Wait, why isn't it compatible with PostgreSQL? -

- - We have focused our initial development on Oracle - compatibility for MIT Sloan. We have made significant headway - in PostgreSQL compatibility, and we (OpenForce) intend to use - dotLRN on PostgreSQL. Full PostgreSQL support is imminent, and - all progress will immediately appear in the CVS tree. - -

Q: Can I use ACS Classic 4.2/4.3? -

- - You can try, but we haven't done any testing with ACS Classic, - nor do we intend to. We suspect that the numerous improvements - made to OpenACS over the past few months will make dotLRN - incompatible with ACS Classic. - -

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

- - Yes, with major caveats. We don't make up-to-date tarballs of - the code regularly during this early phase of development. - Currently, dotLRN CVS requires the most recent OpenACS - development CVS, both of which change on a daily basis. This - means that unless you have up-to-date CVS from both sources, - chances are good that your dotLRN installation will - not function! And since the dotLRN tarball below is - not up-to-date, it won't function either. So why offer it for - download at all? Well, the only use for this is if you want to - read not quite the latest code but not actually use it. - -

- - Please don't tell us this dosen't work. We - already know that. :) Also, remember there is NO - BACKWARDS COMPATIBILITY with this code. - - dotlrn-core-apr-3.tar.gz - - - -

- 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. dotLRN is - pronounced "daught-learn" We are currently accepting - voice applications for the dotLRN MP3 pronounciation file. - -

-<%= [dotlrn_footer] %> +<%= [dotlrn_header "dotLRN FAQ"] %> +
+ +

The dotLRN FAQ

+ +

part of dotLRN + +

Last updated: $Date$ + +

Contents + +

+ + +

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 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: + +

+ +

+ dotLRN will probably work with: + +

+ +

+ dotLRN will NOT work with: + +

+ +

+ + 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: Wait, why isn't it compatible with PostgreSQL? +

+ + We have focused our initial development on Oracle + compatibility for MIT Sloan. We have made significant headway + in PostgreSQL compatibility, and we (OpenForce) intend to use + dotLRN on PostgreSQL. Full PostgreSQL support is imminent, and + all progress will immediately appear in the CVS tree. + +

Q: Can I use ACS Classic 4.2/4.3? +

+ + You can try, but we haven't done any testing with ACS Classic, + nor do we intend to. We suspect that the numerous improvements + made to OpenACS over the past few months will make dotLRN + incompatible with ACS Classic. + +

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

+ + Yes, with major caveats. We don't make up-to-date tarballs of + the code regularly during this early phase of development. + Currently, dotLRN CVS requires the most recent OpenACS + development CVS, both of which change on a daily basis. This + means that unless you have up-to-date CVS from both sources, + chances are good that your dotLRN installation will + not function! And since the dotLRN tarball below is + not up-to-date, it won't function either. So why offer it for + download at all? Well, the only use for this is if you want to + read not quite the latest code but not actually use it. + +

+ + Please don't tell us this dosen't work. We + already know that. :) Also, remember there is NO + BACKWARDS COMPATIBILITY with this code. + + dotlrn-core-apr-3.tar.gz + + + +

+ 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. dotLRN is + pronounced "daught-learn" We are currently accepting + voice applications for the dotLRN MP3 pronounciation file. + +

+<%= [dotlrn_footer] %>