From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f178.google.com (mail-pf1-f178.google.com [209.85.210.178]) by mail.openembedded.org (Postfix) with ESMTP id 3AB55731B1 for ; Mon, 30 Dec 2019 20:05:03 +0000 (UTC) Received: by mail-pf1-f178.google.com with SMTP id p14so18722283pfn.4 for ; Mon, 30 Dec 2019 12:05:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version:thread-index :content-language; bh=WocQWhq7TaptLX8QUvosE0CY7ICCgkpzrOaDLMJwUZ0=; b=Bw6CfmpGsc2JCGrickhbmbgpvFWM/59FdsuuznhRM4oit4gGwifXm2rnFRb/0lT1IP SAcem6kbAQtbMdlQ/iY1qbLHcDcfPypLX11kzZXJvABs/wbekGNxuD+8iQSEd66NjLCc GV6bTIR4QKMnz7xjnkCbOF0J3F2MM5w9AOkwOP7avGgKAUW3FOkst3+uu9k8m0Tx6pea wfO/CFuHb37MnGNiYJRXzr9fhuEmySqv5E2cO2/KpdqPc7R8y4ABgPv6FzmeETHJZb08 EyhD4ri0mNdXU7loYb99+Ww/t2fG3zi05ba0M5iuNwQ0PRn1ZkEJdufEgP43UCOH2lf9 jLQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :thread-index:content-language; bh=WocQWhq7TaptLX8QUvosE0CY7ICCgkpzrOaDLMJwUZ0=; b=Q0MWKR7qXVS+UifUa2gcsqR/0w83a2bFEjTjmswSoti2vwQTaO4+dahMsZNmVlXYG7 rwCIamhBDIEE9HIdc6Fj2o+KavA/XKNkCKw5nRq1YRMMhME4P3aT2sSKJVv+1jm/4XBH 8GJF+cyGvHDOzEucWhNRV28RNRl795koZPoUEcrE2krz2IK9EdO3sliKJiM0PEz37zag SY54x7fZq1oAtwrz+5X2wFiVeM8O5F842uvln8G8qHpOXAuvVHWQYY3xNdx0V7MVz4cb 9cecGiaTdj6k3Dbr8AZ7fX6Yp8HETSYvimQG/51eyUFhreBjX6e53hwLh9yjpdKO5PV8 OPKA== X-Gm-Message-State: APjAAAXHipvZr2FDOf7Pg2vNU3VTZmsTGsVwLaqNXDJIOj9dTaan9t8p xFNCLlHyCSmhOCfcB3PEzLw6gjI5 X-Google-Smtp-Source: APXvYqwpd07G9hf5kq7gje2Gr4KpDJj+J8jOMs4IIM1yRELGPtyZM+6ON1FPcA1vDnRPyy5ri2Z/Ng== X-Received: by 2002:aa7:9af1:: with SMTP id y17mr73269518pfp.21.1577736304136; Mon, 30 Dec 2019 12:05:04 -0800 (PST) Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id a1sm39284437pfo.68.2019.12.30.12.05.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Dec 2019 12:05:03 -0800 (PST) From: To: , Date: Mon, 30 Dec 2019 12:05:03 -0800 Message-ID: <070c01d5bf4c$6cacc7a0$460656e0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJK4CWcphHCymBVMqbl6g76mBcZeA== Subject: Yocto Project Newcomer & Unassigned Bugs - Help Needed X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2019 20:05:03 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_070D_01D5BF09.5E8A23E0" Content-Language: en-us ------=_NextPart_000_070D_01D5BF09.5E8A23E0 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 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 301 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, "3.1", "3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then "3.2". 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#Unassigned_or_Newcomer_Bugs Thanks, Stephen K. Jolley Yocto Project Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_070D_01D5BF09.5E8A23E0 Content-Type: text/html; boundary="----=_NextPart_000_0348_01D5B98C.EC41E880"; 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

 

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 301 = 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, “3.1”, “3.2, = "3.99" and "Future", the more pressing/urgent issues = being in "3.1" and then “3.2”.

 

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#Unassigned_or_New= comer_Bugs

 

Thanks,

 

Stephen K. Jolley<= o:p>

Yocto = Project Project Manager

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

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

 

------=_NextPart_000_070D_01D5BF09.5E8A23E0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from yocto-www.yoctoproject.org (yocto-www.yoctoproject.org [140.211.169.56]) by mx.groups.io with SMTP id smtpd.web11.7799.1577736307222889740 for ; Mon, 30 Dec 2019 12:05:07 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Bw6CfmpG; spf=softfail (domain: gmail.com, ip: 140.211.169.56, mailfrom: sjolley.yp.pm@gmail.com) Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id C339EE01335; Mon, 30 Dec 2019 12:05:06 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (sjolley.yp.pm[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [209.85.215.169 listed in list.dnswl.org] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid Received: from mail-pg1-f169.google.com (mail-pg1-f169.google.com [209.85.215.169]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BB2A6E00963 for ; Mon, 30 Dec 2019 12:05:04 -0800 (PST) Received: by mail-pg1-f169.google.com with SMTP id x7so18483369pgl.11 for ; Mon, 30 Dec 2019 12:05:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version:thread-index :content-language; bh=WocQWhq7TaptLX8QUvosE0CY7ICCgkpzrOaDLMJwUZ0=; b=Bw6CfmpGsc2JCGrickhbmbgpvFWM/59FdsuuznhRM4oit4gGwifXm2rnFRb/0lT1IP SAcem6kbAQtbMdlQ/iY1qbLHcDcfPypLX11kzZXJvABs/wbekGNxuD+8iQSEd66NjLCc GV6bTIR4QKMnz7xjnkCbOF0J3F2MM5w9AOkwOP7avGgKAUW3FOkst3+uu9k8m0Tx6pea wfO/CFuHb37MnGNiYJRXzr9fhuEmySqv5E2cO2/KpdqPc7R8y4ABgPv6FzmeETHJZb08 EyhD4ri0mNdXU7loYb99+Ww/t2fG3zi05ba0M5iuNwQ0PRn1ZkEJdufEgP43UCOH2lf9 jLQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :thread-index:content-language; bh=WocQWhq7TaptLX8QUvosE0CY7ICCgkpzrOaDLMJwUZ0=; b=WRzKARFnoyc4N/w+FVqKi6pcocFtUcKaVOcZtG1OrBs4C2BFJa9zpkt5Jeq3GGNWS3 Ja0Njd90lOLOpEXr2prmKswM0k6Zp1Yh4VTC2vxC56yizLaLxCqp7rR3TPYqJBmX74DZ uE7yEmzmGJswxskoFs7Be7OkI0+TRHNWPu2SqMDcgwCwgMoXYCIggg24AvS6V1AOk9lJ ZCJ3fmUO0vgz4WjooCx9tCzwjbG3AgmfAQvdLTfTIB609kPK8JH+3BItpCg5b/lgPhAL cf8dqOZkoBTPJ3DKJhp0LmzAp5f1siRzELDJyKMi9TVqaTNtNEjIVGeiNuI1wjFk6+SS Fwwg== X-Gm-Message-State: APjAAAUsSdccFxg3a2iQOSwd2QSHs+wDPZnxvRZ4WzxZF3DqltSiN1YD bWnEsgjZnFzrnyuWDEZMvHeYAmnu X-Google-Smtp-Source: APXvYqwpd07G9hf5kq7gje2Gr4KpDJj+J8jOMs4IIM1yRELGPtyZM+6ON1FPcA1vDnRPyy5ri2Z/Ng== X-Received: by 2002:aa7:9af1:: with SMTP id y17mr73269518pfp.21.1577736304136; Mon, 30 Dec 2019 12:05:04 -0800 (PST) Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id a1sm39284437pfo.68.2019.12.30.12.05.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Dec 2019 12:05:03 -0800 (PST) From: "Stephen Jolley" To: , Cc: Subject: Yocto Project Newcomer & Unassigned Bugs - Help Needed Date: Mon, 30 Dec 2019 12:05:03 -0800 Message-ID: <070c01d5bf4c$6cacc7a0$460656e0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJK4CWcphHCymBVMqbl6g76mBcZeA== Content-Type: multipart/alternative; boundary="----=_NextPart_000_070D_01D5BF09.5E8A23E0" Content-Language: en-us ------=_NextPart_000_070D_01D5BF09.5E8A23E0 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 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 301 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, "3.1", "3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then "3.2". 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#Unassigned_or_Newcomer_Bugs Thanks, Stephen K. Jolley Yocto Project Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_070D_01D5BF09.5E8A23E0 Content-Type: text/html; boundary="----=_NextPart_000_0348_01D5B98C.EC41E880"; 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

 

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 301 = 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, “3.1”, “3.2, = "3.99" and "Future", the more pressing/urgent issues = being in "3.1" and then “3.2”.

 

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#Unassigned_or_New= comer_Bugs

 

Thanks,

 

Stephen K. Jolley<= o:p>

Yocto = Project Project Manager

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

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

 

------=_NextPart_000_070D_01D5BF09.5E8A23E0--