From sayak1997sen at gmail.com Tue Jan 3 04:32:09 2017 From: sayak1997sen at gmail.com (Sayak Sen) Date: Tue, 3 Jan 2017 15:02:09 +0530 Subject: [Mailman-Developers] Aspiring for GSoC Message-ID: Hi everyone! I've already setup the mailman components and started to contribute in some of the bugs in Postorius. But recently, I get to know that Mailman may not be accepting projects based on Postorius. So, In what other Mailman component I should try contributing. I know some web-development, Python and of course Django. And yeah! this is my first time with open-source contributions, So I would be obliged to get your help. Regards, Sayak Sen (tech0) | +91 966 157 3582 Undergraduate, Computer Science & Engineering SRM University From siddhartha.gairola18 at gmail.com Wed Jan 4 10:33:48 2017 From: siddhartha.gairola18 at gmail.com (Siddhartha Gairola) Date: Wed, 4 Jan 2017 21:03:48 +0530 Subject: [Mailman-Developers] Reg: core and Hyperkitty issues Message-ID: Hi, I would like to work on beginner level issues which are currently active on mailman core and hyperkitty. Thanking you. Regards, Siddhartha From siddhartha.gairola18 at gmail.com Thu Jan 5 10:58:41 2017 From: siddhartha.gairola18 at gmail.com (Siddhartha Gairola) Date: Thu, 5 Jan 2017 21:28:41 +0530 Subject: [Mailman-Developers] Reg: Postorius Issue 127 Message-ID: Hi, I would like to work on Postorius issue 127 - https://gitlab.com/mailman/postorius/issues/127. I would be grateful if someone could tell me how to start solving this. Thank you. Regards, Siddhartha From turnbull.stephen.fw at u.tsukuba.ac.jp Thu Jan 5 20:30:17 2017 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Fri, 6 Jan 2017 10:30:17 +0900 Subject: [Mailman-Developers] Reg: Postorius Issue 127 In-Reply-To: References: Message-ID: <22638.62249.935139.299344@turnbull.sk.tsukuba.ac.jp> Siddhartha Gairola writes: > I would like to work on Postorius issue 127 - > https://gitlab.com/mailman/postorius/issues/127. > > I would be grateful if someone could tell me how to start solving this. You start by starting. ;-) "Claiming" the issue and posting here was a good start. :-) First, check with Nitish Kumar Dwivedi (https://gitlab.com/nitishkd) that s/he is not currently working on the issue to ensure no conflict over your contribution.[1] You don't need to wait for an answer to start working; it won't be useless duplication for a couple more steps. Now tell me[2] what you think you should do next. (Coding != developing. Developers are engineers who solve problems. We will help you when you get stuck, but you have to solve the problem. Don't worry, we'll wait. :-) Steve Footnotes: [1] No, 7 months silence != issue abandoned. Conflicts over credit are rare in Mailman; we are a pretty flexible, friendly and conscientious group in that respect. On the other hand, we do care about keeping each other in the loop. And it's possible that Nitish has a nearly complete solution in a private branch. If so, your work would likely be redundant -- if Nitish is in no hurry to work on it, try negotiating for joint credit: get that branch MR'ed, and then do the remaining work to integrate. [2] On the issue or on this list -- I will IGNORE personal mail if it doesn't have a reference to a public channel!! so check your headers before sending mail, this list does NOT munge Reply-To. I've assigned the issue to myself so I will get notifications. From siddhartha.gairola18 at gmail.com Fri Jan 6 14:53:46 2017 From: siddhartha.gairola18 at gmail.com (Siddhartha Gairola) Date: Sat, 7 Jan 2017 01:23:46 +0530 Subject: [Mailman-Developers] Reg: Postorius Issue 127 In-Reply-To: <22638.62249.935139.299344@turnbull.sk.tsukuba.ac.jp> References: <22638.62249.935139.299344@turnbull.sk.tsukuba.ac.jp> Message-ID: Thank you Steve for your mail. Will begin reading the code and try to figure out what to do next. Will get back to you once I make progress or have some difficulty. Regards, Siddhartha. On Fri, Jan 6, 2017 at 7:00 AM, Stephen J. Turnbull < turnbull.stephen.fw at u.tsukuba.ac.jp> wrote: > Siddhartha Gairola writes: > > > I would like to work on Postorius issue 127 - > > https://gitlab.com/mailman/postorius/issues/127. > > > > I would be grateful if someone could tell me how to start solving this. > > You start by starting. ;-) "Claiming" the issue and posting here was > a good start. :-) First, check with Nitish Kumar Dwivedi > (https://gitlab.com/nitishkd) that s/he is not currently working on > the issue to ensure no conflict over your contribution.[1] You don't > need to wait for an answer to start working; it won't be useless > duplication for a couple more steps. > > Now tell me[2] what you think you should do next. (Coding != developing. > Developers are engineers who solve problems. We will help you when > you get stuck, but you have to solve the problem. Don't worry, we'll > wait. :-) > > Steve > > Footnotes: > [1] No, 7 months silence != issue abandoned. Conflicts over credit > are rare in Mailman; we are a pretty flexible, friendly and > conscientious group in that respect. On the other hand, we do care > about keeping each other in the loop. And it's possible that Nitish > has a nearly complete solution in a private branch. If so, your work > would likely be redundant -- if Nitish is in no hurry to work on it, > try negotiating for joint credit: get that branch MR'ed, and then do > the remaining work to integrate. > > [2] On the issue or on this list -- I will IGNORE personal mail if it > doesn't have a reference to a public channel!! so check your headers > before sending mail, this list does NOT munge Reply-To. I've assigned > the issue to myself so I will get notifications. > > > > From barry at list.org Fri Jan 6 14:59:37 2017 From: barry at list.org (Barry Warsaw) Date: Fri, 6 Jan 2017 14:59:37 -0500 Subject: [Mailman-Developers] Reg: core and Hyperkitty issues In-Reply-To: References: Message-ID: <20170106145937.0f2990ef@subdivisions.wooz.org> On Jan 04, 2017, at 09:03 PM, Siddhartha Gairola wrote: >I would like to work on beginner level issues which are currently active on >mailman core and hyperkitty. Cool! Have you looked through the Gitlab issues for both trackers? Are there any that interest you? Cheers, -Barry From barry at list.org Fri Jan 6 15:02:17 2017 From: barry at list.org (Barry Warsaw) Date: Fri, 6 Jan 2017 15:02:17 -0500 Subject: [Mailman-Developers] Aspiring for GSoC In-Reply-To: References: Message-ID: <20170106150217.168a7840@subdivisions.wooz.org> On Jan 03, 2017, at 03:02 PM, Sayak Sen wrote: >I've already setup the mailman components and started to contribute in some >of the bugs in Postorius. But recently, I get to know that Mailman may not be >accepting projects based on Postorius. So, In what other Mailman component I >should try contributing. I know some web-development, Python and of course >Django. And yeah! this is my first time with open-source contributions, So I >would be obliged to get your help. Welcome Sayak! It's true, we haven't yet decided if we're going to participate in GSoC this year, but we of course still would still welcome your contributions. If you're into web development, both Postorius and HyperKitty are great places to start. There's no web front-end work in the Core, but there's still interesting things to do there. I'm hoping that we're winding down toward a 3.1 release now though. Cheers, -Barry From siddhartha.gairola18 at gmail.com Fri Jan 6 15:04:41 2017 From: siddhartha.gairola18 at gmail.com (Siddhartha Gairola) Date: Sat, 7 Jan 2017 01:34:41 +0530 Subject: [Mailman-Developers] Reg: Postorius Issue 127 Message-ID: I was going through the postorius code. So this is what we have to implement for postorius - "if the post is from a moderated member, the moderator has a checkbox to clear the member's moderation when accepting the post." But I am not too sure how to get this done. I guess it would require modifying some controller. If I could get some assistance on this, I would be grateful. Thank you. Regards, Siddhartha From barry at list.org Fri Jan 6 15:09:50 2017 From: barry at list.org (Barry Warsaw) Date: Fri, 6 Jan 2017 15:09:50 -0500 Subject: [Mailman-Developers] Contributing to Mailman Core In-Reply-To: References: Message-ID: <20170106150950.3f006ed6@subdivisions.wooz.org> On Dec 09, 2016, at 04:59 PM, Nikhil Rayaprolu wrote: >Hello, I would like to contribute to mailman core . Can any one mentor me >by picking some issues in core application which could make me understand >the code structure. and also guide me through understanding the core module. > >I made two merge requests to postorius and read the documentation of maiman >along with videos on mailman architecture by barry warshaw. Hi Nikhil; apologies for the delayed response. It seems that with travel and holidays, this message got buried in my inbox. I see that you have some interest in Core issue #300. Have you spent time since then looking at how REST works in Core? Do you have any additional questions? We're winding down development on 3.1 so this would be targeted for 3.2. We can discuss further on the specific issue, but if you have any general questions, this is the place to ask! Cheers, -Barry From siddhartha.gairola18 at gmail.com Sat Jan 7 09:08:42 2017 From: siddhartha.gairola18 at gmail.com (Siddhartha Gairola) Date: Sat, 7 Jan 2017 19:38:42 +0530 Subject: [Mailman-Developers] Reg: Writing tests for Mailman modules Message-ID: Hi, To get familiar with the code I wiould like to write some tests for mailman. Which module should I get started with? Also some prototypes for writing tests would be helpful. Thank you. Regards, Siddhartha Gairola From turnbull.stephen.fw at u.tsukuba.ac.jp Sat Jan 7 11:45:36 2017 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Sun, 8 Jan 2017 01:45:36 +0900 Subject: [Mailman-Developers] Reg: core and Hyperkitty issues In-Reply-To: <20170106145937.0f2990ef@subdivisions.wooz.org> References: <20170106145937.0f2990ef@subdivisions.wooz.org> Message-ID: <22641.6960.975638.437288@turnbull.sk.tsukuba.ac.jp> Barry Warsaw writes: > Cool! Have you looked through the Gitlab issues for both trackers? > Are there any that interest you? He and I are already working on Postorius #127. Kibitzers welcome! Steve From turnbull.stephen.fw at u.tsukuba.ac.jp Sat Jan 7 11:46:55 2017 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Sun, 8 Jan 2017 01:46:55 +0900 Subject: [Mailman-Developers] Reg: Postorius Issue 127 In-Reply-To: References: Message-ID: <22641.7039.853119.602275@turnbull.sk.tsukuba.ac.jp> Siddhartha Gairola writes: > So this is what we have to implement for postorius - > "if the post is from a moderated member, the moderator has a checkbox to > clear the member's moderation when accepting the post." Right. > But I am not too sure how to get this done. I guess it would require > modifying some controller. > If I could get some assistance on this, I would be grateful. Postorius is implemented as a Django application, and Django uses a modified MVC model. So you should be prepared for all of model (model), view (template), and controller (view) to be involved (in parens Django terms, outside MVC terms, somewhat stretched as necessary in Django). Model: since the user's moderation bit is already set, it must be present. Since you're just asked to clear it, which is a normal operation for bits, probably no change to model is needed. Template: implements checkbox formatting. Needs change. View: implements checkbox toggling and communication with model. Needs change. To find template, go to template directory (use find(1) or GUI equivalent on your platform), look through templates to find moderation page(s) (there may be more than one). To find code, grep through views for one which invokes that template. Don't promise this will get you what you want, but that's the way I would start. Gotta do other work now, back tomorrow evening (> 06:00 UTC). Steve From mark at msapiro.net Sat Jan 7 13:57:28 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 7 Jan 2017 10:57:28 -0800 Subject: [Mailman-Developers] Reg: Postorius Issue 127 In-Reply-To: <22641.7039.853119.602275@turnbull.sk.tsukuba.ac.jp> References: <22641.7039.853119.602275@turnbull.sk.tsukuba.ac.jp> Message-ID: On 01/07/2017 08:46 AM, Stephen J. Turnbull wrote: > > Model: since the user's moderation bit is already set, it must be > present. Since you're just asked to clear it, which is a normal > operation for bits, probably no change to model is needed. > > Template: implements checkbox formatting. Needs change. > > View: implements checkbox toggling and communication with model. > Needs change. In MM 3 it's a bit more complicated than that. The member's moderation is actually one of 6 possible values. These are None, hold, reject, discard, accept or defer with respective meanings "use the list's default", "hold for moderator approval", "reject the message", "discard the message", "accept the message immediately without considering other rules" or "continue to other rules in the chain". The only cases in which we will see a message held because of moderation are when the user's setting is hold or is None when the list default is hold, and probably the only case we want to deal with with a checkbox while approving the held message is switching from None to defer. The situation that #127 is addressing is the case where the list's default is hold so new member's posts are held, but once a moderator sees an on-topic post from a human member, the moderator can "clear" future holds which means switching the member's moderation to defer. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at list.org Sun Jan 8 12:58:01 2017 From: barry at list.org (Barry Warsaw) Date: Sun, 8 Jan 2017 12:58:01 -0500 Subject: [Mailman-Developers] Reg: Writing tests for Mailman modules In-Reply-To: References: Message-ID: <20170108125801.43ceb9c1@subdivisions.wooz.org> On Jan 07, 2017, at 07:38 PM, Siddhartha Gairola wrote: >To get familiar with the code I wiould like to write some tests for mailman. >Which module should I get started with? Also some prototypes for writing >tests would be helpful. One of the most useful things for Core would be to help boost coverage. Many of the core modules are covered at 100% but a lot of them aren't. Right now the test suite is gated at 93% overall, but you can see that some are dismal at < 90% (even 40% in one case!). I will gladly work with anybody who wants to help boost coverage toward the eventual goal of 100% coverage. Untested code is broken code! The best way to see coverage information is to run this with a checkout of Core: % tox -e py35-cov Adjust if necessary if you don't have Python 3.5 installed (i.e. py36-cov and py34-cov are also available). I'm very happy to answer questions about how to write tests, the testing infrastructure, etc. either here on this mailing list or on IRC. Cheers, -Barry From barry at list.org Mon Jan 9 21:56:55 2017 From: barry at list.org (Barry Warsaw) Date: Mon, 9 Jan 2017 21:56:55 -0500 Subject: [Mailman-Developers] [Mailman-i18n] Translation of Mailman 3 In-Reply-To: <7b9c8001-d4bc-e232-be2a-7e6c702f42bb@serve-me.info> References: <570D766A.9040509@serve-me.info> <570D7892.3000207@msapiro.net> <20160420095815.0f175625@subdivisions.wooz.org> <22296.16208.742523.449355@turnbull.sk.tsukuba.ac.jp> <20160517100630.5f815773.barry@wooz.org> <7b9c8001-d4bc-e232-be2a-7e6c702f42bb@serve-me.info> Message-ID: <20170109215655.494c5090@subdivisions.wooz.org> Reviving an ancient thread. On May 28, 2016, at 10:27 PM, Simon Hanna wrote: >I used Zanata, but found it not very intuitive to use. It's also >painfully slow. > >I'm unaware of any big projects that use zanata. Well openstack does, but >they use a self hosted version and that one is not faster. I'm not sure how >Mailman 2 was translated, but I guess most of the translators did it >offline. You can download translation files from pootle and later upload >them. So anyone that doesn't want to translate in the browser, can still do >it offline. Since gettext will be the interchange format, it will probably not be that difficult to switch to a different service if we ever find we need to. I appreciate your feedback on Zanata, and honestly we just need an i18n champion to make it happen. My apologies for such a long delay in responding here, but Simon, if you're still willing to take the lead on i18n, I will be happy to defer to your preferences. >So If you give me the ok, I write the gnu pootle maintainers and ask >them to create three projects for us. +1 - if you're still willing, let's do this. Core is very nearly ready to start rc'ing for 3.1 so I think this is a great time to being building the infrastructure for i18n. >I guess we could add links in postorius and hyperkitty that request >assistance with translation. +1 Cheers, -Barry From simon.hanna at serve-me.info Tue Jan 10 19:32:55 2017 From: simon.hanna at serve-me.info (Simon Hanna) Date: Wed, 11 Jan 2017 01:32:55 +0100 Subject: [Mailman-Developers] [Mailman-i18n] Translation of Mailman 3 In-Reply-To: <20170109215655.494c5090@subdivisions.wooz.org> References: <570D766A.9040509@serve-me.info> <570D7892.3000207@msapiro.net> <20160420095815.0f175625@subdivisions.wooz.org> <22296.16208.742523.449355@turnbull.sk.tsukuba.ac.jp> <20160517100630.5f815773.barry@wooz.org> <7b9c8001-d4bc-e232-be2a-7e6c702f42bb@serve-me.info> <20170109215655.494c5090@subdivisions.wooz.org> Message-ID: <7c5ac727-fce0-5d81-14e7-6b73ddc46dd7@serve-me.info> On 01/10/2017 03:56 AM, Barry Warsaw wrote: > Reviving an ancient thread. > > On May 28, 2016, at 10:27 PM, Simon Hanna wrote: > >> I used Zanata, but found it not very intuitive to use. It's also >> painfully slow. >> >> I'm unaware of any big projects that use zanata. Well openstack does, but >> they use a self hosted version and that one is not faster. I'm not sure how >> Mailman 2 was translated, but I guess most of the translators did it >> offline. You can download translation files from pootle and later upload >> them. So anyone that doesn't want to translate in the browser, can still do >> it offline. > Since gettext will be the interchange format, it will probably not be that > difficult to switch to a different service if we ever find we need to. > > I appreciate your feedback on Zanata, and honestly we just need an i18n > champion to make it happen. My apologies for such a long delay in responding > here, but Simon, if you're still willing to take the lead on i18n, I will be > happy to defer to your preferences. > >> So If you give me the ok, I write the gnu pootle maintainers and ask >> them to create three projects for us. > +1 - if you're still willing, let's do this. Core is very nearly ready to > start rc'ing for 3.1 so I think this is a great time to being building the > infrastructure for i18n. > >> I guess we could add links in postorius and hyperkitty that request >> assistance with translation. > +1 So it looks like the gnu pootle server is not up anymore. So I guess Zanata is the way to go. The projects are already in place, we would just have to update the pot files I initially uploaded. I updated Hyperkitty and Postorius since I'm familiar with django translation. You can start translating them right aways over at: https://translate.zanata.org/iteration/view/postorius/1.0.3 https://translate.zanata.org/iteration/view/hyperkitty/1.0.3 Mailman on the other hand currently doesn't have any infrastructure, and I don't think I know enough to be sure that I get all the strings in the correct format. Can someone help with that? I'll start working on a wiki page and create merge requests for Hyperkitty and Postorius that include a link to the wiki asking for help. I'll check the other projects and find out if we need to create translation projects for them too. All registered users should be able to translate. I'll enable reviews which allow certain users more rights. If you want to be responsible for a language you should be able to request that from the interface or you can contact me mentioning your username. cheers, Simon From x.abhishek.flyhigh at gmail.com Thu Jan 12 22:56:17 2017 From: x.abhishek.flyhigh at gmail.com (Abhishek Shrivastava) Date: Fri, 13 Jan 2017 09:26:17 +0530 Subject: [Mailman-Developers] Developer Introduction Message-ID: Namaste Developers! I am Abhishek Shrivastava, from India. After lurking around in the mailman list for over a year now, I want to start contributing to the project. I'd love to get involved with mailman core and postorius. Currently I am setting up my development environment and going through the mailman architecture document http://aosabook.org/en/mailman.html. I am also looking through the issue tracker for beginner friendly bugs to fix. Regards, Abhishek Shrivastava From ribanez at sciops.esa.int Fri Jan 13 10:08:51 2017 From: ribanez at sciops.esa.int (Ruben Ibanez) Date: Fri, 13 Jan 2017 16:08:51 +0100 (CET) Subject: [Mailman-Developers] About Mailman 3.1 release date Message-ID: <26798_1484320124_5878ED7C_26798_7708_1_862799767.6884149.1484320131448.JavaMail.zimbra@sciops.esa.int> Dear Mailman Developers, >From our organization we are really looking forward for the coming 3.1 release of Mailman as we would like to migrate our current Mailman 2.1. We are looking that in your git page https://gitlab.com/mailman/mailman/milestones/2 the progress is at 98%, so we hope it will be ready in the coming days. Great! Regarding this, when the new 3.1 version is finished, will it be in a 'Beta' phase, or directly a public release? In the case of being a Beta release, do you know an estimate time of when it will became fully released? Many thanks! Regards, RI ------------------------------------------------------------------ Aurora Technology B.V. for ESA - European Space Agency Ruben Ibanez Computer Engineer / System Analyst Sciops technical IT Unit - SITU Data and Engineering Division Operations Department, Directorate of Science European Space Astronomy Centre (ESAC) European Space Agency (ESA) Camino bajo del Castillo s/n, Urb. Villafranca del Castillo P.O. Box 78 - 28691 Villanueva de la Ca?ada, Madrid, Spain ribanez at sciops.esa.int | www.esa.int | T +34 91 81 31 518 ------------------------------------------------------------------ ----- This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. From barry at list.org Fri Jan 13 11:46:08 2017 From: barry at list.org (Barry Warsaw) Date: Fri, 13 Jan 2017 11:46:08 -0500 Subject: [Mailman-Developers] About Mailman 3.1 release date In-Reply-To: <26798_1484320124_5878ED7C_26798_7708_1_862799767.6884149.1484320131448.JavaMail.zimbra@sciops.esa.int> References: <26798_1484320124_5878ED7C_26798_7708_1_862799767.6884149.1484320131448.JavaMail.zimbra@sciops.esa.int> Message-ID: <20170113114608.64e9b459@subdivisions.wooz.org> Hi Ruben, On Jan 13, 2017, at 04:08 PM, Ruben Ibanez wrote: >From our organization we are really looking forward for the coming 3.1 >release of Mailman as we would like to migrate our current Mailman 2.1. We >are looking that in your git page >https://gitlab.com/mailman/mailman/milestones/2 the progress is at 98%, so we >hope it will be ready in the coming days. Great! I should point out this this milestone technically only describes Core. A potentially more comprehensive overview for the entire suite is at: https://gitlab.com/groups/mailman/milestones/31?title=3.1 but TBH, I'm not sure whether Postorius and HyperKitty are as slavishly focused on milestoning as I am for Core. ;) >Regarding this, when the new 3.1 version is finished, will it be in a 'Beta' >phase, or directly a public release? Beta 2 of Core is already available on PyPI: https://pypi.python.org/pypi/mailman/3.1.0b2 >In the case of being a Beta release, do you know an estimate time of when it >will became fully released? The last major feature for 3.1 Core is done (DMARC mitigation) so we just have a few more minor issues to pick off. Mark Sapiro is already running all the git HEADs on lists.mailman3.org so we're essentially testing integration in production already. We need to concentrate on finishing Postorius and HyperKitty (and mailmanclient, but that should be easy). It doesn't look like a ton of work, but it probably could use some well-placed help here and there. I can't give you an ETA, but once Core is at 100% milestone, I'll release it as an RC, and then jump over to the other projects to help. I do think we're close enough for folks to start using it in anger, and more importantly, providing feedback, bugs, and code. Cheers, -Barry From stephanwehner at gmail.com Thu Jan 26 11:32:48 2017 From: stephanwehner at gmail.com (Stephan Wehner) Date: Thu, 26 Jan 2017 08:32:48 -0800 Subject: [Mailman-Developers] Mailman 3 Dockerfile Message-ID: I've been working with the Dockerfile at https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile for setting up Mailman 3. The page doesn't say who to contact. Is this mailing list a good place to ask questions about where I'm stuck? Stephan From terri at toybox.ca Thu Jan 26 12:51:40 2017 From: terri at toybox.ca (Terri Oda) Date: Thu, 26 Jan 2017 09:51:40 -0800 Subject: [Mailman-Developers] Mailman 3 Dockerfile In-Reply-To: References: Message-ID: <4B53ED25-6ECC-471C-888A-FEE4DF7DD5EE@toybox.ca> Well, my name is all over it so I'm not sure it's true that there's no more obvious contact person than this list... But this list is the correct place, yes. :) I think we have a few better dockerfiles out in the community now, so maybe folk who've set them up would like to chime in? Terri On January 26, 2017 8:32:48 AM PST, Stephan Wehner wrote: >I've been working with the Dockerfile at > >https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > >for setting up Mailman 3. > >The page doesn't say who to contact. > >Is this mailing list a good place to ask questions about where I'm >stuck? > >Stephan >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers at 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/terri%40toybox.ca > >Security Policy: http://wiki.list.org/x/QIA9 From simon.hanna at serve-me.info Thu Jan 26 13:38:15 2017 From: simon.hanna at serve-me.info (Simon Hanna) Date: Thu, 26 Jan 2017 19:38:15 +0100 Subject: [Mailman-Developers] Mailman 3 Dockerfile In-Reply-To: References: Message-ID: <6E6C33BD-89AF-452A-8ED3-295D7155382B@serve-me.info> On 26 January 2017 17:32:48 GMT+01:00, Stephan Wehner wrote: >I've been working with the Dockerfile at > >https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > >for setting up Mailman 3. > >The page doesn't say who to contact. > >Is this mailing list a good place to ask questions about where I'm >stuck? > >Stephan I guess you can ask here. I wrote a couple of docker files that were mainly intended for testing/demoing. It really depends on what you want to do with the containers and how (if) you want to deploy them. I still haven't figured out a way to connect Mailman to an "outside" postfix. Please note that mailman-bundler currently doesn't produce a usable environment. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From barry at list.org Thu Jan 26 14:57:16 2017 From: barry at list.org (Barry Warsaw) Date: Thu, 26 Jan 2017 14:57:16 -0500 Subject: [Mailman-Developers] Mailman 3 Dockerfile In-Reply-To: <6E6C33BD-89AF-452A-8ED3-295D7155382B@serve-me.info> References: <6E6C33BD-89AF-452A-8ED3-295D7155382B@serve-me.info> Message-ID: <20170126145716.4dcc5ad4@subdivisions.wooz.org> On Jan 26, 2017, at 07:38 PM, Simon Hanna wrote: >Please note that mailman-bundler currently doesn't produce a usable >environment. I think bundler does more harm than good. We should probably just abandon it, we don't really have anything better. I don't have any strong opinions about what technology to use (e.g. Docker, Salt, Chef, Juju, etc.) other than it should be relatively easy to use on a wide variety of *nix platforms. It doesn't need to handle anything more than the simple common case of deploying it all to the same server. That's not to say that we can't point to lots of good alternatives, and even distro packages once they're available. Cheers, -Barry From stephanwehner at gmail.com Fri Jan 27 11:18:21 2017 From: stephanwehner at gmail.com (Stephan Wehner) Date: Fri, 27 Jan 2017 08:18:21 -0800 Subject: [Mailman-Developers] Mailman 3 Dockerfile In-Reply-To: <4B53ED25-6ECC-471C-888A-FEE4DF7DD5EE@toybox.ca> References: <4B53ED25-6ECC-471C-888A-FEE4DF7DD5EE@toybox.ca> Message-ID: On Thu, Jan 26, 2017 at 9:51 AM, Terri Oda wrote: > Well, my name is all over it so I'm not sure it's true that there's no more > obvious contact person than this list... But this list is the correct place, > yes. :) > Ok good, sorry, wasn't aware. > I think we have a few better dockerfiles out in the community now, so maybe > folk who've set them up would like to chime in? Ok, I did find a few more Dockerfiles, searching the web; I'll look into those. Thanks for now! Stephan > Terri > > On January 26, 2017 8:32:48 AM PST, Stephan Wehner > wrote: >> >> I've been working with the Dockerfile at >> >> https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile >> >> for setting up Mailman 3. >> >> The page doesn't say who to contact. >> >> Is this mailing list a good place to ask questions about where I'm stuck? >> >> Stephan >> ________________________________ >> >> Mailman-Developers mailing list >> Mailman-Developers at 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/terri%40toybox.ca >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > -- Stephan Wehner -> http://stephan.sugarmotor.org (blog and homepage) -> http://twitter.com/stephanwehner / @stephanwehner -> http://www.thrackle.org Through http://www.buckmaster.ca, my company: -> http://whatzilla.com -> http://loggingit.com -> http://www.trafficlife.com -> http://clocklist.com -> http://stephansmap.org From simon.hanna at serve-me.info Fri Jan 27 13:31:07 2017 From: simon.hanna at serve-me.info (Simon Hanna) Date: Fri, 27 Jan 2017 19:31:07 +0100 Subject: [Mailman-Developers] Mailman 3 Dockerfile In-Reply-To: <20170126145716.4dcc5ad4@subdivisions.wooz.org> References: <6E6C33BD-89AF-452A-8ED3-295D7155382B@serve-me.info> <20170126145716.4dcc5ad4@subdivisions.wooz.org> Message-ID: <667e9df0-9056-859e-eb01-5ef381eae4a8@serve-me.info> On 01/26/2017 08:57 PM, Barry Warsaw wrote: > On Jan 26, 2017, at 07:38 PM, Simon Hanna wrote: > >> Please note that mailman-bundler currently doesn't produce a usable >> environment. > I think bundler does more harm than good. We should probably just abandon it, > we don't really have anything better. I don't have any strong opinions about > what technology to use (e.g. Docker, Salt, Chef, Juju, etc.) other than it > should be relatively easy to use on a wide variety of *nix platforms. It > doesn't need to handle anything more than the simple common case of deploying > it all to the same server. That's not to say that we can't point to lots of > good alternatives, and even distro packages once they're available. > > Cheers, > -Barry I just updated my repository I use for my deployment which can be found here https://gitlab.com/thelinuxguy/mailman-suite following it's readme should result in a usable installation. I can work on providing an ansible playbook