-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start PyLadies Member Database #54
Comments
|
@trallard definitely 👍 on GDPR compliant. It was a total memory lapse when the initial form was made for Chapter Directory. As per the Member Directory what alternative to Google Forms do you suggest? I talked with the PSF and that’s what they have in place (a new CRM is coming sometime next year). I don’t want us locked into paid software if it isn’t necessary as we should be considering plugging into the PSF infra in the future. Specifically the thought is when people register as a PSF member one option for membership is as a PyLadies member! |
I am not sure what alternatives would be suitable in this case. I think Typeform is generally a good alternative. But I will make sure to do more digging around other alternatives that won't prevent us from joining the PSF infra in the future. |
Typeform works for me! Thanks @trallard ! |
QuestionsFor the member chapter directory here's some proposed questions I think we should collect ...
|
That looks good. I think at least the following questions should allow for folks to self define (i.e. provide an "other": option):
|
Some of these questions look like they would take free form responses (How do you use Python? Also, if we're just trying to learn more about members, should we also ask:
|
Asking for members consent to receiving newsletters can be considered. |
Updated with additional questions ... QuestionsFor the member chapter directory here's some proposed questions I think we should collect ... Member Information
PyLadies Chapter Membership
PyLadies Programming and Communication
PyLadies Volunteering
Python Background
General GDPR Compliance
|
There are a lot of questions here... Some thoughts:
|
I understand we do want to collect these info, but it feels that these questions about "programming", "volunteering", "python background" are more like a survey type of question, rather than for building a member directory. |
@Mariatta I can definitely understand. That said here's some thoughts: What are we collecting this info for? Great question! I think we need to maybe refocus. There's two options:
Why would we want to collect for a member database? Outreach is hard, as we have seen with the PyLadies Chapter Directory. It takes a while. Making this a "two for one" effort means we can start collecting data points that are useful for Project teams (and perhaps for us to start developing internal heuristics for measuring PyLadies community and community engagement!). Doesn't collecting this info become static? Yes, @Mariatta definitely we would want to check in on this. We could email members at the start of every year and confirm:
TLDR I think it behooves us to start getting more info at the start but specifically start collecting now since we will start using this for the election.If we are concerned about maintenance or this being too much we can make everything but member info, chapter info, and waiver to say we can email optional. Thoughts? |
I think those are really good points @Mariatta. Maybe we should keep the data collection more minimal for the database purpose and break the rest into a survey if we are interested to know about about the current preferences and status of each member (or collect the data the same way but only store limited entries in the DB). I think @lorenanicole 's idea of having members update transient data every year could work, but will require more effort than keeping a more basic list that people just subscribe and unsubscribe from. |
@jesford @Mariatta I asked the @pyladies/communications for a point person to help us develop a comms strategy for this. Perhaps what we can do is take the questions and break them up to work into that strategy including:
|
As background, would someone familiar with it be able to summarise how membership/voting eligibility is handled in PSF? is there infra or experience there we could leverage? |
@pfctdayelise great question! I'm a Director with the Python Software Foundation and have raised this question in the on-site PSF Board meeting Nov 2019, and the answer right now is no. Why? Future PyLadies Membership Registering
Porting data
Does that answer your question? |
Thanks, yes it does about the infra. What about the eligibility to vote? Seems like in PSF 'Basic' (self sign up) members can't vote, and you need to either pay an annual donation (membership fee) or apply as a managing/contributing member which is reviewed by the board. What's our equivalent expectation? |
@pfctdayelise I believe you are asking, "do all PyLadies registered members get to vote?". In which case, this is a great question and is something that needs to be discussed now that the PyLadies organizers have voted on using public election as part of the selection process. I believe that is beyond the scope of this issue. In fact, it is an issue on my list to open! |
We've got to start getting this moving ... and I actually just noticed a model that maybe is a good one for us to follow to start - the Code for America Bridge National Advisory Council elections. See: https://brigade.codeforamerica.org/about/national-advisory-council/2020-candidates. To vote, members have to confirm they've taken the "census survey", which in effect means confirming membership in a brigade chapter. The survey then collects demographic info, which is something we've been debating. That said, I am going to revisit my proposal:
TLDR; I propose we do the following, please review as I will be moving this forward with a proposal at the next Global Meeting on Feb 12th #55:
@Mariatta @jesford @pfctdayelise @trallard would that sound agreeable? |
This sounds great to me @lorenanicole! On point 3 we could require or request that members without a local chapter join PyLadies Remote (I just checked their site though and it doesn't look like they've been active lately, so maybe not). https://remote.pyladies.com/index.html |
@jesford we can have them do that! I know @ossanna16 use to run that, @ossanna16 is anyone actively maintaining that? If not, could we reset that to perhaps be the global group for now so folks have a chapter they can run? I actually wouldn't mind being a "lead" in that I can schedule a remote chat more easily now these days than an IRL experience. |
Hiya! I actually don't lead PyLadies Remote anymore. Please reach out to Corryn Smith about this. I can provide an email address in a private channel. |
I might be missing something obvious, but where is this database going to live and who will have access to this? Is this going to be access by the PSF and interim gov team? |
@trallard the plan is to turn the database over to the PSF to house in their system when a new CMS is selected in later 2020. For now, we can house the information as a Google spreadsheet and restrict access to only those that are admins on the PyLadies Google account. |
Since we've had some feedback that becoming a basic PyLadies member (e.g. added into PyLadies database) shouldn't be contingent on additional data collection, here is two forms I am proposing for registering to become a member: Registration for Basic Member (No Voting):Member Information
PyLadies Chapter Membership
PyLadies Membership Option
General GDPR Compliance
Registration for Voting Member:Member Information
PyLadies Programming and Communication
PyLadies Volunteering
Python Background
General GDPR Compliance
|
Will the information be shared with the local organizers? |
@wgrus great question! I have amended the question section in this issue above to answer in question 2. |
Not sure if this would be a lot of work, or is it possible at all: would be great if the "chapter affiliation" is a dropdown of known registered pyladies chapter, instead of a freeform text. The rest looks good to me. Thanks. |
@Mariatta we will figure out a way! If we have to we can link to an external list and have them pick from there.
|
We have extended the proposal for: registration for chapters, verification of members, and more in the proposal above. Please weigh in! We are aiming to start member registration Mar 1 2020. |
@deboraazevedo @elainewong here's the questions we need translated: https://gist.github.com/lorenanicole/73a142b1cee06cba7c6eed3dd237129e. Let's aim to get this translated by Feb 28? @BethanyG you can start using this for our forms. |
I suggest that social media handle shouldn't be optional... At least one should be compulsory... Because it will help in networking with the members via other platforms. |
Thanks for the input @treasurechristain! One thing about requiring a social media handle, though, is not everyone uses social media. So unfortunately that’ll mean we need to keep it optional. Was there anything else? |
Any updates on the member registration translation @deboraazevedo @elainewong ? |
There was no edit requests on the docs, as Mariatta pointed out. I'm doing the Portuguese translation myself. Today Mariatta suggested to post this request on the general channel on Slack |
I've posted in psf-community mailing list https://mail.python.org/pipermail/psf-community/2020-February/000770.html |
I can take the Spanish translation. Sorry if I have been MIA |
@Mariatta did you mean https://github.com/alphacentauri82 has done the translation? |
Updated the issue already! |
Nice work so far... |
This is already done ! CLOSING! |
Overview
Now that #50 is open, per the timeline we have to start preparing for outreach with our PyLadies members to in April / May 2020 either vote or nominate themselves for the inaugural PyLadies Global Council. To do this, we need a distribution list to communicate with our PyLadies members directly.
Deliverables
Jan 23rdFeb 12th checkin (@deboraazevedo @lorenanicole) re: translation + outreach strategy plan- Mediums
- Assets for translation
- How are we tracking outreach?
- The Project Comms team is starting to help see: PyLadies Global Council Election Comms Strategy 2020 project-communications#24
PyLadies Membership Registration
Proposal is for:
See: #54 (comment)
Per the Feb 2020 PyLadies Global Meeting we decided the following #60
Registering for a chapter:
other
fieldHow will we disseminate registration
Verifying Members
PyLadies chapter organizers will be able to "verify" their own members: - - No one external will weigh in
PyLadies with no local chapter, inactive, or remote:
Questions
To start, in the PyLadies Google account (e.g. spreadsheets). We can restrict access only then to official
@pyladies.com
Google accounts.The plan is to forward this data to the PSF when they move to a new CRM in 2020 per a chat with @ejodlowska. See: #54 (comment).
Yes. Per question 1, we will house the information initially within the PyLadies Google account. We can then restrict information using the
[email protected]
Google accounts. See: #54 (comment).The text was updated successfully, but these errors were encountered: