<div class="gmail_quote">On Wed, May 25, 2011 at 23:05, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>Thanks for raising this George.</div><div><br></div><div>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 [1] [2]. Hint, focus on the APIs. (Type 't' to see all files and navigate them) </div>
<div><br></div><div>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 feedback.</div><div class="im">
<div><br></div><div>On Thu, May 26, 2011 at 00:47, George Gastaldi <span dir="ltr"><<a href="mailto:gegastaldi@gmail.com" target="_blank">gegastaldi@gmail.com</a>></span> wrote:</div></div><div class="gmail_quote">
<div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I encourage to extend that good practice whenever is possible to other<br>
modules as well.<br>
Could be a topic to discuss on the meeting next week.<br></blockquote><div><br></div></div><div>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.</div>
<div><br></div><div>I recommend using this template for requesting a review:</div><div><br></div><div>Module: (e.g., Social)</div><div>Type: (e.g., code | documentation | example)</div><div>Focus: (e.g., APIs, type names, implementation strategy, etc)</div>
<div>Other notes: </div><div><br></div><div>The clearer the focus, the more feedback you are likely going to get (since people know what to look for).</div></div></blockquote><div><br></div><div>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.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="gmail_quote"><div>-Dan</div><div><br></div></div>[1] <a href="https://github.com/seam/social" target="_blank">https://github.com/seam/social</a><div>
[2] <a href="https://github.com/seam/reports" target="_blank">https://github.com/seam/reports</a></div><div><br><font color="#888888">-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br>
<br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a></div>
</font></div>
<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></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>