[Owasp-leaders] Retiring Mailman - the plan

Wed Feb 27 14:41:08 UTC 2019

@Dirk Wetter <dirk at owasp.org>
  looks like you are volunteering to create an infrastructure committee
under committee 2.0. Good on you ;)

But seriously, it would be time better spent, rather then most people
giving out/ making suggestions, take some action and get involved. We have
limited resources and any help is welcome - =I do like the sounds of an
infrastructure committee ;)

Owen Pendlebury @pendo19
Vice- Chair OWASP Global Board of Directors
OWASP Ireland-Dublin https://www.owasp.org/index.php/Ireland-Dublin
 @AppSecIreland
OWASP AppSec EU https://2018.appsec.eu @appseceu

*Consider giving back, and supporting the open source community by becoming
a member <https://www.owasp.org/index.php/Membership> or making a donation
<https://www.owasp.org/index.php/Donate> today! *

On Wed, 27 Feb 2019 at 14:28, Dirk Wetter <dirk at owasp.org> wrote:

> Hi,
>
> all. Please keep in mind that a fool with a tool is still a fool.
>
> Any CMS -- Wikis are belonging to the CMS category too -- sucks if you
> can't operate it or you
> don't have a housekeeper taking care in different respects of the content.
>
> Discussion around mailman: I am deeply concerned how we operate our
> infrastructure (patches
> missing for five years, not setting priorities) and how we make decisions.
> I have an
> infrastructure background even before Linux was available.
>
> It was kind of a frustrating experience for me to argue with either
> blackholes here (no
> response), getting the same responses over and over without replying to my
> arguments or just
> shouts on the mailing list "discourse", "tool X". It was just wasted life
> time ...
>
> Maybe it's also a mindset / cultural difference, I don't know.
>
>
> Dirk
>
>
>
>
> On 27.02.19 14:02, Owen Pendlebury wrote:
> > Hi Tom,
> >
> > This is something the current board has spoken about and want to
> progress. It’s on it’s way
> >
> > On Wed 27 Feb 2019 at 12:40, Tom Brennan <tomb at owasp.org <mailto:
> tomb at owasp.org>> wrote:
> >
> >     Clap clap clap!
> >
> >     Alcon;
> >     Maybe next is the OWASP Website?  We spend $15,000 and then.... no
> progress
> >
> >     The plan, the details here;
> >
> https://www.owasp.org/index.php/OWASP_Initiatives_Global_Strategic_Focus/website_project
> >
> >     *Tom Brennan, Chapter/Project Leader*
> >
> >     *OWASP Foundation, NYC Metro*
> >
> >     *1 (973) 202-0122 | www.owasp.org <http://www.owasp.org>*
> >
> >
> >     On Feb 26, 2019, at 8:45 PM, Matt Tesauro <
> matt.tesauro at owaspfoundation.org
> >     <mailto:matt.tesauro at owaspfoundation.org>> wrote:
> >
> >>     TLDR:  OWASP will be retiring mailman on March 22, 2019.  Google
> Groups will be used for
> >>     mail lists going forward.  List owners can choose to migrate to
> Google Groups during this
> >>     process.
> >>
> >>     Full details at
> https://www.owasp.org/index.php/Staff-Projects/Mailman-EOL
> >>
> >>     Members of the remaining list can expect more notifications during
> this process.
> >>
> >>     Bit of background:  There's been discussion off and on for years
> about upgrading Mailman,
> >>     retiring mailman, moving to other, similar things, etc.  Due to a
> bunch of factors listed
> >>     in the wiki page linked above, it has been decided that Mailman
> will be retired and any
> >>     community group wanting to have a mail list will use Google
> Groups.  Some communities
> >>     (like OWASP Zap) have been using Google Groups for years.  Some
> chapters who have moved
> >>     to the Foundation's Meetup Pro account, no longer see a need for a
> mail list.  The choice
> >>     is yours.
> >>
> >>     Additionally, as part of the 2019 planning which happened last week
> at the OWASP
> >>     Foundation Staff Summit, it has been decided to discontinue
> Discourse and move any
> >>     'category' which wants a mail list to Google Groups.
> >>
> >>     If you are a list owner, expect future correspondence about
> migrating your list to Google
> >>     Groups  - I will directly contact the email addresses that are list
> owners.  The lists
> >>     which will be migrated are shown at
> https://lists.owasp.org/mailman/listinfo (obviously
> >>     that URL doesn't show private lists)
> >>
> >>     Cheers!
> >>
> >>     --
> >>     -- Matt Tesauro
> >>     *OWASP Foundation*
> >>     Director of Community and Operations
> >>     matt.tesauro at owaspfoundation.org <mailto:
> matt.tesauro at owaspfoundation.org>
> >>
> >>     Consider giving back, and supporting the open source community by
> becoming a member
> >>     <https://www.owasp.org/index.php/Membership> or making a donation
> >>     <https://www.owasp.org/index.php/Donate> today!
> >>
> >>     _______________________________________________
> >>     OWASP-Leaders mailing list
> >>     OWASP-Leaders at lists.owasp.org <mailto:OWASP-Leaders at lists.owasp.org
> >
> >>     https://lists.owasp.org/mailman/listinfo/owasp-leaders
> >     _______________________________________________
> >     OWASP-Leaders mailing list
> >     OWASP-Leaders at lists.owasp.org <mailto:OWASP-Leaders at lists.owasp.org>
> >     https://lists.owasp.org/mailman/listinfo/owasp-leaders
> >
> > --
> > Owen Pendlebury @pendo19
> > Vice-Chair OWASP Global Board of Directors
> >
> > _______________________________________________
> > OWASP-Leaders mailing list
> > OWASP-Leaders at lists.owasp.org
> > https://lists.owasp.org/mailman/listinfo/owasp-leaders
> >
>
> --
> OWASP Volunteer
> Send me encrypted mails (Key ID 0xD0A74569)
> @drwetter
>
> _______________________________________________
> OWASP-Leaders mailing list
> OWASP-Leaders at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-leaders
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-leaders/attachments/20190227/b68f7ea6/attachment.html>