[OWASP-TESTING] Next stage

Eoin Keary eoinkeary at hotmail.com
Wed Jun 22 06:39:35 EDT 2005

Cool shall have a draft to you in the next two weeks.

Regarding contribution, Actually I have the same problem with people coming 
to meetings.
It seems to me people are joining OWASP so they can say on their CV's 
"member of OWASP" but they dont contribute at all.


>From: Daniel Cuthbert <daniel.cuthbert at owasp.org>
>To: Eoin Keary <eoinkeary at hotmail.com>
>CC: owasp-testing at lists.sourceforge.net
>Subject: Re: [OWASP-TESTING] Next stage
>Date: Wed, 22 Jun 2005 11:11:59 +0100
>I haven't put a word limit on the sections, so feel free to go as  deep as 
>you need to (ill be editing them to make it flow etc, so no  worries about 
>On another note, for a list that has over 80 people subscribed, ive  only 
>seen 4 offers!
>I will give it a week and the people who havent contacted me, will be  
>removed from the list. Yes this is harsh but this isnt a freeloading  list 
>and it does require input from everyone on the list (work/time  constraints 
>are taken into consideration)
>On 22 Jun 2005, at 09:47, Eoin Keary wrote:
>>Dan, put me down for the code review part as discussed.
>>PS. Do we have a maximum word count/size for each section.?/
>>>From: Daniel Cuthbert <daniel.cuthbert at owasp.org>
>>>To: owasp-testing at lists.sourceforge.net
>>>Subject: [OWASP-TESTING] Next stage
>>>Date: Tue, 21 Jun 2005 10:05:21 +0100
>>>Morning all,
>>>Sorry for the short break in the testing guide progress, the real   world 
>>>caught up with me.
>>>Attached are the documents needed for the next part of the guide,  and  
>>>they are:
>>>Testing Guide II Structure.doc
>>>This is the final TOC as we agreed and next to each section, there  is  
>>>the option to add your name and your e-mail address(i.e you  will be  
>>>writing this section)
>>>If you could structure all your submissions using this template  (you  
>>>can use any format you like, word/text/xml, as long as i can  read it  on 
>>>a mac!)
>>>Guidelines for creating sections:
>>>Plagiarism won't be accepted.
>>>This testing guide should reflect the experience you all have in   
>>>application testing. One of the benefits of OWASP is that the  wealth  of 
>>>experience from the contributors enables the reader to  understand  the 
>>>section they are reading, as it is presented in a  well structured  
>>>format, which unlike a large amount of research  papers on the web  
>>>today, isn't normally the case.
>>>- Try and use examples where possible and also let other "non-  security" 
>>>individuals read what you have written. This ensures  that  it makes 
>>>sense to everyone and not just the hardcore  penetration  testers out 
>>>- I understand everyone has a life and work commitments, so  please  
>>>don't select loads of sections if you know you may not be  able to  
>>>commit to them in the end run.
>>>- Contact me if you have any issues during this next phase
>>>I think we should aim to have all the sections written by mid  August,  
>>>how does this sound for everyone?
>>>Obviously if you feel there is a section missing from the TOC, by  all  
>>>means contact me
>>>Look forward to seeing the work coming in
>>>Daniel Cuthbert
>>><< template1.htm >>
>>><< Testing_Guide_II_structure.doc >>
>>It's finally here! Download Messenger 7.0 - still FREE http:// 

Send a sexy animated wink with Messenger 7.0 - FREE download! 

More information about the Owasp-testing mailing list