We are talking past each other. We want to solve those exact problems in CB2 but that creates a huge cleanup lift for CB1 that risks CB1 stability.
Adding fix CB1 to the work makes it unlikely to succeed. If you want that as an action item then the field is wide open. ----- Original Message ----- From: Adam Spiers [mailto:aspi...@suse.com] Sent: Wednesday, November 20, 2013 11:14 AM Central Standard Time To: crowbar Subject: Re: [Crowbar] Crowbar 2 Hack Report Sorry, I don't understand your logic. Newbie *users* are confused because the website does not contain a quickly and easily digestible introduction explaining the architecture and how to get started. If you need convincing that the website is inadequate, compare it to https://juju.ubuntu.com/ Newbie *developers* are confused because: - Developing requires learning a complex new tool. - Developing involves a huge number of github repositories with inconsistent branching structure. - Developer documentation is scattered across multiple locations, and is frequently duplicated and/or out of date. - The repositories contain a ton of cruft, as partially documented here: http://crowbar.sync.in/crowbar-repos I don't see how creating a new github organisation will solve *any* of these issues. Judd Maltin (j...@newgoliath.com) wrote: > All the branching doesn't address the confusing situation for newbies who > we are trying to attract to the project. Since we'll be leaving a huge > portion of the 1.x codebase behind for good and forever, I think the gains > of making it easy for newbies to join FAR outweighs branching and cleaning > up. _______________________________________________ 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/
