[GPC] Perl in OWASP
nicholas at periapt.co.uk
Tue Mar 30 18:48:51 EDT 2010
I've sent an email to Lorna. I can't send one to the leaders
mailing list due to permission issues. I attach what I attempted to send.
On 30/03/2010 19:04, dinis cruz wrote:
> I'm pretty sure that there is already good perl community around OWASP.
> Fell free to send an 'into & call to arms' email to the owasp-leaders
> list, and send Lorna (from OWASP's PR Department) a briefing on what
> you are trying to do so that she can include it on the next newsletter
> Dinis Cruz
> Blog: http://diniscruz.blogspot.com
> Twitter: http://twitter.com/DinisCruz
> Web: http://www.owasp.org/index.php/O2
> On 29 March 2010 22:59, Nicholas Bamber <nicholas at periapt.co.uk
> <mailto:nicholas at periapt.co.uk>> wrote:
> Hi Dinis,
> Yes this sounds about right. I am not quite sure what sure what if
> anything I should be doing in the immediate future. I really need
> some more volunteers. I've had some interest from London perl
> mongers but fate prevents me from attending any of their meetings
> for a few months.
> On 29/03/2010 15:33, dinis cruz wrote:
>> Hi Nicholas,
>> Actually what you are trying to create is what we at OWASP are
>> calling 'Security Ecosystems' (see
>> http://www.owasp.org/index.php/Security_Ecosystem_Project )
>> This is still a new idea (and there is quite a lot to define so
>> please help us), but we fell that it is part of the next
>> 'generation of OWASP' initiatives. The core idea is that we look
>> at each technology, platform or tool and create a set of
>> 'security focused' resources for it.
>> There are a number of 'ecosystem' creation efforts under way, so
>> if this makes sense please join them and lets build the 'OWASP
>> Perl Security Ecosystem' :)
>> Dinis Cruz
>> Blog: http://diniscruz.blogspot.com
>> Twitter: http://twitter.com/DinisCruz
>> Web: http://www.owasp.org/index.php/O2
>> On 27 March 2010 18:48, Nicholas Bamber <nicholas at periapt.co.uk
>> <mailto:nicholas at periapt.co.uk>> wrote:
>> Thinking about it what I currently intend is not a
>> project as such but rather a collection of projects. I have
>> put together a very basic page that I can point people to
>> (http://www.owasp.org/index.php/Perl). You will probably know
>> better how it should fit into the OWASP wiki. Maybe we could
>> have a Perl Category. Anyway next I'll start looking into
>> getting the perl community involved.
>> On 22/03/2010 20:39, Nicholas Bamber wrote:
>>> Thanks. No I had no specific questions. I just wondered
>>> if there is anything I should know before I start. I'll
>>> start with a page on the wiki pointing to relevant perl
>>> On 22/03/2010 16:59, dinis cruz wrote:
>>>> Sounds great, what are your specific questions? (I'm CCing
>>>> OWASP's GPC)
>>>> Dinis Cruz
>>>> On 22 Mar 2010, at 07:24, Nicholas Bamber
>>>> <nicholas at periapt.co.uk <mailto:nicholas at periapt.co.uk>> wrote:
>>>>> There are three things I would like to do in OWASP:
>>>>> 1 Bring my own stuff upto OWASP standard.
>>>>> 2 Producing a perl port of AntiSamy.
>>>>> 3 Advocating OWASP in the perl community.
>>>>> Initially I would focus on the last aim and just try to
>>>>> act as an interface between perl and OWASP. So I would
>>>>> start by creating a wiki page for perl. However I thought
>>>>> I had better discuss the with project committee members
>>>>> first (as well as reading the relevant documentation). I
>>>>> tried contacting Paulo via Linked and then I realized your
>>>>> email is on the OWASP webpage.
> *Nicholas Peter Bamber*
> *Email:* nicholas at periapt.co.uk <mailto:nicholas at periapt.co.uk>
> *Professional Profile
> * *
> *Periapt Technologies Ltd* <http://www.periapt.co.uk>
> Want a signature like this?
*Nicholas Peter Bamber*
*Email:* nicholas at periapt.co.uk <mailto:nicholas at periapt.co.uk>
*Periapt Technologies Ltd* <http://www.periapt.co.uk>
Want a signature like this? <http://www.linkedin.com/e/sig/47231258/>
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Perl a call to action.eml
Size: 5506 bytes
Desc: not available
Url : https://lists.owasp.org/mailman/private/global-projects-committee/attachments/20100330/ad48c68f/attachment-0001.bin
More information about the Global-projects-committee