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 I18N, so I think we're off to a good start there. > To the extent that all subprojects can share infrastructure, great, > but that shouldn't come as a sacrifice for Django's natural i18n > workflow. Aurelien and Florian should probably describe how they > want it to work for those two projects. Agreed. I think the main Django I18N frameworks end up producing potfiles, so the translators should not have too much new infrastructure to learn. Steve ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 this. OK, great! You probably can! And don't take my worries too seriously. I'm a professional worrier. Every project should have one -- and only one. :-) And in terms of Python skills necessary, this project *is* beginner- friendly. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] GSOC '16 Help
Hello Vatsal, Welcome to the Mailman community > Hey Devs, > I was going through the list of projects for GSOC '16, and mailman seemed > interesting. Though i read the FAQs, can anyone please guide me about how > to get started? there are a lot of projects, contribution, application and > all... what should be the first step to follow for me? First you should do a local setup and make sure everything is working as expected, since you are new to Mailman it will take some time to setup. > I am a intermediate python developer, have worked on couple of small > projects but haven't done any open source contribution yet. That is great, intermediate knowledge of python is sufficient to get you started, Once you are through the setup, start organizing your thoughts and decide which part of mailman are you comfortable with and then look for aligned projects. Don't jump the gun yet, it might be the case that you find a perfect project among the listed ones or you won't find anything at all, be it either case you should start looking into beginner level bugs and try to fix them. In the mean time get in touch with other devs on the mailing list or IRC, you can certainly propose new projects and admins will help you decide if they can be a part of GSoC pipeline or not. All the best! > > Thanks, > Vatsal Parekh. > ___ > Mailman-Developers mailing list > Mailman-Developers@python.org > https://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/godricglow%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Resuming mailman contribution
On 1 Mar 2016 8:27 pm, "Barry Warsaw" wrote: > > On Mar 01, 2016, at 12:09 PM, Pranjal Yadav wrote: > > >For those who don't know me, I was a part of GSoC 2015 with Mailman, I > >worked on the dynamic sublists aka dlist project. Terri and Steve mentored > >me for this project and except for the timezone issue, I felt the > >mentorship was one of the best experiences I have had in past few years, > >Also Barry and Florian constantly helped me enhance my knowledge about mm3, > >In totality it was a great experience. By the end of my project I started > >with my first job and it was quite a hassle for few months, as soon as I > >was about to settle I got a better opportunity and I switched. So long > >story short I'm finally getting back after 6 months and its a wonderful > >feeling. > > Yay, welcome back! > > We should make a push for getting dlists into the core. Sure Barry, I'll traveling this week so starting next week first I'll update the documentation and then I'll redo the testing part. Will keep you posted :) > Cheers, > -Barry > ___ > Mailman-Developers mailing list > Mailman-Developers@python.org > https://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/godricglow%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] GSOC '16 Help
Hey Devs, I was going through the list of projects for GSOC '16, and mailman seemed interesting. Though i read the FAQs, can anyone please guide me about how to get started? there are a lot of projects, contribution, application and all... what should be the first step to follow for me? I am a intermediate python developer, have worked on couple of small projects but haven't done any open source contribution yet. Thanks, Vatsal Parekh. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] About working on Issue #67
On Mar 01, 2016, at 11:13 PM, Stephen J. Turnbull wrote: >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 clear. I added a comment in #67. The core has a bunch of templates that need translation, although it's unclear whether a gettext approach will help. Probably we can just accept merge requests for translated templates. The core also has some translatable strings, mostly for substitutions into fields that it creates out of whole cloth. For those, gettext-extraction and translation techniques will be helpful. I'm happy to continue discussing both of the above in #67. 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. To the extent that all subprojects can share infrastructure, great, but that shouldn't come as a sacrifice for Django's natural i18n workflow. Aurelien and Florian should probably describe how they want it to work for those two projects. Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Resuming mailman contribution
On Mar 01, 2016, at 12:09 PM, Pranjal Yadav wrote: >For those who don't know me, I was a part of GSoC 2015 with Mailman, I >worked on the dynamic sublists aka dlist project. Terri and Steve mentored >me for this project and except for the timezone issue, I felt the >mentorship was one of the best experiences I have had in past few years, >Also Barry and Florian constantly helped me enhance my knowledge about mm3, >In totality it was a great experience. By the end of my project I started >with my first job and it was quite a hassle for few months, as soon as I >was about to settle I got a better opportunity and I switched. So long >story short I'm finally getting back after 6 months and its a wonderful >feeling. Yay, welcome back! We should make a push for getting dlists into the core. Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] About working on Issue #67
No it wasn't for GSoC, 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 this. On Tue, Mar 1, 2016 at 2:13 PM, Stephen J. Turnbull wrote: > 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 clear. > > Are you thinking about doing this for GSoC? If so, we all need to > talk about this and get it nailed down. This kind of thing can be a > real hairball, something that you don't want to do "on deadline". I > don't want to scare you away, it could be quite straightforward, too. > But let's start talking now. Again, if GSoC, I'm quite unclear on > where the "code" (GSoC only supports coding projects) comes in. Could > be I'm just blind :-) but let's nail that one down too. > ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Regexp filtering
On Mar 01, 2016, at 11:13 PM, Stephen J. Turnbull wrote: >In theory we could use globs as well (some of the modern VCSes permit >glob or regexp syntax), but it's not a serious data loss issue for a >VCS if a mistake is made. You just run the add command again with -f, >or uncommit, or whatever. Granted, a perverse enough user could fail >to add a file, commit, then overwrite the file, but this is much less >serious than the possibility that a particular user would end up as >collateral damage to a spam filter. globs make sense for file system operations, and we've been using them for decades in shells. I think globs make less sense for header value pattern matching. Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[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 clear. Are you thinking about doing this for GSoC? If so, we all need to talk about this and get it nailed down. This kind of thing can be a real hairball, something that you don't want to do "on deadline". I don't want to scare you away, it could be quite straightforward, too. But let's start talking now. Again, if GSoC, I'm quite unclear on where the "code" (GSoC only supports coding projects) comes in. Could be I'm just blind :-) but let's nail that one down too. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
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 anchored? At the beginning of string? At end? Is there really a use case for "?"? I don't see this as an obvious feature. Globs are also too blunt for the use case, especially since bad actors do deliberately use fine distinctions between well-known domains and their own sinkholes of depravity when phishing. Users are likely to be lazy, using "*@*mail.ru" to catch both "badac...@mail.ru" and "badac...@spamsource.mail.ru", trashing "nice...@goodmail.ru"'s posts in the process. > Off the top of my head, the syntax would define if it's an absolute > address (f...@example.com) vs a regexp. "f...@example.com" is unambiguous, but "foo+mail...@example.com" is not. That's a big trap for users, who surely know exactly what they mean by that (and it's not fmail...@example.com!) In theory we could use globs as well (some of the modern VCSes permit glob or regexp syntax), but it's not a serious data loss issue for a VCS if a mistake is made. You just run the add command again with -f, or uncommit, or whatever. Granted, a perverse enough user could fail to add a file, commit, then overwrite the file, but this is much less serious than the possibility that a particular user would end up as collateral damage to a spam filter. Steve ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Regexp filtering
On Tue, Mar 01, 2016 at 04:37:16AM +0900, Stephen J. Turnbull wrote:
> 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
> > understanding that is_regexp=False means the pattern is a literal).
>
> Are regexps sufficiently slow that *always* using a regexp would hurt
> performance?[1] The model I really had in mind was to always use
> regexps, and have a flag in the UI (Postorius) to regexp-quote when
> the user wants a literal.
Or could we meet user expectations (real users, not geeks), and just
interpret * and ? (for example) as being regexp values, as well as
letting power users use more complicated regexps?
Essentially the two classes:
Simples:
*@mail.ru
*@*mail.ru
?@mail.ru
Power-user:
^.*\+.*?\d{3,}@
\.*j\.*o\.*e\.*b\.*l\.*o\.*w\.*+.*@gmail\.com
and the sort we saw in the threads around bot subscriptions and
regexps on Mailman-user?
Off the top of my head, the syntax would define if it's an absolute
address (f...@example.com) vs a regexp.
--
"I never make predictions. I never have, and I never will."
-- Tony Blair
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
