Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?
Thanks. Barry for the detailed explanation. I will surely have a look on that part as you mentioned. Thanks, Ankush Sharma github.com/black-perl On Fri, Feb 27, 2015 at 9:47 PM, Barry Warsaw ba...@list.org wrote: On Feb 27, 2015, at 01:02 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: A personalized mailing list will allow mailman users to send personalized emails to all the list members from a common email template. Almost all the pieces are already there to support mail merging, at least as a plugin. There's quite a bit of functionality in place to allow for pluggable MTA delivery methods. Right now, there's only one. Search src/mailman/config/schema.cfg for the [mta]outgoing variable. We also already do a bit of mixin class composition to implement various aspects of the existing personalized delivery machinery. The proper class is chosen (based on the default [mta]outgoing value) from the value of mlist.personalize. To support mail merge, we'd need a little more flexibility in composing these basic bits. You'd like for individual mailing lists to be able to choose a custom delivery mechanism from a set of site-defined choices, for example. Then a plugin could define a new delivery class which does the database lookups and the mail merge into the template at the point where the VERP'd message is handed off to the upstream MTA. You'd register this new delivery class with the system and them mailing lists could opt into it. 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] GSoC 2015: brainstorming ideas suitable for beginners?
Yes, Stephen also mentioned about its separate working and not being able to get integrated with mailman. But, I guess it would be cool if this metrics project can be integrated with postorius or hyperkitty as you mentioned. Thanks, Ankush Sharma github.com/black-perl On Sat, Feb 28, 2015 at 1:50 AM, Terri Oda te...@toybox.ca wrote: On 2015-02-27 1:06 AM, Stephen J. Turnbull wrote: Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA writes: I was wondering if there is a sort of tool that generates summaries for mailing list activity and charts like number of users, number of active users, etc. Would something like this be a good idea or is it already done? There are such tools but they're not integrated into the Mailman 2 web interface, and I think they're not in Postorius or Hyperkitty yet, either. They're frequently requested and I think Postorius provides some infrastructure for such things. We actually have a whole summer of code project that was on metrics from a few years ago. I believe it worked as separate add-in for Mailman, but perhaps we should take a look at integrating it better into hyperkitty (or maybe postorius?) if people are unaware that it exists. I'd like to see that code integrated part of any new effort in this area. Terri ___ 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 2015: brainstorming ideas suitable for beginners?
There’s a bug at: https://bugs.launchpad.net/mailman/+bug/1423756 Requesting domainowner and serverowner thanks On 26 Feb 2015, at 10:10 am, Barry Warsaw ba...@list.org wrote: On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code. Are you anticipating this will be in V3.0? Please file a bug and we'll see. ;) 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/andrew.stuart%40supercoders.com.au 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] GSoC 2015: brainstorming ideas suitable for beginners?
On 02/27/2015 12:24 AM, Terri Oda wrote: It's not that it's a bad feature in isolation. But there are so *many* potential features for Mailman, and I'd like to see ideas that are less socially problematic get implemented first. And there are many customer relations managements systems available that already do this kind of thing. Mailman doesn't need to do it. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan ___ 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 2015: brainstorming ideas suitable for beginners?
On Feb 27, 2015, at 01:02 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: A personalized mailing list will allow mailman users to send personalized emails to all the list members from a common email template. Almost all the pieces are already there to support mail merging, at least as a plugin. There's quite a bit of functionality in place to allow for pluggable MTA delivery methods. Right now, there's only one. Search src/mailman/config/schema.cfg for the [mta]outgoing variable. We also already do a bit of mixin class composition to implement various aspects of the existing personalized delivery machinery. The proper class is chosen (based on the default [mta]outgoing value) from the value of mlist.personalize. To support mail merge, we'd need a little more flexibility in composing these basic bits. You'd like for individual mailing lists to be able to choose a custom delivery mechanism from a set of site-defined choices, for example. Then a plugin could define a new delivery class which does the database lookups and the mail merge into the template at the point where the VERP'd message is handed off to the upstream MTA. You'd register this new delivery class with the system and them mailing lists could opt into it. Cheers, -Barry pgpDGU7omzpQy.pgp Description: OpenPGP digital signature ___ 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 2015: brainstorming ideas suitable for beginners?
On 2015-02-27 1:06 AM, Stephen J. Turnbull wrote: Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA writes: I was wondering if there is a sort of tool that generates summaries for mailing list activity and charts like number of users, number of active users, etc. Would something like this be a good idea or is it already done? There are such tools but they're not integrated into the Mailman 2 web interface, and I think they're not in Postorius or Hyperkitty yet, either. They're frequently requested and I think Postorius provides some infrastructure for such things. We actually have a whole summer of code project that was on metrics from a few years ago. I believe it worked as separate add-in for Mailman, but perhaps we should take a look at integrating it better into hyperkitty (or maybe postorius?) if people are unaware that it exists. I'd like to see that code integrated part of any new effort in this area. Terri ___ 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 2015: brainstorming ideas suitable for beginners?
Honestly, I don't love this idea. I would be technically feasible with VERP, but it edges into features that are very popular for people sending spam. On 2015-02-26 11:32 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: How about having personalized announcement mailing lists ? A personalized mailing list will allow mailman users to send personalized emails to all the list members from a common email template. Suppose I am the manager of a company and I need to ask all the workers for a meeting. I want each of my workers to prepare a topic to speak on during the meeting. For this I need to send each of them a message separately mentioning the topic he/she has to speak on. Suppose the email /template/ is like this: *To : worker-email* *Subject: sub* * * *Hello worker-name,* * * *Hope you are having fun at worker-place. I am arranging a meeting at 5 p.m. on Saturday. I want you to speak on topic during the meeting. So, come prepared for that.* *other-suff* * * *Best wishes,* * * *Ankush Sharma* *Manager* *foo-bar* And I have a spreadsheet data on the mailing list server like this: https://docs.google.com/spreadsheets/d/1cAbdSmc1NA-C9IZFjc_zB67qEvgmX8Jr3xYyGxPdwdU/pubhtml Mailman can have a functionality of flooding the /template/ by using the spreadsheet data. The variables in the /template/ ( -- stuff) would be replaced by the corresponding row data in the spreadsheet corresponding to the emails of the list members. This can provide great flexibility to mailman users who use mailman as announcement list. Later on, mailman can have the functionality of saving email templates and choosing one of them in a certain scenario. Mailing lists can be made more personalized and powerful in this way. Expecting further feedback or suggestions on this idea. Ankush Sharma IIT-BHU,Varanasi github.com/black-perl http://github.com/black-perl On Thu, Feb 26, 2015 at 4:40 AM, Barry Warsaw ba...@list.org mailto:ba...@list.org wrote: On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code. Are you anticipating this will be in V3.0? Please file a bug and we'll see. ;) Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org mailto: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/ankush.sharma.ece12%40itbhu.ac.in 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] GSoC 2015: brainstorming ideas suitable for beginners?
Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA writes: I was wondering if there is a sort of tool that generates summaries for mailing list activity and charts like number of users, number of active users, etc. Would something like this be a good idea or is it already done? There are such tools but they're not integrated into the Mailman 2 web interface, and I think they're not in Postorius or Hyperkitty yet, either. They're frequently requested and I think Postorius provides some infrastructure for such things. ___ 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 2015: brainstorming ideas suitable for beginners?
I realize the feature I proposed earlier is more of a commercial feature and might not be be so useful for Mailman as you mentioned it's pitfalls. Are there other directions that I should think in? I am good with Python, Javascript, HTML5. I was wondering if there is a sort of tool that generates summaries for mailing list activity and charts like number of users, number of active users, etc. Would something like this be a good idea or is it already done? On Fri, Feb 27, 2015 at 1:54 PM, Terri Oda te...@toybox.ca wrote: I am quite aware of the definition of spam (in fact, I have a master's thesis on the subject). What I'm concerned about is that in the past, mail merges (which is what you're describing) is a feature that has often been requested by people doing marketing lists. It's not a subset of users I'm eager to attract, since a few bad apples could cause some unfortunate fallout for Mailman as users start marking messages as spam and, inevitably, sending us angry messages. (As the person who wrote the 2.1 documentation, I can tell you that I already get these on occasion as upset folk will send to basically any address they can find associated with the project.) It's not that it's a bad feature in isolation. But there are so *many* potential features for Mailman, and I'd like to see ideas that are less socially problematic get implemented first. Terri On 2015-02-26 11:52 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: On Fri, Feb 27, 2015 at 1:13 PM, Terri Oda te...@toybox.ca mailto:te...@toybox.ca wrote: Honestly, I don't love this idea. I would be technically feasible with VERP, I don't know about VERP. I will surely have a look. but it edges into features that are very popular for people sending spam. Spamming would be the case when you are sending the emails to people who don't want to receive such emails. While if we control the email variable to take value from the set of emails of the list members only and not allowing the use of template variables i.e .. stuff in the *To: *field. On 2015-02-26 11:32 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: How about having personalized announcement mailing lists ? A personalized mailing list will allow mailman users to send personalized emails to all the list members from a common email template. Suppose I am the manager of a company and I need to ask all the workers for a meeting. I want each of my workers to prepare a topic to speak on during the meeting. For this I need to send each of them a message separately mentioning the topic he/she has to speak on. Suppose the email /template/ is like this: *To : worker-email* *Subject: sub* * * *Hello worker-name,* * * *Hope you are having fun at worker-place. I am arranging a meeting at 5 p.m. on Saturday. I want you to speak on topic during the meeting. So, come prepared for that.* *other-suff* * * *Best wishes,* * * *Ankush Sharma* *Manager* *foo-bar* And I have a spreadsheet data on the mailing list server like this: https://docs.google.com/__spreadsheets/d/1cAbdSmc1NA-__C9IZFjc___ zB67qEvgmX8Jr3xYyGxPdwdU/__pubhtml https://docs.google.com/spreadsheets/d/1cAbdSmc1NA-C9IZFjc_ zB67qEvgmX8Jr3xYyGxPdwdU/pubhtml Mailman can have a functionality of flooding the /template/ by using the spreadsheet data. The variables in the /template/ ( -- stuff) would be replaced by the corresponding row data in the spreadsheet corresponding to the emails of the list members. This can provide great flexibility to mailman users who use mailman as announcement list. Later on, mailman can have the functionality of saving email templates and choosing one of them in a certain scenario. Mailing lists can be made more personalized and powerful in this way. Expecting further feedback or suggestions on this idea. Ankush Sharma IIT-BHU,Varanasi github.com/black-perl http://github.com/black-perl http://github.com/black-perl On Thu, Feb 26, 2015 at 4:40 AM, Barry Warsaw ba...@list.org mailto:ba...@list.org mailto:ba...@list.org mailto:ba...@list.org wrote: On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code.
Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?
I am quite aware of the definition of spam (in fact, I have a master's thesis on the subject). What I'm concerned about is that in the past, mail merges (which is what you're describing) is a feature that has often been requested by people doing marketing lists. It's not a subset of users I'm eager to attract, since a few bad apples could cause some unfortunate fallout for Mailman as users start marking messages as spam and, inevitably, sending us angry messages. (As the person who wrote the 2.1 documentation, I can tell you that I already get these on occasion as upset folk will send to basically any address they can find associated with the project.) It's not that it's a bad feature in isolation. But there are so *many* potential features for Mailman, and I'd like to see ideas that are less socially problematic get implemented first. Terri On 2015-02-26 11:52 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: On Fri, Feb 27, 2015 at 1:13 PM, Terri Oda te...@toybox.ca mailto:te...@toybox.ca wrote: Honestly, I don't love this idea. I would be technically feasible with VERP, I don't know about VERP. I will surely have a look. but it edges into features that are very popular for people sending spam. Spamming would be the case when you are sending the emails to people who don't want to receive such emails. While if we control the email variable to take value from the set of emails of the list members only and not allowing the use of template variables i.e .. stuff in the *To: *field. On 2015-02-26 11:32 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: How about having personalized announcement mailing lists ? A personalized mailing list will allow mailman users to send personalized emails to all the list members from a common email template. Suppose I am the manager of a company and I need to ask all the workers for a meeting. I want each of my workers to prepare a topic to speak on during the meeting. For this I need to send each of them a message separately mentioning the topic he/she has to speak on. Suppose the email /template/ is like this: *To : worker-email* *Subject: sub* * * *Hello worker-name,* * * *Hope you are having fun at worker-place. I am arranging a meeting at 5 p.m. on Saturday. I want you to speak on topic during the meeting. So, come prepared for that.* *other-suff* * * *Best wishes,* * * *Ankush Sharma* *Manager* *foo-bar* And I have a spreadsheet data on the mailing list server like this: https://docs.google.com/__spreadsheets/d/1cAbdSmc1NA-__C9IZFjc___zB67qEvgmX8Jr3xYyGxPdwdU/__pubhtml https://docs.google.com/spreadsheets/d/1cAbdSmc1NA-C9IZFjc_zB67qEvgmX8Jr3xYyGxPdwdU/pubhtml Mailman can have a functionality of flooding the /template/ by using the spreadsheet data. The variables in the /template/ ( -- stuff) would be replaced by the corresponding row data in the spreadsheet corresponding to the emails of the list members. This can provide great flexibility to mailman users who use mailman as announcement list. Later on, mailman can have the functionality of saving email templates and choosing one of them in a certain scenario. Mailing lists can be made more personalized and powerful in this way. Expecting further feedback or suggestions on this idea. Ankush Sharma IIT-BHU,Varanasi github.com/black-perl http://github.com/black-perl http://github.com/black-perl On Thu, Feb 26, 2015 at 4:40 AM, Barry Warsaw ba...@list.org mailto:ba...@list.org mailto:ba...@list.org mailto:ba...@list.org wrote: On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code. Are you anticipating this will be in V3.0? Please file a bug and we'll see. ;) Cheers, -Barry _ Mailman-Developers mailing list Mailman-Developers@python.org mailto:Mailman-Developers@python.org mailto:Mailman-Developers@__python.org mailto:Mailman-Developers@python.org https://mail.python.org/__mailman/listinfo/mailman-__developers https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ:
Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?
Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA writes: Spamming would be the case when you are sending the emails to people who don't want to receive such emails. While if we control the email variable to take value from the set of emails of the list members only and not allowing the use of template variables i.e .. stuff in the *To: *field. Ah, but Mailman is a winning application because it's easy to add and remove subscribers. You can already upload files in the mass add screen of subscription management. If you're going to work on Mailman, remember the first rule of mail abuse: RULE #1: All mail programs can be used to spam. That said, I'm pretty sure people are already using Mailman for spamming in exactly that way (uploading files of target addresses), and there are some features like headers and footers that could be adapted to personalized spam. I don't see why the good guys should be prevented from using features that the bad guys have anyway. So I don't consider the smells like spam, tastes like spam, argument prohibitive (although I sympathize with Terri). And I have a spreadsheet data on the mailing list server like this: https://docs.google.com/spreadsheets/d/1cAbdSmc1NA-C9IZFjc_ zB67qEvgmX8Jr3xYyGxPdwdU/pubhtml Mailman can have a functionality of flooding the /template/ by using the spreadsheet data. The variables in the /template/ ( -- stuff) would be replaced by the corresponding row data in the spreadsheet corresponding to the emails of the list members. This can provide great flexibility to mailman users who use mailman as announcement list. To be honest, this application would not be very high on my list of interesting projects. In the business application you described, I would be just as happy sending the table of assignments to everybody (and if there are assigned time slots, it doubles as the program). On the other hand, for marketing mail shots I would typically want a more flexible program. For example, if a customer has children and I know their names, then I would insert a whole paragraph about them, including their names, and probably the text would depend on gender and hobbies and so on. Or consider a cellphone service, the customer might be a family with several members and phones, and your letter probably should treat each member appropriately recommending upgrades according to usage patterns and demographics. That doesn't fit well into the rectangular spreadsheet model of row per message. I think that perhaps a more general database that *can* read spreadsheets but is not limited to that model would be more appropriate. But that is likely to be a fairly big project unless you're quite familiar with this kind of object-oriented database. Regards, ___ 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 2015: brainstorming ideas suitable for beginners?
How about having personalized announcement mailing lists ? A personalized mailing list will allow mailman users to send personalized emails to all the list members from a common email template. Suppose I am the manager of a company and I need to ask all the workers for a meeting. I want each of my workers to prepare a topic to speak on during the meeting. For this I need to send each of them a message separately mentioning the topic he/she has to speak on. Suppose the email *template* is like this: *To : worker-email* *Subject: sub* *Hello worker-name,* *Hope you are having fun at worker-place. I am arranging a meeting at 5 p.m. on Saturday. I want you to speak on topic during the meeting. So, come prepared for that.* *other-suff* *Best wishes,* *Ankush Sharma* *Manager* *foo-bar* And I have a spreadsheet data on the mailing list server like this: https://docs.google.com/spreadsheets/d/1cAbdSmc1NA-C9IZFjc_zB67qEvgmX8Jr3xYyGxPdwdU/pubhtml Mailman can have a functionality of flooding the *template* by using the spreadsheet data. The variables in the *template* ( -- stuff) would be replaced by the corresponding row data in the spreadsheet corresponding to the emails of the list members. This can provide great flexibility to mailman users who use mailman as announcement list. Later on, mailman can have the functionality of saving email templates and choosing one of them in a certain scenario. Mailing lists can be made more personalized and powerful in this way. Expecting further feedback or suggestions on this idea. Ankush Sharma IIT-BHU,Varanasi github.com/black-perl On Thu, Feb 26, 2015 at 4:40 AM, Barry Warsaw ba...@list.org wrote: On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code. Are you anticipating this will be in V3.0? Please file a bug and we'll see. ;) 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/ankush.sharma.ece12%40itbhu.ac.in 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] GSoC 2015: brainstorming ideas suitable for beginners?
On Fri, Feb 27, 2015 at 1:13 PM, Terri Oda te...@toybox.ca wrote: Honestly, I don't love this idea. I would be technically feasible with VERP, I don't know about VERP. I will surely have a look. but it edges into features that are very popular for people sending spam. Spamming would be the case when you are sending the emails to people who don't want to receive such emails. While if we control the email variable to take value from the set of emails of the list members only and not allowing the use of template variables i.e .. stuff in the *To: *field. On 2015-02-26 11:32 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: How about having personalized announcement mailing lists ? A personalized mailing list will allow mailman users to send personalized emails to all the list members from a common email template. Suppose I am the manager of a company and I need to ask all the workers for a meeting. I want each of my workers to prepare a topic to speak on during the meeting. For this I need to send each of them a message separately mentioning the topic he/she has to speak on. Suppose the email /template/ is like this: *To : worker-email* *Subject: sub* * * *Hello worker-name,* * * *Hope you are having fun at worker-place. I am arranging a meeting at 5 p.m. on Saturday. I want you to speak on topic during the meeting. So, come prepared for that.* *other-suff* * * *Best wishes,* * * *Ankush Sharma* *Manager* *foo-bar* And I have a spreadsheet data on the mailing list server like this: https://docs.google.com/spreadsheets/d/1cAbdSmc1NA-C9IZFjc_ zB67qEvgmX8Jr3xYyGxPdwdU/pubhtml Mailman can have a functionality of flooding the /template/ by using the spreadsheet data. The variables in the /template/ ( -- stuff) would be replaced by the corresponding row data in the spreadsheet corresponding to the emails of the list members. This can provide great flexibility to mailman users who use mailman as announcement list. Later on, mailman can have the functionality of saving email templates and choosing one of them in a certain scenario. Mailing lists can be made more personalized and powerful in this way. Expecting further feedback or suggestions on this idea. Ankush Sharma IIT-BHU,Varanasi github.com/black-perl http://github.com/black-perl On Thu, Feb 26, 2015 at 4:40 AM, Barry Warsaw ba...@list.org mailto:ba...@list.org wrote: On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code. Are you anticipating this will be in V3.0? Please file a bug and we'll see. ;) Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org mailto: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/ankush.sharma.ece12%40itbhu.ac.in 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] GSoC 2015: brainstorming ideas suitable for beginners?
On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code. Are you anticipating this will be in V3.0? Please file a bug and we'll see. ;) 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] GSoC 2015: brainstorming ideas suitable for beginners?
On Feb 24, 2015, at 07:53 AM, Chris Nulk wrote: Also, I believe I remember a goal for Mailman v3 was to have one instance of Mailman be able to host lists for multiple domains. Yes, but not on physically distinct hosts. Or in other words, yes MM3 supports virtual domains Given that information and information from Andrew and Stephen, there are several different layers of ownership. Thinking about it a little, I see: OwnerDescription -- List Owner can administer a list Server Ownercan administer all lists on one server (server may host multiple domains) Site Ownercan administer for all lists at a site (site has multiple servers) (site is a physical location) Domain Owner can administer for all lists for a domain (domains may be hosted on multiple servers possibly across multiple sites) Note: if site is considered a physical location, then an additional owner permission may be Host Owner for all their sites at different locations I think the distinction between server owner and site owner as described above doesn't exist, or I don't quite understand the definitions. Multiple servers isn't a concept embodied in Mailman anywhere. For example, if you were to run a hosting provider and had clients at A.example.com and B.example.com, and they ran distinct Mailman servers, the two wouldn't have any organizational or administrative overlap, except at a higher level, e.g. postmas...@hosting.example.com. That's not something I see Mailman having to represent in any useful way. 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] GSoC 2015: brainstorming ideas suitable for beginners?
On 2/23/2015 8:08 PM, Stephen J. Turnbull wrote: Andrew Stuart writes: I am currently associating users, not addresses with these permissions, so your suggestion is compatible with my stuff. +1 on associating users with permissions (plus the validation Barry recommends). site owner does sound more appropriate than server owner. Users think of site as being nearly synonymous with domain, though. I don't think we should use site in a different way, that would confuse them. There should be a way to contact the actual operator of the host, which I think of as hostmaster or server owner. Steve My .0002 cents. :) In a previous message, the thought of making Mailman usable in an enterprise environment was brought up. A good idea. Also, I believe I remember a goal for Mailman v3 was to have one instance of Mailman be able to host lists for multiple domains. Given that information and information from Andrew and Stephen, there are several different layers of ownership. Thinking about it a little, I see: OwnerDescription -- List Owner can administer a list Server Ownercan administer all lists on one server (server may host multiple domains) Site Ownercan administer for all lists at a site (site has multiple servers) (site is a physical location) Domain Owner can administer for all lists for a domain (domains may be hosted on multiple servers possibly across multiple sites) Note: if site is considered a physical location, then an additional owner permission may be Host Owner for all their sites at different locations. Nailing down a good permissions structure is very important if Mailman is to be used in the enterprise, both in a large organization or by a hosting company (e.g. Rackspace, etc.). Better people than I can come up with a better solution than my quick thought. I do think it is important that once you get past the List Owner level of permissions, there is potential interaction between Server Owner, Site Owner, and Domain Owner. This also points to a need for a robust authentication system that can handle multiple ways to authenticate the various owners. Well, probably in over my head again. Thanks, Chris ___ 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 2015: brainstorming ideas suitable for beginners?
I’m looking forward to being able to set and get domainowner and serverowner (or siteowner or whatever its called). It will allow me to delete lots of code and there’s no greater joy than deleting code. Are you anticipating this will be in V3.0? thanks as On 24 Feb 2015, at 11:42 am, Barry Warsaw ba...@list.org wrote: On Feb 22, 2015, at 11:20 AM, Andrew Stuart wrote: there was an “application data” table: resource_type | resource_id | private/public | key |value user list domain server and: the ability to set domainowner and serverowner permissions in 3.0, No question, I think domain owner and server owner (or site owner) are concepts that we should capture in the core. I'd accept contributions for this, so let me describe my thinking (open to suggestions!). The first question is whether to associate addresses, users, or both with the permissions. If you look at the member table (Member model class) you'll see we have a foreign key for both, but the logic ensure that we can't get conflicting values. This allows us to implement the address as a member or the user as a member using their preferred address. I'm not sure whether we need this level of complexity for the site and domain owners. The other observation is that we'd like to make it easy for both owners two have multiple contact addresses, so that we have fallbacks in case one of them starts to fail. So I'm thinking we use a User for this association. The user would have to have at least one validated address linked to it. For domains, we already have a domain table (Domain model class). Since we'd like to be able to associate multiple domain owners, it seems like we need a many-to-many table associating domains to users. (More than one user can own a domain, and any user can own more than one domain.) That table probably doesn't need anything else. Since we have no site table/model, I think it would be enough to add a flag to the user table/model to indicate whether they are a site owner or not. Now sprinkle with tests, database migrations, documentation, and REST, and I think you have at least this part solved. 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/andrew.stuart%40supercoders.com.au 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] GSoC 2015: brainstorming ideas suitable for beginners?
Andrew Stuart writes: I am currently associating users, not addresses with these permissions, so your suggestion is compatible with my stuff. +1 on associating users with permissions (plus the validation Barry recommends). site owner does sound more appropriate than server owner. Users think of site as being nearly synonymous with domain, though. I don't think we should use site in a different way, that would confuse them. There should be a way to contact the actual operator of the host, which I think of as hostmaster or server owner. 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] GSoC 2015: brainstorming ideas suitable for beginners?
Do you think this has to be integrated into the core for 3.0? I'd still prefer to keep it separate for better experimentation and testing. if: there was an “application data” table: resource_type | resource_id | private/public | key |value user list domain server and: the ability to set domainowner and serverowner permissions in 3.0, then: there would be a huge payoff in terms of avoiding the downstream challenge of migration upgrade scripts, data migrations, testing, backups, the risk of something going wrong for the end-user sysadmin. else: the alternative for me is to go ahead with deploying application data and domainowner and serverowner into the auth server, and later needing to work out how to migrate these back into Mailman core in some later version - I’m thinking that if those tables were there in Mailman 3.0 rather than say version 3.1 then a vast amount of downstream work, risk and thinking could be saved (for me). Not insurmountable but would really take alot of engineering to do safely. Getting random sysadmins to do stuff like data migrations that is a little anxiety provoking. David Murray, who does the Python email package, implements APIs as “provisional” so they are not part of the official release but are present in the code, until some version further down the track where he formalises the provisional API following road testing and feedback. Sort of a logical separation for experimentation and testing. Could that be a way to implement an application data table and serverowner and domainowner permissions in 3.0? That way, consumers of the REST API can use the provisional API functionality at our own risk that it might change before being formalised. I’d take that any day over the need to write stuff that a random sysadmin could run to migrate their data into a new table structure later. Implementing an application data table and domainowner/serverowner as “provisional” would be a stitch in time for me anyway. As I mentioned I’ve done it myself anyway in the auth server but theres a bunch of unaddressed challenges relating to replication and synchronisation - whenever the application data is accessed, there needs to be checks to verify that both the user and the resource actually exist in Mailman, and there’s no easy way to know when users and resources have been deleted from Mailman, potentially leaving stale application data. As always though, I’m not super attached to the outcomes - you’re the boss Barry so I’m OK with whatever path. as On 22 Feb 2015, at 5:05 am, Barry Warsaw ba...@list.org wrote: On Feb 20, 2015, at 07:25 PM, Andrew Stuart wrote: It’s workable as a part of the auth proxy but feels like it would fit better in the Mailman core database since the data is so tightly bound to Mailman resources. It’ll need an effective replication mechanism to ensure consistency with Mailman which is a challenge I’m not relishing solving. Do you think this has to be integrated into the core for 3.0? I'd still prefer to keep it separate for better experimentation and testing. If the design and API proves stable, then perhaps it'll make sense to integrate it with the core for 3.1. 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/andrew.stuart%40supercoders.com.au 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] GSoC 2015: brainstorming ideas suitable for beginners?
Barry Warsaw writes: On Feb 20, 2015, at 07:25 PM, Andrew Stuart wrote: It’s workable as a part of the auth proxy but feels like it would fit better in the Mailman core database since the data is so tightly bound to Mailman resources. It’ll need an effective replication mechanism to ensure consistency with Mailman which is a challenge I’m not relishing solving. Do you think this has to be integrated into the core for 3.0? I'd still prefer to keep it separate for better experimentation and testing. If the design and API proves stable, then perhaps it'll make sense to integrate it with the core for 3.1. I don't which way this argues, but Mailman 3 already needs effective replication mechanisms because Postorius and HyperKitty both add to the basic database schema. ___ 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 2015: brainstorming ideas suitable for beginners?
On Feb 20, 2015, at 07:25 PM, Andrew Stuart wrote: It’s workable as a part of the auth proxy but feels like it would fit better in the Mailman core database since the data is so tightly bound to Mailman resources. It’ll need an effective replication mechanism to ensure consistency with Mailman which is a challenge I’m not relishing solving. Do you think this has to be integrated into the core for 3.0? I'd still prefer to keep it separate for better experimentation and testing. If the design and API proves stable, then perhaps it'll make sense to integrate it with the core for 3.1. Cheers, -Barry pgpl_M1iHIOsZ.pgp Description: OpenPGP digital signature ___ 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 2015: brainstorming ideas suitable for beginners?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 20.02.2015 um 06:46 schrieb Terri Oda: Thanks all! I've put up stuff for the ideas I could describe well enough off the top of my head. Thank you Terri! Also, mentors, I've listed a few likely key people beside each project idea, but some of them are just a generic anyone can help with this -- if any of these particularly interests you, please put your name down. Google prefers we have actual names listed when we can (I'm not entirely sure why, as this hasn't proven to be helpful, but we can always change the names after the page is reviewed.) Applications are due 1900 UTC Friday, so around 13h from now! I completed the application yesterday and was planning to do a little more wiki-gardening today. So let's keep our fingers crossed. Who knows, maybe we get bonus points for persistence. ;-) Florian -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU5w1BAAoJEEceGbPdavl78HAIAJ9Rj4K+L56TCn6iQd/rjSXC KFpDXcwAQLITr4QRDYs8EAIHDYwp4X/i6ZyZBqyvtSodoeRKPzl6fDjTR+OnXCes BIKw72/zvwMqZLP3U2BY8DosUbWpYTy6G70o3+XoKnvXivIX5hTp50A8L+BbQzfU Rg+0uQ10DN6bJi8/yr5wXgK9qQv2aDoTGjriKhOvln6uT6agtnvFXA6JqiUoF1Es 1eqfdbO9bCl0SJ6HFwTkADwaG0psgaPQPWkKMaQQUB3INku09Duy1OEXuiWk+ceT DPd3iEuCJZ5uSNgZ8Gt1InZtW1T0ZJtw1UxZ/kQm7wJoSKUyGhsDOfZr4BOyKic= =cXki -END PGP SIGNATURE- ___ 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 2015: brainstorming ideas suitable for beginners?
[1] The additional user info bit possibly re-raises the big question of a central user data store for all Mailman components, which will clearly not be solved as part of a GSoC project, especially a beginner-friendly one. But we do already have a little bit of info, the user's email address and the gravatar (if there is one). So all we'd have to store is an opt-in flag somewhere in the Django-DB. I have implemented a central data store into the REST proxy server. It’s a simple table structure as follows: resource_type | resource_id | private/public | key |value user list domain server User access permissions for the data rows is the same as access to the resource_type resource_id It’s workable as a part of the auth proxy but feels like it would fit better in the Mailman core database since the data is so tightly bound to Mailman resources. It’ll need an effective replication mechanism to ensure consistency with Mailman which is a challenge I’m not relishing solving. as On 18 Feb 2015, at 4:42 am, Florian Fuchs f...@florianfuchs.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 17.02.2015 um 10:03 schrieb Terri Oda: I'd love some help brainstorming some actual beginner-friendly ideas, though, because I'm currently all idea'd out. Anyone want to suggest some simpler things they'd like to see in Mailman that we could maybe put on the list? Just from the top of my head, either as a combination of the two or as single projects (if fleshed out a bit further): - - A Dashboard for Admins/Owners/Moderators: A single page that lists all to dos in one place (subscription requests, held messages). Probably useful for owners/moderators of multiple lists. - - Subscriber pages: Let users opt-in to show their membership to other list members. Possibly along with some additional user information[1]. This could be useful for more private lists if you want to get an idea who your audience is. Florian [1] The additional user info bit possibly re-raises the big question of a central user data store for all Mailman components, which will clearly not be solved as part of a GSoC project, especially a beginner-friendly one. But we do already have a little bit of info, the user's email address and the gravatar (if there is one). So all we'd have to store is an opt-in flag somewhere in the Django-DB. Suggesting and idea does not mean you have to volunteer to mentor them, although I'm always looking for new mentors too! Terri ___ 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/f%40florianfuchs.com Security Policy: http://wiki.list.org/x/QIA9 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU432YAAoJEEceGbPdavl7CqEH/AvOLwc+qyWkmNw6Tahm6Jjb IHVnz4yv4sTFmdB9iqYXkOQqt7XgpEoIYUZwV+j7+vltDSYSh2qecKyVyQjBkEUC wc7hU8/czOw2E/I3MG1siRzCGeekGJSTFXf2NoKksUNca9DUQe0leNKs1VWXwaX5 uAsyitJxaiPJIsrKHeVhGO6g4rSmqBMi+Q+HTaBIZQqZZd1Qh7ZgUV4qXFuTjUXw D4Ae20sdFAdLD412e3LrgI58JiXRNIHBfWzN1Zg0RoY95rw/AuDafrlPT37I2E7O mahaaJAJrmPO3EimeDPmj1TTV7NWOpaU9Vlzd6H5BX4KweUxAaafYHFrkYXN/pU= =L+aD -END PGP SIGNATURE- ___ 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/andrew.stuart%40supercoders.com.au 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] GSoC 2015: brainstorming ideas suitable for beginners?
Thanks all! I've put up stuff for the ideas I could describe well enough off the top of my head. Also, mentors, I've listed a few likely key people beside each project idea, but some of them are just a generic anyone can help with this -- if any of these particularly interests you, please put your name down. Google prefers we have actual names listed when we can (I'm not entirely sure why, as this hasn't proven to be helpful, but we can always change the names after the page is reviewed.) Applications are due 1900 UTC Friday, so around 13h from now! Terri ___ 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 2015: brainstorming ideas suitable for beginners?
How about domain-wide settings for default list styles or maybe set a default list style for an entire mailman installation through Postorius? That could make the work of list-admins easy if they manage too many lists and don't want to do repetitive change in each and every list. Additionally ability to change the settings for only a subset of all lists could also be possible. On Tuesday 17 February 2015 02:33 PM, Terri Oda wrote: Hi all, In my role as org admin for Python, I'm trying to make sure we have more beginner-friendly ideas on the GSoC pages, and Mailman's among the groups that doesn't have any. How embarrassing for me as a Mailman developer. ;) It's also a problem for Mailman if we're applying as a separate organization, as Google seldom allows orgs unless they have a reasonable number of ideas suitable for open source newbies. (The idea behind this is that many students are very new to Open Source and we want them to at least get something out of the application process, learn how to set up their environments and learn about what it takes to get hired as a GSoC student. Even if they don't make it in their first year, they'll be much more ready for later years!) I'd love some help brainstorming some actual beginner-friendly ideas, though, because I'm currently all idea'd out. Anyone want to suggest some simpler things they'd like to see in Mailman that we could maybe put on the list? Suggesting and idea does not mean you have to volunteer to mentor them, although I'm always looking for new mentors too! Terri ___ 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/raj.abhilash1%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -- thanks, Abhilash Raj signature.asc Description: OpenPGP digital signature ___ 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 2015: brainstorming ideas suitable for beginners?
On Feb 18, 2015, at 12:24 AM, Abhilash Raj wrote: How about domain-wide settings for default list styles or maybe set a default list style for an entire mailman installation through Postorius? That could make the work of list-admins easy if they manage too many lists and don't want to do repetitive change in each and every list. Additionally ability to change the settings for only a subset of all lists could also be possible. That would be pretty cool. Right now the style system is pretty stupid, mostly a refactoring of the legacy set all the mailing list object attributes approach. I think we could do better, not only in the way we define and apply styles, but maybe also in removing the restriction that styles only take effect at list creation time. That could be a sufficiently large enough task for GSoC. Cheers, -Barry pgp4QYTh7IfW6.pgp Description: OpenPGP digital signature ___ 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 2015: brainstorming ideas suitable for beginners?
On 02/17/2015 04:03 AM, Terri Oda wrote: Hi all, In my role as org admin for Python, I'm trying to make sure we have more beginner-friendly ideas on the GSoC pages, and Mailman's among the groups that doesn't have any. How embarrassing for me as a Mailman developer. ;) It's also a problem for Mailman if we're applying as a separate organization, as Google seldom allows orgs unless they have a reasonable number of ideas suitable for open source newbies. (The idea behind this is that many students are very new to Open Source and we want them to at least get something out of the application process, learn how to set up their environments and learn about what it takes to get hired as a GSoC student. Even if they don't make it in their first year, they'll be much more ready for later years!) I'd love some help brainstorming some actual beginner-friendly ideas, though, because I'm currently all idea'd out. Anyone want to suggest some simpler things they'd like to see in Mailman that we could maybe put on the list? Suggesting and idea does not mean you have to volunteer to mentor them, although I'm always looking for new mentors too! Terri I don't know whether these are beginner-friendly enough, but here are some thoughts: * Per https://twitter.com/gvwilson/status/53527936287118 -- a tool that will take a thread from a Mailman mailing list and turn it into a thread on a GitHub issue. Or any kind of GitHub API integration tool (e.g., to automatically mail a Mailman list when a repo gets a new GitHub pull request) * A shared bookmarking tool that listens to a Mailman list, pulls out URLs that people mention, and adds them to an OPML file or Pinboard * Add new skins/themes to HyperKitty and/or Postorius (per https://fedorahosted.org/hyperkitty/ticket/83 and https://bugs.launchpad.net/postorius/+bug/1196608 ) * Expose new REST API features in Postorius https://bugs.launchpad.net/postorius/+bug/1062925 * HyperKitty: RSS feed generation https://fedorahosted.org/hyperkitty/ticket/84 * HyperKitty: Present all messages in a thread at once, and offer plaintext download of the whole thread https://fedorahosted.org/hyperkitty/ticket/88 -- Sumana Harihareswara http://brainwane.net ___ 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
