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

doc: remove TSC agenda requirement for nominations #19459

Closed
wants to merge 1 commit into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Mar 19, 2018

Remove the requirement that Collaborator nominations be announced in TSC
meetings.

Checklist

Remove the requirement that Collaborator nominations be announced in TSC
meetings.
@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Mar 19, 2018
@Trott
Copy link
Member Author

Trott commented Mar 19, 2018

@ChALkeR
Copy link
Member

ChALkeR commented Mar 19, 2018

@Trott, for background — what was the original reason behind having that requirement?

@Trott
Copy link
Member Author

Trott commented Mar 19, 2018

@Trott, for background — what was the original reason behind having that requirement?

I'm guessing a combination of ensuring TSC awareness and following tradition. /ping @joyeecheung

@joyeecheung
Copy link
Member

@ChALkeR @Trott
The original idea came from #18090 (comment) by @mcollina

e. I think we should have a fixed session on the TSC meeting to nominate people that have been suggested: that should allow a very quick turnaround.

@joyeecheung
Copy link
Member

Also, I did not intend for this to be a requirement, just something that we do to recognize the contribution done by the new collaborator.

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be the other way around. And we just "read the announcement" during the meeting, nothing to discuss really. It's a nice "welcome!" to people that we think have contributed to Node.js significantly.

I won't block this.

@Trott
Copy link
Member Author

Trott commented Mar 20, 2018

I think it should be the other way around.

@mcollina You mean it should be required to be announced at the TSC meeting rather than on the mailing list? I would agree with that. This isn't intended to stop those announcements. It's intended to stop them from being added as agenda items. Maybe I need a different approach here.

@ChALkeR
Copy link
Member

ChALkeR commented Mar 20, 2018

@Trott @mcollina Perhaps adding different section, «Nominations», to the meeting template?

To separate technical things that we actually (should) discuss a lot from nomintations which are mostly acknowledgements at the point when they are announced at the meeting (as they have been previosly discussed e.g. at GitHub by that point).

@targos
Copy link
Member

targos commented Mar 20, 2018

They can be in the existing "Announcements" section.

@mhdawson
Copy link
Member

I have no objection to this, but tagging the issue with the agenda label, versus somebody having to remember and then manually update the agenda is much easier in my opinion. If we still want them announced in the meeting then I don't see the problem with the current approach. If we don't mind one way or the other or prefer to not mention them, then avoiding tagging makes sense.

@Trott
Copy link
Member Author

Trott commented Mar 20, 2018

I'm going to close this. If the current imperfect-but-working-well-enough system is working well enough for people, I won't break it. :-D

@Trott Trott closed this Mar 20, 2018
@Trott Trott deleted the i-have-no-agenda branch January 13, 2022 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants