My concerns come from some of the cookbooks which have a large number of
outstanding pull requests as well as open issues. Often they have not
actually seen pull rquests merged, commented on, or otherwise closed.
Forking is always an option, just not the best one in my opinion.
Moreover, with this approach the issues remain -- without a common well
maintained upstream cookbook, amongst other issues, it becomes very
difficult to find "the right cookbook."
On 05/24/2014 12:44 PM, Scott M. Likens wrote:
This electronic message contains information which may be confidential or* How can the community get involved in this governance process toIssues and Pull requests are you best friend here. Taking back a
ensure high quality standards persist for said cookbooks?
cookbook is likely not easy; it would be easiest to fork it and point
everyone to the new fork? There likely should be a policy here or
otherwise we'll step on peoples feelings.
privileged. The information is intended for the use of the individual or
entity named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this information
is prohibited. If you have received this electronic transmission in error,
please notify us by e-mail at
Archive powered by MHonArc 2.6.16.