-
Notifications
You must be signed in to change notification settings - Fork 70
Node.js Foundation Community Committee Meeting 2018-02-22 #245
Comments
I'll be at IBM Index (giving a workshop), so I won't be able to make it. |
I'm at Index as well, but might be able to make it depending on what is going on at that time (I'm not speaking at that time but still need to check what else is going on at that time). I'd say in 50/50. |
Hooray! 🙌 See y'all there. 🎉 |
Finally, joining in for my first meeting!! HooRRRAYY!!! |
Hope to become a champion soon (at the end of the meeting)!! |
Sorry folks, won't be able to make this one got two meetings in a row this thursday 😞 |
I may have a hard time attending, since I'll be traveling on Thursday. Is there anyone else that could drive it who has used Zoom before? |
I'm quite late to the meeting at the moment, sorry! But I'd still love to join if I can get the zoom link? ...if there is one? |
@obensource I think you are an hour off. It occurs in about 30 min. |
@tobyfarley Oh yes–you're right! My mistake. Awesome, thank you! 🙌 |
I’ve asked @mhdawson to help run this meeting since both @rachelnicole and I may not be entirely available for the meeting. |
Link for participants in case its not already in the issue |
Will post YouTube line for those who want to watch once we start the stream. |
Youtube loink https://www.youtube.com/watch?v=uZKB27_Xu4A |
BTW, the meeting notes for the last meeting are not published yet. |
NO!!! I missed the whole Meeting!! So, Sad Poor Network Ruined It All..... |
@oe How many meetings do I have to attend to become to moved my status from observer to member??Please, what's the link to the mentorship programme? |
@codeekage Usually 6 meetings, meaning 3 months' worth of attendance. For the mentorship initiative: https://github.com/nodejs/mentorship |
Today's meeting had a discussion about adding licenses. The TSC has requested that the Legal Committee review the topic and will be providing some feedback soon. We should hold off on adding new licenses until that information has been made public. PRs are OK- but lets not accept them just yet. Changing them after the fact may not be possible! See: nodejs/TSC#195 |
Sidenote: The YouTube video for this meeting links to the wrong issue |
@williamkapke I'm concerned that that issue has been stalled, seemingly without progress. @mrhinkle I'd like to add a request for an update from the Legal team if at all possible, or a comment that one isn't possible. We do have some work pending on this discussion, including licensing several of the newer CommComm initiatives. |
@bnb Yes, it mostly sat without progress for a very long time. So... I joined the Legal Committee, my attorney and I attended the meeting, and we are seeing this though. It is now in the process of finalizing the deliverable on it. It needs to get approval from the Board before I can do anything else publicly. I hope to see this done at the next board meeting- but that's not a guarantee. |
@williamkapke if there's not resolution in the next board meeting, would you be able to let us know? 🙏 |
Time
UTC Thu 22-Feb-2018 17:00 (05:00 PM):
Or in your local time:
Links
Agenda
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/TSC
nodejs/community-committee
Invited
Observers
Notes
The agenda comes from issues labelled with
cc-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
The text was updated successfully, but these errors were encountered: