Hi,
I started working on docker files for Mailman.
I created three repositories:
- https://github.com/simonsmiley/postorius-docker
Holds the files needed to create a postorius container
- https://github.com/simonsmiley/mailman-docker
Holds the files needed to create a core container
- https://github.com/simonsmiley/mailman-compose
Holds docker-compose files that greatly simply the process of running
the containers
* The mailman repo currently lacks documentation
* Currently no emails can be sent.
I still have to figure out what the best way is...
* Hyperkitty will be added next
(together with a complete "bundler" install)
I pushed two images to the docker hub. Their names are
thelinuxguy/postorius and thelinuxguy/mailman
I created two organizations
mailman on docker hub and gnu-mailman on github
https://github.com/gnu-mailmanhttps://hub.docker.com/u/mailman/
I know we shouldn't use github, but there is no way around
github/bitbucket for automated builds on docker hub.
I post here to inform you about the docker images and I also to ask if
I'm allowed to keep these two organizations and move my images/repos
there. I'll happily give push/owner access to additional people if
requested.
The repositories could be mirrored to the gitlab mailman group,
sadly the process doesn't work the other way round just yet.
In case this request gets denied, I'll just remove the organizations and
let the images be "unofficial".
cheers,
Simon
Hi,
I know all core devs are volunteers, and no one is maintaing the Mailman
projects full-time, but it's a little frustrating to have your merge
request open for a couple of months without any/much reaction to it...
I try to keep my merge requests up to date and conflict-free, but having
to do this for a couple of months, while there is no clear reason why
it's not merged yet, is a little demotivating.
In Postorius there have been (and there still are) merge requests by new
contributors that were probably abandoned, because quite some time has
passed since their creation...
Simon
Respected Member,
Dev Sprint is the best way to collaborate/guide other contributors
physically rather than over IRC / email. We invite this community to
join and hack for whole 3 days during the conference. Programmers are
dreaming of contributing but they are unable to just because of lacking
guidance.
It will be a proud moment to mentor participants for whole three
days and encourage them to be the active contributor for the project.
Large contributing guidelines are always hard to digest.
CFP is already started. We invite you to submit a proposal
[here](https://in.pycon.org/cfp/dev-sprint-2016/proposals/).
Schedule for Dev sprint [Pycon India, New Delhi](https://in.pycon.org)
* Day-I: 23rd September 2016 - Full day
* Day-II: 24th September 2016 - 5.00 PM to 9.00 PM
* Day-III: 25th September 2016 - 5.00 PM to 9.00 PM
Note: If you are reading this mail and you believe referring
interested contributors will help to represent project well, feel free
to drop me a mail. I will try to invite them individually. Many Thanks!
