[Owasp-leaders] Proposed $25K to create OWASP Wiki interface

Wed Oct 21 11:19:31 UTC 2015

 > Better path is to support wiki editing process we have (rather than 
move to a new wiki or other system)

Just to clarify, I think the better path is to use the formal Wikimedia 
editorial oversight and control system. 
https://en.wikipedia.org/wiki/Wikipedia:Editorial_oversight_and_control 
We can turn on features (or use ones already turned on) such as dispute 
resolution, mediation, third-party opinion, and requests for comment and 
consultation.

Since it will likely take us a while to get there, I think the current 
tagging system is a good interstitial step. But the more I look at it, 
the more I think wikimedia has all the features needed to mature our 
editorial process and make a better wiki.

  - Jim

On 10/19/15 2:23 PM, Noreen Whysel wrote:
> I don't recall any discussion of a new interface at the chapter 
> leaders workshops. Jim Manico and I went through the wiki editing and 
> cleanup process but there wasn't much time for a future directions 
> discussion, unfortunately. I was hoping to do a brief series of 
> usability tests but we ran out of time. Recording here:
>
> https://drive.google.com/open?id=0ByZ3H0-PMUGuUE54OU5kS3RCTW8
>
> There have been a few threads on the board and leaders lists on the 
> topic. The board has been focussing discussion on the funding proposals.
>
> I have held two open discussions on GotoMeeting with Jim and members 
> of the Wiki Editing team. Johanna suggested using something like Matt 
> Konda's suggested github pages for developers 
> (http://owasp.github.io/dev-pages/).
>
> I also suggested getting a graduate course to take on OWASP for a 
> usability study. I know a few good professors in NYC who could use a 
> project like this for their classes.
>
> Notes from Oct 1 meeting:
>
>     Wiki Editing meeting/gotomeeting
>
>     October 1, 2015
>
>     Jim suggests:
>
>     Turn on Wiki Editing System
>
>     -Has badge system
>
>     -Has controls
>
>     Hire someone to turn on the plug-ins
>
>     Better path is to support wiki editing process we have (rather
>     than move to a new wiki or other system)
>
>     Wikimedia editorial oversight and control features
>
>     https://en.wikipedia.org/wiki/Wikipedia:Editorial_oversight_and_control
>
>     Categorize the wiki
>
>     Tools to crawl the wiki
>
>     Two types of volunteers
>
>       * Technical review
>       * Editorial review-has subject matter expertise
>
>     Missing from Wiki Cleanup team
>
>       * Prioritize actions
>
>     Top level reorganization:
>
>       * Categorize links by language
>       * Categorize /or just arrange content by audience
>
>     Example:
>     http://owasp.github.io/dev-pages/
>     https://www.owasp.org/index.php/Category:OWASP_Java_Project has
>     good resources for developing a list for Java developers
>
>     Tasks:
>
>     -Review orphan pages for uncategorized redirects
>
>     -Review and fix broken links
>
> Noreen Whysel
> Community Manager
> OWASP Foundation
>
>
> On Oct 19, 2015, at 7:01 AM, Tom Brennan <tomb at owasp.org 
> <mailto:tomb at owasp.org>> wrote:
>
>> Noreen
>>
>> Do you have any discussion points to publish on this topic from 
>> AppSecUSA meeting or other activity to date.
>>
>> With global budgeting coming up if it is going to happen in 2016 now 
>> is the time to do it.
>>
>> Tom Brennan
>> 973-506-9304 <tel:973-506-9304>
>>
>>> On Sep 17, 2015, at 9:19 AM, Noreen Whysel <noreen.whysel at owasp.org 
>>> <mailto:noreen.whysel at owasp.org>> wrote:
>>>
>>> Noreen Whysel
>
>
> _______________________________________________
> OWASP-Leaders mailing list
> OWASP-Leaders at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-leaders

-- 
Jim Manico
Global Board Member
OWASP Foundation
https://www.owasp.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-leaders/attachments/20151021/0904b2bc/attachment.html>