Re: [Webwork-user] Re: [Webwork-devel] Intergrate with OpenSymphony?

[Joseph O. <ep...@ho...>]

>From: "Matt Baldree" <ma...@sm...>

>Great! Now what? I propose the following -
>1. Migrate WW with Opensymphony.
>- OS website and SF update recommendation
>     1. Does OS need 13 mailing lists? I suggest one general mail list, one
>per module, and one cvs mail list. There should be no need to cross post
>messages. If the message pertains to the group, then send it there;
>otherwise, send it to the module specific list. If traffic is light enough,
>then one general and one cvs would be fine with me.

That's been the way of it, actually, where most lists are ignored except for 
-developers, -cvs, -oscache, ans -sitemesh, I believe.

>     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.

Agreed. Does SF have some way for us to pull announcements from there, so we 
can have one source?

>     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.

Our web site sucks. It doesn't suck as much as it could - we could use flash 
and java applets (and activex!) on it, too, but it's not very clear.

>4. Begin work on leveraging the synergy of the merge.
>- 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.

Agreed; formtags, for example, already has some webwork integration (I had 
offered them to Rickard a long, long time ago in a galaxy far, far away) and 
I'd love to see them brought up to date.

>5. Synergy work
>- 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.

Agreed. I had done a version of the OS website using webcompass at one point 
myself, partly because I wanted to use core features and partly because I 
wanted some reorganization of information. Are there any developers who do 
usable web site design on a regular basis on either list who would be 
willing to contribute here?

-----------------------------------------------
Joseph B. Ottinger       jo...@en...
http://enigmastation.com          IT Consultant


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com