Re: [Mailman-Developers] Willing to contribute to GitLab/development tools integration project in GSoC

翁学平 writes: > But one thing is that I receive the response too late, so I have > not enough time to contribute to the mailman before the GSoC > applying deadline. So can I learn the project deeply and do some > extra contribution after the proposal submission deadline? You can contribute on

Re: [Mailman-Developers] Correcting the display name in the recipient address

Simon Hanna writes: > >The concern is that a post as archived and delivered to list members > >should have nothing in it's headers (including things like From:, > >Received:, Message-ID, etc.) that identify the poster or the poster's > >domain. > I don't know that much about email, but

[Mailman-Developers] Interest in "Implement module to process ARC headers" project GSoc

nitish salwan writes: > I am interested in ARC headers project and want to discuss about it. I'm sorry, but for the last 30 hours of submission period I've mostly either been asleep or busy with graduation ceremonies at my university, and haven't been able to address anything in GSoC except

Re: [Mailman-Developers] GSoC Project: pgp plugin

Jonas writes: > I would release the proposal on the project blog > cryptolists.github.io after the proposal deadline has passed. Is > there any reason not to? Privacy of proposals is entirely the student's choice. Legally, neither Google nor Mailman makes any claim to your proposal, except

Re: [Mailman-Developers] Correcting the display name in the recipient address

Aditya Divekar writes: > The case we handled was regarding the welcome message. The display name > property of the address was not actually changed. So if the user has not > supplied a display name for the address, the display name will remain empty > in that case. Only the welcome message

[Mailman-Developers] Willing to contribute to GitLab/development tools integration project in GSoC

翁学平 writes: > I have sent this email for serval days before, but have not received any > response for this, I sent a response, addressed to you and to the list, so you should have received two copies. Try your spam folder. Here it is again: For project details, you should check the archives

Re: [Mailman-Developers] Willing to contribute to GitLab/development tools integration project in GSoC

Mark Sapiro writes: > On 03/24/2016 11:38 AM, Stephen J. Turnbull wrote: > > 翁学平 writes: > > > > > I have sent this email for serval days before, but have not received any > > > response for this, > > > > I sent a response, addressed to

Re: [Mailman-Developers] Correcting the display name in the recipient address

BTW I made a few more comments on your proposal (after you finalized). I'm told you are allowed to revise the final copy until the deadline, it's just that we can't see it until then. I think it's basically in good shape. Aditya Divekar writes: > So according to what I've gathered from the

[Mailman-Developers] Willing to contribute to GitLab/development tools integration project in GSoC

翁学平 writes: > I have sent this email for serval days before, but have not received any > response for this, I sent a response, addressed to you and to the list, so you should have received two copies. Try your spam folder. Here it is again: For project details, you should check the archives

[Mailman-Developers] REVIEW NEEDED: Mailman and Discourse Integration

Ojas Shirekar writes: > I have officially submitted a proposal for GSoC for this feature as > this is something I really found interesting and felt like doing. > Please take a look and do let me know OK, it's visible under the Mailman project. I only had time to make a couple of comments,

[Mailman-Developers] GitLab/development tools integration GSoC Participaring

Nosikov Konstantin writes: > Hello, I am from Russia, Saints Petersbutg, ITMO University > I am interested in Mailman project Welcome! > GitLab/development tools integration > What do I need to do to get started? Is there any special points in > proposal to be mentioned? I'm not going to

Re: [Mailman-Developers] Correcting the display name in the recipient address

Barry Warsaw writes: > On Mar 20, 2016, at 08:15 PM, Mark Sapiro wrote: > >I wonder if we aren't over thinking here. Maybe I didn't associate a > >display name with my user record and my alternate address on purpose for > >my own reasons. Maybe when I subscribe my alternate address to some >

[Mailman-Developers] Interested in GSoC [subject changed]

Abhinav Mishra writes: > Hi,I am a third year Engineering student and had been working on > django and python for almost 3 years. My biggest project is > developing a hospital web application which is funded by my > college. I would like to know the Details of [the Preset list > settings

[Mailman-Developers] ProtonMail opens encrypted mail service to public

... according to Tech Republic. Haven't read the article, but maybe this is a reason to support signed/encrypted lists project(s). Steve ___ Mailman-Developers mailing list Mailman-Developers@python.org

[Mailman-Developers] GSOC 2016 - Project Proposal

Aayush Maini writes: Welcome! > The basic proposal goes along viz. "Making the services offered by > the Postorius available via a browser extension/plugin". I thought > it would be nice to have the functionality offered by the Postorius > clubbed into a user friendly browser plugin. > >

Re: [Mailman-Developers] New lists at lists.mailman3.org

Odhiambo Washington writes: > Thanks, Florian, but why should I go that way when there is a link to sign > in with google, which I already have? Because the mailman3.org system is in beta (to be generous). Google sign-in is "supposed" to work, but doesn't. Try going through Persona with your

Re: [Mailman-Developers] GSoC Project: pgp plugin

Abhilash Raj writes: Thanks for picking this up, Abhilash! Jonas writes: > > However, at the moment I'm in the middle of writing my Project Proposal. > > May I send you a draft along with personal questions? If you mean do I like cats, I don't see what that has to do with GSoC. ;-) If you

Re: [Mailman-Developers] New lists at lists.mailman3.org

Barry Warsaw writes: > I noticed some weirdness and crashes in Postorius and will submit bugs as > appropriate. Bugs go where? That is, these could be Postorius bugs or just kinks in Mark's configuration so far (ok, crashes == uncaught Exceptions, I hope?! aren't configuration bugs, they're

Re: [Mailman-Developers] adding to REST

treal tv writes: > I hadn't considered this yet. I had planned to help with patches so > yeah, I think i'll be rebuilding from the repo! Thanks, I hadn't > even thought about that yet. I think the way to think about it is that bundler is a system for distributing a "turnkey" Mailman

[Mailman-Developers] TLS/SMTP AUTH in MM3? [was: Mailman without localhost ?]

Redirected from -users. I have nothing to add to what Mark wrote there. Mark Sapiro writes: > These are for outgoing mail from Mailman only. They have nothing to do > with delivery of mail TO mailman. You can tell Mailman to connect to any > SMTP server and port by setting SMTPHOST to the

Re: [Mailman-Developers] Basic workflow of the ARC implementation

Aditya Divekar writes: > Yes, in that case the arc verification would need to be postponed to after > the entire code for the header generation has been written. I'll need to > rethink the milestones a bit, since this testing part would have to be > added at the end, and things will change

Re: [Mailman-Developers] Basic workflow of the ARC implementation

Aditya Divekar writes: > > > 4. ARC Authentication Result - arc verification code completed. tests > > > passed. merge request created. > > > > How do you propose to create tests for #4? > > > > > Here, we could consider a few scenarios- > 1. A message is passed to the function which

Re: [Mailman-Developers] Need more information about the GSoC idea 'GitLab/development tools integration'

Mark Sapiro writes: > The definitive reference on threading is > There's also RFC 5256, based on Jamie's page, which defines threading in the context of IMAP, and gives a concise account of the algorithm. ___

Re: [Mailman-Developers] Patch for HyperArch

Mark Sapiro writes: > On 03/12/2016 08:23 AM, Stephen J. Turnbull wrote: > > Mark Sapiro writes: > > > > > The Received: header check is important. For an "imported" mbox, the > > > From_ separators may reflect when the mbox was exported from

Re: [Mailman-Developers] Basic workflow of the ARC implementation

Aditya Divekar writes: > Depending on the message, if it has previous Authentication Results added > as a header, that can be extracted too. The entire message can be parsed, > and then all the possible headers involved in the authentication process, > ie. DKIM signature, Authentication

Re: [Mailman-Developers] Patch for HyperArch

Mark Sapiro writes: > The Received: header check is important. For an "imported" mbox, the > From_ separators may reflect when the mbox was exported from it's source > rather than the message date. If the messages have Received: headers, > the later ones at least tend to have good dates.

Re: [Mailman-Developers] Help regarding an error during installation

Abhilash Raj writes: > On 03/10/2016 07:18 AM, Daman Singh wrote: > > When i run buildout command i get an error saying,"no module > > named 'zlib'" but on running ipython, when i import zlib it works > > all right. > > When running buildout in mailman-bundler, it generally creates a >

Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .

Harshit Bansal writes: > Basically, a style will be having three levels of viewability: > 1: System wide : A style having this level of viewability will be > visible to all the domains as well as the lists. It will be available > to all the list owners for copying however the site owners will

Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .

Harshit Bansal writes: > I think the "Permissions Systems" would have nothing to do with the > core. It would be related to Postorius. We will have to create a style > model separately in Postorius which would store the style name and the > user who created it. Then only the user who has

[Mailman-Developers] Mailman3- postorius_standalone Issues

Fotso Fono writes: > Hello, i am trying to set up Mailman3 everything has been moving on > well. i ran the command "python manage.py runserver" in > postorius_stanalone. when i access localhost:8000 and error pops on > the terminal saying "no module middleware found" and an error page > is

Re: [Mailman-Developers] Mailman-bundler installation

Simon Hanna writes: > Mailman-bundler is for production setups and to just try it out. So? Of course he has to have a checkout to participate in development, but given that we don't have a migration story yet, and bundler keeps throwing errors for people, I don't see why developers shouldn't

[Mailman-Developers] Pastebin considered "suboptimal" [was: Mailman-bundler installation]

Daman Singh writes: > Here is a small suggestion, instead of pasting terminal text here you > should consider using pastebin. -1. Pastebin goes away, making the post useless to anybody who experiences the same problem in the future. Even while it lasts, it mean you have to search the whole

Re: [Mailman-Developers] Mailman 3 on lists.mailman3.org

Mark Sapiro writes: > On 03/06/2016 09:37 AM, Barry Warsaw wrote: > > On Mar 05, 2016, at 04:14 PM, Mark Sapiro wrote: > > > >> The issue is that there is an MX record for mailman3.org pointing to > >> mail.mailman3.org, but mail.mailman3.org doesn't have an A record; it > >> has a CNAME

Re: [Mailman-Developers] CAPTCHA support

Barry Warsaw writes: > I'll be honest, I really hate captchas. I do too, and will not work on adding them. But they're a frequent RFE (or were at one time), and with Google oomph behind reCAPTCHA, I wouldn't be surprised if they rise in popularity again. And they don't violate any RFCs. If

Re: [Mailman-Developers] CAPTCHA support

Barry Warsaw writes: > Great idea. The core already had a 'ui' tag but I renamed that 'usability'. > I also added an 'accessibility' tag, Ah, you're right -- spelling usability as "ui" or "ux" would be an "ax" barrier to everybody but us chickens, er, core devs. +1 for usability and

Re: [Mailman-Developers] CAPTCHA support

David Andrews writes: > Some audio CAPTCHA's are ok, some are virtually impossible to > decipher. Also, audio CAPTCHAs do not work at all for deaf-blind > persons. Thanks for going on record! > So, while it depends, audio CAPTCHA is a mixed experience at best, > and impossible at worst.

[Mailman-Developers] Basic workflow of the ARC implementation

Aditya Divekar writes: > We need to generate a private and a public key for the signing purposes. > For testing purposes, and while working on the code, I can probably > generate the keys locally using the openssl tool. In production, these keys are a *site* resource. I see no reason why we

Re: [Mailman-Developers] CAPTCHA support

Christian Schoepplein writes: > On Sat, 5 Mar 2016 12:08:38 > About captchas. If they are implemented, they > would have to be > > optional in my opinion as they would > > require signing up for a token with the captcha provider. > > Yes, if captchas really have to be implemented,

[Mailman-Developers] CAPTCHA support

Aditya Divekar writes: > But with the new recaptcha, I would like to know if the stand is > the same. ReCAPTCHA looks very good, though I haven't used it. However, the professional spammers are quite capable of hiring humans to do their work, and even conceal it as being charitable work

[Mailman-Developers] Congratulations to us! We're officially in GSoC again!

... especially to Florian, who seems to be on his way to becoming MGOAFL (Mailman GSoC Org Admin For Life)[1]. And of course Barry (who has a real -FL title!), and the mentors. All that goes without saying, sort of, but I'd also like to mention all the folks who have been following this list and

Re: [Mailman-Developers] About working on Issue #67

Barry Warsaw writes: > It's true that the bulk of the translation work project-wide will be for > Postorius and Hyperkitty. Both of those are Django projects, and I'm sure > Django has i18n support, although I really don't know much about those > details. The OP is already aware of Django's

Re: [Mailman-Developers] About working on Issue #67

Saurav Kumar writes: > No it wasn't for GSoC, OK, good! Then you can work on this without time pressure. > i just wanted to do something in opensource and this issue caught > my attention as it was labelled as "beginner friendly" . I went > through the links attached and felt that i can do

[Mailman-Developers] About working on Issue #67

I'm certainly happy to see somebody interested in working on this! However, I have some questions about exactly what the development strategy should be (see my comment on #67). We should talk about it on this list so everybody sees it, then move to #67 (or wherever) when the strategic issues are

Re: [Mailman-Developers] Regexp filtering

Adam McGreggor writes: > Or could we meet user expectations (real users, not geeks), [and > allow glob syntax]. Definitely worth discussing, but my initial reaction is negative for the reasons discussed below. > Simples: > *@mail.ru > *@*mail.ru > ?@mail.ru Are those

Re: [Mailman-Developers] Regexp filtering

Barry Warsaw writes: > On Mar 01, 2016, at 04:37 AM, Stephen J. Turnbull wrote: > >Or we could continue to have the core representation be "leading '^' > >iff regexp", and once again have Postorius prepend "^.*" or whatever. > > In which case, the co

Re: [Mailman-Developers] GSoC Project: pgp plugin

Jonas writes: > On 28.02.2016 10:30, Stephen J. Turnbull wrote: > > End-to-end encryption or signature or both seems to be the right > > thing. > > The concept of a mailserver doesn't allow real end-to-end encryption if > each recipient uses a different keypair.

Re: [Mailman-Developers] Regexp filtering

Barry Warsaw writes: > IBan would need to have a flag which indicate whether the `email` > is a literal address or a pattern. I don't think it's worth having > two separate interfaces/models, but we might want to rename `email` > to something more generic (`pattern` would be fine, with the

Re: [Mailman-Developers] ARC module implementation [was: GSOC 2016]

[Aside @Barry: what's the current state of DMARC handling in Mailman 3? (I assume below that there isn't any yet.) I guess porting some or all of the Mailman 2 facilities be a good GSoC project?] Please keep GSoC traffic on Mailman-Developers. Other developers have need-to-know, as do other

[Mailman-Developers] GSoC Project: pgp plugin

Jonas writes: > The Project Idea: > Encrypted malinglists have been been a much-requested feature in mailman > 2 and I would like to run some encrypted mailinglists myself. I see Abhilash has already mentioned that he has done some work on crypto (PGP) in Mailman 3. I'll let him explain

Re: [Mailman-Developers] [Mailman-Users] Help with installation

Ibrahim Jarif writes: > https://hyperkitty.readthedocs.org/en/latest/development.html was > written for older version of Django (I guess Django-1.6). I first used HK with Django 1.5 I think. HK docs potentially go way back in Django history, and I know we've had backward compatibility issues

Re: [Mailman-Developers] Regexp filtering

Mark Sapiro writes: > I agree it's confusing, and I've been caught in this confusion myself > and neglected to put the leading ^ in what I clearly intended to be a > regexp, but the convention goes back a long way in MM2. Oh, of course I'm -1 on changing "regexps start with '^'" convention in

Re: [Mailman-Developers] [Mailman-Users] Help with installation

First, please make sure you direct replies to the list. If you don't understand why that is appropriate, read Eric Raymond's "How to Ask Questions the Smart Way" (www.catb.org/esr/faqs/smart-questions.html). Redirecting to list is not automatic because we occasionally handle sensitive topics in

[Mailman-Developers] GSoC'16 Contribution

Ibrahim Jarif writes: > I'm Ibrahim Jarif. I'm studying computer engineering (3rd year). I wish to > apply for GSoC'16 with the mailman Project. Welcome! > I'd really appreciate if someone could guide me and get me started with the > project. The place to start is by bookmarking the GSoC

[Mailman-Developers] Regexp filtering

On Mailman-Users, Mark Sapiro writes: > Further, in the ban_list (and many other places in Mailman) if an > address is intended to be a regular expression pattern, it must begin > with '^', so you really want > > ^.*@domain\.com$ > > to match any_addr...@domain.com. I hope we haven't

Re: [Mailman-Developers] ARC module implementation [was: GSOC 2016]

Aditya Divekar writes: > I have taken your suggestion, and started working on a separate > branch to generate the ams from the original dkimpy package. Student applications will be opening shortly. You should finish up anything that is in your head but not in a file soon, and start preparing

Re: [Mailman-Developers] ARC module implementation [was: GSOC 2016]

Aditya Divekar writes: > I have read through the dkimpy library functions and it seems that the code > needs to be modified to generate the ARC headers, and I have started making > some changes. I don't think it's a great idea to change the dkimpy library if you can avoid it. The design I

[Mailman-Developers] ARC module implementation [was: GSOC 2016]

Aditya Divekar writes: > According to the draft, here > , > the ARC-Seal header is constructed from the referenced message > signatures given by the "k" tag. I didn't understand this part > clearly. The "k" tag has been removed

Re: [Mailman-Developers] GSOC 2016

Hi, Aditya! I've had a chance to read your mail and review the I-D (Internet Draft) and relevant RFCs a bit, and can now make a few comments. First, your understanding is a little bit shallow. You should get yourself a "canvas" and draw a detailed flowchart of what's going on here. I don't

[Mailman-Developers] Refried "SPAM" for GSoC 2016

The classic article on writing GSoC proposals, updated a bit for 2016, refactored for Moin (does Moin do ReST? the biggest annoyance was repeating links in several places) and moved to the Wiki. http://wiki.list.org/DEV/SPAM, reviews welcome. Or just fix what's broke. ;-) Steve

Re: [Mailman-Developers] Refried "SPAM" for GSoC 2016

Mark Sapiro writes: > On 02/09/2016 11:31 AM, Stephen J. Turnbull wrote: > > (does Moin do ReST? the biggest annoyance was > > repeating links in several places) > > Yes it does. Thanks for the confirmation! I should have guessed that (and figured out where t

Re: [Mailman-Developers] GSOC 2016

Aditya Divekar writes: > And I had previously mailed you directly, but I think I missed you > there. So I mailed it again here. No, I've just been really busy with work, and a very bad cold, sleeping about 2 hours/day more than usual. I'll get back to you tomorrow evening my time (it's 2am

[Mailman-Developers] GSOC 2016

Aditya Divekar writes: > My name is Aditya Divekar. I am a sophomore from IIT Guwahati. Nice to meet you, Aditya! I'm the main DMARC/IETF wrangler for Mailman, and I would be the main mentor for the ARC project. > I want to work on the project "Implement module to process ARC > headers". I

[Mailman-Developers] [Mailman-Users] RELEASED: Postorius 1.0.3

Thanks, Florian! f...@florianfuchs.com writes: > I'm announcing the release of Postorius 1.0.3. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ:

Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .

Abhilash Raj writes: > I *think* we have had a discussion before about what should be a better > default value for member.moderation_action and > nonmeember.moderation_action. Instead of just copying them to the field, > we could set it to defer in which it case the lookup automatically picks

Re: [Mailman-Developers] Dropping Persona

I disagree, but this being a GNU project it's the party line to deprecate security and privacy in favor of freedom. I won't push the issue of defaults any further since we agree the OAuth option should be available. f...@florianfuchs.com writes: > Non-Profit which doesn't aim at making money

Re: [Mailman-Developers] Dropping Persona

Barry Warsaw writes: > Further, I have a strong personal preference for "no user names", > or alternatively, using email addresses as their "user name". I > think user names are essentially contrived extra information for > which there's no need, when clearly your identity is your email >

[Mailman-Developers] Dropping Persona

Simon Hanna writes: > I propose using the django authentication system by default and > making it easy for people to add other authentication methods. I think we should provide social auth (OAuth2 or whatever Google and Yahoo! do) by default. At least as I recall the discussion at the sprints

Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .

Harshit Bansal writes: > Figure out how to store and access the styles as some of them are > defined in the source code and the ones created by the by users would > have to be stored in databases? You also need a read/print repr. A Python dict may be a reasonable one, but JSON, YAML, init,

[Mailman-Developers] an impossible need to address ?

I see I'm duplicating much of what Terri wrote but there's some new information here. With that caveat (must run, no time to edit), here we go: JFC Morfin writes: > database. It means a way (1) to set-up scores of same style mailing > lists and (2) for a person being a member of my directory

[Mailman-Developers] Need Assistance

Siddhartha Gairola writes: > If you could assist me as to how I should proceed now. Start at https://www.mail-archive.com/mailman-developers@python.org/. A couple of months' worth at first, then the last year or two. First, this question, and several other relevant questions, have been

[Mailman-Developers] Newbie to the "Mailman"

Ankush Khandelwal writes: >I am an undergraduate student pursuing Computer Science from IIIT > Hyderabad ( India ), currently in 3rd year and I'm newbie to this > organization. I am familiar with python and Git. Can somebody tell > me about the bugs which I can solve so that I can

Re: [Mailman-Developers] Facing error while building mailman

> Anirudh > > > > On Tue, Jan 12, 2016 at 7:36 AM, Stephen J. Turnbull <step...@xemacs.org> > wrote: > > > This -- "Python Version: 2.7.9" is also a problem for recent Mailman 3 > > (since 3.1 IIRC) -- Mailman 3 is only supported on Py

Re: [Mailman-Developers] Student looking to contribute towards GNU Mailman

Rishab Jaju writes: > Hi Abhilash, > > I am interested in the following project: "Subscriber Profile > Pages". Can I work on this project, or is somebody else working on > it? Even if somebody else is working on it, they may appreciate the help. Even if they are but don't want help, you

[Mailman-Developers] /opt vs traditional install [was: Mailman 3 production setup testbed]

Note: subject adjusted to reality. Barry Warsaw writes: > On Dec 05, 2015, at 11:38 PM, Stephen J. Turnbull wrote: > > >So /opt/mailman looks really good to me. > > +1 > > Distro packagers will probably make different decisions, but that's okay too. Of course!

[Mailman-Developers] Fwd: Request to mailing list Tom rejected

Fabian Santiago writes: > Someone subscribed a list to this list? We can't know. Write to someone who might: tom-ow...@esestudios.com: > > Your request to the Tom mailing list > > > >Posting of your message titled "[Mailman-Developers] MM3 trying to > > buildout / errors" > > > >

[Mailman-Developers] Upgrading from Mailman 3.0 installed with mailman-bundler: sassc error

Terri Oda writes: > the solution is > 1. install rubygem-sass > 2. update mailman_web/development.py so that COMPRESS_PRECOMPILERS asks > for sass instead of sassc I suppose the idea was to depend on sassc and libsass rather than Ruby. Do we really need to introduce a dependency on Ruby?

Re: [Mailman-Developers] Mailman 3 production setup testbed

Terri Oda writes: > What would be a good default directory to have in the docs if I want to > update them to suggest you start somewhere other than your home directory? > > /opt/mailman > > is probably the most appropriate one according to the LSB. +1 It's the only system hierarchy that

[Mailman-Developers] Mailman 3 production setup testbed

Andrew Hodgson writes: > I want to set up as a production environment, the idea is we will > be getting people used to the MM3 interface and ways of working > before we eventually migrate when 3.1 becomes available. I would > have posted this to the users list, but recent traffic on there >

Re: [Mailman-Developers] Please add multipart/signed to DEFAULT_PASS_MIME_TYPES

Carlos Alberto Lopez Perez writes: > Instead, you suggest to just add [ 'multipart' ] to the list. I > have 2 questions: > - Will 'multipart' match all the 3 previous multipart/variations? Yes. > - Is there any multipart/variation that we shouldn't allow by default? The only other

[Mailman-Developers] [gpg] encrypted list management plug-in

efkin writes: > from calafou hacklab & friends we wanted to reimplement schleuder in > python. URLs would be nice. > first and obvious question: is there already an ongoing effort to > achieve gpg encryption that we could join? Not really, although there's been discussion of it; see below.

[Mailman-Developers] Mailman and Box

Moving to mailman-users, be a better place to post a request for experience. Please respect cross-posting restrictions. If you're just reporting experience, reply-to is set to Mailman-Users which is appropriate (at least, IIRC the Mailman Users/Developers lists don't mess with preexisting

Re: [Mailman-Developers] Mozilla funding opportunity for Mailman work

Barry Warsaw writes: > What would *we* like to do that we can't do because of resources? That's where I'm blocked. I can't honestly put myself up as a money-sink: I wouldn't mind getting paid for my effort, but I wouldn't put in any less effort just because I'm unpaid. ;-) Hm ... maybe

Re: [Mailman-Developers] Let's try to package mailman3 in Debian!

Pierre-Elliott Bécue writes: > Stephen, I was considering that 3.1 would be a better one to release in > debian, but maybe starting before would be good to see how things > would go. Yes, and yes. What I recommended was that you announce "beta" testing once 3.1 is released and you've updated

Re: [Mailman-Developers] Let's try to package mailman3 in Debian!

Simon Hanna writes: > Actually mailman-core is fully functional all alone. That's not really true. Sure, you can telnet to the REST port and speak REST by hand, but that's hardly pleasant. At a minimum, you need mailmanclient. (There will be alternatives, there was a GSoC project to provide

Re: [Mailman-Developers] Migration of header_filter_rules

Aurelien Bompard writes: > Hmm, do you think so? I would have thought that list settings > should take precedence, since they are the most precise. A list > could decide to not filter the spam and deal with it in their own > manner (holding it instead of discarding it). That makes sense when

[Mailman-Developers] Let's try to package mailman3 in Debian!

Pierre-Elliott Bécue writes: > It seems that if I want to have a good source package, I need 5 repos : > > - Mailman > - HyperKitty > - Postorius > - HyperKitty - MailMan Plugin > - MailmanClient In the spirit of the refactoring, I would say mailman-core (mailman + mailmanclient),

[Mailman-Developers] User-centric authentication and access control

Waldbieser, Carl writes: > I would like to actually move the authentication and role > management *outside* of mailman and have the administrative > interface consume the role based information from external sources > (e.g. LDAP, CAS or SAML2 attribute release), so I am looking for a > more

Re: [Mailman-Developers] [Mailman 3] Granting Postorius web access to Mailman users?

Andrew Stuart writes: So there is something to be said for a very simple Mailman Core key/value store mechanism that would meet some simple needs. The argument against this is “well you’re going to outgrow it pretty quick anyway so why not immediately start with a more full featured

Re: [Mailman-Developers] [Mailman 3] Granting Postorius web access to Mailman users?

Barry Warsaw writes: One of the things I think we need is better holistic documentation which describes how to use the integrated system, The big problem is that as Simon points out we no longer have a truly centralized database. Each component now keeps user information related to itself,

Re: [Mailman-Developers] Why is postorius using python2?

f...@florianfuchs.com writes: We don't have any direct Python2-only dependencies in Postorius any more since we made the switch from django-social-auth to python-social-auth/django-browserid in April. I'm pretty sure the same is true for HyperKitty (Aurélien...?). So I guess there's no

[Mailman-Developers] Why is postorius using python2?

Simon Hanna writes: I was astonished to find out that postorius still uses python2 although mailman made the switch to python3. Why astonished? Lots of applications and libraries are still Python 2-based. Is there any reason behind this? It's not always trivial to do a port, and the

[Mailman-Developers] Mailman 3 status

Hi, Mailman Users! Executive summary: In my opinion, Mailman 3 is ready for use in production, but still requires skills and system accesses over and above those required by Mailman 2. Both in principle and in practice, questions about Mailman 3 should be directed to the Mailman Developers list

[Mailman-Developers] Problem Passing Parameters to the REST API

Nafisa Shazia writes: Hello Barry, I had the same (roundabout) problem as my peer in regards to passing parameters to the REST API. Khushboo's solution is going to be different, although most of the following general discussion should apply. My main question is: How deep do I need

Re: [Mailman-Developers] MM 3: bundler; stuck on buildout phase...

bill.co...@unh.edu writes: pip install python-social-auth Gotcha. Just because it's a bundle doesn't mean that it contains all possible dependencies. It is surprising, however, that the buildout just doesn't do the install itself. Restarted the build and... Something in django

[Mailman-Developers] Update 2.0 - Creating threads to handle dynamic list

Pranjal Yadav writes: Blog: prany.github.io code: giitlab.com/godricglow/mailman Sorry about the long brain dump. Pick some of the issues to address now and save the rest for later. I took a look at your blog. First I reviewed your proposal blog from April 29

[Mailman-Developers] Update 2.0 - Creating threads to handle dynamic list

Hi all, I'll get to reviewing Pranjal's blog post later tonight; anybody who's going to be working on it (especially Terri), you might want to wait on mine so we don't duplicate. Steve ___ Mailman-Developers mailing list Mailman-Developers@python.org

[Mailman-Developers] Posting etiquette

Abhilash Raj writes: Subject: Re: [Mailman-Developers] help with ImportError: No module named 'psycopg2' [body omitted] Abhilash, that post had a signal to noise ratio of 0.08 by line count, and it would be worse in bytes. Please trim. If you don't want to trim because you're on a handheld

Re: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks

Barry Warsaw writes: On May 25, 2015, at 05:27 PM, Abhilash Raj wrote: I think a better idea would be to keep everything in Postorius. +1 I really think we should reserve 3.1 for fixing major problems (and I expect to have a lot of user-noticable problems, starting with lots of Mailman 2

[Mailman-Developers] [GSoc Project] Error Creating a New Model for The Database

Bhavesh Goyal writes: But, whenever I try to query an object from the 'task' table, I get an sql error : no such table 'task'. Are you doing attribute access in Python code for Django, or are you writing direct SQL queries? My first guess for either case is that you haven't done the sync

[Mailman-Developers] How to Ask -- reading list for GSoC students, part I

I don't mean to single out a particular student, or even students in general. We've all done this early in our careers. That said, What can it be that I may be missing which is preventing me to query the table. Really desperate for any hep on this :) Thanks... is a poor problem report. We

<    1   2   3   4   5   6   7   8   9   10   >