[Global_membership_committee] OWASP on Linkedin

[Helen Gao]

Helen's two cents: The technicality of allowing paid members only to a
LinkedIn group is a lesser issue comparing to the fundamental of what a
OWASP member is. Do we keep it free and open or start to allow some
distinctions between paid members and the rest? Beside the member only
LinkedIn group, I would also recommend several methods to boost individual
membership.


   - Enforce the policy of granting @owasp.org email accounts for paid
   members only - Requires administrative work.
   - Create a public member directory - Requires administrative work.
   - Create a special space on our website for members where they can find
   career tools, network, sign up for volunteering, etc. – May not require too
   much administrative work

 Here is an example of how CISSP group works.  *Join Professional
Communities  Yes/No    LinkedIn for CISSPs LinkedIn is a business
networking service, allowing you to leverage your social network to gain
access to a broader range of fellow professionals. The CISSP group on
LinkedIn is a subset of LinkedIn members who are also CISSPs.*


Please note that one major difference between CISSP and OWASP is the former
is for profit and certification required.

On Wed, Mar 7, 2012 at 9:58 PM, Kelly Santalucia <kelly.santalucia at owasp.org
> wrote:

> Hi Michael,
>
> This is a wonderful idea to help raise our membership numbers.  My only
> question is how are we going to confirm that the individual is a current
> paid member?  Is there a way for Linked In to be linked to our membership
> and do it automatically?  I am not very Linked In savvy, but getting better
> ;)
>
> Also on the first thread regarding "how we handle the discussions"  Can we
> put the "contact us"  link should they need assistance or have a question?
> That way their inquiry will be addressed through Sales Force cases and
> handled in a timely manner.
>
> Like I said I am not a wiz on Lined In and I could be way off here, but
> just my thoughts.
>
> Thank you,
>
>
> On Wed, Mar 7, 2012 at 8:54 PM, Michael Coates <michael.coates at owasp.org>wrote:
>
>> Here's another idea, we can do a subgroup that is for official members.
>>
>> I've created the subgroup and we can explore / discuss if this is the
>> right approach.
>>
>> http://www.linkedin.com/groups?home=&gid=4342746&trk=anet_ug_hm
>>
>>
>>
>> ---------------------------------------------------
>> Michael Coates | OWASP
>> michael.coates at owasp.org | @_mwc
>>
>>
>>
>> On Mar 7, 2012, at 5:48 PM, Michael Coates wrote:
>>
>> > Membership Committee,
>> >
>> > I'd be very interested to hear your recommendations on how we should
>> handle the OWASP linked in group
>> > http://www.linkedin.com/groups/Global-OWASP-Foundation-36874
>> >
>> > Is this a good way to reach out to new people?
>> > How do we handle the stream of discussions there?
>> > Should the ability to become a "member" of the OWASP linked in group be
>> a benefit of OWASP membership?
>> >
>> >
>> >
>> > ---------------------------------------------------
>> > Michael Coates | OWASP
>> > michael.coates at owasp.org | @_mwc
>> >
>> >
>> >
>>
>> _______________________________________________
>> Global_membership_committee mailing list
>> Global_membership_committee at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/global_membership_committee
>>
>
>
>
> --
> Kelly Santalucia
>
> Operational Support:****
>
> Membership and Business Liaison
> Direct: 973-670-5784
> Url: http://www.owasp.org/index.php/NYNJMetro
>
>
> _______________________________________________
> Global_membership_committee mailing list
> Global_membership_committee at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/global_membership_committee
>
>


-- 
Helen Gao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/global_membership_committee/attachments/20120308/162d9ad1/attachment-0001.html>