I think that article could be made recommended reading in the Module Handbook (I tried but I don't think I have the privileges).

I'm happy to be forwarded Cron questions which slip under the radar. I've noticed a few now on the Forums and will address those shortly.

I think splitting forums into categories is important. I would prefer not to have to check every post that comes through to see if it's Cron related. I'm too easily distracted. An RSS feed for a search result would work well also. Hoping a Google Alert will suffice in the meantime.

Unfortunately the reality is that there will be times when I'm not able to provide any response. In those instances I usually fail to even send a "too busy" response because I try to convince myself I'll get to it. What would be the process there?

Pete R.


Jason Porter wrote:
Those that were at the meeting (or read the minutes / logs) know this is something I'm trying to figure out. This new model (http://www.managementexchange.com/story-36) used at Red Hat I think makes a lot of sense, and something I'm trying to leverage (or will from here out). The part that I think we're missing right now is the Knowledge Base that our users can search. I know the answer is going to Seam University, but it's not here yet. However, when it is here, I want to make sure there is a simple way to mark a forum thread as resolved (maybe we need distinctions as to the type of thread: discussion, question, call for help, etc) and have that added to the knowledge base and analyzed for themes, keywords, etc. This may be something to bring up with Mark Newton as well.

Enough about Seam University, do any of the module leads have a problem if the forum moderator (whomever that may be) emails or otherwise pings (I've been doing this for a few weeks now) the module lead to lend a hand when appropriate? I know we discussed this idea a little bit in the meeting and the general consensus seemed to be allowing the community to try and solve problems on there own (which isn't happening, IMO due to a lack of knowledge about the modules outside of the developers) before one us jumps in with a solution. I'm trying to do what's best for Seam and make sure no one gets overwhelmed.

--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu

_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev