Open kcranston opened 6 years ago
Thanks for summarizing our next steps, @kcranston
Question for @k8hertweck -- do the nominees know about this suggestion for allocating votes to terms? I think everyone may have thought they were running for a one year term.
@maneesha No, we haven't specified how we'd handle the peculiarities of this first round of voting until it came time to put the ballot together. I had assumed all candidates would expect a two year term, as that is what is described in the RFC, but I see that the announcement blog post wasn't explicit about the maximum term. This should be explained when emailing candidates as well. Who wants to handle this?
I've volunteered to send the email to the candidates with this info.
I have done a blog post that links to all 8 nominees so far to make it easier for you http://www.datacarpentry.org/blog/meet-candidates/ @k8hertweck @kcranston
Just for my own notes:
00:00 Dec 4 UTC+12 = 07:00 Sun Dec 3 EST 11:59 Dec 8 UTC-12 = 06:59 Sat Dec 9 EST
Election set up and notices will go out starting at 00:00 UTC+12 Dec 4.
@kcranston Do we have a date when results will be announced? Asking for newsletter.
Likely sometime Monday Dec 11.
On Dec 3, 2017 20:48, "Belinda Weaver" notifications@github.com wrote:
@kcranston https://github.com/kcranston Do we have a date when results will be announced? Asking for newsletter.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/carpentries/2017Merger/issues/12#issuecomment-348840235, or mute the thread https://github.com/notifications/unsubscribe-auth/AATC4pV1PB0_OvT4NCRGq-dduXMz13-kks5s8093gaJpZM4Qr022 .
Thanks @kcranston !
I want to document this whole process for next time. Some notes for reference for here:
We should have had someone specifically designated to check for submitted nominations and post them on the blog until UTC+12 on the last day of nominations (the last time zone in the world that it is still that day)
We had a lot of trouble with the query used to generate the member list. This is the query we used
select contact from
(
select person.personal || ' ' || person.family || ' ' || person.email as contact
from workshops_person as person
join workshops_event as event
join workshops_task as task
join workshops_role as role
join workshops_award as award
join workshops_badge as badge
join workshops_event_tags as event_tags
join workshops_tag as tag
on person.id = task.person_id
and event.id = task.event_id
and role.id = task.role_id
and award.person_id = person.id
and award.badge_id = badge.id
and event_tags.event_id = event.id
and event_tags.tag_id = tag.id
where role.name = 'instructor'
and badge.name in ('swc-instructor','dc-instructor', 'trainer')
and (tag.name = 'LC' or tag.name = 'DC' or tag.name = 'SWC' or tag.name = 'TTT')
and event.start >= '2015-11-30'
and event.end <= '2017-12-01'
group by person.id
having count(*) > 1
union
select person.personal || ' ' || person.family || ' ' || person.email || ' ' as contact
from workshops_person as person
join workshops_award as award
join workshops_badge as badge
on award.person_id = person.id
and award.badge_id = badge.id
where badge.name = 'member'
);
List of things that need to be done for the upcoming election.