[Global_membership_committee] OWASP on Linkedin - Subgroup "Official OWASP Member"

Thu Mar 22 18:09:41 UTC 2012

Great!  What is your plan to socialize this with the community? Will we copy this data onto the wiki somewhere? Is there a  plan to send an update to the leaders list and point to the wiki? How do you want to kick of this program?

Btw, already changed the group name.

-------
Michael Coates | OWASP
michael.coates at owasp.org | @_mwc

On Mar 22, 2012, at 10:53 AM, Helen Gao wrote:

> Hi Michael and GMC members,
> 
> The committee discussed the matter at great length on the Tuesday meeting. It took me a while to summarize it below. The same content has been put in a Google doc shared with you, the committee and the board. Your feedback would be highly appreciated.
> 
> A new LinkedIn group for confirmed members
> 
> What's the issue:
> Currently there is a Global OWASP Foundation LinkedIn group. It is free and open.
> Michael has created a OWASP Official Member subgroup designed for paid members only. See Michael’s email thread OWASP on Linkedin starting March 7, 2012.
> 
> GMC’s recommendation – GMC discussed the matter in the March meeting.
> The existing free and open LinkedIn group should not be changed or impacted by the new group.
> Change the subgroup name from OWASP Official Member to OWASP Confirmed Member. Confirmed means paid membership.
> A new, OWASP Confirmed Member subgroup is a good idea to increase membership.
> The new group should be used as and only as a digital membership card which is similar to the printable membership card currently issued at the end of a RegOnline payment transaction.
> There should be no discussion, forum or other content restricted by this subgroup. OWASP material will remain free and open.
> We should avoid wording that alienate people and deviate from the OWASP mission. We need to pay attention to content on OWASP website, RegOnline, marketing material, etc.
> Protect member privacy in the subgroup
> OWASP reserves the right to remove a subgroup member
> There will be two ways to join the subgroup
> RegOnline – There will be a check box that say something like this: Join LinkedIn for OWASP Confirmed Members:   Yes/No  LinkedIn for OWASP Confirmed Members is a …. This a subgroup of Global OWASP Foundation LinkedIn group which is open to all LinkedIn members. The default option is No.
> LinkedIn – A person can apply to join the subgroup on the webpage and a request will be sent to the group administrator. Once the applicant’s email address is confirmed to be a current paid member then he/she will be added to the group.
> Open issue:
> Should we remove a person from the subgroup after his/her membership expires for certain period of time after a certain number of reminders to renew?
> 
> FYI - The existing Global OWASP Foundation LinkedIn group has 10k+ members. In the week of March 11, 2012, 86 people joined, 12 discussions took place and 7 jobs. It’s created in October, 2007.
> 
> 
> 
> On Sat, Mar 10, 2012 at 4:16 PM, Michael Coates <michael.coates at owasp.org> wrote:
> Helen,
> 
> Your thoughts from the membership committee perspective?  If this is inline with the goals of the membership committee then I think we're good to give it a try.
> 
> Kelly and Kate believe the workload to handle requests is manageable.  I've also addressed the concern of "close vs open" below e.g. its a digital membership card, not a discussion forum.
> 
> Also, here are the stats of the primary OWASP linked in group. This group is totally open and a good place to grow OWASP's visibility.  I wonder if we can tie the OWASP_feed into news posts on our linkedin group?
> 
> http://www.linkedin.com/groups?groupDashboard=&gid=36874
> 
> 
> 
> -------
> Michael Coates | OWASP
> michael.coates at owasp.org | @_mwc
> 
> 
> 
> On Mar 8, 2012, at 11:03 AM, Kelly Santalucia wrote:
> 
>> The idea is good and the work should not be unmanageable.  
>> Thanks,
>> 
>> On Thu, Mar 8, 2012 at 1:58 PM, Michael Coates <michael.coates at owasp.org> wrote:
>> This group won't have a discussion forum or limit access to any data. It's the same ideas as a membership card (which is members only). This is just the digital equivalent.
>> 
>> ---------------------------------------------------
>> Michael Coates | OWASP
>> michael.coates at owasp.org | @_mwc
>> 
>> 
>> 
>> On Mar 8, 2012, at 10:48 AM, Kate Hartmann wrote:
>> 
>> > The maintenance would be manageable.  As long as no one sees any conflict
>> > with the Openness of OWASP in having a "members only" partition.  The idea
>> > of having a "members only" partition to the wiki was voted down as being too
>> > exclusionary.
>> >
>> > Kate Hartmann
>> > Operations Director
>> > 301-275-9403
>> > www.owasp.org
>> > Skype:  Kate.hartmann1
>> >
>> > -----Original Message-----
>> > From: Michael Coates [mailto:michael.coates at owasp.org]
>> > Sent: Thursday, March 08, 2012 1:42 PM
>> > To: global_membership_committee at lists.owasp.org
>> > Cc: OWASP Foundation Board List; Kate Hartmann; Kelly Santalucia; Sarah Baso
>> > Subject: OWASP on Linkedin - Subgroup "Official OWASP Member"
>> >
>> > Well,
>> > It's only been a few hours and I've already received a request to join the
>> > "OWASP Official Member" subgroup.
>> >
>> > The request included the member's name and membership number.
>> >
>> > Seems like there is some interest here. Before I accept it (and commit to
>> > this idea), what are people's thoughts?
>> >
>> > Membership committee - Do you like this idea?
>> > Board - Just a heads up
>> > Kate & Kelly - This would require someone to manage the inbound requests to
>> > verify membership and also a monthly purge of expired members.  I'm guessing
>> > not too much work and potentially a good perk for membership. Thoughts?
>> >
>> >
>> > ---------------------------------------------------
>> > Michael Coates | OWASP
>> > michael.coates at owasp.org | @_mwc
>> >
>> >
>> >
>> > On Mar 7, 2012, at 5:54 PM, Michael Coates 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
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> 
>> 
>> 
>> 
>> -- 
>> Kelly Santalucia
>> Operational Support:
>> Membership and Business Liaison
>> Direct: 973-670-5784
>> Url: http://www.owasp.org/index.php/NYNJMetro
>> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/global_membership_committee/attachments/20120322/52804ed3/attachment-0001.html>