Hi Fellow Developers,
I am a graduate student at University of Toronto, Canada who likes to code
(mainly in python).
I just started to get to know the Mailman product by studying its
architecture available on Aosabook <http://www.aosabook.org/en/mailman.html>
and I am looking forward to contribute to the organization. After reading
some of the email chains, I am assuming the best place to start is by
looking into issues available here
<https://gitlab.com/mailman/mailman/issues/> once I have a better
understanding on the product but any newbie advice/guidance is welcome.
Since you all know that a big reason why we moved to Gitlab from
Launchpad was Continuous Integration. As of now, only the forks of core
developers were automatically built by the Gitlab CI runners that we
have added for Mailman Project.
But now, thanks for Simon Hanna, anyone can enable Gitblab's Shared
Runners and run their tests inside a Docker Container. Right now, this
only works for Mailman Core, but very soon I am going to extend this to
other project repositories too.
1. Pull the latest commits from the Mailman's repo or fork it if you
2. Go to the project settings page of your fork and you will see an
option called 'Runners' in the left hand side menu.
3. In the runners page, push the big green button that says "Enable
After this, each commit that you push to your fork should automatically
be tested. If you don't see the CI running at all, make sure that you
have enabled CI for your fork.
Under the `Project Settings`, in the `Features` section, check the box
that says "Build". AFAIK, this should be enabled by default, but just in
case if it is not.
Again I would like to Simon Hanna for this contribution.
I am a new comer on this list. I am an old cyberactivist and an
administrator of more than 100 mailman lists and I would need to
operate much more for a budled project trough a user/feature
database. It means a way (1) to set-up scores of same style mailing
lists and (2) for a person being a member of my directory to easiliy
select the lists she wants to attend or quit. My idea is to get it
simple, non interfering and robust by having an independent database
used to generate an update script on a cron basis and that scri^pt
being run to create/update the necessary mailman instances.
1) would such a system already exist?
2) considered your experience of mailman do you think such a system
could realisticly be feasible and work?
3) I never looked at the mailman code yet : where in it should I have a look?
4) would this be a big work?
5) where could I get some help to develop it?
Thank you for attention and response.
Siddhartha Gairola writes:
> If you could assist me as to how I should proceed now.
Start at https://firstname.lastname@example.org/.
A couple of months' worth at first, then the last year or two. First,
this question, and several other relevant questions, have been
answered recently. Second, the archives provide background for
understanding the current focus of development.
Then, it's important that you test any changes you make, both with
unit tests and with a "live" installation. It doesn't need to go over
the Internet -- just localhost is enough in most cases -- but you do
need a real MTA (Postfix and Exim are supported and recommended) and
later, for the Postorius and HyperKitty components, a WGSI-capable
webserver (all the usual suspects will work; the Django internal
testing server is not good enough).
Finally, for more hints on developing, you should look at
http://wiki.list.org/DEV/Google_Summer_of_Code_2015 (the 2016 version
is still under construction, but the generic hints you want are fully
developed in last year's version).
I am new to this community and have set up the dev environment.
If you could assist me as to how I should proceed now.
it would be helpful if I could get started with some beginner level bug
I was looking at GSOC 2016 wiki page and I found "Preset List Settings
Templates" project quite interesting.
After reading out the project description and the discussion on the
project from the mail archives I have been able to reach out the
following conclusion :
I will be required to develop a Web Interface that will allow the
admins to set the different attributes to the different mailing lists
using some fixed templates(also known as styles). Not only this they
will be able to define their own styles and use them. This will serve
as our front-end.
In the back-end, we will be using tables for storing style attributes
and permission level(read only or editable). This table will basically
contain all the "stylable" attributes with "default or predefined"
values as contained in the mailing list table and one extra column for
There will also be some back-end python code whose key function would
be to read the attribute values from the styles table and when the
user applies a style on a mailing list it will copy the attribute
values from the style table to that particular mailing list's table.
Please do correct me if I am wrong somewhere. Also,I wish to seek your
views on this approach.
Also tell me if I would need to develop a Command Line Interface(which
I will love to develop) as well or only Web Interface would suffice?
Ankush Khandelwal writes:
> I am an undergraduate student pursuing Computer Science from IIIT
> Hyderabad ( India ), currently in 3rd year and I'm newbie to this
> organization. I am familiar with python and Git. Can somebody tell
> me about the bugs which I can solve so that I can start
Any of the ones listed at https://gitlab.com/mailman/mailman/issues/?
That's a joke, of course, but unfortunately the list if you select
label "beginner-friendly" is rather sparse (currently 1 issue is
listed). So at this point nobody really has a handle on this.
One *really* useful task you could do is go through a handful of
issues (say 10-25) and label the ones you think you *could* do as
"beginner-friendly" (and grab any you *like* by adding a comment that
you're working on them :-). Then post the list of issues you
evaluated (with the results) so somebody can (a) check your
evaluations for you, (b) we get a better idea of what new developers
*think* they can do (as opposed to our idea of what we think they
should be able to do), and (c) change any that are actually far deeper
than they look.
Such "triage" is a more or less neglected task for all the projects
I know of. Of course coding is more fun, but (at least at Mailman's
current state of 1 open "beginner-friendly" issue) triage is more
 https://docs.python.org/devguide/triaging.html This page is for
Python, but the basic principles apply to any project.
I am an undergraduate student pursuing Computer Science from IIIT
Hyderabad ( India ), currently in 3rd year and I'm newbie to this
organization. I am familiar with python and Git. Can somebody tell me about
the bugs which I can solve so that I can start contributing.
(mainly for Florian, but it's not secret)
Since I'm a student, I was thinking about applying for a GSoC spot this summer, but I'll probably
not have the time for it, so I won't do that.
I would however have enough time to be a mentor. (Google says about 5h a week per student, I could
manage up to 10h I guess)
The code of the mailman-suite I know best is postorius, so if a mentor is needed for that, I'm
available. I could of course still manage mentoring other projects.
A little bio:
I'm a 24 year old computer science student, currently pursuing my master degree. I'm studying in
I'm fluent in English, German and Arabic (but I really don't like typing Arabic ^^)
I was a tutor for about 8 different computing courses at my University.
I was always responsible for a group of up to 20 students. My job was to help them with their
assignments, grade them and explain stuff they didn't understand in the lectures.
The courses included practical programming courses, programming languages, distributed computing and
computer networks, algorithms and data structures, ...
If you want to look at my code, you'll find most of it in postorius where my username is 'thelinuxguy'.
So, if a mentor is needed, I'm available :-)
Feel free to ask any questions...
On 01/15/2016 09:33 AM, Harshit Bansal wrote:
> Hello everybody,
> I am Harshit Bansal, a first year undergraduate student from Harcourt
> Butler Technological Institute, Kanpur, looking to contribute to the
> GNU Mailman project for the upcoming Google Summer of Code program.
> I am very proficient in C and python. I also have a good grasp over
> the concepts of cryptography. I also have an intermediate level of
> Currently, I am going through the codebase, the mail archives and
> documentation of GNU Mailman and trying to set up the development
> environment for the GNU Mailman and finding some simple bugs to work
Thanks for choosing Mailman and welcome! Do not hesitate to ask
questions here or on IRC channel #mailman@freenode.
> Looking forward to contributing to GNU Mailman through this year's GSOC program.
> Harshit Bansal,
> HBTI, Kanpur.
> Mailman-Developers mailing list
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/raj.abhilash1%40…
> Security Policy: http://wiki.list.org/x/QIA9