May I know what kind of problems you have with migration from Mailman 2 to Mailman 3? What do you think should be added to improve the current documentation of 'Migrating from Mailman 2.1 to Mailman 3'? Why is the current documentation insufficient?
Link to the documentation: http://docs.list.org/en/latest/migration.html
I'm applying for GSOD 2019 with the project title of 'Instructions for Migrating from Mailman 2 to Mailman 3'. I'd really appreciate any feedback for my proposal.
Link to my GSOD application proposal: http://bit.ly/ariessa_migration_gsod_application
I'm a software developer and technical writer interested in contributing to
GNU Mailman documentation. I'm a Google Summer of Code student but when I
heard about this program, I realized it was a great chance to expand my
technical writing experience and work closely with another organization
that intrigues me.
As for recommended skills, I have experience working in a very similar
capacity. I have a firm grasp over version control using git and I'm a
Python programmer as well. I also have a Linux machine and have setup
development environments for projects such as this before.
I'd like to know if my skills make me a good candidate and whether there's
other key capabilites that would be worth mentioning and building. I'd also
like to get my proposal reviewed. Hoping to hear from you soon.
Noor Binte Amir,
What is the preferred style for the documentation? I noticed that in some part of the documentation, there exists contractions and the documentation is written informally.
Is there a template or specific guidelines for writing documentation? If not, can I propose a new template so that further documentation can be created coherently?
Upon searching more regarding various models in the Gnu Mailman, I learned that technically first a "User" entity is created and then a "Member" entity can be created in correspondence to a "Mailing-List" entity. For example
>harry_member = mlist.subscribe(harry_user)
This, however, is totally different to the subscribe function given in the mailmanclient doc, where you actually do:
>harry_member = mlist.subscribe(harry_email,harry_display_name,pre_verified...)
Why is this behaviour desired?
Pointers on this would be appreciated
Upon searching for various models in the docs of GNU Mailman ( One which is on ReadTheDocs ), I entered a query "Users" which gave me the result .
The problem is that the links to the pages which the search yielded, gave 404.
This behaviour is rather peculiar and if it is reproducible in other machines ( other browsers specifically ), then it is either problem with our docs or with ReadTheDocs as a whole.
It was an observation worth noticing and pondering about hence I created this thread.
If this behaviour is expected or not reproducible or there is something I am missing here, then kindly provide some more pointers on this.
 : https://mailman.readthedocs.io/en/release-3.0/search.html?q=Users&check_key…
On Fri, Mar 15, 2019 at 10:19 AM Jonas Smedegaard <dr(a)jones.dk> wrote:
> Quoting Christian Ehrhardt (2019-03-15 06:39:08)
> > On Fri, Mar 15, 2019 at 12:08 AM Abhilash Raj <maxking(a)asynchronous.in> wrote:
> > > On Thu, Mar 14, 2019, at 1:42 PM, Jonas Meurer wrote:
> > > Christian Ehrhardt:
> > > > I was evaluating the Dependencies of mailman3 in Ubuntu and I was
> > > > wondering if I could cut them down a bit. One thing that got my
> > > > attention is the dependency from mailman3-web  to nodejs for
> > > > less  and ruby-sass .
> > > >
> > > > I was wondering if we could by default not install
> > > > node-less/ruby-sass and what exactly that would imply.
> less is a reinvention of sass: It is often adaptable to sass with a
> simple patch.
> Original sass processor was ruby-sass, but nowadays a better processor
> is sassc. Or if you want to integrated processing with Python then
> python3-libsass which uses same core library for its processing.
> I have not looked closely on mailman3, but I highly doubt there is a
> real need for dynamic processing of less/sass during runtime.
Yeah I doubt that as well.
In the meantime I also found  which seems to have come to the same
conclusion for the majority of default setups.
For upstream to disable it by default it was mentioned that there is a
need for a customize kit which seems fine .
There is a further argument to disable the live compressors, at least
as I read COMPRESS_OFFLINE that seems helpful for production setups
anyway to speed up and safe CPU load.
So while upstream waits until a "customize kit" exists to switch
defaults, as a downstream like Debian/Ubuntu I wonder if we already
- drop sass/less compilers to a suggest
- disable the live compression in the default config that we ship
- keep the config commented-out to make it easy for admins that want
to enable it later
- pre-compress at build time and enable compress_offline for speed
- maybe call `django_admin compress`  or similar at build time?
- having sass/less as build dependencies seems much safer than
pulling it in at runtime
@Jonas M.: what do you think about  (again maybe after Buster)?
Sorry to not know more of this yet, but I hope suggesting what I think
might work helps to get us the right way.
> - Jonas
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136 Website: http://dr.jones.dk/
> [x] quote me freely [ ] ask before reusing [ ] keep private
> -----BEGIN PGP SIGNATURE-----
> -----END PGP SIGNATURE-----
Software Engineer, Ubuntu Server
I am Ayush Goel, an undergraduate student at IIIT Delhi and am interested
in working with GNU Mailman for the Google Season of Docs 19. Currently, I
have already joined the mailing list and am setting up Mailman on my Linux
machine(will reach out at the mailing list if I encounter any problem).
Please guide me on how to proceed further with the application. Looking
forward to hearing from you!
I went through the project ideas page of the GNU Mailman's page for GSoD'19
thoroughly and am interested in working on improving the Developers'
Documentation for Postorius and Hyperkitty. I also went through the
responsibilities mentioned by Steve and have few doubts.
1) Is there any user guide/support page on how to use the mailing list
explaining all the features of Postorius and Hyperkitty? For example, how
to manage subscription, how to manage lists. what does activity summary
means, what does the graph represents, what do the different roles
represent, what is the difference between an owner, a moderator and a
Being new to mailing list, I feel that people may face these issues and
having a proper documentation on how to properly utilize the platform will
be a great win.
2) During my GSoC days, I failed several issues while setting up the
project locally on my machine. It became very difficult to test everything
from end to end. And I feel that there should be documentation on how to
test the complete application from end to end. For example, I faced
difficulty in configuring Mailman to Hyperkitty or how to inject a mail to
a thread in Mailman3 and had to go through many discussions to get it
running. It took many days to get everything running on the web interface.
I feel that we should go through the mail archives of last few years GSoC
season and should work on those areas where most of the developers felt
Let me know your inputs.
I am a fellow GSoC contributor here and as part of my process to write blog posts. I have written 2 blog posts until now in my blog. Since not much has been started for the organization's work, I have mostly focused on the GSoC period, what GSoC is, the how-tos and the tips for getting accepted. The comments part I am working right now. If it is not fixed by the time you see the post, please critique the post here ( but not too much as I do not want to spam this mailing list ). I will be writing further posts regarding my involvement in this organization and how I plan to subsequently execute my proposal.