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
Looking forward to contributing to GNU Mailman through this year's GSOC program.
Glad to hear that!
Keep us informed about what you're doing, and also any problems you
have even if you can resolve them yourself. We want the experience
for non-developer users to be as smooth as possible.
Anirudh Dahiya writes:
> I was building Mailman 3.
> The server is behind a proxy.
> I was using Django 1.9.1 .
> After fixing my /etc/environment file to set the correct proxy thing the
> 403 Forbidden error was resolved well.
> Another thing I faced was the unsuported keyword used in django
> render_to_string(template,context_instance=final_context) method. I
> manually changed it to replace just the context_instance part with
> context=final_context(checked django docs for that) and things worked out
> fine after that. Its finally working now. I hope I can start contributing
> Thanks for the guidance
> On Tue, Jan 12, 2016 at 7:36 AM, Stephen J. Turnbull <stephen(a)xemacs.org>
> > This -- "Python Version: 2.7.9" is also a problem for recent Mailman 3
> > (since 3.1 IIRC) -- Mailman 3 is only supported on Python 3. I guess
> > this is Postorius and it's still OK for 2.7 (upgrading to the most
> > recent Python 2 version, which I believe is 2.7.11, is probably a good
> > idea, as there were security issues in 2.7.9 and 2.7.10).
> > I would guess that your proxy simply isn't permitted to access the
> > REST port by the server. Check firewall settings and try a simple
> > client such as wget or curl from the Mailman host. If you get the
> > same result (ie, 403 Forbidden) with those clients, then you're going
> > to need to talk to your local administrators about how to configure
> > the firewall to permit Postorius to talk to Mailman.
> > Steve
> 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/stephen%40xemacs…
> Security Policy: http://wiki.list.org/x/QIA9
On 01/10/2016 03:11 PM, Gaurav Mittal wrote:
> I want to introduce myself. I am a 3rd year student pursuing my B.Tech in
> CSE from International Institute of Information Technology, Hyderabad.
Welcome and thanks for your interest in Mailman.
> I want to start contributing to Mailman and also hoping to do GSOC'16 with
> mailman. How do i begin?
You can start by reading a bit about mailman from the website (list.org)
and digging out getting started guide. I could give you the direct
links, but it isn't really very hard to find them I guess. Let me know
if you really don't really find the Getting Started Guide on
http://wiki.list.org or http://list.org.
Make sure that you look for Mailman Suite 3.0 and not mailman 2.0 which
is not actively developed now. After you think you know enough about
Mailman, you can then try to fix some small easy bugs in Mailman core or
any of its sister projects (Postorius - the Web UI, Hyperkitty - the
Archiver, Client - Python bindings). There might be less number or bugs
actually tagged "easy" or "beginner friendly", but you can explore other
bugs too. If you have any problems/questions, ask questions here or on
#mailman on Freenode(IRC).
I want to introduce myself. I am a 3rd year student pursuing my B.Tech in
CSE from International Institute of Information Technology, Hyderabad.
I want to start contributing to Mailman and also hoping to do GSOC'16 with
mailman. How do i begin?
On 01/09/2016 09:33 PM, Rishab Jaju wrote:
> Hi all,
> I am trying to build mailman. I assume these are the instructions:
> Although the page is for Hyperkitty, I assume that others will be built in
> the same way since that is the only page I could find.
You should see <http://wiki.list.org/DOC/Mailman3> and
> I can't clone the repositories from gitlab. It gives me the following error:
> Permission denied (publickey).
> fatal: Could not read from remote repository.
> Please make sure you have the correct access rights
> and the repository exists.
The above error indicates you are using ssh to clone the repository from
gitlab but you haven't registered and provided an ssh public key on
gitlab. The easiest way around this is to use http instead.
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
I'm beginning to use mailman 3.
One of the nice feature in mailman 2 was the ability to allow specific
non-member of a list to post in it.
I don't find a way to do this in mailman 3 and as far as I understand
it seems that there is no automatic way of dealing with this.
Am I wrong?
I am trying to build mailman. I assume these are the instructions:
Although the page is for Hyperkitty, I assume that others will be built in
the same way since that is the only page I could find.
I can't clone the repositories from gitlab. It gives me the following error:
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
How do I solve that error? Also, am I following the correct build