[seam-dev] Seam module spotlight series

[Shane Bryzak]

Definitely not too early, I think this is something that people are 
looking forward to finding out more about.

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110403/52b1f02a/attachment.html