It has been my experience that people already do this when they see
the Opscode shirts. If I happen to be wearing an Opscode T-Shirt at
a conference, then it ultimately leads to a conversation about Chef. I like Ann's idea of an incentive to have conference admission compensated for key community contributors. I also like James' idea of putting a monetary bounty on high priority bugs/issues. That would probably work well for many independent consultants, looking for work when business is slow. Monetary bounties may not fly for certain community developers, if there happens to be any ethical non-compete issue with their employment contract, however. I wasn't fully aware there was a list of high priority bugs. Is there a better way to highlight which outstanding issues are a top priority, and bounty worthy, maybe within JIRA? Eric G. Wolfe Senior Linux Administrator, IT Infrastructure Systems -------------------------------------- Marshall University Computing Services Drinko Library 428-K One John Marshall Dr. Huntington, WV 25755 Phone: 304.696.3428 Email: "> Eat right, stay fit, and die anyway. On 02/07/2012 06:20 PM, James wrote: " type="cite"> I'd like to give a +1 to this. Wesley does a great job also in making it clear what is considered a priority and the relative difficulty level of each project. |
Archive powered by MHonArc 2.6.16.