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

[Suggestion] Improve new member experience, allow easier involvement/induction #666

Closed
lumjjb opened this issue May 26, 2021 · 17 comments
Closed
Labels
good first issue Good for newcomers governance inactive No activity on issue/PR suggestion New suggestion for the CNCF sig-security group that don't fall into an existing category

Comments

@lumjjb
Copy link
Collaborator

lumjjb commented May 26, 2021

Description: What's your idea?

Improve new member experience to allow members to be able to contribute faster, or get more comfortable with the contribution process.

Impact:

This will help strengthen the community by getting more members engaged.

Scope:

"not yet determined"

Additional info:

  • Current new members page
@lumjjb lumjjb added suggestion New suggestion for the CNCF sig-security group that don't fall into an existing category triage-required Requires triage labels May 26, 2021
@TheFoxAtWork
Copy link
Collaborator

can we have a bot to message them when they join the channel with details about getting started "read this, create your first PR with us by tackling a good first issue"? and then in another post in a month to say "don't forget to introduce urself at a meeting and add urself to the repo"

@lumjjb
Copy link
Collaborator Author

lumjjb commented May 26, 2021

It would be awesome if new members themselves to be involved with this so we can get feedback on what your questions are first when you joined the TAG!

@lumjjb lumjjb added the good first issue Good for newcomers label May 26, 2021
@TheFoxAtWork TheFoxAtWork removed the triage-required Requires triage label May 26, 2021
@TheFoxAtWork TheFoxAtWork added this to To do in General Business May 26, 2021
@TheFoxAtWork
Copy link
Collaborator

i've also gotten questions about how to lead their first effort. I've been sending them to the process page and linking the to paper process which has some details

@ultrasaurus
Copy link
Member

regarding question of leading first effort, I would suggest that we direct them to our (hopefully well-groomed) backlog and to look for projects that already have a TL/chair sponsor but lack a project lead, and then chime in on issue that they are interested and willing to participate as project lead.

@stale
Copy link

stale bot commented Jul 31, 2021

This issue has been automatically marked as inactive because it has not had recent activity.

@stale stale bot added the inactive No activity on issue/PR label Jul 31, 2021
@sayantani11
Copy link
Contributor

@lumjjb What can we do to contribute to this issue?

@stale stale bot removed the inactive No activity on issue/PR label Aug 22, 2021
@lumjjb
Copy link
Collaborator Author

lumjjb commented Aug 23, 2021

Hi @sayantani11 ! A perfect way for you to contribute to this is to provide some input about what you're experience is of a new member! And some suggestions, some problems you faced, what you think is lacking/we can do better. That would be super valuable!

And maybe from that feedback we can determine if we can create a PR on the current process or even create a project from it!

@sayantani11
Copy link
Contributor

Took me some time to sum up but here are few things I can say as a new member.
Most new contributors try to look for good first issues, and that's because it helps them gain confidence and understand the project, so if we could preserve good first issues for new people joining the community. Next is, people who are new to open source as I can say from my experience have kind of fear and self doubt before contributing to major projects, so while assigning if we could add something like "Feel free to reach out to us with any issues, its okay to ask and we are here for helping".
For good first issues, it would help if the issue explains what are the things they need to implement for resolving, or may be adding reference to previous similar PRs.
Lastly I guess we should try enhancing the docs at intervals, taking feedbacks from new contributors, what they didn't find in the docs that required to do. And a +1 if we allow them to make the change.

I guess I was able to give a point of view
@lumjjb

@sayantani11
Copy link
Contributor

May be we could have someone who could find good-first-issues and guide new contributors if they are facing any issues.

@TheFoxAtWork
Copy link
Collaborator

This is FANTASTIC! a couple things i can see as specific improvements based on this feedback — @sayantani11 @lumjjb @achetal01 do you think the below should become a separate issue so we can track it independent of this?

  • Create a new file in CONTRIBUTING/ called "first-time-contributions"
  • New file should include:
    • Where to find good-first-issues
    • who to contact (co-chairs & tech leads - link to who they are in the repo) and how to contact (slack DMs or channel #tag-security-governance or via email cncf-tag-security-leads@lists.cncf.io ) if there are any questions, comments, requests for help in contributing
    • Link to instructions on contributing to an open source project: https://opensource.guide/how-to-contribute/#how-to-submit-a-contribution & https://docs.github.com/en/github/collaborating-with-pull-requests
    • If the issue under good-first-issue isn't clear comment on it! ask the submitter for more details or contact the co-chairs and tech leads, they are here to help!
    • let them know that contributing to open source can be scary, overwhelming, or can make them feel some doubt, its to be expected. We are happy to have a one-on-one discussion, mentor them, and ensure their contribution is successful so they can keep it up.
  • Update the NEW-MEMBERS doc to link to a new file in CONTRIBUTING/ called "first-time-contributions"

@sayantani11
Copy link
Contributor

@TheFoxAtWork Yeah we should definitely do that.

@stale
Copy link

stale bot commented Oct 27, 2021

This issue has been automatically marked as inactive because it has not had recent activity.

@stale stale bot added the inactive No activity on issue/PR label Oct 27, 2021
@lumjjb
Copy link
Collaborator Author

lumjjb commented Dec 1, 2021

Hi @sayantani11 ! Would you like to help out with this issue?

@stale stale bot removed the inactive No activity on issue/PR label Dec 1, 2021
@sayantani11
Copy link
Contributor

@lumjjb Guess I already made a PR for it!!!

@sayantani11
Copy link
Contributor

#798
cc @lumjjb

@stale
Copy link

stale bot commented Feb 3, 2022

This issue has been automatically marked as inactive because it has not had recent activity.

@anvega
Copy link
Collaborator

anvega commented Jun 21, 2023

We've moved away from the static members file and how we onboard/engage with the community, understanding that the nature of the participation is fluid and members recognize each other for their active participation

@anvega anvega closed this as completed Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers governance inactive No activity on issue/PR suggestion New suggestion for the CNCF sig-security group that don't fall into an existing category
Projects
General Business
In progress
Development

No branches or pull requests

5 participants