Forum OpenACS Q&A: Fresh ideas

Posted by Ben Koot on
This is a continuation of the points raised about how to move on with oacs from a newbie point of view. (in order not to hijack the tread about "why do you use oacs" I will try to create a shortlist of sugestions based on forum postings, so we end up with a clear picture.
2: Re: Fresh ideas (response to 1)
Posted by Ben Koot on
Daniel. * Have the community write the documentation. Write a tool that allows the community to edit the documentation. OpenACS has most of the infrastructure, now use it. Be liberal with permissions.;

Note Ben. The current format is to go for the Wiki. Some interesting points on the topic have been made here, highlighting current problems re. documentation.

* For a webtool with the best translation toolkit I have seen, it is somewhat of a big surpise the OpenACS website is pretty monolingual. All infrastructure is in place, have the community translate it.

* Give more people CVS access, so they can contribute. The procedure should be easy with little bureaucracy.

3: Re: Fresh ideas (response to 1)
Posted by Torben Brosten on
Maybe it would help to read some of the documentation to keep from duplicating what has already been discussed on this topic?

That summary of more than 4 years of forum discusions took nearly 6 months to complete. I am certain readers experience information overload with it. Yet, it beats searching through the forums directly.

In short, most of the recent ideas have already been discussed in detail.

TO be helpful, one can:

1. find items not in that document that have been discussed since July 2003.

2. draft documents that meet some of the requirements in above url.

3. Consider incorporating the relevent requirements in any change efforts to this website or documentation.

For example, relevent requirements have been added to:

a. the wiki page: in reference to the recent thread about changing

b. quality improvement strategies discussion:

4: Re: Fresh ideas (response to 1)
Posted by Adam Aggeusz Jaworski on
5: Re: Fresh ideas (response to 1)
Posted by Jon Griffin on
I contend that although dotLRN has contributed much code, it also has caused many of the problems. We need to use OACS like it was intended when it forked off of ACS.
Don't add package dependencies to the core. If you can't code your package without affecting the core, don't add it to the core just because dotLRN needs it or whatever. It would be interesting to see how may OCT members don't work activly on dotLRN projects.

Also, there is no best practices documentation available at all. This has all been discussed before.

6: Re: Fresh ideas (response to 1)
Posted by Ben Koot on
To suport the spring clean up effort, I have added an overview of all available package to tips & hint's blog. The idea is to use this function as sketchbook, where everbody can add comments. In the end these can be reconciled into the bugtracker.

This way we have all outstanding issues and ideas in one easy to read format. I hope this will reult in a more effective overview than having individual issues about packages discussed in the forums.

7: Re: Fresh ideas (response to 1)
Posted by Nitish Bezzala on
I think we should be maintaining a list of OpenACS newbie things to do, and the estimated amount of time someone might take to do it. Stuff like -
Test the patch for bug number 1234
Check if document to install forums package is accurate
Come up with a nice new logo

If a newbie comes here, and has a couple of hours, or a day, then she must be able to pick a task and complete it in that time, and publish the results.

Also, I think it is important for a newbie to have a person who can provide direction, if the newbie is interested in doing something, but is not sure what. I believe this is true for students, and volunteers who have not been part of open source projects earlier.

Is it possible for experienced hands to 'adopt a newbie'? I think this will be a better approach than just expecting them to participate in IRC chats.

There should be a place where I can say, "Volunteer available", and the amount of time I am willing to give, and the skills I already possess.


8: Re: OACSAds (response to 1)
Posted by Adam Aggeusz Jaworski on
Another interesting thread, this time about Ads ideas for/in OACS:

Happy new 2006 OACS Year !


Posted by Adam Aggeusz Jaworski on
OK, this one is not-so-fresh but still valuable, especially from point of view both Tcl/OACS newbies like me, new users like Joe and enthusiast like Robert

I feel this is what all OACS programmers should also remember when discussing about all those Tcl/OACS issues (OO and others)

this one post is the one which have "sold" me OACS and made me a big fan of it (Thanks Robert!):

and here is something for all those loving LAMP and/or hating Tcl/AOLserver, but please, don't start another debate here, it is only for reference 😉

interesting analyze and also links to others interesting places:

also interesting:

framework - better late than never 😉

OK. that is enough on this Saturday