Forum OpenACS Improvement Proposals (TIPs): TIP #28: (Approved) Create package-specific enhancement lists under
Create package-specific enhancement lists under https://openacs.org/projects/.
People ask very frequently whether a new feature is planned for a package or what kind of work in general is going on for a package. For example here https://openacs.org/forums/message-view?message_id=142461
The place for new features to be requested actually is the bugtracker, but it seems that bugtracker listings are not concise enough, hence my idea to create a one-stop page for each package that'll list future enhancements.
Here's an example for calendar:
------ SNIP HERE ------
Calendar Development Roadmap
(Author: Dirk Gomez)
For the 5.1 release I am planning to do these things:
- Cleaning up code
- ical integration
- Plotting out a new datamodel
5.2 will bring the new datamodel which will help integrating time-based events into calendar views. Blabla
------ SNIP HERE ------
It would be great to show bugtracker tickets, todos, and enhancements here for this particular package via an include tag.
I volunteer for programming the include snippet for bugtracker.
So not sure how this helps collaboration on the status and specifications of packages.
Shouldn't the TIP forum be a voting forum and if there is a YES on a particular proposal its details will be discussed elsewhere?
Currently the TIP process is very ineffective: we seem to never achieve results.
Anyone who is working on a package should be given access to edit the page.
We don't use openacs.org enough as a test bed for new functionality (I feel like the biggest improvements in forums, bug tracker, notifications, etc came as a consequence of all of us using the packages). If you want to implement something you think would be useful on openacs.org go ahead (the stuff Bart has done with irc logging and his new cvs frontend to cvsweb/viewcvs are good examples of this).
Its also why it's so important to get openacs.org back to the head. We are not really using the current head code here and I think the additional scrutiny and having to eat our own dogfood (frankly bad tasting in some cases) would translate to a much improved toolkit. Nothing else improves things faster than having us all using the code.
Things that might be great to have on openacs.org include wp, Jade's project manager, Dave's wiki stuff, project blogs, my cvs browser (integrated with bug tracker would be even better), photobook (once there is a postgres port), and many more that I can't think of off the top of my head. I would love to see an "Open Source Intranet" that helped bring together the things Dirk and Malte (and Joel) have mentioned in one place, consolidating blogs, bug tracker, forums, etc and making it all much more useful in keeping people informed, coordinating work, and ultimately making it a testimony to the power of the toolkit for building communities.
My only concern is stale info, which we've seen enough of already.
My idea is to have a library to export (just formatting one calendar into iCal RFC's 2445) and then be able to upload from iCal (apple's Calendar tool) using webdav to OpenACS's calendar....