Blender modules are present on various channels. Chat, Phabricator, Forum, Wiki... New contributors look for information or want to get in contact with developers. These channels and pages are not consistent though, some information is missing or hard to find. This is a proposal to improve the Module pages.
1) Module landing page
Currently, module information are scattered throughout two places, the wiki and phabricator.
- The wiki Modules
- And the landing pages on phabricator, for example https://developer.blender.org/tag/sculpt_paint_texture/
In order to avoid duplication and to have one single place with all relevant information I suggest the following re-structure:
- The wiki page will be simplified, and will become an overview of the modules with links to the landing pages Proposal - Wiki page
- All further information will be on the modules landing page then: Example landing page
These information include:
- Scope / Information about the module
- The tag to use for reports / patches
- Status of the module (actively developed, in maintenance etc...)
- List of Members / Subprojects
- Contact information (Chat, forum, mailing list, meetings...)
- Links to bug reports, known issues, easy tasks to work on...
- Link to documentation
Modules can add additional information if they like.
This part needs further work. Apart from the main channel #blender-coders, there are several channels dedicated to the modules.
- Make the channel names consistent (not all end with "module").
- Have basic information in the channel header:
#geometry-nodes: Meet 14 CEST | Agenda | Workboard | Archived Meeting Notes | Project Wiki | Agile | Fields Task Force | Channel for development, please stay on topic
#nodes-physics-module: Module Overview | Development
These headers should be streamlined, providing a minimum of information & links but still leave additional freedom for more information if needed.
Link to landing page (minimum requirement) | Time of next meeting (if scheduled) | Link to last meeting notes (if available) | additional links and information as needed
3) Role of Artist members
This part needs further work. Every module ideally consists of developers and artists. The role of artist members is very important and should be properly defined and strengthened.
Current responsibilities according to Modules/Roles
- Make sure the module is well tested for a release
- Help documenting and with release logs
- Feedback on public forums or mailing lists on feature requests
- Check on the most demanding feature requests (for example from Right Click Select) and work them into a roadmap, in consultation with developers.
- There are a lot of opinions and feedback online and it is time consuming for developers to read through. The artist members can act as kind of gatekeepers (in an including way) and bring up certain opinions to developers if many people share an idea or concern. Basically channel important feedback.