search

pyladies / global-organizing

Repository to track global organizing
46 stars 14 forks source link

PyLadies Global Election - Public Election Tracker Issue #59

Closed lorenanicole closed 3 months ago

lorenanicole commented 4 years ago

PyLadies Global Election - Public Election Tracker Issue

Questions to answer for Public Election

Deliverables

Hack session

@lorenanicole will work on Sun at 10:00 CT

issues to open:

lorenanicole commented 4 years ago

Should voting will be open to any registered PyLadies member?

I would advocate that voting should be open to any self identified PyLadies member registered in the database.

@pfctdayelise what are your thoughts?

Mariatta commented 4 years ago

should voting will be open to any registered PyLadies member?

1) How does one became registered as a PyLadies member? (I assume the will be a form). Does membership means they must be belonging to a chapter? (local/remote) or say if they are in PyLadies slack, and there is no local chapter in their area, can they still become a member?

2) Do we need to set a deadline, e.g must be registered before MMM, DD, YYYY in order to be eligible to receive the voting ballot? E.g. if they became a member after voting has started, can they still vote?

What tech should be used for voting?

The PSF uses Helios voting system, that seems to work and familiar to PSF members. Perhaps we should just use the same.

pfctdayelise commented 4 years ago

@lorenanicole Maybe it's paranoia but I was just thinking about how things like twitter are stormed with bots. Imagine if pyladies got flooded with fake registrations that in the future were used to put some, IDK, MRA person that had nothing to do with pyladies, into the council.

It's generally easier to extend voting rights than to take them away, so maybe start cautiously with people that have somehow been 'vetted' by others. (eg core team vets chapter leaders, chapter leaders vet people in their chapters) It's a lot more work though...

@Mariatta I think your Qs are covered in #54

Is Helios based on a first-past-the-post method or something else? (I'm really surprised this isn't prominent on the Helios site.) How does it work when there are multiple seats, is it just first-N-past-the-post?

lorenanicole commented 4 years ago

@pfctdayelise regarding:

Maybe it's paranoia but I was just thinking about how things like twitter are stormed with bots. Imagine if pyladies got flooded with fake registrations that in the future were used to put some, IDK, MRA person that had nothing to do with pyladies, into the council.

The PSF doesn't do vetting per say, instead there's just a registration form on the website. That said, being cognizant of groups for underrepresented people being targeted is a huge point to say being more thoughtful is better.

So that said, are you suggesting that instead of an open link online instead we can have chapter organizers disseminate a registration form? I am 👍 that. However what is someone is a PyLadies member but there's no local PyLadies chapter for them to participate in? In considering precedence, anyone can claim to be a PyLadies member for the PyLadies financial sponsorship opportunities for PyCon US. If we start moving away from that we are in effect starting new precedence here.

Mariatta commented 4 years ago

I found the following documentation on what happens in case of a tie in PSF's board of directors election: https://github.com/python/psf-election#in-the-event-of-a-tie not sure if this is up to date information.

Other org like Open Source Initiative does run-off voting in case of the tie. I think that's an option as well. But perhaps we need to choose upfront, whether we will do the run-off, or doing what the PSF does (use a script to break a tie)

pfctdayelise commented 4 years ago

The PSF doesn't do vetting per say, instead there's just a registration form on the website.

But Basic members can't vote. To vote you need to be Supporting (donate money, which is automatic but adds enough friction to stop bots) or Managing/Contributing/Fellow.

Well I guess there is one form for Managing/Contributing, maybe it doesn't get meaningfully reviewed? I was assuming someone at least glanced at it before someone got 'approved' in one of those categories.

So that said, are you suggesting that instead of an open link online instead we can have chapter organizers disseminate a registration form? I am 👍 that.

Having diff organisers disseminate a form sounds difficult. I was thinking they could nominate a chapter that they have participated in and then the responsibility for saying 'have I ever heard of this person' would fall to the organisers of the chapter they nominated.

However what is someone is a PyLadies member but there's no local PyLadies chapter for them to participate in? In considering precedence, anyone can claim to be a PyLadies member for the PyLadies financial sponsorship opportunities for PyCon US. If we start moving away from that we are in effect starting new precedence here.

Well, there is pyladies 'remote'. But it comes back to how do we actually consider someone part of our community? What does participation in the pyladies community look like? I would presume it includes some Python at some level. Maybe the simplest way to do this would be have a write-in field 'What does participation in the pyladies community mean to you?' which is reviewed for some comprehensible mention of Python related activities.

lorenanicole commented 4 years ago

Some thoughts:

Having diff organisers disseminate a form sounds difficult. I was thinking they could nominate a chapter that they have participated in and then the responsibility for saying 'have I ever heard of this person' would fall to the organisers of the chapter they nominated.

I'm +1 on the format being: someone applies to be a member, selects a chapter, the chapter organizers "review".

That said, though, I can say as a community organizer for 5+ years for PyLadies Chicago, I definitely cannot recall all our members. I would probably at least do something like: confirm they are in the slack, or they are in the meetup.

Would some minimal review like that work for you?

Maybe the simplest way to do this would be have a write-in field 'What does participation in the pyladies community mean to you?' which is reviewed for some comprehensible mention of Python related activities.

I like this idea! I think we should error on being more inclusive rather than exclusive.

pfctdayelise commented 4 years ago

That said, though, I can say as a community organizer for 5+ years for PyLadies Chicago, I definitely cannot recall all our members. I would probably at least do something like: confirm they are in the slack, or they are in the meetup.

Would some minimal review like that work for you?

Yes, that is exactly what I would do (additionally I would check they have been a meetup member since before the election date).

Mariatta commented 4 years ago

Sorry in advance for long reply, lots of thoughts and concerns:

trallard commented 4 years ago

I agree with @mariatta on the points above I would not like this to turn into extra burden for both the local organisers or any of us.

The GitHub option sounds like a good one to reduce the number of bots. I would agree also on having those being nominated mainly as a PyLadies member and have some way of verifying this info (this should be easier than verifying the info of all the ones willing to vote)

pfctdayelise commented 4 years ago

@Mariatta fair points. Is requiring a github account a reasonable burden? There may be some people that have closed their account for ethical reasons...on balance, I would be prepared to defend that requirement as a reasonable one.

sleepypioneer commented 3 months ago

@lorenanicole could this issue be closed as it appears to have been moved to Done on the project board? Perhaps however there is a reason to keep the issue open?

BethanyG commented 3 months ago

@sleepypioneer -- Thanks for pointing out these open issues! I am going to go through and do some general housekeeping/closing. 😄 We can always refer back/reopen anything if its needed in the future.