[Owasp-testing] OWASP Testing Guide v4 call for contributions

Andrew Muller andrew.muller at owasp.org
Mon Aug 26 15:20:51 UTC 2013

Hi guys,
  Here cometh the whip! ;) We're nearing the end of the August sprint on
the Test Guide and there is still lots to be done. There have been some
excellent articles submitted by some of the world's leading webappsec
researchers and testers.

If you're unable to continue contributing, or you feel you've
over-committed, then please let us know and we'll help you out. Some folks
are working offline and then posting the final version to the wiki, so the
wiki isn't the final word on where the Test Guide is at.

If you could please give us an update on your progress, we can plan our
next move.

Thanks again for your efforts in helping us revamp the Test Guide!


On Tue, Jul 30, 2013 at 11:26 PM, Andrew Muller <andrew.muller at owasp.org>wrote:

> Hi OWASP testers,
>   The Testing Guide is one of the most visible OWASP products and used by
> testers all over the world. So Matteo and I are seeking contributors for
> the update to the Guide. We've cataloged all of the articles that require
> writing, how much effort is required and started a list of contributors to
> each of these articles (
> https://docs.google.com/a/owasp.org/spreadsheet/ccc?key=0AmEhPtZ0cHq3dDc5ZFI0Nm9oSkhzNkNxTzNJbGdPdVE#gid=0
> ).
> Many of the main tasks required for release are now complete, so now we're
> focused on a sprint to release. For this we need your help. We're asking
> OWASP testers to help us find and revive contributors with the time,
> expertise and [most importantly] commitment to complete the writing of
> Testing Guide articles. Currently we are seeking contributors for the
> Authorization chapter, many Data Validation articles and Cryptography
> chapter, but need many more to help write and review other articles. We'll
> be conducting a set of sprints to get the revision wrapped up and released
> by the *end of 2013*. *The first sprint will be over the month of August*.
> One of the key tasks we're seeking to achieve is alignment between the
> Testing Guide and other OWASP products, chiefly the Dev Guide. Finding
> vulnerabilities is only the halfway point to fixing them. Again, we've
> cataloged the Test Guide test cases and aligned them with their equivalents
> in the Dev and Code Review Guides. The list is incomplete, but we're making
> progress (
> https://docs.google.com/a/owasp.org/spreadsheet/ccc?key=0ArkIkLbjWyP6dGhsNkdGLXhKanZqcklmWG41blZ3WWc#gid=0).
> So if you've worked on the Dev or Code Review Guide, we could also use your
> help.
> Sam Groves will be helping us wrangle the contributors (including Mat and
> myself) so if you hear from her, please don't ignore her. Even two words in
> an email will let everyone know how you're progressing.
> So strap in and get ready for Version 4 of the Testing Guide!
> regards,
> Andrew Muller
> Testing Guide Project co-leader
> Canberra, Australia chapter leader
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-testing/attachments/20130827/9433dbb0/attachment.html>

More information about the Owasp-testing mailing list