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!
Hi, i'm Ali İlteriş Keskin. I'm developer and student from Turkey. I have
been using GNU/Linux for more than 4 years. I write Python, Django, Flask
I want to work with you in Google Docs Season 2019. I would be very happy
if you accept me.
Ali İlteriş Keskin
Dear Mailman Developers,
I hope this message finds you well. I was looking over the Mailman Season
of Docs page, and I am very interested in contributing as a technical
I'm a journalist turned into a Full-Stack Developer. I love to write and
code, and I have written several technical and non-technical articles over
I'd love this opportunity to contribute as a technical writer at Mailman.
As a front-end focused developer, I would love to work on Postorius, the
Mailman’s web frontend.
Looking forward to hearing from you.
I'm porting a mailman installation from a legacy server into docker.
To make it not more complicated I decided to stay on the same mailman
version 2.1.29 (build from source)
Now I'm faced to the problem that mailman is started with "mailmanctl start"
This fork a daemon running in background. In an ideal docker world
there is only one process per container.
If the process return/end, the container terminate.
For now I solved this by running "fghack mailmanctl start"
fghack -> https://cr.yp.to/daemontools/fghack.html
Q1: is there a better way to start mailman in some kind of non forking mode?
Q2: is it possible to run mailman3 supervised?
So I was scrolling down the GSoD page of the org and found out that a major link important for GSoD folks under the "Writing Your Application" section is giving 404.
I am copy pasting the line here
>The [[https://developers.google.com/season-of-docs/docs/|Introduction to Season of Docs page] is the place to start.
Check it yourself.
P.S -- If someone wants to change something in these wiki pages, how to do that formally, any pointers on this will be helpful
As mentioned in my proposal I will create new variables and modify the schema of how we save things in the database.
Here I am facing issues (most probably because I am a newbie in SQL Alchemy). I am not able to understand how to exactly implement this.
Relevant searches in the docs provided nothing substantial ( If there is then provide the appropriate link in the reply )
If there is not then GSoD guys take note, we can have a doc page on how to modify database if the admin wants to according to its needs( although it is highly rare for someone to do that so not that much priority upon this ).