Follow up on ideas to fix device maintainer burnout

fresh from the hackathon:

what to do about device maintainer burnout?

possible solutions:

• announce that we want to have 5 maintainers per device (at least 2, see below)
  • Write blog post: Aim for 5 maintainers per SoC <--
    • what we want groups of maintainers for 1 SoC to do, and it is fine if people can just do one part of it:
      • triage issues!
      • stable kernel upgrades (without rebase)
      • kernel upgrade with rebasing patches etc
      • test all kinds of stuff on their device (new kernel upgrades, new postmarketOS releases, possibly new alsa/modemmanager/etc.)
      • motivate each other
      • remove people from the team who are not active anymore
      • find new people
      • automation (like Caleb's cool thing!)
    • new requirements for community:
      • require at least two maintainers
      • the group must be able to do all of the above!
• update the Contributing page <---
  • on the pmos home page, move it up to the top
• update requirements for device maintainers <---
  • see above, and in more detail:
  • maintain kernel (Luca's process):
    • as soon as _rc1 is out upstream:
      • rebase it
      • test it (smaller kernel config)
        • a couple of devices per SoC
      • make issues/ML posts upstream for everything that broke (and maybe revert temporarily)
      • bisect if needed
    • final version / or .1:
      • rebase again
      • put in pmaports
• to reduce wrong incentive of getting images when in community:
  • allow images for testing devices if we kinda know the maintainer
  • if they fail to build, we just remove 'em
  • show the images on the homepage! (main / community / then a note? / testing)

brainstorming:

• ask for help with maintaining devices / kernels, e.g. in the monthly blog posts