--- title: Mentoring Repo - Refactor 2022 tags: TAG-CS Mentoring WG --- # Mentoring Repo ## Organisation Plan ### Notes * Change links e.g. no 'here' * Not convinced TAG content should be in MenWG, move to TAG repo * Program Guidelines etc. should be prioritised above Maintainer information for example * 2 groups of people in mind: **Audience #1** - * People looking to apply, often those new to Open Source, applying for jobs, sometimes coding in general * Need to make it easy for these people to navigate the space, apply for jobs etc. e.g., Getting Started, How can I start contributing Perceived hole in documentation. *We're not making it easy enough for people to get involved.* **Audience #2** Project Maintainers and Potential Mentors Good example: Projects open 2023 March - May Nothing that outlines what a good proposal is Benefits to your project etc. **Front page:** * Consider the UX closely, what is most relevant to first-time visitors for instance? *Not an Archive* * CNCF is *not* the primary audience! * Potentially 1000's of people interacting with page(s). * Part of the site does have to remain an internal workspace for the mentorship team, however the **readme** pages **Layout:** * Reference or create visual architecture e.g. MindMap, sitemap etc. * 'Docs for Developers' book for reference - Chapter 10 - 'Organising documentation' * Figure out: 1. *What do we have?* 1. *Who our audience is and their needs?* 1. *Consider how we change the architecture to align with this.* *Expected audiences:* Mentees, Mentors and (ourselves) Members of WG - as well as a reporting tool. We should cater to our constituents to reflect this. 'Get through page in three swipes' * Once sorted; what are the most likely personas that will visit/interact with our site? What will we do to personalise the experience for each respective demographic? https://github.com/cncf/tag-contributor-strategy/tree/main/website/ https://github.com/cncf/tag-contributor-strategy/ *** ### Actions * Remove soc@cncf.io email link (spam) * 'How do I start' etc. should be in discussion board * Add 'Google' to Summer of Code etc. * Add sections for Outreachy, GSoDocs etc. * Reorganise home page and each project page to better reflect needs for both mentees/tors according to project * Will help towards creating Mentoring.io (Contributor site) * Ensure Repo is cleaned, even it won't be adopted into the site * FAQs can follow once key information has been identified * Global or Project FAQ? (Pros and cons to both) ***Consistent flow/template for each section to improve ease of navigation** Prepare proposal, bring TAG-CS in once ready to present to include/add to Contributor.io *** README.md * Short overview * What * Why * When * Where * Include reference to the 4 main sanctions with hyperlinks * Communication *** **(Mentoring Initiatives)** The Cloud Native Computing Foundation (CNCF) participates in a variety of mentoring programs. CNCF is a great place to spend a summer learning, coding, participating, and contributing. We are an exciting open source foundation with a vibrant community of projects, and we look forward to your application and your project ideas! ## **MENTEES** **Overview** Becoming a mentee can be the ideal way to develop your professional skillset, connect with industry experts and build a strong foundation for your career in Open Source. Whether you're looking at becoming a Mentee for the first time or refining your experience at a higher level, CNCF support a wide range of programs, projects and community members to help cultivate your Contributor journey. **New Mentees or Contributors: Getting Started!** *(what's relevant for this section or better suited for FAQs?)* * What's a Mentee? * What support is available * What is a Mentorship? * Why become a Mentee? * When? (Semester intake dates etc.) * Where - to register, connect with the community, learn more about opportunities. **Experienced or returning Mentees: Helping to grow our Community!** * What are my options? * Register with another program * Become a Mentor * What other opportunities are available to me? * Why re-engage with programs? * When (Semester intake dates etc.) * Where - to find out more about Mentoring, to connect with others who have walked the path etc. *** ## Repo Meeting ### November 3/4, 2022 **Attendees:** * Nate, Riaan, Jay * PR comments to reflect changes * [ ] Upload diagrams - before and after * Edit description intermittently * [Mentoring Repo - Draft Layout](https://docs.google.com/presentation/d/1eoWLjG7OWkL1_9aFJys8UfrxcJkIDvXI/edit#slide=id.g176351963fc_0_0) * https://github.com/cncf/mentoring/issues/735 Next steps: - [ ] Start on Mentor section - [ ] What is the mentor's next step if they want to propose a project - [ ] Instructions and a working space - [ ] Idea file - [ ] Accepted projects list - This will go to the Website - https://github.com/cncf/mentoring/issues/736 - [ ] Mentee track - [ ] Mentee folder with - [ ] timelines - [ ] dates - [ ] link to LFX site to apply - [ ] prospective pathways - [ ] https://github.com/cncf/mentoring/issues/737 **NOTE** - Be careful not to duplicate information; cooridnate well across locations e.g. repo - Mentees priority persona due to inexperience w/ OS - Mentors have a direct line to us so not as much immediate support required (initially) User personas: ie. - 2nd language Eng - University student - Career change adult - Young coder *** **NOTE:** - Role-based folders should be informational - Program folder would be the working folder where PR's would merge for proposals and Accepted programs **Archive** - [x] Archive info can go in a folder within Programs folder - [x] Cross info can be moved to Archive folder, all others duplicated into archive - [x] Top level programs only show most recent information **LFX** - [x] Move data to Archive - [ ] Active and next Semester kept in main folder (Programs file); everything else shifted to the Archive - [ ] Excessive archive info can be cut from the ReadMe (index) and moved to the appropriate file. - programs - lfx-mentorship - README.md - archive - 2016 - ... - 2022 - term 1 - term 2 - 2022 - term 3 - 2023 - term 1 - https://github.com/cncf/mentoring/issues/738 **Mentor WG admin folder:** - [ ] Each program - set out a list of tasks that need to occur for each program - [ ] In the Mentor WG for make a TODO list and set up Project board like the [CNCF LFX Mentoring '22 Term 3: Sept-Nov example](https://github.com/orgs/cncf/projects/12/views/1) (public access) - Can be used to teach/onboard new admins; this is the process to run a term of an LFX Mentorship - Should be formalised into a document - [ ] Current CNCF Event calendar is packed; create instead a **public Mentoring calendar** to inform of things such as due dates (projects, applications etc.) - Need to decide who needs/has access - https://github.com/cncf/mentoring/issues/741 * [ ] Docs such as 'licence', 'Contributing', 'CoC' etc should be in the root directory of the Repo * If the CoC differs for a specific program, we can adapt/file it as such * for example: https://github.com/cncf/project-template - https://github.com/cncf/mentoring/issues/740 **PR** - [x] Branch V2 can also be created in CNCF Mentoring; what will be the best way to capture comments, interaction etc. - [x] Create a Project Board for the work, use 'Issues' going forward to help coordinate efforts - [x] Make an issue from each action item* - [X] Once V2 branch is running, everyone else in the WG can move on specific actions - [x] AI: Riaan - add name to GH file as maintainer