Re: [security-dev] PicketLink Integration Github organization

To be honest I find it confusing. We all know that people have hard time understanding what picketlink is because it contains many components. Having 3 github organizations won't help. We could have renamed picketlink-idm to picketlink-idm-legacy to make it clear it is under maintanance or something like this. Similar for other components. Keep -legacy versions of repos for what is still used and maintained and move abandoned stuff to the separate organization. https://github.com/jbossas has 20 repos. We are not that bad :) I know it is hard to put things into order in current state but IMO changing version from 3.x to 2.5.x and reshuffling stuff between 3 organizations will make it quite hard to digest for people outside. Time to time I'm even lost myself what is where and why... On 05/14/2013 05:39 PM, Anil Saldhana wrote: > Hi All, > footprint of PicketLink is pretty huge considering the components it > has - idm,core,saml,social,scim etc. Currently PicketLink components are > housed in the GitHub PicketLink organization > (https://github.com/picketlink). The PL2 workspaces have been moved to > a separate organization called picketlink2 (https://github.com/picketlink2). > > We will need to host integration code for at least the following projects: > a) Camel > b) Undertow > c) Infinispan > > Since the integration workspaces is only going to grow over time, I > would like to propose a separate github organization called > picketlinkintegration. > > This is just an attempt to de-clutter and separate concerns. > > Wdyt? > > Regards, > Anil