-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Create matrix of people as subject matter experts #22625
Labels
roadmap
Top level issues for major efforts in the project
Comments
dod you mean "subject matter experts"? |
mosabua
changed the title
Create matrix of people and subject matters
Create matrix of people as subject matter experts
Jul 9, 2024
I reworded along that notion. |
Current attributes and details I can think of:
Attributes for each person:
|
Please reference the list of SMEs in the PR issue template. |
Good idea @findinpath |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In our Trino Contributor Call we talked about establishing a matrix or so of people in the community and their focus/knowledge in terms of contributing to Trino. The aim is to have a list of people for different parts that you can ping in pull request and design reviews and so on.
My current idea is to implement a data file on the website about people and their areas and roles and whatever, similar to users as well as the ecosystem pages.
I can then use the data file to render multiple pages or a single page with different sections for roles, skills, and so on and with info like github username, full name, linkedin profile or whatever else desired.
I think the website is the right place since it has the infrastructure for this already in place, and the scope of the list should be all projects within the trinodb org.
I can start with collecting the info for all maintainers and subproject maintainers and a number of other experts I am aware of. From there we can then crowdsource and get individuals to update their own info as well as supply info for others.
The text was updated successfully, but these errors were encountered: