I'll volunteer the JMS module for #3, since we're targeting a release this week; unless you think it's too early.<br><br><div class="gmail_quote">On Sun, Apr 3, 2011 at 5:42 AM, Shane Bryzak <span dir="ltr"><<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Awesome, consider yourself locked in! Any takers for the third one?<br>
<div><div></div><div class="h5"><br>
On 03/04/11 08:01, Brian Leathem wrote:<br>
> If Jason does the first, I'll follow up with the second, using his as an<br>
> example :P<br>
><br>
> Brian<br>
><br>
> On 04/02/2011 08:10 AM, Jason Porter wrote:<br>
>> I can do it. I'll have a bit plane time coming up :)<br>
>><br>
>> On Friday, April 1, 2011, Shane Bryzak<<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br>
>>> Guys,<br>
>>><br>
>>> I'd like to start up a weekly Seam module spotlight. Basically, each<br>
>>> week I'd like one of you to write up an article that we can publish on<br>
>>> <a href="http://in.relation.to" target="_blank">in.relation.to</a> that shows off the best features of your module.<br>
>>> Preferably the article would be use-case centric, as opposed to the<br>
>>> feature-centric style that we generally write with in the reference<br>
>>> documentation. For example, if I was writing a blog post about the<br>
>>> persistence module I would make the point that if you're writing POJO<br>
>>> beans to implement your business layer that I would not have transaction<br>
>>> support by default, and that is where the transaction features of the<br>
>>> persistence module come in. I'd also explain how it could be useful in<br>
>>> other container environments, such as Tomcat or even Java SE.<br>
>>><br>
>>> This style of writing is more likely to get your readers to a point<br>
>>> where they understand why your module is as cool as we say it is, as<br>
>>> they can relate its coolness in terms of real life use cases. Whereas<br>
>>> explaining things from a feature point of view might leave some confused<br>
>>> as to how they can actually *use* that feature in their own projects.<br>
>>><br>
>>> Anyway, I'm looking for a brave volunteer to go first. Ideally we'd get<br>
>>> the first spotlight article published by the end of next week (before<br>
>>> the 9th) so that should leave enough time to put together an informative<br>
>>> article.<br>
>>><br>
>>> Shane<br>
>>> _______________________________________________<br>
>>> seam-dev mailing list<br>
>>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>>><br>
> _______________________________________________<br>
> seam-dev mailing list<br>
> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br>