[Owasp-guide] Developer Guide 2014

Jim Manico jim.manico at owasp.org
Fri Jan 31 14:15:05 UTC 2014


Folks,

I'm busy with other projects but this is important. If any of you need a
resource for questions or want me to proof read edited work, please let me
know.

Rock on Andrew and Matt!

Aloha,
--
Jim Manico
@Manicode
(808) 652-3805

On Jan 31, 2014, at 9:06 AM, Andrew van der Stock <vanderaj at owasp.org>
wrote:

Hi folks,

I am (if a lot belatedly) pleased to announce that we have a new project
manager, Matt Konda, who I spoke with at AppSec USA. I want everyone to say
hi and help him achieve our goals!

Welcome Matt!

I've started cutting back on the roadmap and really retreating to our core
at Matt's suggestion. This is where you come in. I really need for us to
move to a more agile model as "big bang re-write" has failed miserably
since 2005. So we're going to refactor not re-write. It's lot easier to
edit than re-write. Also, you don't need Scrivener or Word or anything
fancy, just a browser to contribute.

I have proposed four milestones for this year, one for each quarter. The
first 3 quarters, I want to update all of the main 2005 content to be 2014
ready, and then spend the last quarter providing a level of polish.

Then repeat the process in 2015, updating only what must be updated in the
first three quarters, but aim to write some of the new sections that I had
set out in my massive TOC wish list, and then a polish in Q4 2015. Rinse
and repeat in 2016. I don't want to ever get to a point that our main thing
we are famous becomes like a historic curiosity.

*Materials*

Our materials were everywhere and in a rather poor state. So I've done some
housecleaning.

I've updated the Developer Guide home page:
* https://www.owasp.org/index.php/OWASP_Guide_Project#tab=Main

Please review the milestone and wiki home here:
* https://github.com/OWASP/DevGuide/wiki

If you have donated content to us over the last 18 months, I will be
putting it up on the Wiki at GitHub (access control + crypto from Kevin).
The old Wiki at my VPS will go away. The old sourceforge CVS tree will go
away. The old OWASP wiki content will eventually go away, probably late
this year as we polish our material properly.

I've uploaded all of the old Developer Guides to GitHub:
* https://github.com/OWASP/DevGuide

Please don't fork the old content, it's there for historical reasons. I am
still looking for content pre-1.0, so if you have some, please let me know.
If you feel you have been left off the contributors page, please just
update it or let me know. There is an effort to make a 2.1.1 DocBook
version, which is nice, but I'd rather us spend our time on building the
2014 edition.

*How you can help*

* Please review the material, road map, and Wiki.
* Volunteer (again if necessary) for chapters you are interested in,
particularly in Milestone 1.
* Work in groups if you need, but basically, you only need a browser to
contribute to the Guide. I will do the heavy lifting to build it into a PDF
and move it to the OWASP wiki later this year.
* Work with Matt Konda to deliver these chapters to a schedule that makes
sense to both you and works with Matt's project management. This goes
doubly for me.

Please let me know if you think the roadmap is achievable, and let's get
this thing written.

thanks
Andrew

_______________________________________________
Owasp-guide mailing list
Owasp-guide at lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-guide
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-guide/attachments/20140131/5d90811c/attachment.html>


More information about the Owasp-guide mailing list