Hello, I am Satbir Singh, a sophomore pursuing B.Tech in Information and
Communication Technology at DA-IICT.
I am a full stack web developer proficient in Django Framework. I want to
contribute to Mailman. I am aiming for GSoC 2019. I have previously
contributed to open source organizations and really excited to contribute
in this project. I am new to this organization please help me to get
started!
Thanking you
Satbir Singh
Hey all
We need to decide if we're going to go under the PSF umbrella or if we
want to go standalone.
The real advantages to the standalone are two tickets (most expenses
paid by Google) to the Mentor Summit, and the $500/student gift to
Mailman. But it's more work and lower chance of acceptance.
For PSF, we need to have project and idea pages up by Monday IIRC. I
think Google's deadline is a couple days later.
Steve
Dear Mailman Developers,
TL; DR: Please change the CNAME record of *docs.mailman3.org
<http://docs.mailman3.org>* from gnu-mailman.readthedocs.org to *readthedocs.io
<http://readthedocs.io>*.
I would like to raise the awareness that https://docs.mailman3.org is
having a wrong SSL certificate due to DNS misconfigure.
I once saw the Mailman 3 project in GSoC orgs page, and since I have
configured mailman before I would like to know about the ideas, I click on
the docs link. Wow, not secure.
Since the prompt tells me it is using *.readthedocs.org, I dig into the doc
of RTD (https://docs.readthedocs.io/en/latest/custom_domains.html) and it
tells it support custom domain SSL with some limitations. So, `dig
docs.mailman3.org`, got you, an old (may not wrong?) record.
Because the link is already published on GSoC, I don't know if it is
possible to change from https to http. So the better way might be support
https :).
Regards,
Xiaoxing Ye
Hello everyone, congratulations for getting selected for GSoc '19. I'm new
to this organisation. I wanted to know if there is any other platform where
we could connect?
Thank you.
Hi Everyone,
My name is Saurabh and I am new to open source development . I want to
contribute to Mailman but I am confused how to exactly do it.
It would be really helpful if anyone could guide me.
Yours sincerely,
Saurabh
Myself Nayan Khanna. Currently, I'm a 2nd year student at BITS Pilani
pursuing Bachelors of Engineering in Computer Science and Integrated Msc.
Mathematics.
I was exploring the projects of Mailman and was highly impressed by some of
them.
I have been into Web Development from the past 2 years and have worked a
lot on Django and Flask.
Apart from these, I have a good programming command in C, C++ and Python,
and know MySQL and DBMS concepts well.
Been into Web Development, I have also worked on HTML, CSS, JS, AngularJS.
Being more of a Back End Developer, I have worked on System Administration
and Web Hosting through Nginx+Gunicorn.
I love exploring new things and this is something which keeps me going.
I really look forward to spend my summer contributing to MailMan projects
while being a GSoC candidate for the org.
I would feel lucky if I could find a mentor who can guide me on getting
started with my contributions.
Hi,
I am running mailman 3 using the docker images created by Abhilash. Whenever I try to create a new user or reset password for an existing user, I get the error shown in the screenshot.
The only thing I can see in docker logs is "POST /accounts/password/reset/ HTTP/1.0" 500 1102. Any suggestions on how to debug this?
–Kamran
I am working on cutting out a release for Mailman Core, 3.2.1, soon. Most probably by end of this week. If you have anything small you really want to get into this release, please ping me, I'd prefer if we don't put anything huge. I'll cut out an -rc1 release EOD today.
We are going to move to more of SemVer[1] approach and avoid having to bump major versions (which, in our case, is minor version) if we don't need to. We will keep on bumping minor versions till we really need to bump major version due to backwards incompatibility reason.
This would also help us make more point releases that downstreams can upgrade to, without having to worry about bumping major versions. We don't really break API everytime when bumping major versions, which is slightly confusing and hard to keep track of.
This should also help us not worry too much about backporting fixes to old release branches. We will continue to release minor versions, till we have to bump major, after which the old version will be unmaintained. But in history of Mailman 3, we only had to break compatibility once with REST API change with 3.1 release.
Finally, I'll keep the release codename of 3.2.0 series and keep 'Tom Swayer' reserved for the next major version bump, whenever we end up doing that.
[1]: https://semver.org/
--
thanks,
Abhilash Raj (maxking)
