- SQLSaturday events can email attendees with sponsors offers as part of the overall event, obviously using some discretion and restraint about how many times they contact the registrants. [I agree with this policy]
- SQLSaturday events can provide registrant demographics to sponsors only if the registrant opted-in. [Sane and fair, I agree with this policy]
- SQLSaturday registrations cannot be added to the supporting Chapter membership list. This is due to PASS being unable to make the privacy agreement specific enough on a per Chapter/Event basis. [I disagree – strongly]
The last two items are in conflict. SQLSaturday was designed as a membership drive and a fund raiser. It’s absurb to create the situation where the parent organization can grow their membership list but the local Chapter cannot. I see a few options to fix this:
- Add a checkbox to opt-in to Chapter membership. I’m not thrilled with this, but it’s a fair option.
- Send an email post event to anyone not on the Chapter list and ask them to join. The click through rate will probably be low, but it’s something – and it perhaps helps decrease the ‘duplicates’ that end up on the membership list.
- I’m hard pressed to say why it wouldn’t be equally fair to do this for joining PASS. Maybe they are already members, maybe they don’t want to be members. I don’t like this, I think it’s anti-success, but what is good or not for Chapters should be the same for PASS
- Perhaps simplest is to have the Chapter sign the SQLSaturday event agreement. In the handful of cases where the event is not affiliated with a a Chapter then the current rule would make sense, otherwise the chapter/event are one and the same – and that was really the intent from the beginning.
Apologies for the mid week rant, but this is important stuff.