From: "Stephen Jolley" <sjolley.yp.pm@gmail.com> To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org> Cc: <sjolley.yp.pm@gmail.com> Subject: Yocto Project Newcomer & Unassigned Bugs - Help Needed Date: Mon, 20 Jan 2020 10:55:21 -0800 [thread overview] Message-ID: <08fe01d5cfc3$2ad25f20$80771d60$@gmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 2142 bytes --] 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 294 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 <mailto: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 Program Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com <mailto:sjolley.yp.pm@gmail.com> [-- Attachment #2: Type: text/html, Size: 6601 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: <sjolley.yp.pm@gmail.com> To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org> Subject: Yocto Project Newcomer & Unassigned Bugs - Help Needed Date: Mon, 20 Jan 2020 10:55:21 -0800 [thread overview] Message-ID: <08fe01d5cfc3$2ad25f20$80771d60$@gmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 2142 bytes --] 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 294 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 <mailto: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 Program Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com <mailto:sjolley.yp.pm@gmail.com> [-- Attachment #2: Type: text/html, Size: 6601 bytes --]
next reply other threads:[~2020-01-20 18:55 UTC|newest] Thread overview: 259+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-20 18:55 Stephen Jolley [this message] 2020-01-20 18:55 ` Yocto Project Newcomer & Unassigned Bugs - Help Needed sjolley.yp.pm -- strict thread matches above, loose matches on Subject: below -- 2024-04-23 5:01 Stephen K Jolley 2024-04-15 21:34 Stephen K Jolley 2024-04-08 19:36 Stephen K Jolley 2024-04-01 21:56 Stephen K Jolley 2024-03-25 20:47 Stephen K Jolley 2024-03-18 23:51 Stephen K Jolley 2024-03-11 22:27 Stephen K Jolley 2024-03-05 5:39 Stephen K Jolley 2024-02-27 6:53 Stephen K Jolley 2024-02-20 7:52 Stephen K Jolley 2024-02-13 4:50 Stephen K Jolley 2024-02-06 15:07 Stephen K Jolley 2024-01-29 22:02 Stephen K Jolley 2024-01-23 4:13 Stephen K Jolley 2024-01-15 19:50 Stephen K Jolley 2024-01-08 22:44 Stephen K Jolley 2024-01-02 20:54 Stephen K Jolley 2023-12-25 23:20 Stephen K Jolley 2023-12-19 0:07 Stephen K Jolley 2023-12-11 23:36 Stephen K Jolley 2023-12-04 23:53 Stephen K Jolley 2023-11-28 1:54 Stephen K Jolley 2023-11-21 10:31 Stephen K Jolley 2023-11-13 11:12 Stephen K Jolley 2023-11-06 11:50 Stephen K Jolley 2023-10-23 12:53 Stephen K Jolley 2023-10-16 23:47 Stephen K Jolley 2023-10-09 23:25 Stephen K Jolley 2023-09-26 1:26 Stephen K Jolley 2023-09-26 4:41 ` MOHAMMED HASSAN 2023-09-19 4:03 Stephen K Jolley 2023-09-11 21:42 Stephen K Jolley 2023-09-04 23:55 Stephen K Jolley 2023-08-29 1:43 Stephen K Jolley 2023-08-22 0:16 Stephen K Jolley 2023-08-14 21:00 Stephen K Jolley 2023-07-24 19:59 sjolley.yp.pm 2023-08-07 18:45 ` Stephen K Jolley 2023-07-17 21:44 sjolley.yp.pm 2023-07-10 16:20 sjolley.yp.pm 2023-07-03 15:06 sjolley.yp.pm 2023-06-26 20:51 sjolley.yp.pm 2023-06-20 0:35 sjolley.yp.pm 2023-06-12 23:50 sjolley.yp.pm 2023-06-06 3:23 sjolley.yp.pm 2023-05-30 0:09 sjolley.yp.pm 2023-05-23 0:08 sjolley.yp.pm 2023-05-15 23:00 sjolley.yp.pm 2023-05-09 0:29 sjolley.yp.pm 2023-05-02 0:44 sjolley.yp.pm 2023-04-24 19:20 sjolley.yp.pm 2023-04-11 3:33 sjolley.yp.pm 2023-04-03 19:37 sjolley.yp.pm 2023-03-28 0:22 sjolley.yp.pm 2023-03-20 21:21 sjolley.yp.pm 2023-03-13 22:32 sjolley.yp.pm 2023-03-07 2:12 sjolley.yp.pm 2023-02-28 5:35 sjolley.yp.pm 2023-02-20 19:12 sjolley.yp.pm 2023-02-13 22:48 sjolley.yp.pm 2023-02-07 3:31 sjolley.yp.pm 2023-01-31 0:55 sjolley.yp.pm 2023-01-24 1:06 sjolley.yp.pm 2023-01-17 3:11 sjolley.yp.pm 2023-01-09 20:40 sjolley.yp.pm 2023-01-02 21:43 sjolley.yp.pm 2022-12-26 22:53 sjolley.yp.pm 2022-12-19 20:20 sjolley.yp.pm 2022-12-13 4:21 sjolley.yp.pm 2022-12-06 6:52 sjolley.yp.pm 2022-11-29 5:02 sjolley.yp.pm 2022-11-21 22:35 sjolley.yp.pm 2022-11-14 20:16 sjolley.yp.pm 2022-11-08 0:38 sjolley.yp.pm 2022-10-31 21:04 sjolley.yp.pm 2022-10-24 22:03 sjolley.yp.pm 2022-10-17 15:25 sjolley.yp.pm 2022-10-11 6:37 sjolley.yp.pm 2022-10-04 2:34 sjolley.yp.pm 2022-09-27 0:06 sjolley.yp.pm 2022-09-19 22:01 sjolley.yp.pm 2022-09-13 0:38 sjolley.yp.pm 2022-09-06 0:42 sjolley.yp.pm 2022-08-29 19:32 sjolley.yp.pm 2022-08-23 0:36 sjolley.yp.pm 2022-08-15 20:57 sjolley.yp.pm 2022-08-08 23:18 sjolley.yp.pm 2022-08-01 21:34 sjolley.yp.pm 2022-07-18 20:01 sjolley.yp.pm 2022-07-11 22:11 sjolley.yp.pm 2022-07-04 20:51 sjolley.yp.pm 2022-06-27 22:46 sjolley.yp.pm 2022-06-20 23:20 sjolley.yp.pm 2022-06-14 14:15 sjolley.yp.pm 2022-06-07 15:21 sjolley.yp.pm 2022-05-30 23:00 sjolley.yp.pm 2022-05-24 14:50 sjolley.yp.pm 2022-05-17 6:09 sjolley.yp.pm 2022-05-09 10:13 sjolley.yp.pm 2022-05-03 12:57 sjolley.yp.pm 2022-04-25 17:08 sjolley.yp.pm 2022-04-18 19:45 sjolley.yp.pm 2022-04-11 23:33 sjolley.yp.pm 2022-04-05 0:36 sjolley.yp.pm 2022-03-29 0:42 sjolley.yp.pm 2022-03-21 23:56 sjolley.yp.pm 2022-03-14 23:02 sjolley.yp.pm 2022-03-08 16:06 sjolley.yp.pm 2022-03-01 16:28 sjolley.yp.pm 2022-02-21 23:32 sjolley.yp.pm 2022-02-15 0:45 sjolley.yp.pm 2022-02-07 23:58 sjolley.yp.pm 2022-02-01 2:38 sjolley.yp.pm 2022-01-25 3:06 sjolley.yp.pm 2022-01-17 22:27 sjolley.yp.pm 2022-01-10 21:34 sjolley.yp.pm 2022-01-03 22:29 sjolley.yp.pm 2021-12-27 23:07 sjolley.yp.pm 2021-12-20 22:57 sjolley.yp.pm 2021-12-13 22:19 sjolley.yp.pm 2021-12-06 21:32 sjolley.yp.pm 2021-11-29 22:10 sjolley.yp.pm 2021-11-22 22:16 sjolley.yp.pm 2021-11-16 0:05 sjolley.yp.pm 2021-11-08 23:30 sjolley.yp.pm 2021-10-25 22:40 sjolley.yp.pm 2021-10-18 17:37 sjolley.yp.pm 2021-10-11 23:01 sjolley.yp.pm 2021-10-05 0:25 sjolley.yp.pm 2021-09-27 21:59 sjolley.yp.pm 2021-09-20 21:58 Stephen Jolley 2021-09-13 21:54 Stephen Jolley 2021-09-06 20:28 Stephen Jolley 2021-08-31 0:04 Stephen Jolley 2021-08-23 23:00 Stephen Jolley 2021-08-17 3:15 Stephen Jolley 2021-08-10 0:48 Stephen Jolley 2021-08-10 0:34 Stephen Jolley 2021-08-02 23:34 Stephen Jolley 2021-07-26 21:41 Stephen Jolley 2021-07-19 18:26 Stephen Jolley 2021-07-13 14:47 Stephen Jolley 2021-07-06 14:41 Stephen Jolley 2021-06-29 2:16 Stephen Jolley 2021-06-21 19:01 Stephen Jolley 2021-06-15 0:18 Stephen Jolley 2021-06-08 0:22 Stephen Jolley 2021-05-31 23:44 Stephen Jolley 2021-05-25 2:28 Stephen Jolley 2021-05-18 1:58 Stephen Jolley 2021-05-10 23:38 Stephen Jolley 2021-05-04 1:00 Stephen Jolley 2021-04-26 23:59 Stephen Jolley 2021-04-20 0:51 Stephen Jolley 2021-04-13 0:27 Stephen Jolley 2021-04-06 3:52 Stephen Jolley 2021-03-29 22:34 Stephen Jolley 2021-03-22 20:42 Stephen Jolley 2021-03-15 19:08 Stephen Jolley 2021-03-08 16:17 Stephen Jolley 2021-03-02 2:43 Stephen Jolley 2021-02-22 22:07 Stephen Jolley 2021-02-15 23:11 Stephen Jolley 2021-02-09 0:25 Stephen Jolley 2021-02-02 1:46 Stephen Jolley 2021-01-26 15:39 Stephen Jolley 2021-01-19 1:14 Stephen Jolley 2021-01-12 0:09 Stephen Jolley 2021-01-04 18:34 Stephen Jolley 2020-12-29 4:47 Stephen Jolley 2020-12-22 0:34 Stephen Jolley 2020-12-15 3:01 Stephen Jolley 2020-12-08 3:12 Stephen Jolley 2020-12-01 1:41 Stephen Jolley 2020-11-24 22:19 Stephen Jolley 2020-11-17 1:02 Stephen Jolley 2020-11-10 0:04 Stephen Jolley 2020-11-02 22:21 Stephen Jolley 2020-10-26 21:48 Stephen Jolley 2020-10-19 20:50 Stephen Jolley 2020-10-12 19:39 Stephen Jolley 2020-09-29 1:15 Stephen Jolley 2020-09-22 14:34 Stephen Jolley 2020-09-15 3:20 Stephen Jolley 2020-09-07 18:51 Stephen Jolley 2020-08-31 22:27 Stephen Jolley 2020-08-24 20:11 Stephen Jolley 2020-08-18 2:43 Stephen Jolley 2020-08-11 0:23 Stephen Jolley 2020-07-27 23:37 Stephen Jolley 2020-07-20 21:34 Stephen Jolley 2020-07-13 22:05 Stephen Jolley 2020-07-07 1:32 Stephen Jolley 2020-06-30 23:19 Stephen Jolley 2020-06-22 21:29 Stephen Jolley 2020-06-15 22:39 Stephen Jolley 2020-06-09 14:58 Stephen Jolley 2020-06-01 16:47 Stephen Jolley 2020-05-25 22:11 Stephen Jolley 2020-05-18 16:21 Stephen Jolley 2020-05-11 16:19 Stephen Jolley 2020-05-04 16:10 Stephen Jolley 2020-04-27 16:39 Stephen Jolley 2020-04-13 17:06 Stephen Jolley 2020-04-06 18:10 Stephen Jolley 2020-03-30 17:32 Stephen Jolley 2020-03-23 16:52 Stephen Jolley 2020-03-16 16:42 Stephen Jolley 2020-03-16 16:42 ` sjolley.yp.pm 2020-03-09 17:23 Stephen Jolley 2020-03-09 17:23 ` sjolley.yp.pm 2020-03-02 19:45 Stephen Jolley 2020-03-02 19:45 ` sjolley.yp.pm 2020-02-24 22:06 Stephen Jolley 2020-02-24 22:06 ` sjolley.yp.pm 2020-02-10 17:09 Stephen Jolley 2020-02-10 17:09 ` sjolley.yp.pm 2020-02-03 17:28 Stephen Jolley 2020-02-03 17:28 ` sjolley.yp.pm 2020-01-27 16:56 Stephen Jolley 2020-01-27 16:56 ` sjolley.yp.pm 2020-01-14 0:01 Stephen Jolley 2020-01-14 0:01 ` sjolley.yp.pm 2020-01-06 17:08 Stephen Jolley 2020-01-06 17:08 ` sjolley.yp.pm 2019-12-30 20:05 Stephen Jolley 2019-12-30 20:05 ` sjolley.yp.pm 2019-12-23 20:31 Stephen Jolley 2019-12-23 20:31 ` sjolley.yp.pm 2019-12-17 1:41 Stephen Jolley 2019-12-17 1:41 ` sjolley.yp.pm 2019-12-09 17:01 Stephen Jolley 2019-12-09 17:01 ` sjolley.yp.pm 2019-12-02 16:55 Stephen Jolley 2019-12-02 16:55 ` sjolley.yp.pm 2019-11-25 17:23 Stephen Jolley 2019-11-25 17:23 ` sjolley.yp.pm 2019-11-18 17:59 Stephen K Jolley 2019-11-12 15:25 Stephen K Jolley 2019-11-05 4:46 Stephen K Jolley 2019-10-28 16:04 Stephen K Jolley 2019-10-21 16:23 Stephen K Jolley 2019-10-14 16:23 Stephen K Jolley 2019-10-07 16:37 Stephen K Jolley 2019-09-23 16:36 Stephen K Jolley 2019-09-16 17:14 Stephen K Jolley 2019-09-10 1:56 sjolley.yp.pm 2019-08-19 20:38 sjolley.yp.pm 2019-08-13 0:14 sjolley.yp.pm 2019-08-06 1:49 sjolley.yp.pm 2019-07-29 21:54 sjolley.yp.pm 2019-07-22 19:14 sjolley.yp.pm 2019-07-15 17:16 sjolley.yp.pm 2019-07-08 20:39 sjolley.yp.pm 2019-07-01 18:00 sjolley.yp.pm 2019-06-24 19:16 sjolley.yp.pm 2019-06-17 23:29 sjolley.yp.pm
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='08fe01d5cfc3$2ad25f20$80771d60$@gmail.com' \ --to=sjolley.yp.pm@gmail.com \ --cc=openembedded-core@lists.openembedded.org \ --cc=yocto@yoctoproject.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.