Re: [Mod-security-developers] 2nd ModSecurity(-dev) community meeting
Brought to you by:
victorhora,
zimmerletw
From: Felipe C. <FC...@tr...> - 2016-01-25 18:55:27
|
Hi, The doodle for the 2nd ModSecurity(-dev) community meeting is now closed. The meeting will be held on Wed (27th) at #modsecurity channel at FreeNode. Further information: http://doodle.com/poll/tc9dydh2t6d4quwn Br., Felipe “Zimmerle” Costa Security Researcher, Lead Developer ModSecurity. Trustwave | SMART SECURITY ON DEMAND www.trustwave.com <http://www.trustwave.com/> On 1/18/16, 11:21 AM, "Felipe Costa" <FC...@tr...> wrote: >Hi Guys, > >I would like to invite you the second ModSecurity(-dev) community meeting. >This invitation is extended to everyone which follow or participate actively >on the ModSecurity community. > >The meeting agenda will be: > - Review of every open topic from the last meeting. > - Open Issues on GitHub. > - Open Merge requests on GitHub. > - Release dates (and content?) for v2.9.1. > - State of v3, open for question, answers and ideas. > >The meeting will be held at #modsecurity channel at FreeNode. > >The suggested date is: 2015-01-25 (Mon). > >Please use Doodle to tell the best date/time for you: > >http://doodle.com/poll/tc9dydh2t6d4quwn > >If you think that we should add or remove something from the agenda, please tell. > >The minutes from our last meeting can be found here: >https://www.modsecurity.org/developers/meetings/modsecurity.2015-10-14-19.06.html > > > >Br., >Felipe “Zimmerle” Costa >Security Researcher, SpiderLabs > >Trustwave | SMART SECURITY ON DEMAND >www.trustwave.com <http://www.trustwave.com/> > > > > ________________________________ This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. |