Skip to content
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

Voting CPC Representatives from Projects #152

Closed
jorydotcom opened this issue Apr 8, 2019 · 34 comments
Closed

Voting CPC Representatives from Projects #152

jorydotcom opened this issue Apr 8, 2019 · 34 comments

Comments

@jorydotcom
Copy link
Contributor

jorydotcom commented Apr 8, 2019

Creating this issue to capture the appointments and nominees for the CPC per a question from one of our projects!


Impact Project Representative Appointments (up to 2 per project)

Growth & At Large Nominees (up to 2)

@molant
Copy link
Contributor

molant commented Apr 8, 2019

webhint: @molant

@Jonahss
Copy link
Member

Jonahss commented Apr 12, 2019

Appium representatives will be @dpgraham and myself 👋

@christian-bromann
Copy link
Member

christian-bromann commented Apr 12, 2019

As mentioned in webdriverio/webdriverio#3824 for WebdriverIO it will be TSC members of the project, depending who is available in US/Europe. These are:

@kborchers
Copy link
Contributor

Architect's nominee is @kborchers per architect/architect#349

@knolleary
Copy link
Contributor

knolleary commented Apr 15, 2019

Node-RED's rep nominee will be @knolleary (node-red/node-red#2129)

@mhdawson
Copy link
Member

TSC progress on electing one Node.js rep, nodejs/TSC#689 CommComm will kick off process as well.

@eemeli
Copy link
Member

eemeli commented Apr 16, 2019

Messageformat's nominee will be @eemeli (messageformat/messageformat#232).

@amiller-gh
Copy link
Contributor

CommComm nominations now open: nodejs/community-committee#470

@mhdawson
Copy link
Member

mhdawson commented Apr 25, 2019

@mcollina has been confirmed as the TSC Node.js Voting CPC member. @amiller-gh will confirm when the CommComm Node.js voting member has been confirmed.

@keywordnew
Copy link
Member

Thank you for taking on the work, @mcollina 🙏🏽

@keywordnew
Copy link
Member

CommComm will announce a CPC rep on 30th April. Progress is on nodejs/community-committee#470.

@dylans
Copy link
Contributor

dylans commented May 1, 2019

For Dojo we would like to nominate Matt Gadd ( @matt-gadd) and me (Dylan Schiemann, @dylans). Let me know if that’s fine or if you have any questions.

@TheLarkInn
Copy link

For webpack we nominate @TheLarkInn Sean Larkin and @evenstensberg Even Stensberg as representatives.

@amiller-gh
Copy link
Contributor

Joe Sepi (@joesepi) has been elected the CommComm voting CPC member: nodejs/community-committee#470

@jorydotcom
Copy link
Contributor Author

WOWOWOW way to go everyone, we got all our impact reps & nominees in right on schedule!!!!!!!!!!!!!
THANKYOU!!!!

@jorydotcom
Copy link
Contributor Author

follow-up ask to all reps & nominees - please take a sec and share your meeting time availability on this spreadsheet - note that there are 2 tabs!

@jorydotcom
Copy link
Contributor Author

Heads up, everyone who was selected or nominated to the CPC from an Impact, Growth, or At Large project has now been invited to join this repo for write access. Please check your notifications!

@brianwarner
Copy link
Contributor

@matt-gadd, @dpgraham, and @evenstensberg - I need your email addresses to populate the mailing list, please. Can you drop me a line at [email protected]?

@joesepi
Copy link
Member

joesepi commented May 8, 2019

In the most recent meeting, it was suggested and there was discussion around having all nominees from growth and at-large projects be voting members this first year to help bootstrap the council and further the work with more hands. (Rather than voting it down to only 2)

One thing I notice is that 3 of those 5 nominees are IBMers. If we were to invite all 5 of them to be voting members, that would make 4 out of 15 voting members IBMers (including me). The language states no more than 25% from one company. @boneskull said he would withdraw if this was an issue. I just want to share the situation for the group to discuss.

@boneskull
Copy link

(4 of 15 is 26.66%)

@Jonahss
Copy link
Member

Jonahss commented May 8, 2019

Thanks for pointing it out. I think one of them should drop out then.

@boneskull
Copy link

or we could add another rep to make it 25% 😇

@MylesBorins
Copy link
Contributor

I'd like to +1 what @Jonahss suggested, one of the IBM members should drop out.

@mcollina
Copy link
Member

+1 to @Jonahss proposal

@joesepi
Copy link
Member

joesepi commented May 13, 2019

It was proposed last week--and discussed then as well as today's meeting--that we take on all growth and at-large nominees to bootstrap the CPC group for the first year and then next voting cycle elect 2 members from growth and at-large projects. There seems to be general consensus on this proposal.

The only issue is that that would put too many people from one company. We will work out that offline, one member from that company will withdraw, we will post an update on this thread soon with the withdrawn member. (some discussion above)

Beyond this one issue, we will assume consensus unless objections are noted here. Thanks!

@knolleary
Copy link
Contributor

Having discussed with @boneskull, I withdraw my nomination.

@MylesBorins
Copy link
Contributor

Thanks @knolleary

With Nick withdrawing from the race we have our voting members! I've added everyone to the @openjs-foundation/cpc-voting-members team, which is a child team of @openjs-foundation/cpc

They have write access on this repo! Closing the issue

@joesepi
Copy link
Member

joesepi commented May 21, 2019

Hey y’all. I made a mistake.

When I posted shared the CPC nominees in our IBM slack chat, the name @eemeli was highlighted and when I looked at that users profile there were things that made me assume the IBMer and Eemeli were the same person. THEY ARE NOT. I should have checked this but I didn’t.

Therefore, with the original intent being an inclination to have more voting members actively participating to “bootstrap” the first year of the CPC, I propose we allow @knolleary to be a voting member as well.

Sorry for the mixup. :/

@joesepi joesepi reopened this May 21, 2019
@boneskull
Copy link

so we're clear, @eemeli, you don't work at IBM, right?

@eemeli
Copy link
Member

eemeli commented May 21, 2019

This is correct. I do not, and never have, worked for IBM. On the other hand, if this is the most indirect recruitment pitch I've received so far, please do get in touch with me directly as well.

@MylesBorins
Copy link
Contributor

MylesBorins commented May 22, 2019

I went through and did my best to map folks to their affiliation

Node: Matteo Collina (@mcollina ) NearForm & Joe Sepi (@joesepi) IBM
jQuery: Dave Methvin (@dmethvin) Independent & Timmy Willison (@timmywil) Pylon
Dojo: Matt Gadd ( @matt-gadd) Independent & Dylan Schiemann (@dylans). SitePen
Appium: Jonah (@Jonahss) Cloud Grey & Dan Graham (@dpgraham) Sauce Labs
webpack: Sean Larkin (@TheLarkInn) MSFT & Even Stensberg (@evenstensberg) Independent

Antón Molleda (@molant) MSFT
Kris Borchers (@kborchers) MSFT
Eemeli Aro (@eemeli) Vincit
Chris Hiller (@boneskull) IBM
Nick O'Leary (@knolleary) IBM

Total: 15

IBM: 3
Independent: 3
Microsoft: 3
Cloud Grey: 1
NearForm: 1
Pylon: 1
Sauce Labs: 1
SitePen: 1
Vincit: 1

Did I get anything wrong?

@eemeli
Copy link
Member

eemeli commented May 23, 2019

If we're listing these associations anywhere, I'd appreciate myself as being listed under Vincit, as they do pay my salary and are sponsoring some of my work on messageformat.

@joesepi
Copy link
Member

joesepi commented May 30, 2019

This was briefly discussed in person at Collab Summit CPC meeting just now and there were multiple +1s and no objections to including @knolleary as a voting member. See above comments for more context.

@joesepi joesepi closed this as completed May 30, 2019
@dylans
Copy link
Contributor

dylans commented May 31, 2019

Sorry for the very delayed reply... Matt Gadd is also with SitePen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests