8021 (#4)

* Set up directory structure and start planning Group Cohorts

* Set up directory structure and start planning Group Cohorts

* Set up directory structure and start planning Group Cohorts

* copied group-mentoring.md to program folder

* Create hugo.yaml

* Update hugo.yaml, add workflow

.github/workflows/hugo.yaml

@@ -0,0 +1,78 @@
+# Sample workflow for building and deploying a Hugo site to GitHub Pages
+name: Deploy Hugo site to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches:
+      - 8021
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+# Default to bash
+defaults:
+  run:
+    shell: bash
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    env:
+      HUGO_VERSION: 0.128.0
+    steps:
+      - name: Install Hugo CLI
+        run: |
+          wget -O ${{ runner.temp }}/hugo.deb https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_linux-amd64.deb \
+          && sudo dpkg -i ${{ runner.temp }}/hugo.deb          
+      - name: Install Dart Sass
+        run: sudo snap install dart-sass
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          submodules: recursive
+          fetch-depth: 0
+      - name: Setup Pages
+        id: pages
+        uses: actions/configure-pages@v5
+      - name: Install Node.js dependencies
+        run: "[[ -f package-lock.json || -f npm-shrinkwrap.json ]] && npm ci || true"
+      - name: Build with Hugo
+        env:
+          HUGO_CACHEDIR: ${{ runner.temp }}/hugo_cache
+          HUGO_ENVIRONMENT: production
+          TZ: America/Los_Angeles
+        run: |
+          hugo \
+            --gc \
+            --minify \
+            --baseURL "${{ steps.pages.outputs.base_url }}/"          
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./public
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

mentoring/README.md

@@ -24,9 +24,9 @@ it's necessary to keep a continuous pipeline of quality contributors and we want
 
 ## Programs
 
-| Program                                                                                         | Status                   | Target Date                                                                   |
-|-------------------------------------------------------------------------------------------------|--------------------------|-------------------------------------------------------------------------------|
-| [Group Mentoring Cohorts](/mentoring/programs/2024/groupmentorship/group-mentor-planning.md) | **Planning in progress** | [Sept-Nov](/mentoring/programs/2024/groupmentorship/group-mentor-planning.md) |
+| Program                                                                | Status                   | Target Date                                                                   |
+|------------------------------------------------------------------------|--------------------------|-------------------------------------------------------------------------------|
+| [Group Mentoring Cohorts](/mentoring/mentors/group-mentoring.md) | **Planning in progress** | [Sept-Nov](/mentoring/programs/2024/groupmentorship/group-mentor-planning.md) |
 
 
 ### Self Paced
@@ -50,8 +50,6 @@ it's necessary to keep a continuous pipeline of quality contributors and we want
 
 Please reach out to #sig-contribex on slack or come to a mentoring meeting to get involved in planning //TODO add contribex README when this is updated
 
-Please reach out to #sig-contribex on slack or come to a mentoring meeting to get involved in planning //TODO add contribex README when this is updated
-
 
 #### Inspiration and Thanks
 

mentoring/programs/group-mentoring.md

@@ -0,0 +1,80 @@
+# Contributor Ladder Growth Programs
+
+These programs place an emphasis on learning in groups for active contributors
+that would like to be a reviewer or other leadership roles like a Chair. The 
+groups are semi-structured learning environments over the course of three
+months or a release cycle. Want to get `/lgtm` rights? Be a decision maker in an
+ OWNERS file? This could be a great way to get the knowledge you need, and some 
+ accountability to do it. Through this program you will get the opportunity to 
+ interact with active contributors who may be on the same path as you as well 
+ very experienced Kubernetes contributors.
+
+## How This Works
+Foundation:  
+This program is built around our [community membership guidelines] as well as 
+our [Chair] and [Tech Lead] governance descriptions.
+These docs show how you can grow through the project in different roles and
+provides the requirements to get to each level on our ladder. Building trust is 
+key.
+
+## Cohorts
+- No more than 4 mentees per 1 mentor; no more than 8 total in the group
+  - this scales better than 1:1 and peers can help each other in a community
+  setting
+- Everyone is on the same journey 
+Member -> Reviewer | Reviewer -> Approver | SIG Member -> Chair
+- Three months / one release cycle 
+- Private slack channel
+ For you to progress, the community wants to know you are dependable and 
+ understand the domain.
+
+Mentors can rotate facilitating once a week for slack standups with the 
+expectation that cohort members need to check in with a predetermined status 
+update (accomplishments, challenges, etc)  
+
+## Benefits of a Cohort
+* Peer mentoring  
+* Clear goals, objectives, and timelines  
+* Each mentee is working toward the same goal, cohort has an end date/timeframe  
+* Exposure to multiple areas of the project making well-rounded contributors  
+* Mentors share time commitments and responsibilities  
+* Exposure to multiple mentors in an open and collaborative environment
+
+
+## Mentor requirements  
+- Github Org Member
+- At least the same level as the goal of the group (example: Reviewer for 
+Reviewers) 
+- Time commitment: facilitate biweekly, hour long zoom sessions plus curriculum 
+planning in between sessions (~1-2h/wk total).
+
+## First Cohort Success Rates
+5/10 graduated into OWNERs files from members to reviewers in 2019. 2 are
+subproject owners in 2021.  
+
+## FAQs
+I'm a SIG Chair/TL/Subproject Owner and have a need for more members, reviewers,
+approvers, how can we form a cohort?  
+Reach out to #sig-contribex in slack or file an issue against 
+kubernetes/community 
+
+I'm a contributor looking for a cohort, where do I go?  
+Look in the kubernetes/community repo for issues labelled "contributor ladder
+mentoring" 
+
+I'm not a chair, tech lead, or subproject owner but I'm a reviewer or approver,
+how can I help?  
+Talk to your Chairs and Tech Leads about forming a group that you can help 
+mentor.  
+
+
+## Important Links
+[Mentor Guide]  
+[Mentee Guide]
+
+[Mentee Guide]: /mentoring/programs/archive/group-mentee-guide.mdguide.md
+[Mentoring/Contributor Info Form]: https://goo.gl/forms/SHWAiZ9Ih1qwuJbs1
+[Mentor Guide]: /mentoring/mentors/mentor-guide.md
+[community membership guidelines]: /community-membership.md
+[Chair]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#chair
+[Tech Lead]: https://github.com/kubernetes/community/blob/master/contributors/chairs-and-techleads/technical-lead.md