<div><span style="color: rgb(160, 160, 168); ">On Thursday, October 4, 2012 at 12:24 PM, Anil Saldhana wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Hi all,</div><div> here is what Shane and I have been discussing in the last 10 days </div><div>that we can come to an agreement in this thread. Please provide your </div><div>feedback and insights as we move forward with the PicketLink main workspace.</div><div><br></div><div>Proposal:</div><div>PicketLink main workspace will have the following modules:</div><div>a) core : will contain the CDI based security code that Shane has been </div><div>driving.</div></div></div></span></blockquote><div>Maybe as already suggested, split into core and CDI, could be a good idea. </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div>b) idm: will contain the idm api and impl submodules. This is low </div><div>dependency JavaSE library for Identity Management functionality (CRUD of </div><div>users/roles/groups). This module is ultra critical to all projects. c) federation: will contain the core SAML (and maybe WS-Trust) code</div></div></div></span></blockquote><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div>c) federation: will contain the core SAML (and maybe WS-Trust) code </div><div>without any EE container dependencies. Mainly parsing, writing and model </div><div>code.</div><div>d) social: will contain social login code that allows signin using </div><div>facebook, google/openid, twitter.</div></div></div></span></blockquote><div>+1 </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div><br></div><div>Versioning:</div><div>Last major release of PL has been with 2.1.5 </div><div>(<a href="https://docs.jboss.org/author/display/PLINK/v2.1.5.Final">https://docs.jboss.org/author/display/PLINK/v2.1.5.Final</a>)</div><div>So definitely we can release above with 3.x</div><div><br></div><div>Since we may need some container binding code with AS, Tomcat etc, we </div><div>have two possibilities:</div><div>a) Create another workspace in PicketLink github organization for the </div><div>container binding. (My preference)</div></div></div></span></blockquote><div>+1 </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div>b) Create a separate github organization that will host all the </div><div>container bindings, integration testing workspaces etc. We can call it </div><div>picketlinkbindings.</div></div></div></span></blockquote><div>-1 </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div><br></div><div>Regards,</div><div>Anil</div><div>_______________________________________________</div><div>security-dev mailing list</div><div><a href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/security-dev">https://lists.jboss.org/mailman/listinfo/security-dev</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>