<br><br><div class="gmail_quote">On Mon, May 23, 2011 at 19:04, Pete Royle <span dir="ltr"><<a href="mailto:howardmoon@screamingcoder.com">howardmoon@screamingcoder.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
I think that article could be made recommended reading in the Module
Handbook (I tried but I don't think I have the privileges).<br>
<br>
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.<br>
<br>
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.<br>
<br>
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?<br></div></blockquote><div><br></div><div>That's a good question, if our SME (Subject Matter Expert) is not available to comment, the moderator could take a best guess, or someone from the community, but that's really all we can do, unless there's someone else with knowledge out there. I think this is the main problem we have currently, and the lack of a getting started guide. We have lots of knowledge amongst the leads, but it's not shared knowledge, we're all fairly silo'd as well in our knowledge. Some of us know little bits about one maybe two modules, but not many. I think that may need to be a topic for the agenda for the next meeting. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000">
Pete R.<br>
<br>
<br>
Jason Porter wrote:
<blockquote type="cite"><div><div></div><div class="h5">Those that were at the meeting (or read the minutes /
logs) know this is something I'm trying to figure out. This new model (<a href="http://www.managementexchange.com/story-36" target="_blank">http://www.managementexchange.com/story-36</a>)
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.
<div><br>
</div>
<div>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.<br clear="all">
<br>
-- <br>
Jason Porter<br>
<a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br>
<a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br>
<br>
Software Engineer<br>
Open Source Advocate<br>
Author of Seam Catch - Next Generation Java Exception Handling<br>
<br>
PGP key id: 926CCFF5<br>
PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>
</div>
</div></div><pre><hr size="4" width="90%"><div class="im">
_______________________________________________
seam-dev mailing list
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a>
</div></pre>
</blockquote>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br>
<br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>