Hi guys, since this continuously surfaces, could someone from Dell clarify which parts of their development still take place in the 'crowbar' org? I'm just guessing here but if crowbar-2.0 development in practice moved to opencrowbar completely, we could likely re-use the 'master' branch for something else rather than letting it bit-rot. So as far as I understand, some hadoop and mesa branches still show some activity. How are Dell's future plans around these?
I'm asking this in good faith since Crowbar-1.x branches are all in heavy development and brought a host of awesome features during the last months. But we somewhat hide these in awkwardly named branches much to the confusion of interested newcomers. The current layout mostly results from how the ./dev tool works. But this tool is only used by one halve of the community that seems to gather around opencrowbar. So IMO there are less and less compelling reasons for keeping up with our baroque (to say the least) way of organizing things under the 'crowbar' organization. Thoughts? -- Viele Grüße, Sascha Peilicke _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
