Shane, Thank you the perspective. We started this discussion during the Crowbar Hack-a-thon in Hong Kong and did not resolve it. Unfortunately, there's not a "makes everyone happy" answer and, as you point out, we need to accept that and move forward. That said, forward progress is not really blocked yet. We've made great strides with Crowbar 2 (including recent installs) and it's buildable within the current Crowbar 1 for those brave enough. I've come to the conclusion that there are fixes that require a more distinct split between the two code bases and I'd be interested in your (and the communities') thoughts. Along those lines, I'm starting a new thread titled "Rationalizing Crowbar Project Infrastructure for our new code base" as the (re)kick off for that discussion. I hope it addresses the concerns that you've raised. I want to add that I 100% agree with your sentiment - time for discussion is closing. Thanks again for speaking up! Rob
-----Original Message----- From: crowbar-bounces On Behalf Of Shane Gibson Sent: Tuesday, December 17, 2013 1:13 PM To: Adam Spiers; crowbar Subject: Re: [Crowbar] crowbar-utils repo moved to http://github.com/opencrowbar/crowbar-utils/ All, It seems that there is a significant amount of confusion or maybe more acurately; disagreement on how to maintain the Crowbar 1.x vs. the Crowbar 2.x products going forward. I realize that there are complexities and issues with either course. Is someone within the Crowbar community going to take ownership of this, and help define the direction/processes going forward? I'm not certain how this community works - since I'm relatively new to it - so I apologize if I'm stepping on toes. My concern is our use of Crowbar going forward will absolutely be based on CB2 - and it seems that these issues are holding up the process going forward. As an end-user of the product, I'm concerned that this dissent is causing a significant hiccup with advancement of the product. If someone could please step up and help define/usher this process along - that would be fabulous... ~~shane Sr. Principal Infrastructure Architect Symantec Cloud Platform Engineering On 12/17/13, 8:29 AM, "Adam Spiers" <aspi...@suse.com> wrote: >*sigh* > >How does duplicating confusion reduce it? > >So basically every single one of my unanswered concerns were ignored: > > http://thread.gmane.org/gmane.comp.cloud.crowbar/1233/focus=1299 > >and this was done without any consensus or heads up on this list. > >And worse, the new repos have been done with a straight import, so >opencrowbar is completely devoid of history. > >BIG mistake :-( > >Even if people disagree with my concerns about a new organization[1], >surely at very least it would make sense to preserve commit history in >the transition?? > >[1] I still didn't see any valid explanation for that - "risk of > destabilization" is a completely bogus argument, as I have > explained several times. > >Judd Maltin (j...@newgoliath.com) wrote: >> Just somewhere a bit less confusing for me. I'm fairly lost in all >> this talk about versioned main repos and stuff. >> >> Judd Maltin >> 1-917-882-1270 >> I have suffering to learn compassion once and once again. >> On Dec 17, 2013 3:04 AM, "Vincent Untz" <vu...@suse.com> wrote: >> >> > Hi, >> > >> > Le lundi 16 décembre 2013, à 23:30 -0500, Judd Maltin a écrit : >> > > http://github.com/opencrowbar/crowbar-utils/ >> > >> > What is the opencrowbar github organization? >> > >> > Vincent > >_______________________________________________ >Crowbar mailing list >Crowbar@dell.com >https://lists.us.dell.com/mailman/listinfo/crowbar >For more information: http://crowbar.github.com/ _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
