From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0AB23C433FE for ; Tue, 29 Nov 2022 05:02:45 +0000 (UTC) Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by mx.groups.io with SMTP id smtpd.web11.141738.1669698156277636959 for ; Mon, 28 Nov 2022 21:02:36 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=W0cQROtG; spf=pass (domain: gmail.com, ip: 209.85.210.181, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pf1-f181.google.com with SMTP id 130so12586050pfu.8 for ; Mon, 28 Nov 2022 21:02:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:from:to:cc:subject:date:message-id:reply-to; bh=qvGAErPyYoa8BGFOA7VHzeKeRIx5bt+3gUjQKr40+xw=; b=W0cQROtG0/ruhDcu35Q3OUWhwUVJFLYEZBBzD7rMBbTuv4zuDm9U66Duaao+jTTXEh foj2/WaaNHqH7CqevVsTD5LfsPF5ns5hnWYgopgQ10Hr1jeRoU49JawploDjoISmTSqV lOVZIIj1axN/lT+pVEnJkPZ6lpyEIuHNRiff7avjbUYYQHEW5wUL9iZF4+58hQ1Rb9te ck8gPOcbOjWwL1hkedKIytDalqFkfKfquJ0hoXPg3Utter/vgfa5dNXTlxw9tbxutOoi oTLPo+i1kSHQnxbv8CbP1dCYY2FwjAnx1thNXpJFdypeJd48Ogq/Fm12sRElb9KSp81m m/Vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qvGAErPyYoa8BGFOA7VHzeKeRIx5bt+3gUjQKr40+xw=; b=lp/3cIXh2/nBHzrSUFYnQHTbYQcdniL6ocb/Phl32gdjQtwRwuyYRWZqtVZK84GoBw vCVJ3g08Obzi2YMLXXE0rEV4ea70it/jIO4CReoQzBIVXYMDpc9Wo4h7YrctGc2T72IL ehhojL4KFJRjD42Ce6SzXFEEw+nHVZzya6zTZlgJ7FvjE74jMP9s4oth3xVkpiu6wBQj /GIC/Qw3Lqbsevz2FAF7U+LZdfspK07tSOwYRiVe/9lHlwZ5zUjmheJJREbpHZx1RbOO 0l0SWP49cLAgBNbQayytSEmLT3ROD4VZLvbABvfkCnj8E1mJ9cV/HxAGYMGBU61DzSvn ivVA== X-Gm-Message-State: ANoB5pkNaj3NBf1DWt6/xL1XVbW/PfRT1JH58vbYviSYhBywTuz5QMfe 8xzPAlk8xXdzlERsJ1hQBNs= X-Google-Smtp-Source: AA0mqf5TY2emgYSW7AxkKcgiz1cYUZ6mXmlFSdfnfdI/X1EniiEsC9iPxBfgpbkXpLBE83ojOirFYg== X-Received: by 2002:a63:1302:0:b0:439:e030:3fa8 with SMTP id i2-20020a631302000000b00439e0303fa8mr31039579pgl.554.1669698155416; Mon, 28 Nov 2022 21:02:35 -0800 (PST) Received: from skjolley ([2600:1011:a11b:4d68:b0f:13fd:906e:7366]) by smtp.gmail.com with ESMTPSA id f26-20020aa79d9a000000b00575448ab0fdsm2322350pfq.114.2022.11.28.21.02.34 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Nov 2022 21:02:34 -0800 (PST) From: To: , Subject: Yocto Project Newcomer & Unassigned Bugs - Help Needed Date: Mon, 28 Nov 2022 22:02:34 -0700 Message-ID: <0b1101d903af$cb810250$628306f0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0B12_01D90375.1F242620" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQFm7e+mMQzYnW3QjWyETR16tVtXLg== Content-Language: en-us List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 29 Nov 2022 05:02:45 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/yocto/message/58646 This is a multipart message in MIME format. ------=_NextPart_000_0B12_01D90375.1F242620 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too. Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 415 unassigned or newcomer bugs. We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, "4.2", "4.3", "4.99" and "Future", the more pressing/urgent issues being in "4.2" and then "4.3". Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@gmail.com ) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer _Bugs Thanks, Stephen K. Jolley Yocto Project Program Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_0B12_01D90375.1F242620 Content-Type: text/html; boundary="----=_NextPart_000_117E_01D8FDBE.EC5F1EE0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

 

The triage team is starting to try and = collect up and classify bugs which a newcomer to the project would be = able to work on in a way which means people can find them. They're being = listed on the triage page under the appropriate = heading:

http= s://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also = please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEm= bedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi<= /span>

The idea is these bugs should be straight = forward for a person to help work on who doesn't have deep experience = with the project.  If anyone can help, please take ownership of the = bug and send patches!  If anyone needs help/advice there are people = on irc who can likely do so, or some of the more experienced = contributors will likely be happy to help too.

 

Also, the triage team = meets weekly and does its best to handle the bugs reported into the = Bugzilla. The number of people attending that meeting has fallen, as = have the number of people available to help fix bugs. One of the things = we hear users report is they don't know how to help. We (the triage = team) are therefore going to start reporting out the currently 415 = unassigned or newcomer bugs.

 

We're hoping people may be able to spare = some time now and again to help out with these.  Bugs are split = into two types, "true bugs" where things don't work as they = should and "enhancements" which are features we'd want to add = to the system.  There are also roughly four different = "priority" classes right now,  “4.2”, = “4.3”, "4.99" and "Future", the more = pressing/urgent issues being in "4.2" and then = “4.3”.

 

Please review this link and if a bug is = something you would be able to help with either take ownership of the = bug, or send me (sjolley.yp.pm@gmail.com) an = e-mail with the bug number you would like and I will assign it to you = (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#U= nassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley<= o:p>

Yocto = Project Program Manager

(    Cell:         = ;       (208) = 244-4460

* Email:           = ;   sjolley.yp.pm@gmail.com

 

------=_NextPart_000_0B12_01D90375.1F242620--