[Owasp-guide] Owasp-guide Digest, Vol 56, Issue 1

Brad Chesney bradchesney79 at gmail.com
Fri Jan 31 18:48:45 UTC 2014


Hi, I am Brad. I have been playing with Docbook 5. I am the 2.1.1 guy-- and
I'm doing it mostly to learn the Docbook XML syntax and toolchain in
absence of more productive work. Happy to help in the Docbook area,
editing, or random request. I picked this project to learn app security by
learning Docbook. It is like learning inception... We have to go deeper.

Anyway, I will look at the new content posted and see if my time can be
used more constructively.

-Brad
On Jan 31, 2014 10:59 AM, <owasp-guide-request at lists.owasp.org> wrote:

> Send Owasp-guide mailing list submissions to
>         owasp-guide at lists.owasp.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.owasp.org/mailman/listinfo/owasp-guide
> or, via email, send a message with subject or body 'help' to
>         owasp-guide-request at lists.owasp.org
>
> You can reach the person managing the list at
>         owasp-guide-owner at lists.owasp.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Owasp-guide digest..."
>
>
> Today's Topics:
>
>    1. Developer Guide 2014 (Andrew van der Stock)
>    2. Re: Developer Guide 2014 (Jim Manico)
>    3. Re: Developer Guide 2014 (Eoin Keary)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 1 Feb 2014 01:00:15 +1100
> From: Andrew van der Stock <vanderaj at owasp.org>
> To: "owasp-guide at lists.owasp.org" <owasp-guide at lists.owasp.org>
> Cc: Matt Konda <matt.konda at owasp.org>
> Subject: [Owasp-guide] Developer Guide 2014
> Message-ID:
>         <
> CAEdoTfLW2NyoM+po4qmHYVvk-MyApYb9dhvy2G42+5rzG87kAA at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.owasp.org/pipermail/owasp-guide/attachments/20140201/e1335051/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 31 Jan 2014 09:15:05 -0500
> From: Jim Manico <jim.manico at owasp.org>
> To: Andrew van der Stock <vanderaj at owasp.org>
> Cc: "owasp-guide at lists.owasp.org" <owasp-guide at lists.owasp.org>,
>  Matt
>         Konda <matt.konda at owasp.org>
> Subject: Re: [Owasp-guide] Developer Guide 2014
> Message-ID: <-3343736332902481465 at unknownmsgid>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Fri, 31 Jan 2014 15:58:14 +0000
> From: Eoin Keary <eoin.keary at owasp.org>
> To: Andrew van der Stock <vanderaj at owasp.org>
> Cc: "owasp-guide at lists.owasp.org" <owasp-guide at lists.owasp.org>,
>  Matt
>         Konda <matt.konda at owasp.org>
> Subject: Re: [Owasp-guide] Developer Guide 2014
> Message-ID: <5629BC6E-44E4-4186-931D-CA11D09D7CE8 at owasp.org>
> Content-Type: text/plain; charset="us-ascii"
>
> Good deal mr Konda.
>
> Eoin Keary
> Owasp Global Board
> +353 87 977 2988
>
>
> On 31 Jan 2014, at 14:00, 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/74cb62d9/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> Owasp-guide mailing list
> Owasp-guide at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-guide
>
>
> End of Owasp-guide Digest, Vol 56, Issue 1
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-guide/attachments/20140131/75f43734/attachment-0001.html>


More information about the Owasp-guide mailing list