Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Stephano Cetola <stephano.cetola@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [Call to Action] Yocto Project Bug Triage
Date: Tue, 29 May 2018 07:00:56 -0700	[thread overview]
Message-ID: <311eb084-2556-c39c-a7d3-e210afc9c14a@linux.intel.com> (raw)

Hi All,

Sorry for the cross posting but I want to be sure to hit both the Yocto
Project and OpenEmbedded communities with this information.

It has been brought to our attention that the weekly bug triage has
fallen out of the spotlight and we'd like to get it back into focus.
We'd like to encourage anyone who is interested to join us. The invite
was sent out to the Yocto Project mailing list:

https://lists.yoctoproject.org/pipermail/yocto/2018-May/041308.html

We meet once per week to discuss new bugs (bugs with no target
milestone) and bugs that might have missed their target milestone.

This is a chance for the community to weigh in on features or bugs they
care about, as well as to volunteer their time to see that those items
are completed on schedule.

For those who don't know, we track bugs using bugzilla:
https://bugzilla.yoctoproject.org/

To quickly view the bugs that we are triaging during the meeting, you
can follow along on the wiki:
https://wiki.yoctoproject.org/wiki/Bug_Triage

We triage bugs in this order:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Bug_Triage_Order

Joining this meeting can help keep you up to date with the latest news
from the OpenEmbedded and Yocto Project communities. It also helps us
better understand and meet the community's needs.

Cheers,
Stephano



                 reply	other threads:[~2018-05-29 14:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=311eb084-2556-c39c-a7d3-e210afc9c14a@linux.intel.com \
    --to=stephano.cetola@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox