• Home »
• OpenACS

This is an email I sent out about ETP 2 to some interested parties. I want to create a "Joel-on-Software" type of schedule so I can figure out when its done.

Also see: Original ETP Planning doc

Here are some items I think need to be addressed to get ETP2 going:

• UI redesign: This has not been addressed. It won't be really tricky we can base it on the modetp design and use some spiffy icons.
• ad-form: let's rewrite the forms with ad_form
• file upload: I think we can use cr_import_content to handle this, the tricky part is associating the images/files with pages. Possbily use the simplified cleaned up attachments package.
• workflow: this has been deferred until workflow is finished. Well, workflow is finished, but to get something released, it probably will not be in ETP 2.0.
• search: I want to fix the search triggers to only index live_revisions. This is not specifically an ETP2 issue. DONE
• user submitted content: This works, but I want to clean it up. I used ad_form with ETP1 to create the link submission for openacs sites and opeancs hosting and openacs companies and it was very easy.
• clean up APIs: abstract parts out to pl/pgsql or tcl procs
• sample applications: create sample applications such as weblog, news, faq etc...
• use internal_redirect instead of rp_serve_abstract_file DONE
• extract queries to XQL files, port to oracle
• test with subsites
  subsites need their own content-folder MOSTLY WORKS
• categorization: I really want to implement Neophytos' plan for a acs_object categorzation package, instead of using the CR only categorization. Timo is added a new categorization package. It meets most of the design goals of Neophytos system. We can use that. It won't be ready until 5.0 at least.

  OK, this is all I can think of, its a long list. I wanted to look into CMS to see if there are any nice bits to borrow.

  There is probably something to associate images, and templates to content items.

  We just have to decide what to put in, and what to save for ETP3.