-
Notifications
You must be signed in to change notification settings - Fork 70
Mentorship Team under the CommComm #172
Comments
@hollomancer of Operation Code mentioned he is interested. Moreover, he shared these resources which they use to support mentorship at Operation Code: |
@dshaw I am interested to help in the mentorship program |
@dshaw @hollomancer @Bamieh Can you attend the next CommComm meeting? One of the things we've been talking about with all of the moving parts in CommComm right now is finding a way to identify and track initiatives that need to happen, but that we also don't want to be starting up projects if we don't have a sufficient number of people able do the work(the hours needed not just in meeting to organize but in this instance, to find/screen/provide a framework/provide ongoing support for the mentors and mentees). Let's make sure we're setting this up for success! |
@hackygolucky Sure I'd love to join, when is the next meeting going to be? |
@Bamieh Thursday at 12pm ET - I will be posting the meeting proposal tomorrow or Thursday 👍 |
Hi, I am at the CommComm meeting and due to time constraints as suggested by @bnb , I'm preferring to comment here. I'm new to the NodeJS processes however, have good experience working at the Outreachy Initiative and mentoring folks at other open source foundation. So, I think I can help out well with the Mentorship initiative, setting and maintaining processes, guides etc. Please consider me for any possible co-championship required help. cheers. |
@bnb In highlight of today's meeting, you offered to help in getting this initiative started. I have some notes written that i'd like to discuss but i have no idea how to contact you 😄 |
Totally interested in this but I've been taking a wait-and-see-what-it-shapes-up-to-be approach. It's not clear to me who the mentees are supposed to be, for example. (Anyone? New collaborators who have already gone through the onboarding process? Something else?) |
I think that I was one of the people to originally suggest a mentorship program. I was originally envisioning that each new collaborator would get a mentor with their commit bit |
@Bamieh sorry for not getting back to you sooner, I was OOO on Thursday/Friday and the meeting was the only Node.js-related thing I did those days 😅 You can reach me via DM on Twitter or via email at hello [at] bnb.im |
This was raised as well in the last meeting, so we should probably follow up here.
|
Is there any way we could have some sort of polling on the interwebs/on the org to gather informations about these questions? |
Here's the repo that @Bamieh has been doing this work on - amazing work! |
@bnb how can i help with the |
@Bamieh so we're going to have to do that work here - the next steps will be agreed upon by the TSC and CommComm in this issue: nodejs/admin#35 |
Going to remove the CC-agenda label from this, since I added it to nodejs/admin#35 |
Since we've made significant progress, and it's generally acknowledged that this will be a joint CommComm + TSC effort under Admin, I'm going to close this. Looks like it's relatively well referred to by the Mentorship team members, so feel free to re-open if needed. |
During this week's TSC meeting, it was mentioned that @nodejs/tsc has not found a champion for the Mentorship core initiative. I offered to take on the Mentorship initiative and bootstrap it in the CommComm. https://youtu.be/eSgqJg7pu_M?t=47m0s
@MylesBorins notes that it will be vital to have TSC input and participation. I think that means Myles is volunteering. 😜
I'm a bit saturated with bootstrapping @nodejs/user-feedback and Governance right now. I personally don't think I'll be able to start meeting on this until mid-December. If you are interested in helping lead, my experience is that will take about 10 hours a month while getting started. I would love to help someone lead rather than taking this on myself.
If you are interested in co-organizing. The expectations would be ~5 hours/month for co-organizers. Please raise your hand if you're interested.
The text was updated successfully, but these errors were encountered: