Hi Daniel, My idea is that the committers create the listing of labels and the template.
So, when someone is going to open an Issue he/she will be asked those questions to select the issue that makes sense. Then the template will associate automatically the labels when Issue is created. The examples at https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository don't show that multiple checkbox idea for labels, but I think it should work. BR, Alan On Mon, Jul 22, 2024 at 3:41 PM Daniel Appiagyei <daniel.appiag...@braincorp.com.invalid> wrote: > Hi Alan, > I like that template, let's run with it! > > Are you suggesting that: > 1. we just use that issue template, > 2. create a listing of labels, use that issue template, and have people > with commit access manually add labels to each issue based on that, or > 3. create a listing of labels, use that issue template, and have github > actions automatically add labels to each issue based on that. *(with the > caveat that some labels like PRIORITY can only be set by committers)* > > I would be in favor of either 2 or 3 so that we retain the ability to > filter issues when searching based on the label field. > Best, > Daniel > > > On Mon, Jul 22, 2024 at 10:55 AM Alan C. Assis <acas...@gmail.com> wrote: > > > Hi Daniel, > > > > I think all committers have the rights to create it. > > > > We need to create the listing of labels, but my ideas was to create it as > > separated questions: > > > > This issue is a(n): [ ] BUG, [ ] Crash, [ ] Feature Request, [ ] > > Improvement, [ ] Logic Error, etc > > > > This issue apply to the architecture(s): [ ] All, [ ] ARM, [ ] ARM64, [ ] > > AVR, [ ] CEVA [ ] HC, [ ] MIPS, etc > > > > What areas are this issue related to: [ ] Audio, [ ] Clock Control, [ ] > > Ethernet, [ ] GPIO, [ ] Memory, etc > > > > Which vendors are affected: [ ] AMD, [ ] Atmel/Microchip [ ] Broadcom, [ > ] > > Espressif, [ ] Renesas, [ ] STMicroelectronics, etc > > > > What do you think? > > > > BR, > > > > Alan > > > > On Mon, Jul 22, 2024 at 2:27 PM Daniel Appiagyei > > <daniel.appiag...@braincorp.com.invalid> wrote: > > > > > Neat, seems like we're in agreement regarding labels. Also, good point > > > Alan. > > > I don't have permissions to the github repo to create new labels or add > > > them to existing issues. > > > Is there someone here with those permissions that would like to update > > them > > > as such that anyone that has contributed to the repo has the ability to > > > add/remove labels? > > > Best, > > > Daniel > > > > > > On Sun, Jul 21, 2024 at 5:11 PM yfliu2008 <yfliu2...@qq.com.invalid> > > > wrote: > > > > > > > Alan, > > > > > > > > > > > > Here is how > > > > > > > > > > https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository > > > > > > > > > > > > Regards, > > > > yf > > > > > > > > > > > > > > > > Original > > > > > > > > > > > > > > > > From:"Alan C. Assis"< acas...@gmail.com >; > > > > > > > > Date:2024/7/21 20:17 > > > > > > > > To:"daniel.appiagyei"< daniel.appiag...@braincorp.com.invalid >; > > > > > > > > CC:"dev"< dev@nuttx.apache.org >; > > > > > > > > Subject:Re: Github Issue Labels > > > > > > > > > > > > Arggg, I need to wake up and take coffee before typing an email, > hehehe > > > > > > > > Should be: > > > > > > > > Is there some way to create a template with checkboxes when opening > an > > > > Issue? > > > > > > > > It could help when users create a new issue. > > > > > > > > BR, > > > > > > > > Alan > > > > > > > > On Sun, Jul 21, 2024 at 9:15 AM Alan C. Assis wrote: > > > > > > > > > Totally agree! > > > > > > > > > > Yes there some way to create a template with checkboxes when > > opening > > > > an > > > > > Issue? It could help when users create a new issue. > > > > > > > > > > BR, > > > > > > > > > > Alan > > > > > > > > > > On Sat, Jul 20, 2024 at 8:58 PM Daniel Appiagyei > > > > > <daniel.appiag...@braincorp.com.invalid> wrote: > > > > > > > > > >> Hi, > > > > >> Is anyone opposed to: > > > > >> - creating more specific github issue labels, > > > > >> - encouraging everyone to use them, and > > > > >> - setting up permissions on github such that anyone that has > > > > contributed > > > > >> to > > > > >> the repo has the ability to add/remove labels? > > > > >> > > > > >> This would help a ton if anyone is curious about any > reported > > > > issues on > > > > >> their board or platform. Github lets you filter by labels. > > This > > > is > > > > >> something that zephyr does really well. Click the following > > link > > > > >> < > > > > >> > > > > > > > > > > https://github.com/zephyrproject-rtos/zephyr/labels/platform%3A%20NXP%20Drivers > > > > >> > > > > < > > > > > > https://github.com/zephyrproject-rtos/zephyr/labels/platform%3A%20NXP%20Drivers>> > > > >; > > > > > > > > > >> and check out the labels filter. > > > > >> > > > > >> What I'd like to see is a *platform* label with the > following > > > > variants: > > > > >> - platform: NXP > > > > >> - platform: nRF > > > > >> - platform: > > > > >> > > > > >> I'd also like the availability of more specific platform > > labels: > > > > >> - platform: STM32 > > > > >> - platform: STM32F4 (if this isn't too specific) > > > > >> - platform: IMXRT > > > > >> - platform: IMXRT1064 (again, if this isn't too specific) > > > > >> .... > > > > >> > > > > >> I'd also think that some priority labels would be good: > > > > >> - priority: low, priority: medium, priority: high > > > > >> > > > > >> Additionally, using the label of 'bug' or 'enhancement' > would > > > > make it > > > > >> easier to understand what the 400+ open issues pertain to. > > > > >> > > > > >> Thanks for the consideration! > > > > >> Best, > > > > >> Daniel > > > > >> > > > > >> > > > > >> > > > > >> -- > > > > >> > > > > >> > > > > >> *Daniel Appiagyei | Embedded Software Engineer *Email: > > > > >> daniel.appiag...@braincorp.com > > > > >> *Brain* > > > > >> * Corp™ *10182 Telesis Ct, Suite 100 > > > > >> San Diego, CA 92121 > > > > >> > > > > >> (858)-689-7600 > > > > >> www.braincorp.com > > > > >> > > > > > > > > > > > > > > > > > -- > > > > > > > > > *Daniel Appiagyei | Embedded Software Engineer *Email: > > > daniel.appiag...@braincorp.com > > > <bog...@braincorporation.com>*Brain* > > > * Corp™ *10182 Telesis Ct, Suite 100 > > > San Diego, CA 92121 > > > > > > (858)-689-7600 > > > www.braincorp.com > > > > > > > > -- > > > *Daniel Appiagyei | Embedded Software Engineer *Email: > daniel.appiag...@braincorp.com > <bog...@braincorporation.com>*Brain* > * Corp™ *10182 Telesis Ct, Suite 100 > San Diego, CA 92121 > > (858)-689-7600 > www.braincorp.com >
