Forum OpenACS Forum Summaries: OpenACS Core Team Summary for 28 Dec 2004

Collapse
1: OpenACS Core Team Summary for 28 Dec 2004
Posted by Joel Aufrecht on 12/28/04 05:47 PM
Present: Caroline, Don, Jade, Joel, Malte
  1. OpenACS Core 5.1.4. Waiting for DaveB to fix bugs in CR TCL API. Possibly some other things pending from Andrew Grumet for .LRN 5.1.
  2. OpenACS 5.2 branch: waiting on 5.1.4 release
  3. Forums next release (1.1) is waiting for someone (Andrew?) to test the Oracle upgrade. The release after that, which will go on OpenACS, will be 1.2; discussion of 1.2 design issues deferred until Dave and Jeff are present.
  4. Malte proposed making help text mandatory for ad_form fields
  5. OpenACS.org upgrade. Remaining problems are cataloged.
Collapse
2: Re: OpenACS Core Team Summary for 28 Dec 2004 (response to 1)
Posted by xx xx on 12/28/04 09:04 PM
If openacs.org bugs are cataloged in the general bugtracker, should the separate bugtracker still be available (https://openacs.org/bugtracker/)?

Is any special priority given to openacs.org bugs?

Collapse
5: Re: Re: OpenACS Core Team Summary for 28 Dec 2004 (response to 2)
Posted by Jade Rubick on 12/31/04 05:35 AM
No special priority are given to bugs in either place.
Collapse
3: Re: OpenACS Core Team Summary for 28 Dec 2004 (response to 1)
Posted by xx xx on 12/29/04 12:26 PM
Concerning 1./2.

CR didn't benefit from not having an UI in the past, IMO.

The docs say that CR is never supposed to have an UI, but I think it would be a good idea to include XCMS-UI in 5.2

AFAIK this package shows good practice of dealing with CR and I think including it in the core could stimulate use of CR.

Furthermore, if XCMS-UI doesn't get enough support, I am afraid it may just become the next out-of-date UI to CR.

Any opinions?

Collapse
4: Re: Re: OpenACS Core Team Summary for 28 Dec 2004 (response to 3)
Posted by Dave Bauer on 12/29/04 02:49 PM
Aldert,

I am planning on working on releasing this package so it is usable with OpenACS 5.1. This will require switching from the BCMS api to the CR api and cleanup to make sure it installs correctly.