Re: Feedback on Flex board report

2013-04-27 Thread Benson Margulies
Lewis, did you or anyone else feel that you were pushed to git? While your story has a bit of @infra-specific business to it, the majority of it and flex's seem to be composed of 'we heard that git was cool, so we moved to it, and we stepped on a rake.' Personally, I wouldn't recommend that any c

Feedback on Flex board report

2013-04-27 Thread Lewis John Mcgibbney
Hi, (removed board@ and dev@flex from my reply) I've watched this thread with a keen sense of interest. I would like to point out that we (the Any23 community) have more or less experienced the exact same as the flex guys. The build was broken as git binaries are not available on solaris slaves for

Re: Feedback on Flex board report

2013-04-27 Thread Noah Slater
Ross, agreed. A list of potential "gotchas" would be sensible! On 27 April 2013 17:26, Ross Gardler wrote: > Let me repeat again that the value I see in the Flex report is that it > identifies some issues that projects moving to git should consider and plan > for. This will make other projects

Re: Feedback on Flex board report

2013-04-27 Thread Ross Gardler
Let me repeat again that the value I see in the Flex report is that it identifies some issues that projects moving to git should consider and plan for. This will make other projects migrations smoother. Sent from a mobile device, please excuse mistakes and brevity On 26 Apr 2013 18:35, "Luciano Re

Re: Feedback on Flex board report

2013-04-27 Thread Noah Slater
I interpreted Luciano's -1 as a general "I am not in favour of this proposal", which seems like a perfectly valid use. Even if it were being cast _as_ a veto on some code change or other, I still think it would be valid, as it comes with justification. (That other people might disagree with that ju

Re: Feedback on Flex board report

2013-04-27 Thread Daniel Shahaf
Luciano Resende wrote on Fri, Apr 26, 2013 at 10:34:39 -0700: > -1 for using Apache Flex's bad experience, as a concrete example, as this > might give the wrong perception about Git at Apache. Sorry, invalid veto. You can't veto people from citing a datapoint because it's not favourable to one si

Re: Feedback on Flex board report

2013-04-26 Thread Luciano Resende
On Fri, Apr 26, 2013 at 2:17 AM, Ross Gardler wrote: > I just wanted to thank you for the feedback you provided in your last > board report with respect to your experiences with moving to Git. This > kind of information is really useful to those in other projects. For > the benefit of the archives

Re: Feedback on Flex board report

2013-04-26 Thread Dave Cottlehuber
On 26 April 2013 18:18, Alex Harui wrote: > It is true that there is less negativity about git every day in the Flex > community. I doubt we will go back to SVN. > > I'm not sure it is worth blogging it. The draft of the report is captured > on the dev@flex.a.o archives so it is public and searc

Re: Feedback on Flex board report

2013-04-26 Thread Alex Harui
On 4/26/13 2:41 AM, "Bertrand Delacretaz" wrote: > Hi, > > On Fri, Apr 26, 2013 at 11:17 AM, Ross Gardler > wrote: >> I just wanted to thank you for the feedback you provided in your last >> board report with respect to your experiences with moving to Git. This >> kind of information is real

Re: Feedback on Flex board report

2013-04-26 Thread Ross Gardler
Yes, good point Bertrand. Me being a glass half full kind of person I read the original content as positive in the sense it provided valuable forewarning for those planning on moving to Git. I was hoping that we could express it as "this is what you should plan for if you choose to switch to Git",

Re: Feedback on Flex board report

2013-04-26 Thread Bertrand Delacretaz
Hi, On Fri, Apr 26, 2013 at 11:17 AM, Ross Gardler wrote: > I just wanted to thank you for the feedback you provided in your last > board report with respect to your experiences with moving to Git. This > kind of information is really useful to those in other projects... Note that the Flex team'

Feedback on Flex board report

2013-04-26 Thread Ross Gardler
I just wanted to thank you for the feedback you provided in your last board report with respect to your experiences with moving to Git. This kind of information is really useful to those in other projects. For the benefit of the archives (and ComDev PMC) I've copied the relevant section at the end