Chef Developers

[chef-dev] Re: Re: Opscode Ticket Triage 11/16


Chronological Thread 
  • From: Bryan McLellan < >
  • To: Brandon Philips < >
  • Cc:
  • Subject: [chef-dev] Re: Re: Opscode Ticket Triage 11/16
  • Date: Wed, 30 Nov 2011 19:48:32 -0500

On Wednesday, November 30, 2011, Brandon Philips wrote:

On 21:48 Thu 17 Nov 2011, Bryan McLellan wrote:
> Phew. I feel like I've been living in github and JIRA for two days
> straight. We've been doing a ton of housekeeping on pull requests and
> providing new users with information about the process.

Thanks for doing this work. I wasn't aware about the chef process until
after my pull request had been sitting for a month+, oops :(

If I write a github bot that justs closes all pull requests immediatly
with a link to the how to contribute would that be helpful?  Or better
yet use the Jira API to create a CHEF issue everytime a pull request is
opened without a CHEF-BLAHBLAH string in it.


 

Great ideas. We were talking about this today at the Community Summit.

I don't think we would want to close them immediately but we should develop something to auto-respond to a pull-request with a standard blurb and a link to the How to Contribute page on the wiki. I wouldn't want to create a JIRA ticket because if the user has already properly created a ticket than we would have duplicates. I would like to encourage:

* Creating a ticket on JIRA is always the first step

* Pull requests should contain a link to the JIRA ticket

* Conversation regarding the issue and the fix should be on the ticket, and longer conversations may be on the mailing list, but we should limit the conversation on the pull requests. This way others can easily find the whole conversation without having to be familiar with all the tools.

If you could write something I would be appreciative and happy to run it.

Bryan

 

On Nov 30, 2011 9:44 AM, "Brandon Philips" < "> > wrote:
On 21:48 Thu 17 Nov 2011, Bryan McLellan wrote:
> Phew. I feel like I've been living in github and JIRA for two days
> straight. We've been doing a ton of housekeeping on pull requests and
> providing new users with information about the process.

Thanks for doing this work. I wasn't aware about the chef process until
after my pull request had been sitting for a month+, oops :(

If I write a github bot that justs closes all pull requests immediatly
with a link to the how to contribute would that be helpful?  Or better
yet use the Jira API to create a CHEF issue everytime a pull request is
opened without a CHEF-BLAHBLAH string in it.

       Brandon

Archive powered by MHonArc 2.6.16.

§