Clarification regarding opscode jira and community mantained cookbooks


#1

ohai chefs!

it is probably a trivial question, but is opscode jira the official ticket
tracking system to be used for community mantained cookbooks also? isn’t it?


#2

Someone else may correct me if I’m wrong, but I believe that opscode jira is specifically for opscode supported/maintained cookbooks. Other community cookbooks are most likely hosted on Github and you should be able to submit issues on their respective repositories.

  • Curtis

On Jan 30, 2014, at 9:11 AM, Marco Betti m.betti@gmail.com wrote:

ohai chefs!

it is probably a trivial question, but is opscode jira the official ticket tracking system to be used for community mantained cookbooks also? isn’t it?


#3

I’m sorry,
I wasn’t precise enough in my question.
I was specifically referring to opscode cookbooks that have been hand over
to community mantainers.
In this specific case, I’m referring to PostgreSQL cookbook, now mantained
by heavywater.
http://community.opscode.com/cookbooks/postgresql

On Thu, Jan 30, 2014 at 4:30 PM, Curtis Stewart cstewart@momentumsi.comwrote:

Someone else may correct me if I’m wrong, but I believe that opscode jira
is specifically for opscode supported/maintained cookbooks. Other
community cookbooks are most likely hosted on Github and you should be able
to submit issues on their respective repositories.

  • Curtis

On Jan 30, 2014, at 9:11 AM, Marco Betti m.betti@gmail.com wrote:

ohai chefs!

it is probably a trivial question, but is opscode jira the official
ticket tracking system to be used for community mantained cookbooks also?
isn’t it?


Ing. Marco Betti
RHCE RHEL4 id 804006512121056


#4

Hi Marco!

Cookbooks transferred to community maintainers should be using github
issues instead of the Opscode JIRA.

We’re removing the JIRA components as we close out all the issues… but
some (like postgres) are taking a while to drain the queue. Unfortunately,
there’s no easy way to “lock” a component in JIRA do prevent new tickets
being filed against a cookbook.

Please the Github issues on the cookbook’s page instead of JIRA for those.

Thanks,

-s

On Thu, Jan 30, 2014 at 10:11 AM, Marco Betti m.betti@gmail.com wrote:

ohai chefs!

it is probably a trivial question, but is opscode jira the official ticket
tracking system to be used for community mantained cookbooks also? isn’t it?


#5

Sean - Please take a moment had have the documentation for that repo
updated (CONTRIBUTING.md) to reflect the state of “how to” for projects
like that.

On Thu, Jan 30, 2014 at 11:15 AM, Sean OMeara someara@opscode.com wrote:

Hi Marco!

Cookbooks transferred to community maintainers should be using github
issues instead of the Opscode JIRA.

We’re removing the JIRA components as we close out all the issues… but
some (like postgres) are taking a while to drain the queue. Unfortunately,
there’s no easy way to “lock” a component in JIRA do prevent new tickets
being filed against a cookbook.

Please the Github issues on the cookbook’s page instead of JIRA for those.

Thanks,

-s

On Thu, Jan 30, 2014 at 10:11 AM, Marco Betti m.betti@gmail.com wrote:

ohai chefs!

it is probably a trivial question, but is opscode jira the official
ticket tracking system to be used for community mantained cookbooks also?
isn’t it?


#6

Hey Marco,

Marco Betti m.betti@gmail.com writes:

I’m sorry,
I wasn’t precise enough in my question.
I was specifically referring to opscode cookbooks that have been hand over
to community mantainers.
In this specific case, I’m referring to PostgreSQL cookbook, now mantained
by heavywater.
http://community.opscode.com/cookbooks/postgresql

Just to confirm, We (heavywater) will be using github issues so please submit any
new issues there.

Thanks!

-sean


#7

Mike,

I imagine a lot of the Opscode cookbooks that became non-Opscode fall
into this category of needing to update their CONTRIBUTING.md.

Just in case had fallen; it was heard.

Scott

On 1/30/14, 9:23 AM, Mike wrote:

Sean - Please take a moment had have the documentation for that repo
updated (CONTRIBUTING.md) to reflect the state of “how to” for
projects like that.

On Thu, Jan 30, 2014 at 11:15 AM, Sean OMeara <someara@opscode.com
mailto:someara@opscode.com> wrote:

Hi Marco!

Cookbooks transferred to community maintainers should be using
github issues instead of the Opscode JIRA.

We're removing the JIRA components as we close out all the
issues.. but some (like postgres) are taking a while to drain the
queue. Unfortunately, there's no easy way to "lock" a component in
JIRA do prevent new tickets being filed against a cookbook.

Please the Github issues on the cookbook's page instead of JIRA
for those.

Thanks,

-s



On Thu, Jan 30, 2014 at 10:11 AM, Marco Betti <m.betti@gmail.com
<mailto:m.betti@gmail.com>> wrote:

    ohai chefs!

    it is probably a trivial question, but is opscode jira the
    official ticket tracking system to be used for community
    mantained cookbooks also? isn't it?

!DSPAM:52ea8ab576311440839711!