[Mailman-Developers] Re: Logging
On Thu, Jan 7, 2021, at 8:13 PM, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > There are a couple of loggers the Mailman Core uses and you can set > > their logging path to be `/dev/stdout` to log to standard output > > which I think your container manager should be able to > > grab. Unfortunately, there isn't a way yet to change all of their > > "path" using a single config, so you'd have to do it individually > > for each of them. > > GSoC 2021? Yeah, we could couple this with some other changes in Core to get to a sizeable level project for GSoC. > > -- thanks, Abhilash Raj (maxking) ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] GSoC 2021 org applications
Abhilash Raj writes: > On Mon, Jan 4, 2021, at 12:49 PM, Terri Oda wrote: > > Happy new year everyone! > > Happy new year to you too Terri! And Happy New Year to everyone, as best we can. > > I'm starting to prep Python for GSoC 2021, and I wanted to issue > > the usual invitation that we'd be happy to have Mailman as a > > sub-org if anyone wants to do GSoC this year. (Mailman's been > > fine as a separate org, but I have to do the paperwork for Python > > anyhow so I figured I'd offer if there's interest but no one > > wants to cover the admin side of things.) Thank you very much! Depending on how many students we get, I'm probably available as an emergency/backup mentor for Python. > Thanks for the head start, I do want us to participate this year > and am planning to mentor at least one student. I am also planning to participate. I wonder if there will be an in-person Mentor Summit; if so, I'd like to attend and do some networking. I'm only a couple of years from retirement from the university and likely conversion to full-time software developer (including Mailman, of course, but I have a bunch of ideas and postponed projects). If we go the separate application route, I'm willing to do the org admin part. I have to get grades in by Jan 18th, and after that I'll be in good shape to work several hours/week on org and/or idea proposals. Terri, in the past you've allowed rejected orgs to apply as Python suborgs. Did that work out ok? Do you expect to have that policy again this year? Steve ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Logging
On Thu, Jan 7, 2021, at 1:27 PM, costavitor...@gmail.com wrote: > Hi > > Is it possible to log to console? > > I've changed gunicorn configuration: > accesslog='-' > errorlog='-' Which file did you change to apply these configurations? > > Then logs are not written to log files, but I can't see what's being logged. > > I'm on a docker environment and having log files it's something that I > want to avoid to control disk usage. > And I'm capturing what's shown in console, so it was great if I could > log into console. There are a couple of loggers the Mailman Core uses and you can set their logging path to be `/dev/stdout` to log to standard output which I think your container manager should be able to grab. Unfortunately, there isn't a way yet to change all of their "path" using a single config, so you'd have to do it individually for each of them. The available loggers are: # - archiver-- All archiver output # - bounce -- All bounce processing logs go here # - config -- Configuration issues # - database-- Database logging (SQLAlchemy and Alembic) # - debug -- Only used for development # - error -- All exceptions go to this log # - fromusenet -- Information related to the Usenet to Mailman gateway # - http-- Internal wsgi-based web interface # - locks -- Lock state changes # - mischief-- Various types of hostile activity # - plugins -- Plugin logs # - runner -- Runner process start/stops # - smtp-- SMTP activity # - subscribe -- Information about leaves/joins # - vette -- Message vetting information And you can set their logging path by adding the following (for example) to your mailman.cfg [logging.archiver] path: /dev/stdout Same goes for the rest of the loggers. Hope this is helpful! -- thanks, Abhilash Raj (maxking) ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: GSoC 2021 ideas
On Mon, Jan 4, 2021, at 12:49 PM, Terri Oda wrote: > Happy new year everyone! Happy new year to you too Terri! > > I'm starting to prep Python for GSoC 2021, and I wanted to issue the > usual invitation that we'd be happy to have Mailman as a sub-org if > anyone wants to do GSoC this year. (Mailman's been fine as a separate > org, but I have to do the paperwork for Python anyhow so I figured I'd > offer if there's interest but no one wants to cover the admin side of > things.) Thanks for the head start, I do want us to participate this year and am planning to mentor atleast one student. > Also, I have two mailman related ideas! > > 1. Seamless archive converter for 2.1 -> 3.* > > A friend was grousing that there was no "nice" way to retain old archive > urls without keeping a static copy of things, and it got me to thinking > that it would definitely be possible to build something that handled the > old urls and redirected or made them work seamlessly, but we didn't do > it because parsing the old archives basically requires you to scrape > them because otherwise we couldn't guarantee that the urls would be > stable from a re-parsed mbox. > > It's boring and finicky web scraping work to associate the old url and > do the right things to make it work seamlessly in hyperkitty, but > probably not too hard, so I was thinking that it might be suitable for a > GSoC student. This sounds like a very nice idea! How are you thinking of associating the web URLs (basically, number of the page I guess?) to Email entries in Hyperkitty since I don't see the web pages having Message-ID. > > 2. Old mailman "skin" for postorius > > Make mailman look like the 2.1 interface for people who really love the > old system. There's a few options that would be different, but the > goal would be to make it pretty much look the same only with a few > options changed, for people who are very change adverse. We had > intended for it to be *possible* to reskin Postorius, but I don't think > too many people have done it, so this would be a test to see how doable > that is and probably fix any underlying issues that make reskinning the > interface hard. Honestly, we could also have a student do a brand new > skin if we had someone who loved UI design, but I suspect replicating > the old interface would be less work, and since this year's GSoC hours > have been cut in half, i'd rather start with something easier. Is this intended to be like a CSS refresh or like re-write the interface kind of project? I am thinking it might be more of the former than latter, which might be a much bigger project. > I've been out of mailman dev for 3 years, so I'm probably not the ideal > mentor, but I'm up for helping on either of those if Mailman as a whole > is interested in doing the GSoC thing this year. Another idea that I've been thinking is supporting User management in Postorius. It would list all registered Users in Django & Core along with their Addresses and perhaps Subscriptions. If time permits, allow doing some actions on user's behalf like adding a new address, verifying a new address, deleting the User and all their subscriptions etc. -- thanks, Abhilash Raj (maxking) ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Logging
Hi Is it possible to log to console? I've changed gunicorn configuration: accesslog='-' errorlog='-' Then logs are not written to log files, but I can't see what's being logged. I'm on a docker environment and having log files it's something that I want to avoid to control disk usage. And I'm capturing what's shown in console, so it was great if I could log into console. Kind regards Emanuel ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
