Bradley Beddoes <bedd...@intient.com>

Hi,

I'd like to get others input on moving ESOE code bases to GIT backed  
SCM. Some of the positives I believe this would bring include:
* The internal functionality Git brings to the development team is  
amazing, we're using it exclusively at Intient now.
* The collaborative nature of de-centralized SCM is a much more  
natural fit for a large OSS project like ESOE.
* Using a service like GitHub would bring many additional benefits,  
especially in terms of exposure and speed (for centralized push/pull)

I certainly am +1 for a (well planned) move to Git, this may be an  
opportunity to do some needed modification around sub-project names  
etc as well.

At this time we (as core devs) would really like to get any other  
input list members would like to provide about future ESOE direction  
(features, build processes, releases, documentation - whatever is on  
your mind).

Additionally we'd really like to start attracting more active folks  
into our group especially to help out with building SAML connectors to  
applications (or development languages) in their area of expertise and  
promoting the project and its benefits more widely. Any suggestions in  
what we can do better in this regard will be well received.

cheers,
Bradley

http://www.intient.com
Twitter: @bradleybeddoes