OK, if it is more like a subscription then I retract my comments.
IP was a 'just in case' than making an arbitrary assumption.
And yes, Bylaws is a bit heavy for a subs org.. tho' some of that sentiment should transfer to the new instrument.

Executive Director
Cell: +44 (0)7490 266 778






On Fri, Jun 16, 2017 at 7:55 PM, Andrew Hughes <andrewhughes3000@gmail.com> wrote:
One topic we've discussed in the past is that membership to IDPro is more like a subscription rather than a membership in the sense of Kantara's membership. There is no IP contribution for ID Pro, and I'm having trouble thinking of how the bylaws would be relevant to this kind of subscription/membership. Sure, a Terms of Membership maybe.

Andrew Hughes CISM CISSP 
Independent Consultant
In Turn Information Management Consulting

o  +1 650.209.7542
m +1 250.888.9474
1249 Palmer Road,
Victoria, BC V8P 2H8
AndrewHughes3000@gmail.com 
ca.linkedin.com/pub/andrew-hughes/a/58/682/
Identity Management | IT Governance | Information Security 


On Fri, Jun 16, 2017 at 11:49 AM, Colin Wallis <colin@kantarainitiative.org> wrote:
So my sense is that it is a bit thin.
Understandable for a new org, but the CoCo points outwards that you will be a good person to the industry users does not say anything to the 'contract' to join the org. And it is a Contract.
Kantara has been a little light on this too, but is intending to tighten up in coming months.
An ideal membership Agreement would have a confirmation/signature that the applicant has read the essentials of the org.. that usually involves the benefits, Bylaws, Operating Procedures, privacy statement, IPR agreement and so on.
I know ID Pro does not have these but pointing it out now for consideration later.
The hard part is making an awesome UX while preserving the fact that there is an exchange - consideration of money in return for benefit with these rules applying. 
Cheers
Colin


On Fri, Jun 16, 2017 at 5:54 PM, Andrew Hughes <andrewhughes3000@gmail.com> wrote:
Looks about right...

One thought - how easy would it be to put #2 first then #3, pull the name/address etc from PayPal, then #1 as a confirmation step?

It would be nice to optionally collect twitter handles to allow a post-registration mutual follow - I don't think that's a large personal information liability to have that in the simple starter profile - probably same degree as email addy.

Andrew Hughes CISM CISSP 
Independent Consultant
In Turn Information Management Consulting

o  +1 650.209.7542
m +1 250.888.9474
1249 Palmer Road,
Victoria, BC V8P 2H8
AndrewHughes3000@gmail.com 
ca.linkedin.com/pub/andrew-hughes/a/58/682/
Identity Management | IT Governance | Information Security 


On Fri, Jun 16, 2017 at 9:47 AM, Sarah Squire <sarah@engageidentity.com> wrote:
Hey,

I'm building out the join experience today and tomorrow. Here's the flow I'm envisioning:

1. Form with name, title, org, email address
2. Code of conduct with checkbox to agree
3. Redirect to paypal and pay
4. Redirect back to IDPro "welcome to the org" page
5. Someone manually adds them to the mailman list (I'm sure we can find a way to automate that later)
6. Someone sends them a welcome email (again, automate that later)

Thoughts? Any steps I'm missing? Anything that could make the experience awesomer? Any other information we legally need to collect from them as members?


Sarah Squire
Engage Identity

_______________________________________________
IDProSC mailing list
IDProSC@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/idprosc



_______________________________________________
IDProSC mailing list
IDProSC@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/idprosc