[Owasp-board] SWAMP

Jim Manico jim.manico at owasp.org
Thu Oct 16 20:35:56 UTC 2014


Next move is on them, Fabio. They suggested that they would open source 
several components as OWASP projects but I have no seen any movement there.

I also continue to believe that we as OWASP should not be endorsing any 
service or product per our current bylaws and other guidelines.

Aloha,
- Jim

On 10/16/14, 4:31 PM, Fabio Cerullo wrote:
> hiya,
>
> just wondering if we receive any further updates regarding SWAMP 
> roadmap, etc?
>
> thanks
> Fabio
>
> On Mon, Sep 22, 2014 at 5:10 PM, Jim Manico <jim.manico at owasp.org 
> <mailto:jim.manico at owasp.org>> wrote:
>
>     SWAMP is a fairly prolific sponsor. That does not mean they get
>     any special pass regarding our bylaws and other rules of play, but
>     our responsibility on the board certainly is fundraising and
>     financial security of OWASP.
>
>     So having one •clear• point of contact for strategic partnership
>     is a nice courtesy to extend to our sponsor. Again, that does not
>     mean they get any special pass regarding our bylaws and other
>     rules of play.
>
>     Aloha,
>     --
>     Jim Manico
>     @Manicode
>     (808) 652-3805
>
>     On Sep 22, 2014, at 11:35 AM, Michael Coates
>     <michael.coates at owasp.org <mailto:michael.coates at owasp.org>> wrote:
>
>>     Agreed. Just a suggestion so we don't overwhelm swamp with
>>     multiple threads or conversations from different sources.
>>
>>     On Sep 22, 2014, at 1:55 AM, Eoin Keary <eoin.keary at owasp.org
>>     <mailto:eoin.keary at owasp.org>> wrote:
>>
>>>     I don't think once it is a project we need board involvement. Up
>>>     to then I think we would.
>>>
>>>     Eoin Keary
>>>     Owasp Global Board
>>>     +353 87 977 2988 <tel:%2B353%2087%20977%202988>
>>>
>>>
>>>     On 22 Sep 2014, at 03:44, Michael Coates
>>>     <michael.coates at owasp.org <mailto:michael.coates at owasp.org>> wrote:
>>>
>>>>     Board
>>>>
>>>>     May I suggest we establish a point of contact within the board
>>>>     to coordinate discussions with our partner?
>>>>
>>>>      This way we have clear requests to our partners and we avoid
>>>>     inadvertently copying people into long discussions while we
>>>>     hash out ideas "internally".
>>>>
>>>>     Michael
>>>>
>>>>     On Sep 21, 2014, at 6:00 PM, Eoin Keary <eoin.keary at owasp.org
>>>>     <mailto:eoin.keary at owasp.org>> wrote:
>>>>
>>>>>     I'd think a call to go through would be beneficial.
>>>>>
>>>>>
>>>>>     Eoin Keary
>>>>>     Owasp Global Board
>>>>>     +353 87 977 2988 <tel:%2B353%2087%20977%202988>
>>>>>
>>>>>
>>>>>     On 21 Sep 2014, at 20:22, Tom Brennan - proactiveRISK
>>>>>     <tomb at proactiverisk.com <mailto:tomb at proactiverisk.com>> wrote:
>>>>>
>>>>>>     Your looking for updated in edition to:
>>>>>>     https://continuousassurance.org/technical-resources/project-roadmap/
>>>>>>
>>>>>>     The SWAMP FAQ is useful and will be referenced
>>>>>>     https://continuousassurance.org/faqs/
>>>>>>
>>>>>>
>>>>>>
>>>>>>     On Sep 21, 2014, at 5:54 PM, Jim Manico <jim.manico at owasp.org
>>>>>>     <mailto:jim.manico at owasp.org>> wrote:
>>>>>>
>>>>>>>     +1 Eoin.
>>>>>>>
>>>>>>>     Patrick,
>>>>>>>
>>>>>>>     I'm eager to find all of the various places where OWASP and
>>>>>>>     SWAMP intersect! I think there is a lot we can do for each
>>>>>>>     other in terms of helping the community achieve excellence
>>>>>>>     in application security.
>>>>>>>
>>>>>>>     Aloha,
>>>>>>>     Jim
>>>>>>>
>>>>>>>
>>>>>>>     On 9/21/14, 12:47 PM, Eoin Keary wrote:
>>>>>>>>     Hi Patrick,
>>>>>>>>     Good meeting this last week.
>>>>>>>>
>>>>>>>>     Can we look at next steps assuming we can all agree the
>>>>>>>>     openness of SWAMP is understood.
>>>>>>>>     Items like the roadmap would be a good discussion point to
>>>>>>>>     kick off.
>>>>>>>>     Thanks,
>>>>>>>>     Eoin
>>>>>>>>
>>>>>>>>
>>>>>>>>     Eoin Keary
>>>>>>>>     Owasp Global Board
>>>>>>>>     +353 87 977 2988 <tel:%2B353%2087%20977%202988>
>>>>>>>>
>>>>>>>>     _______________________________________________
>>>>>>>>     Owasp-board mailing list
>>>>>>>>     Owasp-board at lists.owasp.org
>>>>>>>>     <mailto:Owasp-board at lists.owasp.org>
>>>>>>>>     https://lists.owasp.org/mailman/listinfo/owasp-board
>>>>>>>
>>>>>>>     _______________________________________________
>>>>>>>     Owasp-board mailing list
>>>>>>>     Owasp-board at lists.owasp.org <mailto:Owasp-board at lists.owasp.org>
>>>>>>>     https://lists.owasp.org/mailman/listinfo/owasp-board
>>>>>     _______________________________________________
>>>>>     Owasp-board mailing list
>>>>>     Owasp-board at lists.owasp.org <mailto:Owasp-board at lists.owasp.org>
>>>>>     https://lists.owasp.org/mailman/listinfo/owasp-board
>>>>     _______________________________________________
>>>>     Owasp-board mailing list
>>>>     Owasp-board at lists.owasp.org <mailto:Owasp-board at lists.owasp.org>
>>>>     https://lists.owasp.org/mailman/listinfo/owasp-board
>>     _______________________________________________
>>     Owasp-board mailing list
>>     Owasp-board at lists.owasp.org <mailto:Owasp-board at lists.owasp.org>
>>     https://lists.owasp.org/mailman/listinfo/owasp-board
>
>     _______________________________________________
>     Owasp-board mailing list
>     Owasp-board at lists.owasp.org <mailto:Owasp-board at lists.owasp.org>
>     https://lists.owasp.org/mailman/listinfo/owasp-board
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20141016/4b48a0d4/attachment-0001.html>


More information about the Owasp-board mailing list