Hello, Two notes as followup: 1.) The modules are listed here as headers in the main panel and also in the right side panel: https://wiki.blender.org/wiki/Modules They are as follows:
- Blender (auto tagged as BF Blender to all non-add-on reports) <https://wiki.blender.org/wiki/Modules#Blender> <https://wiki.blender.org/wiki/Modules#Development_Management> - Development Management <https://wiki.blender.org/wiki/Modules#Development_Management> - User Interface <https://wiki.blender.org/wiki/Modules#User_Interface> - Modeling <https://wiki.blender.org/wiki/Modules#Modeling> - Sculpt, Paint, Texture <https://wiki.blender.org/wiki/Modules#Sculpt.2C_Paint.2C_Texture> - Animation & Rigging <https://wiki.blender.org/wiki/Modules#Animation_.26_Rigging> - Grease Pencil <https://wiki.blender.org/wiki/Modules#Grease_Pencil> - Eevee & Viewport <https://wiki.blender.org/wiki/Modules#Eevee_.26_Viewport> - Render & Cycles <https://wiki.blender.org/wiki/Modules#Render_.26_Cycles> - Data, Assets & I/O <https://wiki.blender.org/wiki/Modules#Data.2C_Assets_.26_I.2FO> - Python & Add-ons <https://wiki.blender.org/wiki/Modules#Python_.26_Add-ons> - VFX & Video <https://wiki.blender.org/wiki/Modules#VFX_.26_Video> - Nodes & Physics <https://wiki.blender.org/wiki/Modules#Nodes_.26_Physics> - Platforms, Builds & Tests <https://wiki.blender.org/wiki/Modules#Platforms.2C_Builds_.26_Tests> Documentation also has it's own module tag. 2.) Module tags are colored on Phabricator. If you add a tag and it is grey, it isn't a module. Sincerely, Evan Wilson (EAW) On Thu, May 21, 2020 at 6:38 AM Dalai Felinto via Bf-committers < [email protected]> wrote: > Hi, > This is a friendly reminder to follow the triaging process more closely > [1]. > > At the moment there are around 80 tasks that are not tagged with any > of the module tags. That means these reports, known issues and bugs > won't ever be classified, found and fixed (respectively), since they > don't show in the modules queries and workboards. > > To keep track of this there is a new global query called "Needs Module > Tag" to show all the reports that were not fully tagged [2]. > > Triaging team: please go over these tasks, tag them accordingly, and > remember the person who confirmed without a proper tag to do so next > time [3]. Focus on the bugs first, then the known issues. > > Modules owners: if you want to include more tags in your module is > very simple. You need to tag the project task with it, and update the > queries accordingly [4]. > > Currently module-less tags from untagged reports [2]: > * Alembic > * Audio > * Compositing > * Dependency Graph > * Freestyle > * Images & Movies > * Modifiers > * Performance > * Translations > > [1] - https://wiki.blender.org/wiki/Process/A_Bugs_Life > [2] - https://developer.blender.org → Maniphest →Needs Module Tag > [3] - e.g., "Confirmed reports should always be tagged to a module, > otherwise they don't show up in the queries and workboards." > [4] - Queries that need to be updated: "Needs Module Tag", the > module's "Bug", "Known Issue" and "Unclassified queries", the module > queries when changing a sub-module (e.g., if changing Text Editor, the > Python & Addons' queries need update too). > > Thank you, > -Dalai- > -------------------------------------------------------------------- > Dalai Felinto - [email protected] - www.blender.org > Blender Development Coordinator > _______________________________________________ > Bf-committers mailing list > [email protected] > https://lists.blender.org/mailman/listinfo/bf-committers > -- Evan Wilson 773.354.6758 _______________________________________________ Bf-committers mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
