On Wed, May 25, 2011 at 23:05, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Thanks for raising this George.
Both of these modules are really on fire right now (come to think of it,
that's true of a lot of modules). But anyway, definitely look through them.
That's what really matters early on. And it's really easy to browse the code
on github  . Hint, focus on the APIs. (Type 't' to see all files and
Unfortunately, at this point you can only comment on commits, so simply
post to the mailinglist or chat in IRC if you want to provide general
On Thu, May 26, 2011 at 00:47, George Gastaldi <gegastaldi(a)gmail.com>wrote:
> I encourage to extend that good practice whenever is possible to other
> modules as well.
> Could be a topic to discuss on the meeting next week.
George and Antoine got me thinking that perhaps we should have a "request
for review" section on the project site (or some other feed mechanism) so
that you can see what's currently "up for review". This should help
passer-byes know when and where to jump in.
I recommend using this template for requesting a review:
Module: (e.g., Social)
Type: (e.g., code | documentation | example)
Focus: (e.g., APIs, type names, implementation strategy, etc)
The clearer the focus, the more feedback you are likely going to get (since
people know what to look for).
Where would we put them right now? I know it seems like "the new site" or
Seam University will be our 42, but we need something to fill the gap now. A
thread in the forum? I don't know of any other way right now to have it show
up to as many people.
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
seam-dev mailing list
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net