Message from discussion
git, future directions
Received: by 10.114.102.1 with SMTP id z1mr188691wab.0.1235636580624;
Thu, 26 Feb 2009 00:23:00 -0800 (PST)
Return-Path: <bedd...@intient.com>
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.189])
by mx.google.com with ESMTP id k19si12026527waf.0.2009.02.26.00.22.59;
Thu, 26 Feb 2009 00:23:00 -0800 (PST)
Received-SPF: pass (google.com: domain of bedd...@intient.com designates 209.85.142.189 as permitted sender) client-ip=209.85.142.189;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of bedd...@intient.com designates 209.85.142.189 as permitted sender) smtp.mail=bedd...@intient.com
Received: by ti-out-0910.google.com with SMTP id w7so562201tib.19
for <esoe-dev@googlegroups.com>; Thu, 26 Feb 2009 00:22:59 -0800 (PST)
Received: by 10.110.11.7 with SMTP id 7mr1529382tik.56.1235636579032;
Thu, 26 Feb 2009 00:22:59 -0800 (PST)
Return-Path: <bedd...@intient.com>
Received: from ?192.168.1.2? (203-214-47-180.dyn.iinet.net.au [203.214.47.180])
by mx.google.com with ESMTPS id d7sm164828tib.2.2009.02.26.00.22.56
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Thu, 26 Feb 2009 00:22:57 -0800 (PST)
Message-Id: <EF21CAFB-258E-4DFB-8986-85981E155D03@intient.com>
From: Bradley Beddoes <bedd...@intient.com>
To: esoe-dev@googlegroups.com
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: git, future directions
Date: Thu, 26 Feb 2009 18:22:52 +1000
X-Mailer: Apple Mail (2.930.3)
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
|
