2023-01-24 meeting minutes (#773)

Co-authored-by: HackMD <37423+hackmd-hub[bot]@users.noreply.github.com>

Signed-off-by: Nate W <[email protected]>

TAGCS-Mentoring-WG/2023-meeting-minutes.md

@@ -34,7 +34,73 @@ https://zoom.us/my/cncftagcontributorstrategy?pwd=TnI0WU9Eb2I1RlRWdkl1R0k1WkZXUT
 Passcode: 77777
 
 
-# Upcoming Meetings
+# Upcoming Meeting
+
+
+## February 14, 2023
+
+21:00 UTC (1:00 PM PDT on 2023-02-14; 10:00 AM NZST on 2023-02-15)
+
+
+# Past Meetings
+
+
+## January 24, 2023
+
+21:00 UTC (1:00 PM PDT on 2023-01-24; 10:00 AM NZST on 2023-01-25)
+
+### Attendance
+
+* Nate W.
+* Ali Ok
+* Josh 
+* Alexandre
+* Riaan
+* Jay
+
+### Agenda
+
+* LFX Mentorship Project Proposals
+  * https://github.com/cncf/mentoring/tree/main/lfx-mentorship/2023/01-Mar-May
+* 2023 Goals
+  * https://hackmd.io/@tag-cs-mentoring-wg/2023-goals
+* Repo revisions
+  * project board: https://github.com/orgs/cncf/projects/16/views/1
+* GSoC Org applications
+  * Nate W. to work with Chris A. to apply as an org
+  * https://groups.google.com/d/msgid/google-summer-of-code-discuss/649212c4-fe0d-4cb6-8e48-17f961e3d0ben%40googlegroups.com?utm_medium=email&utm_source=footer
+
+- Ali:
+Could we have the [Ideas page](https://github.com/cncf/mentoring/blob/main/summerofcode/2022.md) open earlier? Motivation for the ask is that the potential mentees want to start exploring the project ideas earlier. Similarly, maintainers want to list their ideas earlier for encouraging a head start.
+
+- Options are making the Ideas page availible through out the year
+- Incorporate CLOtributor with the process with `Help wanted` & `Mentor Available` labels
+    - AI: Riaan & Jay add CLOTributor to the Mentoring repo
+- **Could use Git discussions for this as well.** 
+    - GSOC 2022 - Nate opened a thread to support this, however only 15% of this thread was used; also creating alot of overhead to maintain. Because this will all link back to upstream issues; preferred this would occur off the boards. 
+    - Might also be hard to filter convos back into the issues themselves as well. An ideas page however would give a centralised reference point for those seeking information. 
+    - We should keep encouraging mentees to reach out to potential mentors; aiming to give mentors more time to make their selections as well.
+    - Having alot of mentees/applicants can be difficult to filter/process effectively otherwise.
+    - Another option might be for mentees to 'source' their own mentors to support/drive projects as well > Application Process
+        - If a potential mentee is interested in a CNCF project and wants to do a mentorship, this should put the impetus on the mentee themselves; this mechanism currently exists but is not explicitly communicated.
+        - This might be an issue especially for paid mentorships such as LFX. This could be exploited from a faculty of an education provider for instance that could implement their own mentee without following the preferred process.  
+**How to incorporate Clotributor into the existing onboarding process?** Future working session(s) to determine best course of action.
+
+**Repo update**
+- Thank you for review Ali & Nate
+- Next step might be to merge in v2 branch
+    - Then clean up and distill information in Mentee and Mentor files to a single readme for people to the contribute
+    - Try and make the info clear one stop place to find info
+    - Might have to hold back on merging in the v2 branch because links have been publish to current repo info.
+    - When would be a good time to remove the WIP label from the PR.
+        - Likely after updating Mentee and Mentor sections is in a workable state + FAQs
+* Should be rebasing but leave number of commits
+* Folder restructure, mentee/mentor page and FAQ
+* GitHub doesnt have a redirection tool; maintainters have been notified, potential applicants will seek this information - work can be continued once ideas have been confirmed/agreed upon, possibly next week.
+Q. Keep v1 page blank with link to v2 page
+Edit page we would link to, highlight page move. Can hold off on this until the last minute; let's keep it clean in the meantime. 
+
+Links important to share with others - Mentoring tree main, LFX Mentorship 2022... [link](https://github.com/cncf/mentoring/tree/main/lfx-mentorship/2023/01-Mar-May)
 
 
 ## January 10, 2023
@@ -77,12 +143,18 @@ Passcode: 77777
   * work with LF mentoring admins to reach out to universities to work with co-op programs
   * increase number of programs we participate in
       * ex. Outreachy
-      * recruit community members to help manage/run the program
+      * recruit community members to help manage/run the programs
   * others?
-  * Organize projects (and SIGs and TAGs) to supply an ongoing list of mentorship opportunities based on the job
-*  https://clotributor.dev/
+    * [name=Nate W.][time=Thu, Jan 12, 2023 10:05 AM] Look into creating a 2-term program for longer/larger projects (How would this work with the req that mentees can only participate in one mentorship)
+    * [name=Nate W.][time=Thu, Jan 12, 2023 1:13 PM] Reduce percentage of failed/withdrawn mentees
+
+* Organize projects (and SIGs and TAGs) to supply an ongoing list of mentorship opportunities based on the Clotributor.
+    * https://clotributor.dev/
+    * That way we can reach out based on existing tasks
+    * Plus skim a list of potential mentors
+* Participate in MC, doing session on "participating in mentorship programs"
+    * Nate + 1-2 project maintainers who did mentorships
 
-# Past Meetings
 
 
 ---