[Owasp-board] Wiki RFQ

Tom Brennan - OWASP tomb at owasp.org
Sat Jan 16 16:19:48 UTC 2016

Lets all be sure to all focus the goals of the investment effort;

1) business workflow analysis of staff processes documentation and
automation with improvements to core Salesforce system the runs the
backoffice and community services to the visitor/consumer of data/project
user/project leader, chapter member, chapter leader etc.

The goal is to increase efficiency of processes with technology systems
deployed (do more with less) identify gaps and processes that can be
documented, streamlined and potentially automated with NGO.

Step #1 is have a 3rd party business process expert with NGO engaged.

Adding, incorporating gamification of volunteer activities including those
connected to GoogleDocs / MediaWiki etc..etc.. is in scope.  Key job
functions as it pertains to interfacing with volunteers and core business
is analyzed from chapters to projects. This will happen with a 3rd party
business analyst who has worked on non-profits with proven experince with
organizations and growth stages as OWASP and has a focus on NGO (
http://www.salesforce.org/introducing-ngo-connect/ )

Resulting data will be then proposed for adjustments to the existing
deployed tool NGO that has been in place since 2009 with limited
customization and this will be merged with the results of the Mediawiki
upgrade/update/refresh/refine plan

simpler navigation, simple content, wiki updates, clean up, streamlining
etc. is associated task and part of the project but with independant work

** HISTORY HERE when it stalled the last time

In summary we need the business analyst to drive the technical change as a
3rd party and is a strategic goal for 2016.

Have a great weekend.

Tom Brennan
Global Board of Directors / NYC/NJ Metro Chapter Leader
(d) 973-506-9304

OWASP Foundation | www.owasp.org

On Sat, Jan 16, 2016 at 10:55 AM, Noreen Whysel <noreen.whysel at owasp.org>

> I wonder if the RFQ process shouldn't prevent the wiki editing team from
> going after low hanging fruit like broken links and the like. Thoughts?
> Also just so you know, I am attending Wikimedia Day at NYU today and can
> ask around for experience since its the same platform. I'll be at Bsides
> NYC later today as well.
> Noreen Whysel
> Community Manager
> OWASP Foundation
> On Fri, Jan 15, 2016 at 6:00 PM, Jim Manico <jim.manico at owasp.org> wrote:
>> Folks,
>> There are conflicting efforts with the wiki revamp initiative, and since
>> I am not operations I will put an end to my wiki update efforts and let
>> Noreen and Tom drive.
>> If you would like suggestions moving forward, just ask. I have a lot of
>> experience with wiki work.
>> Aloha,
>> Jim
>> On 1/15/16 11:36 AM, Noreen Whysel wrote:
>> I talked with Tom B last night at the NYC meetup last night about the
>> status of the wiki RFQ.
>> We have a document here with some comments:
>> https://docs.google.com/a/owasp.org/document/d/1Jigb9CnvXl5FhtZULp9fQjDT5y_bN3vgAjBxpmGJN7c
>> All should take a look and comment/approve/reject suggestions. The
>> timeline included Letter of Intent deadline of January 28, with a proposal
>> deadline of Feb 15, so we should either get this out very soon or update
>> the timeline.
>> Next step would be to publish it and send out an open call. How best to
>> publish the RFQ? I could use the traditional channels, blog post, social
>> media, community and leaders mailing lists. Any other streams?
>> I'm splitting my time tomorrow between Bsides NYC and the Wikimedia Day
>> at NYU and will see if I can find any wiki programmers.
>> Noreen Whysel
>> Community Manager
>> OWASP Foundation
>> _______________________________________________
>> Owasp-board mailing listOwasp-board at lists.owasp.orghttps://lists.owasp.org/mailman/listinfo/owasp-board
> _______________________________________________
> Owasp-board mailing list
> Owasp-board at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-board

The information contained in this message and any attachments may be 
privileged, confidential, proprietary or otherwise protected from 
disclosure. If you, the reader of this message, are not the intended 
recipient, you are hereby notified that any dissemination, distribution, 
copying or use of this message and any attachment is strictly prohibited. 
If you have received this message in error, please notify the sender 
immediately by replying to the message, permanently delete it from your 
computer and destroy any printout.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20160116/3fcda707/attachment.html>

More information about the Owasp-board mailing list