[Webwork-user] Intergrate with OpenSymphony?

[Patrick L. <pli...@ho...>]

> - WW documentation will be changed to HTML and moved from DocBook. DocBook
> code will be removed from source tree. I hate having to tote DocBook crap
> around in the source tree.

Yeah, I went with DocBook in OSCore and OSWorkflow initially, but gave up on
it. Documentation should be simple enough for the developers, with the
limited time we have, to be able to open up some crappy WYSIWG editor and
tap away at the keyboard for a couple minutes.

>     1. Does OS need 13 mailing lists?

Yes, we hate our mailing lists, but the admin tools don't have any way to
remove them! We'll have to bug the SF people directly I suppose. We really
only want os-dev, os-users, and os-cvsmail.

>     2. The news announcements seem out of sync with the home page. I know
it
> is a pain to keep them in sync, but I think it is important since
potential
> new users will first read the news announcements on SF. If you decide not
to
> use it, then I suggest turn it off or delete old announcements and
announce
> that announcements are posted on the home page.

Also a good point. I'd go for deleting them and then posting a single item
pointing to the new site.

>     3. As a user, I don't see where to go for issue tracking. Is this on
the
> main web site? If so, I don't see it. Ahh!, you have to click on a product
> to see the link at the bottom. That is fine, but I suggest that a brief
> paragraph and link concerning issue tracking should be on the main page.

At the top, "Bugs/Tasks"... but yes, the site could use some work to make it
more user friendly.

> - IMO, I believe a key to OS is concise well-built building blocks. A
> developer can choose to use only OS-Cache, Sitemesh, WW, FormTags,
> OS-Workflow, or all of them. Abstracting out core functionality like bean
> manipulation, configuration, etc. just makes sense. With core pieces
> abstracted, you have a leaner, easier to maintain, easier to extend,
easier
> for developers to comprehend, and more popular modules. This abstraction
> creates common core pieces that become rock solid because the extra review
> and use they receive.

Very well said, that's always been a core goal with all the code and should
continue to be a primary focus.

> - It would be nice if the main website was redone utilizing most, if not
> all, of the modules as a solid example of best practices with the modules.
> Then the website itself would be a module that would be released and
> available for download.

Yes, the website redesign should include taking advantage of all the modules
possible. It is currently also updated every hour from CVS, which is
probably something we should continue doing, even after the overhaul.