[Owasp-board] Wiki RFQ

Kate Hartmann kate.hartmann at owasp.org
Mon Jan 18 15:59:08 UTC 2016

I just wanted to throw out some information.  I spoke with our SF account
manager about the functionality of NGO.

NGO does not have a native membership module, and while the events module
does have some different features like seating charts, it is not robust
enough to manage the complexity of our events as they exist today.

Before OWASP could migrate to the NGO platform there would need to be some
serious developer work to build the membership and events platforms for

I was told by the Salesforce Foundation (the branch that works with the Non
Profit organizations) that for associations like ours, the recommendation
is frequently Fonteva and the Member Nation platform.  This is what we
currently have in place and have been using since April 2014.

There are modules within the existing MN platform that we have not
implemented.  Specifically, there are modules for Chapters, Fundraising,
Education, and Awards.

Out of the box, the functionality doesn't match what OWASPs current
processes are, but the baseline for the concept is there.

I'm not convinced that MN can help streamline back office processes (I
don't believe that is within their scope) but I have communicated with
several consulting firms who specialize in working with NP orgs like ours.

I am active in the DC Non Profit SF user group and, when we have clearly
defined the scope of the RFQ as it relates to our back office operations
and Salesforce, I would like to be sure that it gets submitted to some
companies that I am familiar with and who have a really good reputation for
their work with Non Profit organizations.

One company, in particular, is Cloud for Good

I, and the ops team, have spent a little time looking at different
gamification platforms.  Time and time again, the biggest roadblock is
trying to integrate a platform or tool with the wiki.  We first attempted
Mozilla Badges in 2013, and since then have poked a couple of different
options without much success.  Most recently ThinkSmartOne
There are a couple of open source platforms
out there, but I am not familiar enough with the coding side of things to
know if any of them would work for OWASP.  I would like to be sure that
wiki integration with some of our other systems is included in the scope of

I think Tom is correct that there is a #1 and a #2 to the infrastructure
goals and although they do have a relationship, they are not necessarily
the same thing.  I'm not sure that they can be combined into the same RFP
unless the primary objective is to integrate our back office systems with
the wiki - and that may be the case.

I would welcome an outsider's perspective on our existing workflow and
operational processes.  I am not a developer, but I'm pretty good at
declarative development (point and click building and integrations) so as
we've been building our SF instance, most of the additions and improvements
have been of that nature.  I'm pretty sure that a SF developer who can
write the code and triggers could help us to streamline and improve our
existing processes.

Thank you

On Sat, Jan 16, 2016 at 11:19 AM, Tom Brennan - OWASP <tomb at owasp.org>

> 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
> 2) WIKI
> simpler navigation, simple content, wiki updates, clean up, streamlining
> etc. is associated task and part of the project but with independant work
> streams.
> ** HISTORY HERE when it stalled the last time
> https://www.owasp.org/index.php/RFO_Web_Design
> 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>
> wrote:
>> 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.
> _______________________________________________
> Owasp-board mailing list
> Owasp-board at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-board


Kate Hartmann
kate.hartmann at owasp.org
+1 301-275-9403
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20160118/68a07224/attachment.html>

More information about the Owasp-board mailing list