On Tue, 21 Sep 2004, Wendy Smoak wrote:

 Editor: WendySmoak <[EMAIL PROTECTED]>
 + * StrutsGmail

Well... it sounded like a good idea to get all the back-and-forth about GMail off the users list, until I got this far and realized that it would all come HERE instead!

What's the "policy" on the Wiki? Keep it professional, minimal fun stuff?

There isn't an "official" policy, but that would be my recommendation. I, for one, have pretty much given up on the user list as a lost cause, because of the amount of noise, whether it's "fun" stuff, off-topic posts, people not doing their own homework, etc. I would *like* to keep in touch with the user list, but the volume is simply too high, and my available time too low.


The wiki is there for people to collaborate on Struts-related topics. If we don't keep reasonably tight reins on that, it could turn into a free for all, where people start putting up pictures of their favourite beer bottles on Fridays, or their new-born kids, or whatever. Then we'd have to shut down access, which is against the spirit of a wiki.

As for the change messages coming here, that is necessary. The Struts PMC is responsible for oversight of our wiki. We need to know what changes are being made, and that they are being made responsibly. And we are also responsible for removing any defacements or other scribbling as soon as we can, to avoid liability or other issues.

I hate that it causes so much traffic here, I feel like if I modify a page
I'm "bothering" the dev list.

The best thing you can do is to use Preview before you save changes to a page. That way, you won't clutter up the list with Saves that you didn't get quite right.


--
Martin Cooper



-- Wendy Smoak


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to