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

Dennis Groves dennis.groves at gmail.com
Tue May 15 00:20:55 UTC 2012


Still very interested. :-)


--
Dennis Groves <http://about.me/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<https://www.owasp.org/index.php/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 <http://about.me/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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-appsensor-project/attachments/20120515/712cb3fb/attachment.html>


More information about the Owasp-appsensor-project mailing list