[Owasp-board] A new LinkedIn group for confirmed members only - A GMC proposal to OWASP board

Michael Coates michael.coates at owasp.org
Thu Mar 29 19:28:47 UTC 2012


Happy to change that setting (need to find it). I don't think it will be
relevant for the discussion part (since there is no discussion enabled
here).

I like the auto approve of owasp.org email address idea. I'll look for that
option too.

Michael
On Mar 29, 2012 10:49 AM, "Helen Gao" <helen.gao at owasp.org> wrote:

> I believe the new subgroup should be an Open Group, but users must request
> to join this group and be approved by a manager. An Open Group fits
> the openness of OWASP better and also provides perks to members. Below is
> from LinkedIn:
>
> *In addition to today's members-only groups, Open Groups enable the world
> to see and share your discussions. In either kind of LinkedIn group, you
> have full control over the quality of contributions and membership. We can
> create the subgroup as a member-only group and convert it to an open group
> later.*
>
>  Benefits
>
> Open Group/New
>
> members-only Group
>
> Discussion visibility
>
> Anyone*
>
> Members only
>
> Indexing by search engines
>
> Yes
>
> No
>
> Sharing to Twitter and Facebook
>
> Yes
>
> No
>
> Anyone on LinkedIn can contribute
>
> Optional
>
> No
>
> * When a group is converted, only new discussions are open to everyone.
> Previous discussions get stored in a read-only Archive open to members
> only.
>
> If @owasp.org are granted to members only, then we can configure LinkedIn
> to pre-approve members with this domain. Just a thought to reduce
> administrative overhead.
>
> On Thu, Mar 29, 2012 at 11:54 AM, Michael Coates <michael.coates at owasp.org
> > wrote:
>
>> A few points to consider:
>>
>> 1. We won't be doing a mass import - in fact, I don't think we should
>> ever submit user data to third parties. Let our users do that if they want
>> to.
>> 2. We only have to respond to people that specifically ask to join the
>> group. At first, I imagine there will be a lot of people, but then it will
>> slow down
>> 3. The default message to join the group asks for the owasp membership id
>> number and associated email address. I don't expect the larger owasp linked
>> in people (10k) will attempt to join without first becoming members
>>
>>
>> It may be a bit of work at first. But I think it could be a good
>> membership perk to attract new people.
>>
>>
>>
>>
>> -------
>> Michael Coates | OWASP
>> michael.coates at owasp.org | @_mwc
>>
>>
>>
>> On Mar 29, 2012, at 3:51 AM, Helen Gao wrote:
>>
>> I am not a board director so this is just my 2 cents:
>>
>> This could possibly take Kelly and/or Kate a lot of time to match email
>> addresses, verify paid or honorary membership, add new members and remove
>> expired/disqualified people after reminding them to renew. After all, there
>> are more than 10 thousands OWASP LinkedIn members, over 2 thousands paid
>> members and many people qualified for honorary memberships. The only way to
>> verify qualification seems to be the email address. Luckily LInkedIn allows
>> you to add as many email addresses to your profile. Remove people every 6
>> months should be more than enough.
>>
>> On Wed, Mar 28, 2012 at 10:10 AM, Michael Coates <
>> michael.coates at owasp.org> wrote:
>>
>>> Not an import. Opt-in by request from the member only (via linked in).
>>>  I don't think its appropriate to take an email address provided by a
>>> member and submit it to another system without their approval.
>>>
>>> My thought is we announce this program and tell people how they can get
>>> invovled e.g. make the request within linked in and include the membership
>>> number and associated email address.
>>>
>>> There is a work factor for Kelly / Kate that includes:
>>> * verifying inbound requests and approving or requesting additional
>>> details
>>> * monthly review to remove individuals that are no longer members
>>>
>>> We have discussed with Kelly / Kate and they feel this is manageable.
>>>
>>> Social networking can be powerful and this additional membership benefit
>>> may help attract new members and also continue strengthening/growing the
>>> overall community.
>>>
>>>
>>>
>>>
>>>
>>> -------
>>> Michael Coates | OWASP
>>> michael.coates at owasp.org | @_mwc
>>>
>>>
>>>
>>> On Mar 28, 2012, at 7:05 AM, Thomas Brennan wrote:
>>>
>>> To be clear your advocating having a employee (likely Kate or Kelly) as
>>> part of the job import the paid member list of individuals to a subgroup of
>>> OWASP and designate "member".  This will be synced manually with the global
>>> membership list and the @owasp.org email on file for that member. This
>>> person will take on that duty of "connections" and be a liason for social
>>> media for the OWASP business.
>>>
>>> In the event that they do not renew they will be decommissioned from
>>> that group in sync with the membership document perhaps quarterly.
>>>
>>> ----
>>>
>>> Did I capture the spirit of this correctly?
>>>
>>>
>>> On Mar 28, 2012, at 9:54 AM, Michael Coates <michael.coates at owasp.org>
>>> wrote:
>>>
>>> Board,
>>>
>>> Is discussion desired on this topic or clarification?  Or are we able to
>>> vote via email?  If passed, we can include this as one of the new items
>>> within the board slides.
>>>
>>>
>>> Thoughts?
>>>
>>>
>>> -------
>>> Michael Coates | OWASP
>>> michael.coates at owasp.org | @_mwc
>>>
>>>
>>>
>>> On Mar 26, 2012, at 8:13 PM, Helen Gao wrote:
>>>
>>> Dear board directors,
>>>
>>> I am submitting a proposal on behalf of the Membership Committee. The
>>> document<https://docs.google.com/a/owasp.org/document/d/1jxaF8srnud3yRVYwZDSfqX-xrBfXFGrcPtrV3rd9Uq0/edit#>has been shared with you 3/22/12. There are two main modifications.
>>> Qualified people include honorary members in addition to paid members.  A
>>> person will be removed from the group if his/her paid membership expires or
>>> he/she stops being qualified for honorary status. One issue remains
>>> open. Should all qualified people be automatically added to the group
>>> or each person has to request to join?
>>>
>>> A new LinkedIn group for confirmed members
>>>
>>> What's the issue:
>>>
>>>    - Currently there is a Global OWASP Foundation LinkedIn group<http://www.linkedin.com/groups/Global-OWASP-Foundation-36874>.
>>>    It is free and open.
>>>    - Michael has created a OWASP Confirmed Member<http://www.linkedin.com/groups?about=&gid=4342746&report%2Esuccess=TAGQm5_B9ecwEPi7AtV-NGJjHoJV7WxoFbipydZrtoVPNQgWOUnL8lZj8v4Fi_efzerGsu5jt1ZNxbgOz-yQ8GA_JKRAMRHOdq9GTte76LaFDnVn3UJvJ9HrtwZdeRxnzSnL05Yi8ixSheCQVUTLJuPjHSEFDntOORiL00SBEWCSCN2GOP53E3gwyQES_UVQ4mMvuF1jt1Z1NDmQIe7vu9PrkoadDQtpb_DnGQi>subgroup designed for paid and honorary members only. See Michael’s email
>>>    thread OWASP on Linkedin starting March 7, 2012.
>>>    - This document has been shared with the board and several other
>>>    OWASP personals on 3/22/12. Jason Li, Jim Manico, Kelly Satalucia and
>>>    Michael Coates have provided feedback as of 3/26/12. Helen Gao has modified
>>>    the document based on their feedback.
>>>    - This document will be submitted to the board on 3/26/12 for
>>>    approval prior to AppSec DC.
>>>    - Helen Gao will email this document to committee members and OWASP
>>>    leaders on 3/26/12. Helen will collect feedback and submit to the board
>>>    Sunday, 4/2/12.
>>>
>>>
>>> GMC’s recommendation – GMC discussed the matter in the March meeting.
>>>
>>>    - The existing free and open LinkedIn group<http://www.linkedin.com/groups/Global-OWASP-Foundation-36874>should not be changed or impacted by the new group.
>>>    - The name of the group is OWASP Confirmed Member. Confirmed means
>>>    paid and honorary 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.
>>>       1. 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.
>>>       2. 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 or honorary
>>>       member then he/she will be added to the group.
>>>    - A person will be removed from the group if his/her paid membership
>>>       expires or he/she stops being qualified for honorary status.
>>>
>>>    FYI - The existing Global OWASP Foundation LinkedIn group<http://www.linkedin.com/groups/Global-OWASP-Foundation-36874>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.
>>>
>>> _______________________________________________
>>> Owasp-board mailing list
>>> Owasp-board at lists.owasp.org
>>> https://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
>>>
>>>
>>>
>>> _______________________________________________
>>> Owasp-board mailing list
>>> Owasp-board at lists.owasp.org
>>> https://lists.owasp.org/mailman/listinfo/owasp-board
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20120329/dd1f2b73/attachment-0001.html>


More information about the Owasp-board mailing list