[Owasp-appsensor-project] AppSensor Book V2 - Community Driven Book Writing

Dinis Cruz dinis.cruz at owasp.org
Fri Sep 7 11:11:11 UTC 2012


Hi, any updates on this book?

I just looked at the latest list archives and couldn't find any recent
thread about it

Dinis Cruz

On 31 July 2012 17:56, Colin Watson <colin.watson at owasp.org> wrote:

> I am doing some work on this in the next week or so, and will post up
> a draft table of contents. I will make sure we have a slot for
> "glossary".
>
> Colin
>
> On 16 June 2012 05:36, John Melton <jtmelton at gmail.com> wrote:
> > Michael or Colin,
> > Looks like the first step here is to agree on the table of contents.
> Could
> > one of you point to that doc? Maybe we can have a quick comment/review
> > period to make sure we get appropriate feedback and get that milestone
> > crossed off the list?
> >
> > Thanks,
> > John
> >
> >
> > On Thu, May 17, 2012 at 12:40 PM, Michael Coates <
> michael.coates at owasp.org>
> > wrote:
> >>
> >> Colin,
> >>
> >> No need to fall on the sword (so to speak) - we were all enthused about
> >> the next book revision from the AppSensor Summit and we just didn't
> >> collectively get the ball rolling.
> >>
> >> I think we can all take another pass at it in this new format together.
> >>
> >>
> >> -------
> >> Michael Coates | OWASP
> >> michael.coates at owasp.org | @_mwc
> >>
> >>
> >>
> >> On May 15, 2012, at 1:27 PM, Colin Watson wrote:
> >>
> >> > Experts and enthusiasts
> >> >
> >> > I have to admit that I think I agreed to lead the effort to write a
> >> > new book, and I am sorry I have not progressed this further to date. I
> >> > have begun writing some sections based on the structure discussed at
> >> > the summit.
> >> >
> >> > Additionally Manuel Lopez offered assistance and tried to solicit
> >> > input for the case studies section, but without too much success.
> >> >
> >> > I agree it would be better to allow for the inclusion of material
> >> > relating to the GSoC 2012, but that means we can focus on the other
> >> > parts before then. I am happy to continue contributing, or even
> >> > drafting outline sections for others to write, expand, improve and
> >> > review. Personally I wouldn't want money, a paid project manager, wiki
> >> > editor or copywriter - but I'm sure those suggested resources might
> >> > help on other projects. I just need time, which I am hoping to make
> >> > available soon.
> >> >
> >> > Colin
> >> >
> >> > On 15 May 2012 21:16, John Melton <jtmelton at gmail.com> wrote:
> >> >> I'm game for being a core contributor to the development /
> >> >> implementation
> >> >> sections. I'll add to Kevin's note that my primary goal for the
> summer
> >> >> is
> >> >> the mentoring for the google summer of code resource we have, so the
> >> >> heavy
> >> >> lifting from me will probably come in a couple months.
> >> >>
> >> >> Thanks,
> >> >> John
> >> >>
> >> >>
> >> >> On Tue, May 15, 2012 at 11:01 AM, giri vara prasad nambari
> >> >> <girinambari at gmail.com> wrote:
> >> >>>
> >> >>> This approach does add value. I am interested too. June 1st week
> >> >>> onwards I
> >> >>> will get more time to spend on Appsensor.
> >> >>>
> >> >>> Thank you,
> >> >>> Giri
> >> >>>
> >> >>> On Mon, May 14, 2012 at 8:20 PM, Dennis Groves
> >> >>> <dennis.groves at gmail.com>
> >> >>> wrote:
> >> >>>>
> >> >>>> Still very interested. :-)
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Dennis Groves, MSc
> >> >>>> dennis.groves at gmail.com
> >> >>>>
> >> >>>> "What is the use of living, if it be not to strive for noble causes
> >> >>>> and
> >> >>>> make this muddled world a better place for those who will live in
> it
> >> >>>> after
> >> >>>> we have gone."
> >> >>>>
> >> >>>> -- Winston Churchill, October 10th, 1908
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> On Tue, May 15, 2012 at 1:07 AM, Michael Coates
> >> >>>> <michael.coates at owasp.org> wrote:
> >> >>>>>
> >> >>>>> Before we get ahead of ourselves I want to gauge interest.
> >> >>>>>
> >> >>>>> Per our wiki page we have the following core contributors to the
> >> >>>>> project
> >> >>>>> (if someone is missing, please update) -
> >> >>>>> https://www.owasp.org/index.php/OWASP_AppSensor_Project
> >> >>>>>
> >> >>>>> Are any of you interested in this idea and shepherding a section
> (as
> >> >>>>> a
> >> >>>>> core contributor) where you are a subject matter expert?
> >> >>>>>
> >> >>>>> Michael Coates
> >> >>>>> John Melton
> >> >>>>> Colin Watson
> >> >>>>> Ryan Barnett
> >> >>>>> Simon Bennetts
> >> >>>>> August Detlefsen
> >> >>>>> Dennis Groves
> >> >>>>> Randy Janida
> >> >>>>> Jim Manico
> >> >>>>> Giri Nambari
> >> >>>>> Eric Sheridan
> >> >>>>> John Stevens
> >> >>>>> Kevin Wall
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> Thanks,
> >> >>>>> Michael Coates
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On Mon, May 14, 2012 at 4:59 PM, Dennis Groves
> >> >>>>> <dennis.groves at gmail.com>
> >> >>>>> wrote:
> >> >>>>>>
> >> >>>>>> I would prefer it if we funded it using the GSD project. It
> makes a
> >> >>>>>> lot
> >> >>>>>> more sense - think of the momentum that would be generated behind
> >> >>>>>> simple
> >> >>>>>> things like paying $500 per chapter written with in the deadline
> on
> >> >>>>>> topic
> >> >>>>>> and hiring a designer to lay it out for $1500?
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> --
> >> >>>>>> Dennis Groves, MSc
> >> >>>>>> dennis.groves at gmail.com
> >> >>>>>>
> >> >>>>>> "What is the use of living, if it be not to strive for noble
> causes
> >> >>>>>> and
> >> >>>>>> make this muddled world a better place for those who will live in
> >> >>>>>> it after
> >> >>>>>> we have gone."
> >> >>>>>>
> >> >>>>>> -- Winston Churchill, October 10th, 1908
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> On Tue, May 15, 2012 at 12:03 AM, Jim Manico <
> jim.manico at owasp.org>
> >> >>>>>> wrote:
> >> >>>>>>>
> >> >>>>>>> If the AppSensor team needs more resources, please consider:
> >> >>>>>>>
> >> >>>>>>> https://www.owasp.org/index.php/Projects_Reboot_2012
> >> >>>>>>>
> >> >>>>>>> Aloha!
> >> >>>>>>> - Jim
> >> >>>>>>>
> >> >>>>>>>> For this to work, we will need to hire a project manager + wiki
> >> >>>>>>>> editor
> >> >>>>>>>> + copywriter (some Design skills for graphs, cover and diagrams
> >> >>>>>>>> would
> >> >>>>>>>> also help)
> >> >>>>>>>>
> >> >>>>>>>> That way the Core Authors + Contributors can focus (with 'soft
> >> >>>>>>>> pressure' from the project manager) on creating content.
> >> >>>>>>>>
> >> >>>>>>>> Dinis Cruz
> >> >>>>>>>>
> >> >>>>>>>> On 14 May 2012, at 16:30, Michael Coates
> >> >>>>>>>> <michael.coates at owasp.org>
> >> >>>>>>>> wrote:
> >> >>>>>>>>
> >> >>>>>>>>> AppSensor Experts & Enthusiasts,
> >> >>>>>>>>>
> >> >>>>>>>>> Last fall at the AppSensor summit we hashed out the framework
> >> >>>>>>>>> for
> >> >>>>>>>>> the next version of the AppSensor book.  Based on several
> years
> >> >>>>>>>>> of feedback
> >> >>>>>>>>> and the collective expertise of core contributors, and those
> >> >>>>>>>>> with fresh new
> >> >>>>>>>>> perspectives, we arrived at a good skeleton. But, alas, we
> don't
> >> >>>>>>>>> have a
> >> >>>>>>>>> single page written so far!
> >> >>>>>>>>>
> >> >>>>>>>>> I'd like to discuss how we can collectively go about creating
> >> >>>>>>>>> the
> >> >>>>>>>>> next great app sensor book. The traditional approach is for a
> >> >>>>>>>>> few of us to
> >> >>>>>>>>> sit down and crank out the whole book over 12-14 months and
> have
> >> >>>>>>>>> some pier
> >> >>>>>>>>> review - but I just don't think that truly leverages our open
> >> >>>>>>>>> source and
> >> >>>>>>>>> collective skills effectively.
> >> >>>>>>>>>
> >> >>>>>>>>> I'm going to propose an alternative approach - community
> driven
> >> >>>>>>>>> book writing.
> >> >>>>>>>>>
> >> >>>>>>>>> Approach
> >> >>>>>>>>> 1. Collectively agree on the skeleton / table of contents
> >> >>>>>>>>> (pretty
> >> >>>>>>>>> close here)
> >> >>>>>>>>> 2. Determine writing style guides / tone / language (region
> for
> >> >>>>>>>>> spelling purposes)
> >> >>>>>>>>> 3. Determine a small number of core authors
> >> >>>>>>>>> 4. Determine a larger number of contributing writers
> >> >>>>>>>>> 5. Divide responsibilities (e.g. book sections/ chapters) to
> >> >>>>>>>>> core
> >> >>>>>>>>> authors
> >> >>>>>>>>> 6. Core authors map out overall flow of their sections
> >> >>>>>>>>> 7. Core authors and contributing writers create their sections
> >> >>>>>>>>> 8. Continual review from core authors across their sections
> >> >>>>>>>>> 9. Review, adjust, repeat
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> Core Author
> >> >>>>>>>>> - Subject matter expert on their section
> >> >>>>>>>>> - Responsible for entire chapter or section
> >> >>>>>>>>> - Drives the main ideas covered in the sections
> >> >>>>>>>>> - Responsible for pier review of all content in respective
> >> >>>>>>>>> section,
> >> >>>>>>>>> organization of ideas
> >> >>>>>>>>> - Works with contributing writers to arrange material, flow
> >> >>>>>>>>> - Nomination and acceptance process for all Core Authors
> >> >>>>>>>>>
> >> >>>>>>>>> Contributing Writers
> >> >>>>>>>>> - Contributes a small (or larger) amount of material within
> any
> >> >>>>>>>>> section they feel comfortable
> >> >>>>>>>>> - Expert within the areas they are contributing text
> >> >>>>>>>>> - Stays within the defined style guidelines
> >> >>>>>>>>>
> >> >>>>>>>>> Attribution:
> >> >>>>>>>>> Everyone that contributes would be recognized. We would
> >> >>>>>>>>> emphasize
> >> >>>>>>>>> individuals that contribute substantial amounts of work.
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> Think of a core author as an architect and a contributing
> writer
> >> >>>>>>>>> as
> >> >>>>>>>>> a developer (except we have an architect per major book
> section
> >> >>>>>>>>> & there are
> >> >>>>>>>>> pier review between the architect and all developers in the
> >> >>>>>>>>> respective
> >> >>>>>>>>> section)
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> Crazy idea? Suggestions? Could this work?
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> -------
> >> >>>>>>>>> Michael Coates | OWASP
> >> >>>>>>>>> michael.coates at owasp.org | @_mwc
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> _______________________________________________
> >> >>>>>>>>> Owasp-appsensor-project mailing list
> >> >>>>>>>>> Owasp-appsensor-project at lists.owasp.org
> >> >>>>>>>>>
> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>>>>>>> _______________________________________________
> >> >>>>>>>> Owasp-appsensor-project mailing list
> >> >>>>>>>> Owasp-appsensor-project at lists.owasp.org
> >> >>>>>>>>
> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> --
> >> >>>>>>> Jim Manico
> >> >>>>>>>
> >> >>>>>>> Connections Committee Chair
> >> >>>>>>> Cheatsheet Series Product Manager
> >> >>>>>>> OWASP Podcast Producer/Host
> >> >>>>>>>
> >> >>>>>>> jim at owasp.org
> >> >>>>>>> www.owasp.org
> >> >>>>>>> _______________________________________________
> >> >>>>>>> Owasp-appsensor-project mailing list
> >> >>>>>>> Owasp-appsensor-project at lists.owasp.org
> >> >>>>>>>
> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> _______________________________________________
> >> >>>>>> Owasp-appsensor-project mailing list
> >> >>>>>> Owasp-appsensor-project at lists.owasp.org
> >> >>>>>> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> _______________________________________________
> >> >>>>> Owasp-appsensor-project mailing list
> >> >>>>> Owasp-appsensor-project at lists.owasp.org
> >> >>>>> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>> _______________________________________________
> >> >>>> Owasp-appsensor-project mailing list
> >> >>>> Owasp-appsensor-project at lists.owasp.org
> >> >>>> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> _______________________________________________
> >> >>> Owasp-appsensor-project mailing list
> >> >>> Owasp-appsensor-project at lists.owasp.org
> >> >>> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Owasp-appsensor-project mailing list
> >> >> Owasp-appsensor-project at lists.owasp.org
> >> >> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >> >>
> >> > _______________________________________________
> >> > Owasp-appsensor-project mailing list
> >> > Owasp-appsensor-project at lists.owasp.org
> >> > https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
> >>
> >
> _______________________________________________
> Owasp-appsensor-project mailing list
> Owasp-appsensor-project at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-appsensor-project/attachments/20120907/cb69a96d/attachment-0001.html>


More information about the Owasp-appsensor-project mailing list