Rob Hirschfeld (rob_hirschf...@dell.com) wrote: > Adam, > As you know, we use a very different build process than your team. We have > tried several times to duplicate your process using Kiwi and your tool chain > without success. We are not going to put additional effort into that.
Sure - that idea was given up several months ago, and anyway, that would not be required in order to proceed with my proposal of introducing branches to the main repo. > For us to make the needed changes to our build process, we have an > overwhelming consensus on our team that it will break CB1 builds. > Please accept that our opinion on this does not match yours. We can agree to disagree, but I'm disappointed that noone provided any *technical* justification to the rest of the community. In particular, even though I'm fully aware of the fundamental architectural differences between 1.x and 2.0 (after all, I did contribute to the design in a small way), I still completely fail to understand why my branches proposal would have broken anybody's builds. If someone could have explained that, I would have happily accepted it weeks ago. Additionally, AFAICS there has been no public explanation on how any of the difficulties caused by creating a new github organization are to be addressed: http://thread.gmane.org/gmane.comp.cloud.crowbar/1233/focus=1299 If we want to grow a community outside Dell, IMHO transparency around decision making is not optional. And the only reliable community-wide communication medium is this mailing list. This all seems symptomatic of a wider trend I have noticed within the project since I joined 20 months ago: create something, become dissatisfied with it, then create a replacement without cleaning up the original problem. This has happened with code, wiki pages, in-tree documentation, build tools, issue trackers, test / CI infrastructure, Trello cards, Trello boards, and now an entire github organisation. When will the accumulation of technical and organisational debt end? I'm really sorry if this and some of my other recent posts have sounded primarily negative, but hopefully I'm not alone in believing that honestly and openly airing concerns is the best way to make successful progress. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
