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'm Ariessa Norramli, a 2nd year student in Software Engineering and
freelance writer. Before I started college, I did a number of freelancing
jobs on Upwork. I've written for diverse topics such as finance,
technology, pop culture, weddings, and cryptocurrency.
I'm interested in working on the Mailman documentation for GSOD because I
love writing and programming. I taught myself coding at the age of 15. My
syntax. So having the opportunity to combine both of my passion is
definitely something that I'd love to try.
As of now, I own a website <https://bitsized.me/> and personal blog
I am really looking forward to hearing from you. Thank you in advance.
Postorius, as you all know, is the Web UI for Mailman 3 and is based
on Django Web Framework. For some time now, we have been using
VCRPy, a HTTP Stubbing library to record test interactions with
Mailman Core' API so that the code can be tested in CI environments
with the need to have Core.
However, in the past, we have observed that it creates more problems
than it solves. First, we test against the state of Mailman Core in past,
since the interactions are recorded once and replayed all the time.
There are tapes dating back years, which could in theory have
changed (though, API's backward compatibility guarantees avoids
breaking changes to happen without notice, but even with notice,
tests would continue to pass).
Other problem is that it creates friction when writing tests, which
was the biggest pain point for myself. You have to write tests, record
tapes and then make sure that you keep re-recording till the tests
pass. It is not easy to explain to early stage developers either.
Pytest is a new test runner and is pretty popular these days. I decided
to use it mostly due to strong support for fixtures and plugins. I wrote
a new fixture to make sure that Core's API is started before tests start
and all data is erased before each test class.
The changes are in this MR.
I am also working on moving Core's tests to use pytest instead of
nose2,but that process is going to be longer since I am going to
have to rewrite some of the nose2 plugins we use there. Doctests
also need some attention. Here is the WIP MR for that.
Abhilash Raj (maxking)
I would like to propose (if not already there) an idea/feature regarding
your mailing web app as a part of GSoC. Since it runs on python I would
like to integrate NLP text summarisation using the nltk library.
Sometimes when people are on the go they wouldn't want to read the whole
email and maybe just summarise the relevant parts. This feature allows them
to do that with a click of a button and see the result as a pop up or
I hope my idea has been conveyed properly. Let me know if it can be
integrated into your web app and also whether I should add it as a proposal
for GSoC selection process.
Kurian Thomas Pulimoottil
I am a beginner to GSoC and I want to contribute to your amazing
organisation. I have read all the docs surrounding how to setup the
development environment and have a fair idea on what to do.
I had a few questions I wanted to ask
1)If I have a unique idea to implement do I send it to a specific email
address or add it as my proposal for GSoC?
2)In order to work on one sub project is is necessary to install the whole
thing? If not how may I go about working on just the subproject?
Kurian Thomas pulimoottil
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
First of all, I apologize for not being active in the Gitlab codebase and only on the mailing-lists. This is because my semester is ending and had a lot of tests, moreover I was focusing only on my proposal and its related work. Fornutaley, that is not a problem anymore. I do not have any other commitments this summer and my timeline in the proposal explains it all.
Here is the full proposal.
I have given commenting rights
Abhilash it has some comments made by you which I had replied extensively and made the appropriate changes. If you find the time, please resolve them if you find them fine.
I have been working this past weekend trying to change some UI elements
of Hyperkitty to make it a bit more cleaner, easier to read quoted emails and
make unread posts more visible than they were before.
As a test bed, I have deployed my changes to lists.mailman3.org. A complete
summary of changes is available in my MR on Gitlab.
I would appreciate some feedback from users to make sure that is is a step in
the right direction.
Since it has been a long long time since I ever designed a UI, I would also
really appreciate if there people who want to work with me on fixing some
of the UX issues in Hyperkitty.
Summary of Changes:
- The grey background for the email headers are removed.
- Gravatars are now round in shape instead of square.
- Links to permalink of the message and fixed-font button has been moved to the
bottom to remove clutter from the top of the message.
- The date format is changed to remove the Day of the week and uses 3 letter
month names for minimalism.
- Right sidebar is now fixed and doesn't scroll with the page.
- All buttons on the bottom of the email now have a hover property that changes
their background on mouse hover.
- Quoted part of the email now has a different background. Each level of
quoting gets a different background till 3-levels of indentation. After,
which we don't process more quoted text.
- Unread threads show a blue bar on the left side as a more prominent indication
as compared to current envelope icon.
Feel free to reply here or just comment on MR in Gitlab.
Abhilash Raj (maxking)