Who is maintaining this repo? about docker

[PeerRich]

hey @pat-s we've given this topic a much higher priority inside of the team and will find a better solution for this! 🎉 until then, you can make PRs at any time and we'll merge them accordingly

[krumware]

@PeerRich I'm ok with committing to help out on the docker repo + dockerhub + helm, if the support is needed.
(personal opinion on location? it should stay located in the calendso org)

[PeerRich]

Hey @pat-s I've just wrote a post about the new GitHub Docker Team: #32

[PeerRich]

hey @pat-s, yeah i agree this has been very confusing. any recommendations? do you want to contribute to it? We can make a new team that has some writing authority over this repo

[pat-s]

I can certainly help but I think there needs to be an "official" solution how to apply for write permissions and who is in charge of reviewing requests (e.g. by commenting in this issue).

I can't promise to have enough time to look at all requests - I think there needs to be a community effort to make this work in the long run if the Calendso team does not want to do it themselves.

A follow up topic would be how (and if) a docker image from this repo would be distributed on Dockerhub (or similar) so that people do not need to build the image first.

[baileypumfleet]

The problem is, if we make it an "official" solution, then people start expecting us to support it, which we can't guarantee

[pat-s]

Yes you mentioned this point quite often already. Even though I am not sharing your view, I did not expect/aim for this to change here.

I just asked for clarification about this repo and if it could be opened to more contributors, otherwise it won't be able to catch up.

I see the following options (with "you" being the Calendso maintainers):

• You curate the people with write access to this repo yourself
• You give a set of people permissions to add additional people with write access so the repo can manage itself

There will always be the discrepancy of you stating not to support docker/this repo but having it living within your organization.

Another option would be to move this repo to a different organization and link it from the Calendso README. I see linuxserver.io as a potential candidate here.

[pat-s]

I am also happy to help with testing and small recs, though I can't contribute substantially since I have too much on the list atm and my nodejs experience is limited.

Great to see something happening though!

[PeerRich]

cool. will set up a new team for docker and give out permissions more deliberately