From ooo-dev-return-65-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Tue Jun 14 16:34:25 2011 Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9BE036A75 for ; Tue, 14 Jun 2011 16:34:25 +0000 (UTC) Received: (qmail 70197 invoked by uid 500); 14 Jun 2011 16:34:25 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 70164 invoked by uid 500); 14 Jun 2011 16:34:25 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 70156 invoked by uid 99); 14 Jun 2011 16:34:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jun 2011 16:34:25 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Mathias_Bauer@gmx.net designates 213.165.64.23 as permitted sender) Received: from [213.165.64.23] (HELO mailout-de.gmx.net) (213.165.64.23) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 14 Jun 2011 16:34:19 +0000 Received: (qmail invoked by alias); 14 Jun 2011 16:33:56 -0000 Received: from d191185.adsl.hansenet.de (EHLO [192.168.1.2]) [80.171.191.185] by mail.gmx.net (mp069) with SMTP; 14 Jun 2011 18:33:56 +0200 X-Authenticated: #17242763 X-Provags-ID: V01U2FsdGVkX1+QkIMz41qQpL8oDzG++Fh9vq+5MuAnFX8XYguly1 le6MFC3W0Riz8R Message-ID: <4DF78D74.1070306@gmx.net> Date: Tue, 14 Jun 2011 18:33:56 +0200 From: Mathias Bauer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Mnenhy/0.8.3 OracleBeehiveExtension/1.0.0.2-OracleInternal ObetStats/CATCATCATCATCATCAFCATLAF_1292428138647-396660266 Thunderbird/3.1.10 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: Subversion & Git (was: Proposed short term goals) References: <4DF77E0A.9030006@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Simon, On 14.06.2011 17:47, Simon Phipps wrote: > On Tue, Jun 14, 2011 at 4:40 PM, Greg Stein wrote: > >> I know that many people also have concerns with >> potential community issues. But that is all a discussion for a later >> time. Not here and now. >> > > With respect, that was the same phrase used to defer discussion during the > proposal process. Leaving community concerns until all the decisions are > made and the only remedy is "those other folk will just have to do like we > do" doesn't seem wise. if you talk about "community concerns", you should be more specific about which parts of the community are involved here. As we are talking about a code repository, we should let the developers have their say about it, as they are the ones that have to work with the tool. As I'm one of them, let me start. With Sam's explanations and promises ;-) I'm fine with giving the current svn a chance. As I wrote, in the beginning we won't be hurt by merging a lot as most probably we will have to work on "head" a lot until we get a first build running. If there was a chance to move to git in the future, we can do that without losing anything. If there wonn't, why waste words about it now? Even if we stayed with svn for a longer time, there wasn't a problem for the LO devs, as interfaces or bridges between svn and git exist and are known to work. AFAIK go-oo.org has practiced that already in the past, even in times where OOo development produced much more code than it will do in the forseeable future. If consuming OOo@Apache by Libre Office did not work in the future, I'm pretty sure that the SCM would not be the reason for that. Nevertheless, if the LO devs will need help to make that bridging as smooth and painless as possible, I will help where I can. Starting with svn won't set anything in stone. Perhaps we should think about our usage of svn now so that at least a later conversion to git will be easy and without losses. We should be able to do that. Besides that I would welcome to see git at Apache moving forward. Perhaps I can ask our colleague Jens-Heiner Rechtien if he wanted to help a bit with that, if that was possible. Regards, Mathias