Forum OpenACS Development: bboard2procurement & eCommerce bank transfer payment method

We are currently adapting the bboard module to serve as a procurement marketplace. Our customer explicitly insists that  we make the module publicly available 😊 - which requires not only postgresql but also oracle support.

On of the enhancements is for example that posts are expirable.

We would like to ask to whom we should report for acceptance on behalf of the OpenACS community. Targeted date of release is middle of March.

Beside the bboard we will also make the bank transfer payment method publicly available in the eCommerce package and make the use for the ssl option for shopping optionable as our customer is using the AOL-Server behind a Proxying-Apache that does already SSL encryption, please also tell us to whom we should refer to.

Please get in touch with mailto:unido-acs@lanifex.com (eMail alias containing list of active developers).

Gregor

Gregor,
great news that you will be enhancing forums (you refer to Bboard but I'm sure you mean the forums package)!

Why don't you post the enhancements that you are planning and their patches in the Bug Tracker. That way the whole OACS community has a chance to review the changes.

... unfortunately we are building on the bboard package and not the forums package - I am aware of that the bboard package  won't be maintained in the future but that was the decision as both packages we compared and the customer prefered bboard. This is why I am concerned whether the code will be maintained in the future.

Depending on how strongly we modify the bboard package we could maybe rephrase to procurement package - jsut an ad hoc thought.

I will list the patches in the bug-tracker as proposed.

Nice greetings to Denmark - btw, I really like your new keyboard!

If there is only a overview of the proposed design I would find it more useful to post it here than to clobber the bug-tracker with it.

It seems that you have already a concrete improvement for the ecommerce package - that would make sense to put in bug-tracker including a patch if available. From there it can be applied by Bartt who as far as I know is the maintainer of ecommerce.

In the case of your planned bboard enhancements I got the impression that you are seeking for general advice before you start, so I think it's better to post them here for a wider audience.

I think there are still some people using bboard instead of forums for whatever reasons, and would be interested in keeping that package maintained (e.g. having bugfixes going into the main CVS etc.). They might not feel comfortable with radical changes, so maybe you should consider making your own version of bboard, for example bboard-enhanced, and make it available to whoever is interested. Whatever is the best solution can only be judged after you posted all your planned changes here.

Btw., for expiring posts you might be able to use existing CR functionality.