many thanks to michi, antville got a recently modified-list. now this is done, i'd like to propose a list of whats next (as soon as there are sections available in antville this would go to the section "todo" ;-):

1. as soon as hannes finishes dbmapping inheritance in helma migrate the db-tables "story" and "comment" to a new table named "text"
2. authors should be able to define who is allowed to edit a story they created: only admins/admins and contributors/all registered users/only themselves (=default). for comments i'd propose we keep the present way: admins are allowed to delete comments, but editing is only allowed for the authors of comments.
3. sections - admins should be able to define sections for their weblog which will appear as [weblog]/[section] with their own overview-page. authors should be able to choose if their story should also be placed in a section or just appear in the default-storypool (as it is now). this should be done with a section-editor and a dropdown-box in story-editor. it should also go hand-in-hand with a set of macros (i.e. "sectionlist") and maybe some changes in the link-macro to provide easy linking to sections ...
4. implement shortcuts for stories. shortcuts should be defined in story-editor to provide easy linking without remembering the creation-date/section of a story. one question is how the url of those stories should look like: [weblog].antville.org/stories/[story-shortcut]?
5. weblogs should be accessible with an url like [weblog-alias].antville.org (i assume this also means some changes/added functionality in helma, right?)
6. story-manager: should provide a listing of all stories with their basic parameters (title, which section, when created, who created it ...) and a basic set of actions: edit/set off- or online/delete. the basic view of the weblog for admins/contributors should be the normal users-view. instead of navigating with a calendar this storymanager should ev. provide a scroll-navigation (next 10/prev. 10).
7. create a "goodie"-manager similar to the image manager to be able to upload binaries (sounds, pdf-files etc.) and to link them in stories/comments

so, what ya think about? anything missing (of course there is, but this is just to fulfill the basic requirements ...)?

Re: Point 5: Yes, I think we need a big enhancement of the HopObject's href() function. I originally thought it would be enough to just stop at the weblog level (i.e generate a URL like /20010720/101/ instead of /project/20010720/101/, but it's really not. This would simply not be enough to link between web sites/weblogs, and it wouldn't work for the recently-modified-weblogs-list on central antville.org.

So we really want href() to produce the absolute URL in this case, for instance project.antville.org. How do we specify that? Some app property like

hrefpattern=%weblog%.antville.org hrefroot=weblog

Hm, this makes me think if we could somehow leverage our skin infrastructure for this.

href() to return an absolute url would also be necessary to render usable exchange formats (e.g. rss) as well as if we ever want to include stories from one weblog in another. +1

for the different user rights i just want to emphatically ask for simplicity. personally, i really would like to see some real world examples for those access restricion features.

...you're probably not going to like this from the programmer's viewpoint, but it would be great if a story could be added to more than one section. I always saw the restriction to one section as a major drawback.

Not sure how to do this though.

't would seem a little clumsy to me...