John Terpstra (john_terps...@dell.com) wrote: > The fact that Crowbar has a high barrier to new participants is > undeniable. It is of utmost importance to the future of the project > that the obstacles to entry of new developers must be removed.
Agreed! > The positive steps to remove barriers should result in: > > a) Greater recognition that Crowbar is an Open Source and > Community-driven project Right. Recognition will come only if the project becomes truly community-driven. > b) Ability to readily identify the exact code repositories that make up > all components of the Crowbar project Yes. Architecture quickstarts, reduction in the number of repos, and simplification / elimination of a monolithic dev tool would address this. > c) Improved information - Ready ability to find and locate all essential > documentation (web as well as documents) Yes! > d) Ease of getting from start to effective and efficient code > development/production Yes! > e) Easy to get new organizations on board in support of the project Yes! > Achievement of these achievements (in my opinion) validates any > challenges of efforts required. Agreed! > The new information resources should point to all the old Crowbar > 1.x code and documentation. I don't understand the logic behind this last statement. Currently we have one set of crufty docs. Creating another set which points back to it is going to hinder not help the above goals. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
