Forum .LRN Q&A: Packages and where they currently are - OpenACS/dotLRN

Carl was aiming me today and sharing with me ideas about the OpenACS/.LRN packages.  In the ideal technical division, all generically-applicable packages would be part of OpenACS and .LRN would be a light package and some configuration of OpenACS.  A few months back, I divided the modules into 3 categories
1. Those that are part of the OpenACS repository and .LRN uses
2. Those that are part of the .LRN repository
3. Those that are part ofthe .LRN repository and .LRN does not use

I've heard that the OpenACS wanted to merge the CVS directories so the division between 1 and 2 will not be as apparent.

The other thing that happenned historically is that there are different portal systems in .LRN and OpenACS.  If .LRN moved to OpenACS portal system, the majority of the packages (potentially new-portal, all the portlets, and the ones like "dotlrn-faq") would then be using standard OpenACS packages.  I've starred these below ***

This isn't new information to those intimately involved. One approach to thinking about .LRN is that it is more of a marketing term - a configuration of a product that serves a specific set of users out of the box.  Looking at the list, particularly #2, and removing the the ones with the ***, you can see that it is really close...

1. Packages in the open-acs repository that are used by dotlrn
    acs-admin
    acs-authentication
    acs-bootstrap-installer
    acs-content-repository
    acs-core-docs
    ? acs-datetime
    ? acs-developer-support
    ? acs-events
    acs-kernel
    acs-lang
    acs-ldap-authentication
    ? acs-mail
    acs-mail-lite
    ? acs-messaging
    acs-notification
    acs-service-contract
    acs-subsite
    acs-tcl
    acs-templating
    attachments
    auth-ldap
    ? auth-pam/
    ? auth-server/
    ? authorize-gateway/
    bulk-mail/
    calendar/
    curriculum/
    faq/
    file-storage/
    forums/
    ? general-comments/
    logger/
    monitoring/
    news/
    news-aggregator/
    news-aggregator-portlet/
    notifications/
    photo-album/
    ref-countries/
    ref-currency/
    ref-itu/
    ref-language/
    ref-timezones/
    ref-us-counties/
    ref-us-states/
    ref-us-zipcodes/
    rss-support/
    survey/
    timezones/
    trackback/
    weblogger-portlet/

  2. Packages that are in the dotlrn repository and therefore are dotlrn-only

    bm-portlet    ***
    dotlrn-dotlrn
    dotlrn-portlet
    fs-portlet    ***
    calendar-portlet  ***
    dotlrn-faq        ***
    dotlrn-static    ***
    new-portal        ***
    curriculum-portlet
    dotlrn-forums    ***
    dotlrn-survey    ***
    news-portlet      ***
    dotlrn
    dotlrn-fs        ***
    dotlrn-syllabus
    profile-provider
    dotlrn-bm        ***
    dotlrn-homework
    dotlrn-weblogger  ***
    static-portlet    ***
    dotlrn-calendar  ***
    dotlrn-news      ***
    faq-portlet      ***
    survey-portlet    ***
    dotlrn-curriculum
    dotlrn-news-aggregator
    forums-portlet    ***
    user-profile

B. Those that would be not be considered in the core DotLrn product

  ? acs-api-browser/
  ? acs-automated-testing/
  acs-interface/
  acs-person/
  acs-reference/
  address-book/
  adserver/
  bookmarks/
  bookshelf/
  bug-tracker/
  categories/
  chat/
  clickthrough/
  cms/
  cms-news-demo/
  cronjob/
  directory/
  download/
  ecommerce/
  edit-this-page/
  email-handler/
  file-manager/
  gatekeeper/
  glossary/
  intermedia-driver/
  lars-blogger/
  notes/
  openfts-driver/
  organizations/
  page/
  payflowpro/
  payment-gateway/
  places/
  postal-address/
  press/
  redirect/
  robot-detection/
  sample-gateway/
  schema-browser/
  search/
  shipping-gateway/
  simple-survey/
  site-wide-search/
  skin/
  spam/
  static-pages/
  telecom-number/
  user-preferences/
  value-based-shipping/
  version-control/
  webmail/
  ? workflow/
  wp-slim/
  xml-rpc/