This is a rather intricate topic, so I will try my best to be as objective and neutral as possible. I'm trying to get as many maintainers in here as possible so we can have a debate about this.

We are currently having two big issues that I would like to have solved:

1. Creating multiarch images within one repository (see Publish multi architecture image #1678)
2. Enabling automated docker builds (with buildx, see 1. and Enable automated docker builds #1207)

@tomav seems to have very little time at hand, but without permissions to the build and test services, there is nothing we as maintainers can do. Therefore, one valuable solution could be this:

Transferring the main development repository to someone else, preferably a (somewhat active) maintainer. This can easily be done with a fork. All current maintainers shall be invited so they can collaborate as before. We can use GitHub actions or another solution to solve 1. and 2. Current issue can be solved here, new issues will be marked so they can be opened in the new repository.

In #1678, @radicand offered to help with the GitHub actions to build for multiple architectures.

I would like to hear what everyone thinks about this - whether this is a possible solution, what's bad, what's good, what is to be improved on; maybe I'm completely missing something? Let's debate on this.

All the Tasks - Tracking

Tier 1

• Create a description of how the test suite should work / works, in a clear, concise way, for example with diagrams, etc.
• As @wernerfred provided a beautiful overview, all actions shall be implemented as described in his post

Tier 2

• See whether GH Organizations brings a benefit in terms of workflow for (multiple) collaborators
• Use GH Actions to build multiarch with docker buildx
• Create a scheduled build to have the images up-to-date (with GH Actions)
• Integrate tests into GH actions to only build when tests are successful
• Integrate automatic parsing / labelling

Tier 3

• Look into Dependabot
• Look into Codecov as an action
• Resolve old issues in tomav/docker-mailsever
• Resolve old pull requests in tomav/docker-mailserver