-
Notifications
You must be signed in to change notification settings - Fork 133
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
doc: add minutes for meeting 10 Jan 2018 #468
Conversation
I was thinking that there's no reason an observer can't do the minutes. So maybe there's a Collaborator or other regular listener to the stream that might be willing/able to volunteer to take minutes some time, since it seems to be a lot to ask Michael to both run the meeting and take the minutes, and it's not like any attendees are jumping at the chance to take the minutes right now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
meetings/2018-01-10.md
Outdated
* Franziska: who is responsible for receiving and acting on the feedback. | ||
* James: will attend as observer and will provide feedback, other TSC members are | ||
free to participate as observer as well. | ||
* Franziska: should we clarify in the charter that there is no commitment on the TSC's part. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The indentation looks off here, this (and subsequent) bullet(s) are still part of the Enterprise Advisory Group discussion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed commit to fix.
* Async Hooks: Some help getting changes for Async hooks for Nan would be good. | ||
* V8 currency: Nothing new | ||
* TSC governance, Myles will be reviving this and initial focus may be on providing growth | ||
paths for contributors. Refactoring on strategic initiatives to include .stakeholders. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these supposed to be separate lines/sub-bullet points or something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Trott, they could be but not sure they have to be. Myles mentioned 2 things that he would be reviewing that issue and work that would be started would have an initial focus on providing growth for contributors. The other thing he mentioned is that he had a PR oven to refactor the list of strategic initiatives to include stakeholders in addition to the champions. Notes were a bit terse.
meetings/2018-01-10.md
Outdated
* Moderation | ||
* One user permanently banned for wiki vandalism. | ||
* Myles dealt with a spam-bot invasion on #node-dev IRC channel | ||
* One user.s comment was moderated by a Collaborator, moderation group called into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
user.s
-> user's
meetings/2018-01-10.md
Outdated
* One user.s comment was moderated by a Collaborator, moderation group called into | ||
advise. User was also emailed by a moderation team member. Conversation | ||
seems to have righted itself, and user is getting necessary help in the correct forum. | ||
* We.ve received two or so blank emails to the CoC reporting address. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We.ve
-> We've
No description provided.