On 26 January 2017 17:32:48 GMT+01:00, Stephan Wehner <stephanwehner(a)gmail.com> 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.
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
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(a)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.
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
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
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
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