Improve module pages / roles

Finally took a moment to check out the updated proposal in more detail. Generally something I can get behind. Just two points of feedback:

  1. Referring to non-active modules:

    For critical issues (like crashes), the core developers can take a look, if the issue is considered severe by the admins

    Does that mean admins are responsible for finding severe issues in non-active (“red”) modules? That seems like quite a burden loaded onto them. I’d say the triaging team can just do this, if in doubt core developers or admins can help out with their judgement.

  2. As example for the channel header, you use #geometry-nodes as an example. I think that’s okay to demonstrate the point, but I’d note that this in fact is not a module channel, but a project channel. We should always be very explicit about this difference (especially since a project may involve multiple modules). By the way, as naming convention I’d propose using -module and -project suffixes respectively.

1 Like