[OWASP-wiki-editors] [Owasp-board] Wiki Cleanup

Mon Nov 30 21:39:59 UTC 2015

 > For your proposal, Can we structure this into two 90-day 'phases' so 
we can compate some fixed costs with some fixed outcomes/deliverables?

Absolutely. I already CC'ed you, Noreen and Tom (part of why he ran) 
into this conversation with Elger. If anyone else wants in let me know.

Aloha,
Jim

On 11/30/15 6:50 PM, Paul Ritchie wrote:
> Hi Jim, thanks for taking the initiative with an active leadership 
> role to help get some of this addressed asap.
>
> I'm in favor of moving forward in bite-sized chunks with tangible results.
>
> For your proposal, Can we structure this into two 90-day 'phases' so 
> we can compate some fixed costs with some fixed outcomes/deliverables?
>
> Then at end of each 90 day period we can determine prioritize what was 
> accomplished and what is next to do?
>
> In other words, what would we have 'Elger' address in first 90 days as 
> top priority and at what cost.?
>
> Paul
>
> Best Regards, Paul Ritchie
> OWASP Executive Director
> paul.ritchie at owasp.org <mailto:paul.ritchie at owasp.org>
>
>
> On Sun, Nov 29, 2015 at 11:27 AM, Jim Manico <jim.manico at owasp.org 
> <mailto:jim.manico at owasp.org>> wrote:
>
>     Board and others,
>
>     Recently a wiki media and security expert -  Elger Jonker -
>     approached me with a desire to help the OWASP foundation
>     reorganize the wiki and help ensure future edits are done in a
>     categorized and sensible way. Elger provided a report on his
>     initial analysis of the wiki and here is a summary.
>
>     Currently, there are 8979 URLs on the OWASP wiki. This is a very
>     large wiki. If we spend 10 minutes on each URL it would take ~1500
>     hours to just review each page, not to mention the need to tag,
>     re-categorize or more.
>
>     The wiki is broke up into three major categories.
>
>     1) Organizational / Community: conferences, chapters, events,
>     meetings, notes, OWASP board, procedures, names of people
>     2) Knowledge: Attacks, vulnerabilities, testing, vulnerabilities,
>     business impacts
>     3) Projects: Tools and content that overlap with knowledge resources
>
>     They rate is estimated about 40%, 30%, 30%. Not all pages are that
>     easy to identify.
>
>     Here is a full list of pages that make up all of the wiki.
>
>     https://docs.google.com/spreadsheets/d/13FqA7OoFNLFebXTxV7xYtwzDO2bR5A_NaNj6jbmoZ8U/edit#gid=397931366&vpid=A8948
>
>     I'd like to hire Elger to serve as a technical consultant to
>     assist me in a deeper effort to re-organize and clean up the
>     current wiki.
>
>     In general, I am happy to take lead on the wiki and website
>     redesign project. I would like to complete my promise to the
>     community before my board tenure ends on December 31, 2016. One of
>     the final goals is to enable editorial controls on the wiki for a
>     more formal review process around appsec content. I am happy to
>     serve as one of the chief editors of the wiki after my board
>     tenure is over or until someone is hired to take on this duty.
>
>     Aloha,
>
>     -- 
>     Jim Manico
>     Global Board Member
>     OWASP Foundation
>     https://www.owasp.org
>
>     _______________________________________________
>     Owasp-board mailing list
>     Owasp-board at lists.owasp.org <mailto:Owasp-board at lists.owasp.org>
>     https://lists.owasp.org/mailman/listinfo/owasp-board
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-wiki-editors/attachments/20151130/e2073258/attachment.html>