Comments (12)
I'd be happy to invite you to the @docker-mailserver/core-administrators team, if you'd like to join.
👍
When it comes to DockerHub: I would very much like to have a +1 in the DockerHub organization in case I cannot access my account, and we need to do something. If someone else is willing to step in here, please let us know! The only thing required is a DockerHub account, and a high trust factor of course.
You can add me there too as a backup. I have an DH account and a high trust factor 😆
from docker-mailserver.
I'd be happy to invite you to the @docker-mailserver/core-administrators team, if you'd like to join.
👍
Done 🚀
When it comes to DockerHub: I would very much like to have a +1 in the DockerHub organization in case I cannot access my account, and we need to do something. If someone else is willing to step in here, please let us know! The only thing required is a DockerHub account, and a high trust factor of course.
You can add me there too as a backup. I have an DH account and a high trust factor 😆
Perfect; I invited you and removed @fbartels. @polarathene the organization on DockerHub is now full again (max 3 people; IDK why they have such a low limit...).
from docker-mailserver.
I can of course do that @fbartels; I will move you to moderators :) This way, you are still listed, but you do not have any obligations, and you will also not be able to accidentally break anything.
When it comes to DockerHub: I would very much like to have a +1 in the DockerHub organization in case I cannot access my account, and we need to do something. If someone else is willing to step in here, please let us know! The only thing required is a DockerHub account, and a high trust factor of course.
from docker-mailserver.
CC @docker-mailserver/helm-maintainers @docker-mailserver/admin-maintainers @docker-mailserver/core-moderators @docker-mailserver/core-maintainers @docker-mailserver/core-administrators
While in the process of resolving this issue, I took the time to review the current organization & team structure. I renamed the teams slightly (-
-> /
to better visualize the "namespacing" of the team).
- I have added @polarathene to the @docker-mailserver/core-administrators team (removing him from the moderators team at the same time).
- I made @casperklein a maintainer in the @docker-mailserver/core-maintainers team. I'd be happy to invite you to the @docker-mailserver/core-administrators team, if you'd like to join.
- I moved @NorseGaud from the @docker-mailserver/core-maintainers teams to the @docker-mailserver/core-moderators team.
- I removed @erik-wramner from the @docker-mailserver/core-maintainers team.
- I have moved @fbartels and @wernerfred from the @docker-mailserver/core-administrators team to the @docker-mailserver/core-maintainers team with member access. @fbartels will remain as a team member on DockerHub for the
mailserver/docker-mailserver
image. - I have removed myself from @docker-mailserver/core-maintainers.
- I have flattened hierarchies so that everyone will be in one and only one team, while keeping the same privilege. Only where people would miss out on privilege have I left them in additional teams.
- The @docker-mailserver/admin-maintainers team now has the proper role ("maintain") for the docker-mailserver/docker-mailserver-helm repository.
- I removed administrators from other teams because they already have administrative privileges in all repositories, making their membership superflous. Tagging the team should reach out to active maintainers first, before going to admins. @polarathene has already voiced concerns about the time he has for maintenance - hence, I am trying to reduce the time effort for everyone here.
If you have concerns, please share them with me!
from docker-mailserver.
Thanks for taking the time to tackle this ❤️
If someone else is willing to step in here, please let us know! The only thing required is a DockerHub account, and a high trust factor of course.
I may create an account in future once I have some projects of my own to publish, probably months away at earliest though 👍
from docker-mailserver.
Hi team,
Could you please completely remove myself from this project. I intend to migrate to @stalwartlabs a mail server written in Rust. You will see me closing my issues when the migration is done. Thank you for maintaining this project over the years!
from docker-mailserver.
Hi team,
Could you please completely remove myself from this project. I intend to migrate to @stalwartlabs a mail server written in Rust. You will see me closing my issues when the migration is done. Thank you for maintaining this project over the years!
I can do that too. Thank you for helping us :) I was recently made aware of this project as well, I will have a look at the project, too.
from docker-mailserver.
Please note that this response was created using generative AI, leveraging previously available information from the repository. This information may be helpful. However, it is our strong recommendation that you carefully consider the information before blindly applying it.
To request admin access to the docker-mailserver-helm repository, it's best to follow the official contribution guidelines and communicate through the appropriate channels. Since Docker Mailserver is a community-driven project, such requests are typically handled by the maintainers and might require discussion or approval from other contributors.
You should start by creating an issue in the docker-mailserver-helm repository explaining your request and the reasons for needing admin access. Make sure to provide detailed information and any relevant contributions you have made to justify the need for admin access.
Additionally, directly mentioning the maintainers in a public issue or pull request, as you've done, is a good way to get their attention. However, for specific permissions like admin access, a more formal request through an issue might be more appropriate to allow for transparent discussion among the community.
Here are some links that might help you:
Please ensure to follow these guidelines and use the provided templates when making your request.
This comment was generated by Glime.
from docker-mailserver.
I will have a look tomorrow.
from docker-mailserver.
Done :)
from docker-mailserver.
Hi @georglauterbach,
since my contributions are quite minimal since I no longer use docker-mailserver professionally I would also not be offended if you remove me from the remaining groups. If you need my input on something I am of course glad to help.
from docker-mailserver.
If someone else is willing to step in here, please let us know! The only thing required is a DockerHub account, and a high trust factor of course.
I may create an account in future once I have some projects of my own to publish, probably months away at earliest though 👍
When you're ready, please let me know :) No pressure here; just so that we have a proper perspective.
from docker-mailserver.
Related Issues (20)
- bug report: can't receive emails (Traefik v3, HAProxy v2, DMS Edge) HOT 4
- question: Why does `doveadm auth test` fails with user added by `setup dovecot-master add` and `setup email add` HOT 11
- docs: IPv6 updates with Docker v27
- bug: Container restarts skip ownership fixes
- question: How can I verify that the integration with iptables is actually working? HOT 12
- bug report: Scaling issues with check-for-changes.sh when managing mailboxes/aliases HOT 4
- docs: `ACCOUNT_PROVISIONER=FILE` additional Dovecot user attribtues
- postfix/submissions/smtpd: SASL authentication failure: Couldn't find mech XOAUTH2 HOT 12
- feature request: OAUTH - autoprovision accounts on first login using post-login scripting HOT 5
- bug report: Upgrading to v14 - postfix does not start HOT 12
- question: Why does `DEFAULT_RELAY_HOST` fail to authenticate? (DMS release prior to v14) HOT 3
- bug report: Postfix logs the error `fatal: bad string length 0 < 1: virtual_mailbox_base` HOT 4
- question: How to send email on port 465 without using a relay HOT 10
- Question: How to add reply-to header information HOT 1
- [TODO]: `SMTP_ONLY=1` feature should swap `virtual_mailbox_domains` with `virtual_alias_domains`
- bug report: `postfix-main.cf` is appending warnings to `/etc/postfix/main.cf` HOT 7
- [TODO]: Small tasks
- other: Proposal to change Getmail working directory HOT 8
- [TODO]: DMS v14 regression - Container restart support may fail due to unclean exit
- bug report: `postconf: fatal: open /etc/postfix/main.cf for reading: No such file or directory` HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker-mailserver.