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

EFI: New Technical Committee #168

Closed
sheplu opened this issue Feb 20, 2024 · 6 comments
Closed

EFI: New Technical Committee #168

sheplu opened this issue Feb 20, 2024 · 6 comments
Assignees

Comments

@sheplu
Copy link
Member

sheplu commented Feb 20, 2024

Motivation

The Technical Committee is the core group of the project, responsible for all actions and the Express organizations on part with other large Open Source Project.
Without this core group of people, the project is at risk and some critical decision cannot be validated. By having a sufficiently large group of people, it is certains that in a 2-4 weeks timeline decisions can be validated and acted on.

Expectation

Reform a full TC and do all the setup required leading to a global success.

Implementation

Update contribution
Update website
Announcement
Setup access (Github, Social, SaaS if any...)
Setup a new regular meeting for the TC

Status

Part: Organization
Status:

Draft

The Technical Committee (TC) is the core group of the project, responsible for all actions and guaranteeing a bright future for Express.
Reforming an active TC

@wesleytodd
Copy link
Member

expressjs/express#5483

That landed. I was thinking we need to consolidate the charter and contributing docs, did we have any more planed changes? Do we need this one still?

@sheplu
Copy link
Member Author

sheplu commented Feb 21, 2024

Updated this one with all the points, I think we are covered and we can close it.
The only missing point is the recurring meeting, but the issue is open, so I think we are covered here

If there is no objection I am closing that this weekend, giving a few days for people in the @expressjs/express-tc to comment

@UlisesGascon
Copy link
Member

Great consolidation, @sheplu!

One comment on setup access, the expected outcome is to grant access for all the TC members to all the repos in the orgs (I assume as owners?) and also to the NPM publication?

@sheplu
Copy link
Member Author

sheplu commented Feb 22, 2024

This would include all necessary access, so Github Orgs, NPM, zoom if we use one, Youtube, Twitter and all (for example specific SaaS products that could be used for ci/cd, security or other)

@wesleytodd
Copy link
Member

I guess we maybe do still want to call this incomplete until we get the npm stuff sorted. I think @dougwilson added Kylie to the youtube (and myself), but we do need to get a plan documented for managing that going forward as well. I guess the idea is, like the other things, any TC member should be able to manage it to make sure have no bottlenecks on getting things done.

@wesleytodd wesleytodd self-assigned this Mar 1, 2024
@wesleytodd
Copy link
Member

The npm stuff is sorted out and the first release went out. I say we call this one complete.

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

3 participants