+1 on an announcements list. This is a great idea given the volume on struts-user nowadays.
+0 on a FAQ list. A central submission point might be useful, but IMHO the information needs to make it to a web page and be browseable (in the non-web sense of the term) to be truly useful. I know that I glean much more from scanning a FAQ than I would do by searching for something. (But then perhaps that's just because I don't seem to be too good at formulating the right queries. :) Thanks for volunteering to moderate, Ted. -- Martin Cooper -----Original Message----- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 09, 2002 9:00 AM To: Struts Developers List Subject: [VOTE] struts-ANNOUNCE / struts-FAQ James Mitchell wrote: > I know for a fact that there are many people who monitor the list > but never ask questions or reply. They simply want to keep up with > the latest features. Hmmm, you mean like an announcement list. You know, judging by the Struts News and Status page, http://jakarta.apache.org/struts/news_2002.html we do get enough announcements to justify a dedicated list for that. Committers: Should we request Struts-Announce as a moderated list, like Jakarta-Announce? Obviously, I'm also volunteering to moderate here. We'll undoubtedly have people replying to the announcements to chat, but my plan would be to forward those to the user list myself, so that the threads continue there. If we also start the weekly list recaps for the Jakarta Newsletter, this would be a good place to post those. I've also wondered about using a moderated list for a FAQ. The idea being if someone wanted to write up a FAQ, or summarize a thread, they could submit that to Struts-FAQ. If the list moderator (like, say, me) agreed it was cool, we could let it through. We couldn't edit the messages later, but any errata or updates could be added to the (moderated) thread. The mail-archive search engines are as good as anything. Just thinking that if we're setting up a moderated list, we might want to do both at once, so I piggybacked this idea too. -Ted. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
