Dell - Internal Use - Confidential To be consistent opencrowbar/crowbar-docs -> opencrowbar/crowbar-core-docs add opencrowbar/crowbar-hardware-docs.
Do we need opencrowbar/docs where we cover things that effect whole opencrowbar. For example, if somebody wants to create a new workload, or sleshammer how to do that. Or development environment to work on all repos. Arkady From: crowbar-bounces On Behalf Of Judd Maltin Sent: Friday, February 21, 2014 12:51 PM To: crowbar Subject: [Crowbar] OpenCrowbar org's repository names Seems to me that the org name does not have to match the product name, and we should keep calling it crowbar. It's the OpenCrowbar project, helping to create Crowbar, and other stuff. Ideally, we should also have: opencrowbar/crowbar-core opencrowbar/crowbar-docs opencrowbar/crowbar-hardware opencrowbar/crowbar-openstack opencrowbar/crowbar-openstack-docs opencrowbar/crowbar-hadoop opencrowbar/crowbar-hadoop-docs opencrowbar/sledgehammer opencrowbar/sledgehammer-docs That way, I can fork them as per normal github behavior, and have: newgoliath/crowbar-core newgoliath/crowbar-docs newgoliath/crowbar-hardware newgoliath/crowbar-openstack newgoliath/crowbar-openstack-docs newgoliath/crowbar-hadoop newgoliath/crowbar-hadoop-docs newgoliath/sledgehammer newgoliath/sledgehammer-docs I'm so sorry to mention this so late in the game. I spend a lot of time in outer space. Takers? -judd -- Judd Maltin T: 917-882-1270 F: 501-694-7809 what could possibly go wrong?
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
