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

Repo refactor PR #899

Merged
merged 48 commits into from
Apr 11, 2023
Merged
Show file tree
Hide file tree
Changes from 22 commits
Commits
Show all changes
48 commits
Select commit Hold shift + click to select a range
60fc2bf
[WIP] Refactoring the Mentoring Repo for better user interaction (#732)
jaytiaki Nov 3, 2022
ccbcbc0
Moved archive info form readme to the archive file (#744)
riaankleinhans Nov 24, 2022
6450cba
Add Riaan Kleinhans as maintainer (#734)
riaankleinhans Nov 3, 2022
1f71291
2022-11-08-mentoring-wg-meeting (#742)
nate-double-u Nov 8, 2022
77aab1d
September comes before November (#747)
nate-double-u Nov 21, 2022
2c9b52b
updating 2022 stats. adding LFX Mentoring 2022 term 3: Sept-Nov (#750)
nate-double-u Jan 13, 2023
bbed216
2022-12-13 (#751)
nate-double-u Dec 13, 2022
5c92907
Archiving the 2022 mentorship wg meeting minutes (#756)
nate-double-u Jan 12, 2023
119943e
create 2023 meeting minutes file (#757)
nate-double-u Jan 13, 2023
e2eddb3
updating LFX Mentorship templates (#759)
nate-double-u Jan 12, 2023
b4f5efd
Moving LFX Mentoring 2022 data into the archive
nate-double-u Jan 13, 2023
8d4c6aa
Merge pull request #761 from nate-double-u/v2
nate-double-u Jan 16, 2023
ee2520b
Create relative links and expand readme content (#769)
riaankleinhans Jan 24, 2023
59d9c89
Merged main v2 2023-03-14 (#881)
nate-double-u Mar 16, 2023
a09d306
Revert "Merged main v2 2023-03-14 (#881)"
nate-double-u Mar 16, 2023
b52fd20
Merge pull request #884 from cncf/revert-881-merged-main-v2-2023-03-14
nate-double-u Mar 16, 2023
a773186
GSoC admin guide (#871)
aliok Mar 16, 2023
158ff45
Merge remote-tracking branch 'upstream/main' into v2
nate-double-u Mar 17, 2023
356869f
moving lfx mentorship terms into their new positions.
nate-double-u Mar 17, 2023
0db39c8
Merge pull request #886 from nate-double-u/merged-main-v2-2023-03-17
nate-double-u Mar 17, 2023
42ee8c4
moving old season of docs. adding new summer of code 2023.md (#887)
nate-double-u Mar 21, 2023
dbcb668
Update mentor mentee sections (#891)
nate-double-u Mar 21, 2023
a59d027
Update GSoC admins list
aliok Mar 8, 2023
b3bc337
Address comments
aliok Mar 21, 2023
b70b375
Add recommended skills for buildpacks Dockerfiles project (#889)
natalieparellano Mar 21, 2023
81af1cd
Add another Jaeger project (#893)
yurishkuro Mar 23, 2023
1021008
Revert "Add another Jaeger project (#893)"
aliok Mar 28, 2023
c2695bc
Revert "Add recommended skills for buildpacks Dockerfiles project (#8…
aliok Mar 28, 2023
5584cde
Revert "Address comments"
aliok Mar 28, 2023
23e4807
Revert "Update GSoC admins list"
aliok Mar 28, 2023
0571e60
Merge pull request #903 from cncf/revert-900-merged-main-v2-2023-03-28
aliok Mar 28, 2023
057a240
Merge remote-tracking branch 'upstream/main' into v2
nate-double-u Mar 28, 2023
945c96e
Merge pull request #905 from nate-double-u/merged-main-v2-2023-03-28-…
aliok Mar 28, 2023
b451002
Merge remote-tracking branch 'upstream/main' into v2
nate-double-u Mar 30, 2023
340887c
updating v2 based on PR feedback (#909)
nate-double-u Apr 1, 2023
ba97ae2
Merge pull request #908 from nate-double-u/merged-main-v2-2023-03-30
aliok Apr 3, 2023
c58ad9b
relocating some of Lee's changes from #914. Making some updates that …
nate-double-u Apr 4, 2023
54b1355
Merge pull request #915 from nate-double-u/merged-main-v2-2023-04-04
nate-double-u Apr 4, 2023
6a37596
Merge remote-tracking branch 'upstream/main' into v2
nate-double-u Apr 5, 2023
741737c
Merge pull request #919 from nate-double-u/merged-main-v2-2023-04-05
nate-double-u Apr 5, 2023
c6ba792
Update GSoC admin guide with example announcements (#920)
aliok Apr 7, 2023
f7d6a93
Merge remote-tracking branch 'upstream/main' into v2
nate-double-u Apr 7, 2023
e461973
Merge pull request #922 from nate-double-u/merged-main-v2-2023-04-07
nate-double-u Apr 7, 2023
8d1d8b0
Merge remote-tracking branch 'upstream/main' into v2
nate-double-u Apr 10, 2023
7078aca
Merge pull request #924 from nate-double-u/merged-main-v2-2023-04-10
nate-double-u Apr 10, 2023
b3c568e
Delete contributor-growth.md (#925)
riaankleinhans Apr 11, 2023
970f43d
Calling out draft pages. Updating formatting
nate-double-u Apr 11, 2023
c45fa62
Merge pull request #927 from nate-double-u/calling-out-wip-pages
riaankleinhans Apr 11, 2023
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
444 changes: 19 additions & 425 deletions README.md

Large diffs are not rendered by default.

20 changes: 0 additions & 20 deletions lfx-mentorship/2023/03-Sep-Nov/project_ideas.md

This file was deleted.

264 changes: 264 additions & 0 deletions mentees/README.md

Large diffs are not rendered by default.

File renamed without changes.
6 changes: 6 additions & 0 deletions mentoring-wg/code-of-conduct.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
CNCF TAG Contributor Strategy
# Mentoring Working Group

## Code of Conduct

CNCF Mentoring programs follow the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
19 changes: 19 additions & 0 deletions mentoring-wg/communications.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
CNCF TAG Contributor Strategy
# Mentoring Working Group


## About TAGCS Mentorship Working Group

[Mentoring WG Charter](https://github.com/cncf/tag-contributor-strategy/tree/main/mentoring)

* CNCF Slack: [#tag-contributor-strategy](https://cloud-native.slack.com/archives/CT6CWS1JN)
* [Discussion boards](https://github.com/cncf/mentoring/discussions)
* [Email list](https://lists.cncf.io/g/tag-cs-mentoring-wg/)

## Communications

Please reach out to us using the [Discussions boards](https://github.com/cncf/mentoring/discussions).

We are also available on the [CNCF slack](https://slack.cncf.io/). Please don't use DMs unless strictly necessary as doing so both has the potential of overwhelming project maintainers and others with similar questions lose the benefit of public discussion.

It's best if you use a public communication channel whenever possible; however, if you need to communicate in private, please feel free to send the admins a note via mentoring@cncf.io (please use the public channels for any project-related discussion).
12 changes: 12 additions & 0 deletions mentoring-wg/contributor-growth.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
CNCF TAG Contributor Strategy
# Mentoring Working Group


## About TAGCS Mentorship Working Group
nate-double-u marked this conversation as resolved.
Show resolved Hide resolved

[Mentoring WG Charter](https://github.com/cncf/tag-contributor-strategy/tree/main/mentoring)

* CNCF Slack: [#tag-contributor-strategy](https://cloud-native.slack.com/archives/CT6CWS1JN)
* [Discussion boards](https://github.com/cncf/mentoring/discussions)
* [Email list](https://lists.cncf.io/g/tag-cs-mentoring-wg/)

33 changes: 33 additions & 0 deletions mentoring-wg/faqs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
CNCF TAG Contributor Strategy
# Mentoring Working Group


## About TAGCS Mentorship Working Group

[Mentoring WG Charter](https://github.com/cncf/tag-contributor-strategy/tree/main/mentoring)

* CNCF Slack: [#tag-contributor-strategy](https://cloud-native.slack.com/archives/CT6CWS1JN)
* [Discussion boards](https://github.com/cncf/mentoring/discussions)
* [Email list](https://lists.cncf.io/g/tag-cs-mentoring-wg/)


## Meeting details

### Recurring monthly
* 2nd Tuesday of the month at 8PM UTC
* 4th Tuesday of the month at 8PM UTC (during the setup phase)

[CNCF Public Events - TAG CS Mentoring WG](https://tockify.com/cncf.public.events/monthly?search=CNCF%20TAG%20Contributor%20Strategy%20Mentoring%20WG)

### Zoom

Zoom Meeting
https://zoom.us/my/cncftagcontributorstrategy?pwd=TnI0WU9Eb2I1RlRWdkl1R0k1WkZXUT09

Passcode: 77777

# Meeting Minutes

* [2022](./2022-meeting-minutes.md) (current)

Choose a reason for hiding this comment

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

Now that we have a 2023 page for minutes, we should link to it here

Copy link
Member Author

Choose a reason for hiding this comment

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

+1

Copy link
Member Author

Choose a reason for hiding this comment

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

We removed mentoring-wg faqs — i need to double check that we have the 2023 meeting minutes in the main mentoring-wg readme

* [June 30, July 12, July 26, 2022](https://docs.google.com/document/d/1ZVFf_GRB5yrcTQieudtk3W-gWL6KuwHn1QG8XKdrARo/edit?usp=sharing)

166 changes: 166 additions & 0 deletions mentoring-wg/gsoc-org-admin-guide.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,166 @@
# CNCF GSoC admin guide

## Introduction

> **Note**
> This is a guide for Google Summer of Code admins at CNCF.

While Google [defines](https://developers.google.com/open-source/gsoc/help/responsibilities#org_admin_responsibilities) responsibilities for organization admins and gives some [tips](https://developers.google.com/open-source/gsoc/help/oa-tips), there are variations in how organizations run the program suitable for their communities.

> **Note**
> The "contributor" term throughout this document is used as "mentee." Please do not mix the word "contributor" with regular contributors and maintainers of the CNCF projects. Here, the term "contributor" follows Google's terminology for the GSoC program.

## Outline of responsibilities

First of all, GSoC admins are required to read these documents from Google:

* [GSoC admin responsibilities](https://developers.google.com/open-source/gsoc/help/responsibilities#org_admin_responsibilities)
* [GSoC admin tips](https://developers.google.com/open-source/gsoc/help/oa-tips)

In summary, responsibilities can be outlined as follows:

* Recruitment: GSoC admins are responsible for recruiting mentors from among the maintainers of the CNCF projects. They also recruit new contributors to participate in the program as mentees. They reach out to communities, promote the program, and answer questions from interested parties.
* Mentor management: GSoC admins ensure mentors are qualified and have the experience to mentor contributors effectively. They provide guidance and feedback to help mentors improve their mentoring skills.
* Contributor management: GSoC admins set up the foundation for communication between the mentors and the contributors. They provide guidance for contributors and mentors to connect, monitor the progress of projects, and provide non-technical support as needed.
* Program coordination: GSoC admins coordinate the program logistics. This may include applying to the program, ranking proposals, setting deadlines, communicating with involved parties, and ensuring that all contributors and mentors have the resources they need to be successful.
* Program evaluation: Admins evaluate the program's success and identify areas for improvement. They do this by analyzing program data, collecting feedback from contributors and mentors, and making recommendations for future program iterations.

The following are not responsibilities of a GSoC admin:
* Verifying the eligibility of contributors in terms of age, country of residence, and similar criteria. Google does this.
* Providing technical support to mentors or contributors about the project.
* Technically mentoring the contributors (e.g., technical troubleshooting), other than giving general guidance and/or replying to questions by pointing at possible places to find an answer.
* Providing non-technical mentoring to the contributors (e.g., career advice, personal advice, etc.).

## Checklist

### GSoC program announcement

At this stage, Google announces it will have GSoC in the upcoming year. There is no guarantee from Google that CNCF will be accepted to GSoC.

Tasks:
* Create GSoC ideas page in [`cncf/mentoring`](https://github.com/cncf/mentoring/tree/main/summerofcode) repository. An ideas page will be necessary during the organization application.
* [Announce](#Announcements) the intention to participate in the program. Mention these:
* Deadline to add ideas is the contributor application period start date.
* CNCF has not yet been accepted into the program.
* We are collecting ideas.
* We encourage communities to add ideas earlier rather than later to give potential contributors more time.
* Start monitoring PRs to ideas page, review ideas added by mentors using the [proposal review guideline](#Project-idea-proposal-review-guidelines).

### Pre- organization application period

At this stage, there is still no guarantee from Google that CNCF will be accepted to GSoC. CNCF is collecting ideas for potential contributors and preparing for the organization's application to GSoC.

Tasks:

* Send a reminder to CNCF project communities to add ideas as stated in the previous stage.


### Organization application

At this stage, an ideas page should be listed with a few ideas.

Tasks:
* Apply to the program.

### Acceptance announcement

* [Announce](#Announcements) the acceptance in the program. Mention these:
* CNCF is accepted to the program.
* It is still possible to add ideas until the contributor application period start date.
* We encourage communities to add ideas earlier rather than later to give potential contributors more time.
* We encourage contributors to explore project ideas and engage with mentors and communities.
* Create a mailing list specific to the current GSoC session, which will be used to communicate with mentors.
* Although there can be ideas/mentors added until contributor applications, it is encouraged to get mentors ([example Github task](https://github.com/cncf/mentoring/issues/864)):
* Added to GSoC platform
* Added to GSoC program for the current year in GSoC platform

### Contributor applications

* [Announce](#Announcements) that the contributor applications have started. Mention these:
* We encourage contributors to submit proposals early to be able to get feedback from mentors and fix any issues.
* We are no longer collecting ideas from mentors.
* Inform member mentors (mentors who added an idea) about these:
* They need to review proposals from contributors before they submit the final proposal.
* As we are not collecting ideas anymore, finalize getting mentors:
* Added to GSoC platform
* Added to GSoC program for current year in GSoc platform


### Rankings

* Ask mentors to
* Review proposals and select contributors they want to mentor
* Provide feedback in the GSoC system around the matters listed in the [contributor+proposal selection and ranking criteria](#Contributorproposal-selection-and-ranking-criteria), such as community interaction, proposal quality, etc.
* Refrain from commenting on any contributor's chances of being accepted.
* Run the ranking process

### Accepted projects announcement

* [Announce](#Announcements) that accepted contributors and projects have been chosen.
* Add selected mentors to the mailing list created earlier
* Inform mentors and contributors about:
* Community bonding
* Getting up to speed to begin working on projects

### Coding period

* Inform mentors and contributors about the following:
* Coding starting date
* Midterm evaluation date
* TODO: anything to inform around monitoring their progress? While GSoC admins cannot technically review the progress, we can ask biweekly/monthly reports from mentors

### Midterm evaluations
* Inform mentors and contributors about:
* Midterm evaluations and deadlines
* [Google's evaluation guide](https://google.github.io/gsocguides/mentor/evaluations)


### Final evaluations
* Inform mentors and contributors about:
* Final evaluations and deadlines
* [Google's evaluation guide](https://google.github.io/gsocguides/mentor/evaluations)


### Results
* Run a retrospective using processes such as:
* Feedback survey for contributors and mentors
* Analyze data
* Retrospective session for GSoC admins
* Fill Google's feedback survey.
* [Announce](#Announcements) the results.

### Additional tasks

* Mentor stipend: TODO
* Maintain this guide

## Project idea proposal review guidelines

* Make sure the mentor is in the [project-maintainers.csv](https://github.com/cncf/foundation/blob/main/project-maintainers.csv) file for the related project. If not, ask the PR author to ask for a `lgtm` from the people on that list.
* Check if the formatting is right.
* Make sure the upstream ticket actually exists and is open and unassigned.
* Check if the project size in hours is one of the values provided by Google.
* Check if the mentors have names, Github usernames and emails listed.
* Make sure that the description provides a good sense of context and motivation for the idea to attract contributors.
* Ensure the expected outcome benefits contributors (e.g. learning, growth) and the project (e.g. new features/functionality, bug fixes).
* Check if the idea is a coding project. Projects such as documentation-only tasks are not accepted to GSoC per [program rules](https://summerofcode.withgoogle.com/rules).

## Contributor+proposal selection and ranking criteria

TBA

## Contributor guidance

TBA

## Announcements

* Target channels for the public announcements:
* Create a Github discussion on [`cncf/mentoring`](https://github.com/cncf/mentoring), which serves as the main announcement page
* Do the social media promotions of the announcement page.


## References

* [GSoC timeline](https://developers.google.com/open-source/gsoc/timeline)
* [GSoC org admin tips](https://developers.google.com/open-source/gsoc/help/oa-tips)
20 changes: 20 additions & 0 deletions mentoring-wg/org-admins.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
CNCF TAG Contributor Strategy
# Mentoring Working Group

## About TAGCS Mentorship Working Group

[Mentoring WG Charter](https://github.com/cncf/tag-contributor-strategy/tree/main/mentoring)

* CNCF Slack: [#tag-contributor-strategy](https://cloud-native.slack.com/archives/CT6CWS1JN)
* [Discussion boards](https://github.com/cncf/mentoring/discussions)
* [Email list](https://lists.cncf.io/g/tag-cs-mentoring-wg/)

## Organization Admins

If you need help with anything mentoring at CNCF, you can file an issue at this repo or reach out to us using the [Discussions boards](https://github.com/cncf/mentoring/discussions).

Organization admins for specific mentorship programs are listed on the program's respective pages.

## Organization admin guides

* [Google Summer of Code organization admin guide](gsoc-org-admin-guide.md)
33 changes: 33 additions & 0 deletions mentoring-wg/strategy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
CNCF TAG Contributor Strategy
nate-double-u marked this conversation as resolved.
Show resolved Hide resolved
# Mentoring Working Group


## About TAGCS Mentorship Working Group

[Mentoring WG Charter](https://github.com/cncf/tag-contributor-strategy/tree/main/mentoring)

* CNCF Slack: [#tag-contributor-strategy](https://cloud-native.slack.com/archives/CT6CWS1JN)
* [Discussion boards](https://github.com/cncf/mentoring/discussions)
* [Email list](https://lists.cncf.io/g/tag-cs-mentoring-wg/)


## Meeting details

### Recurring monthly
* 2nd Tuesday of the month at 8PM UTC
* 4th Tuesday of the month at 8PM UTC (during the setup phase)

[CNCF Public Events - TAG CS Mentoring WG](https://tockify.com/cncf.public.events/monthly?search=CNCF%20TAG%20Contributor%20Strategy%20Mentoring%20WG)

### Zoom

Zoom Meeting
https://zoom.us/my/cncftagcontributorstrategy?pwd=TnI0WU9Eb2I1RlRWdkl1R0k1WkZXUT09

Passcode: 77777

# Meeting Minutes

* [2022](./2022-meeting-minutes.md) (current)
* [June 30, July 12, July 26, 2022](https://docs.google.com/document/d/1ZVFf_GRB5yrcTQieudtk3W-gWL6KuwHn1QG8XKdrARo/edit?usp=sharing)

76 changes: 76 additions & 0 deletions mentors/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
## **Become a Mentor -- Draft**



## **Mentor Expectations**



## **Support Networks**



## **Programs**



## **Project Idea (Template)**



## **Success Stories**



## **FAQs**




---

Mentees - Frequently Asked Questions (FAQs)
FAQs: New Mentees and Contributors
General Questions



If you have some basic experience, check out the CNCF Contributor page. It has a list of projects that may suit your skillset.



The Linux Foundation also offers a free short course for Beginners which can help you get familiar with the fundamentals of Open Source and started on your contributor journey.



## FAQs: Returning Mentees - Full List

1. I've graduated a mentorship program. What's next?
1. How do I become a Mentor for a project?
1. I'm having trouble finding a job now I've graduated. What steps should I take?
1. I didn't finish a program in the past. Can I still take part in mentorship opportunities?
1. Can I apply for the LFX Mentorship again after successfully completing a Semester?
1. I've submitted my application or requested information and haven't heard back by the expected timeframe. How can I follow up?




---



Participating in the community: Join mailing lists, attend virtual events, and engage in discussions to get involved with the community.

Contributing code: Find a project that you're interested in and submit a pull request to start contributing code.

Reporting bugs: If you find a bug, report it on the project's issue tracker.

Writing documentation: Many CNCF projects are in need of clear, up-to-date documentation. You can help by writing or improving documentation.

Providing feedback: Participate in design reviews, provide feedback on feature proposals, and engage with the project community.

Organizing events: You can help the project by organizing or participating in meetups, workshops, or other events.

Mentoring: Share your knowledge and experience by mentoring new contributors to the project.

Testing: Help test new features, validate bug fixes, and provide feedback to improve the quality of the project.
Loading