Mailman 3 June 2019 - Mailman-Developers

Bounce processing should be done to only USER entities?
by Aaryan Bhagat 20 Jun '19

20 Jun '19

This is with reference to a discussion in a thread [1] here: I need two requirements : - I need an object of a user which has an attribute which tells us what are all the emails of the following user. - I need an object of an email having an attribute which tells us what mailing-lists that email has been subscribed to. For the first one, we already have a User model each object of which is mapped to more than one Address objects For the second one, we technically have the Address class but it does not contain the details as to which lists email has subscribed. What we do know is an object of Member class is created when we subscribe. Pointers on the above would be helpful I can do the following, Create a many-to-one relationship between Member and Address Variables for processing bounces including CURRENT_BOUNCE_SCORE and CROSSED_OR_NOT will be in the Member object MODIFIED_THRESHOLD variables will be in Address model ( Please refer to my proposal[2] under the "Approach and Detailed Explanation" Section if the above seems foreign to you ) Is the following approach plausible or am I missing something here? [1]:https://mail.python.org/archives/list/mailman-developers@python.org/thre… [2]:https://docs.google.com/document/d/1Pv-EuIwrhKM-_inf2HMHVgVzRKjEUwRl-_fl…

5 28

Problems with Migration from Mailman 2 to Mailman 3
by ariessa.norramli＠gmail.com 15 Jun '19

15 Jun '19

Hello everyone. 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 Thank you. Best Regards, Ariessa

1 0

Google Season of Docs
by Noor Binte Amir 13 Jun '19

13 Jun '19

Hi! 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. Regards, Noor Binte Amir, NUST H-12

2 1

Questions Regarding the Mailman Documentation's Style
by ariessa.norramli＠gmail.com 12 Jun '19

12 Jun '19

Hello everyone, 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? Thank you. Best Regards, Ariessa

3 4

Subscribing members to list through 2 different methods?
by Aaryan Bhagat 12 Jun '19

12 Jun '19

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

3 9

Possible Bug in the Docs of GNU Mailman?
by Aaryan Bhagat 11 Jun '19

11 Jun '19

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 [1]. 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. [1] : https://mailman.readthedocs.io/en/release-3.0/search.html?q=Users&check_key…

4 7

Re: How strict are the dependencies on the django-compressor related backends?
by Christian Ehrhardt 11 Jun '19

11 Jun '19

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 [1] to nodejs for > > > > less [2] and ruby-sass [3]. > > > > > > > > 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 [1] 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 [1]. 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 could: - 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` [3][4] 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 [2] (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. [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2]: https://salsa.debian.org/paelzer-guest/mailman-suite/commits/make-sass-less… [3]: https://django-compressor.readthedocs.io/en/latest/usage/#offline-compressi… [4]: https://gitlab.com/mailman/django-mailman3/issues/17#note_81807465 > - 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----- > > iQIzBAABCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlyLbfwACgkQLHwxRsGg > ASHlqw//Vkkke6aulFYeLkq7vQOIt08j+DMMDBpJ/vXapwtQJ2WbWEYsHbbFv75v > k80SILudsOyGMwQ0HKRGqDmhJw2Voi9mWoV2fBQeCQn5w/G9N2Ddw8hAMrzGsLxO > C2FOV8Db0irJ6FS6AO0YQpAselKnnX387AvyWBCpVcWWuydf46pMkPpYajVJTvZg > UZxtBh1epmv/VdQlw2OeLrV+bZJWfjULjr1qFPYdqFnEUnOA2cC44RMagxSV7kNh > JmCc7DvL/VjX/dkPHJCW/VvRrvfxzOR4bimVr7BeuvcjNljlUnKhRwP+PQZt80gp > CbOoVCeEOFJuHwqTlvasUpxo/aSZZPFeF8aQBtdyzefEx9QjjGwx8bYQFn+Zo0CX > TVsB7qWyCwMZIR0DP5+A8ityXQb+FwOTXjySMzO+Z/rA9+h1PHZrK+WJMB0O9z5r > hWYDk3jGSJIkwL+AemE06gUPuSaXZWhzoduI2Mbzs8a20qhrW08Ij338RVGalyhC > QHJT4JoI3bXylaK+IEpH9xxUEW0i8gOge32dBFiqg9/dGFm06Tf3z8dUuBFyXgG3 > BsNJaO6Cn3ghfNS/OfNN04nPS+luPqPQ1r9yZMztrIqwv8oOWyVj1YQpKW1vRN/v > BK/2IpBA+6O3OE2X4RCW8pouwPmsSgMmXpIsuFE61dox/8tOPmE= > =490O > -----END PGP SIGNATURE----- -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd

3 4

Proposal for GSoD'19
by ADITI GUPTA 09 Jun '19

09 Jun '19

Hello, I have created my proposal for GSoD'19. It would be really helpful if you can go through it and provide your feedback. ( https://docs.google.com/document/d/1H-h2_TFDAl_o8c0WeT60OkeZedcDicGIPripaVM… ) Also, I found a small typo error/ spelling mistake in the documentation. The word relevant is spelled wrong. https://postorius.readthedocs.io/en/latest/development.html#view-authorizat… Thank You, Aditi ᐧ

3 6

Season of docs' 19
by Ayush Goel 06 Jun '19

06 Jun '19

Hey! 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! Yours sincerely Ayush Goel IIIT-Delhi

4 4

Season of docs' 19 Doubts
by ADITI GUPTA 05 Jun '19

05 Jun '19

Hello, 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 member. 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 difficulty. Let me know your inputs. Thanks, Aditi ᐧ

3 3