-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Mentorships and Badging Programs (#466)
Signed-off-by: yarille <[email protected]> Co-authored-by: John Mertic <[email protected]>
- Loading branch information
Showing
6 changed files
with
251 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
name: Mentorship Program mentor application | ||
description: Submit to become a mentor for the Open Mainframe Project mentorship program | ||
title: 'Mentor application - NAME' | ||
labels: ["mentor-application"] | ||
assignees: | ||
- openmainframeproject/tac-voting-members | ||
- openmainframeproject/omp-staff | ||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
Thank you for your interest in becoming an Open Mainframe Program Mentorship Program Mentor. To be considered, create an [LF ID](https://openprofile.dev), put your mentorship project name in the title in place of NAME, and then answer the following questions. Reference the [Mentorship Program overview](https://github.com/openmainframeproject/tac/blob/master/process/mentorships.md) for any questions. | ||
- type: input | ||
id: name | ||
attributes: | ||
label: Name | ||
placeholder: ex. John Doe | ||
validations: | ||
required: true | ||
- type: input | ||
id: email | ||
attributes: | ||
label: Email | ||
description: Please use the email that matches your [LF ID](https://openprofile.dev) | ||
placeholder: ex. [email protected] | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: description | ||
attributes: | ||
label: Mentorship Description | ||
description: Please detail what the mentorship is, which project(s) would this be for, and the expected goals and outcomes. | ||
validations: | ||
required: true | ||
- type: input | ||
id: repo_url | ||
attributes: | ||
label: URL to the code repository for the project | ||
description: If there currently is no code repository, please put in 'N/A' | ||
- type: textarea | ||
id: technologies_used | ||
attributes: | ||
label: What technologies would be used by this mentorship? | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: skills-required | ||
attributes: | ||
label: What skills will mentees need to be successful in this mentorship? | ||
description: Also indicate any training/pre-reads required for the mentee | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: key_learnings | ||
attributes: | ||
label: What are 2-3 key learnings for mentees? | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: fun_facts | ||
attributes: | ||
label: 2-3 fun facts about you as a mentor | ||
description: This will be used for the mentorship announcement blog post | ||
validations: | ||
required: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
parent: Programs | ||
--- | ||
|
||
# Badging Program | ||
|
||
Open Mainframe Project hosted projects and working groups can issue badges through [Credly](https://credly.com) at no cost. Badges are a great way to showcase leaders in a community or achievements made. Some ideas for badges include: | ||
|
||
- Project maintainers/committers | ||
- Event speaker | ||
- Completing a program | ||
|
||
You can view the current list of badges issued by the Open Mainframe Project [on Credly](https://www.credly.com/organizations/the-linux-foundation/collections/open-mainframe-project/badge_templates). You can also [view the full list of badges available through the Linux Foundation](https://www.credly.com/organizations/the-linux-foundation/badges). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
--- | ||
parent: Programs | ||
has_children: true | ||
--- | ||
# Mentorship Program | ||
|
||
Helping connect the next generation with mainframe and open source, the mentorship program has helped students over the past several years become contributors to open source on mainframe, as well as develop the skills for a long career in technology. | ||
|
||
* TOC | ||
{:toc} | ||
|
||
## Why become a Mentor? | ||
|
||
With the goal of promoting Open Mainframe Project and its hosted projects around the globe, we are offering the following benefits for our Mentors: | ||
|
||
- Give back by introducing new participants to project communities | ||
- Pass along to mentees the skills and expertise you have developed | ||
- Leverage mentees to help augment the existing developer community’s resources and efforts | ||
- Grow your project’s community by helping new developers get involved | ||
|
||
Mentors are awarded the [Open Mainframe Project Mentorship Mentor badge](https://www.credly.com/org/the-linux-foundation/badge/open-mainframe-project-mentorship-mentor) upon successful completion of a mentorship. | ||
|
||
## Requirements for becoming an mentor | ||
|
||
- Must be affiliated with an Open Mainframe Project member OR is a contributor to an Open Mainframe Project hosted project. | ||
- Must be at least 18 years of age. | ||
- Must be a participant (TSC member, maintainer, contributor, or equivalent) in the project for which you want to be a mentor. | ||
- Should have significant experience on the subject matter and the skills that the mentees will be developing. | ||
- Must not be subject to any obligations to third parties (such as contractual obligations to an employer) that would restrict or prohibit performing as a mentor. | ||
- Must be able to devote sufficient time to assisting one or more mentees on a regular basis throughout their mentorships. | ||
|
||
## Mentorship Terms | ||
|
||
Open Mainframe Project Mentorship Program uses the [LFX Mentorship platform](https://lfx.linuxfoundation.org/tools/mentorship/) and aligns with their timelines for mentorships to get the maximum visability and engagement for it's mentorships. Terms and timeslines are listed below. | ||
|
||
### Spring Term: March 1st - May 31st | ||
|
||
- Mentorships available on LFX Mentorship: mid-January | ||
- Mentee applications open on LFX: approximately 4 weeks | ||
- Mentee application review and acceptance: approximately during the 2 weeks before the term begins. | ||
|
||
### Summer Term: June 1st - August 31st | ||
|
||
- Mentorships available on LFX Mentorship: mid-April | ||
- Mentee applications open on LFX: approximately 4 weeks | ||
- Mentee application review and acceptance: approximately during the 2 weeks before the term begins. | ||
|
||
### Fall Term: September 1st - Nov 30th | ||
|
||
- Mentorships available on LFX Mentorship: mid-July | ||
- Mentee applications open on LFX: approximately 4 weeks | ||
- Mentee application review and acceptance: approximately during the 2 weeks before the term begins. | ||
|
||
## How to submit a mentorship? | ||
|
||
You can submit a mentorship [here](https://github.com/openmainframeproject/tac/issues/new?template=mentorship-proposal.yml). Mentorships should be submitted at least 2 weeks before Mentee applications open on the LFX Mentorship platform. | ||
|
||
## Code of Conduct | ||
|
||
The Open Mainframe Mentorship program follows the [Open Mainframe Project Code of Conduct](https://github.com/openmainframeproject/foundation/blob/master/CODE_OF_CONDUCT.md). | ||
|
||
## FAQ | ||
|
||
Mentorship FAQs can be found here: | ||
[https://docs.linuxfoundation.org/lfx/mentorship/mentorship-faqs](url) | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
title: Mentee Final Evaluation | ||
grand_parent: Programs | ||
parent: Mentorship Program | ||
nav_order: 3 | ||
--- | ||
|
||
# Mentee Final Evaluation | ||
|
||
**Mentee:** | ||
|
||
**Mentor:** | ||
|
||
**Project:** | ||
|
||
**Project Description:** | ||
|
||
|
||
|
||
____ | ||
1. Rate Mentee (1-10, 10 being the highest): | ||
|
||
|
||
1. Rate Project - the project itself (was it defined properly? Too ambitious, too easy? | ||
|
||
1. Did the project have clearly defined goals and milestones for/by the mentee?) | ||
|
||
|
||
1. Evaluation of Mentee's accomplishments - technical and project management: | ||
|
||
|
||
1. Evaluation of Mentee's skills and ability - areas of mastery and of improvement: | ||
|
||
1. Final Mentorship Assessment? Pass/Fail: | ||
|
||
1. Anything else to share about the Mentee: | ||
|
||
|
||
1. How could the Open Mainframe Project Mentorship Program and/or processes be improved?: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
--- | ||
title: Project Weekly Status Report | ||
grand_parent: Programs | ||
parent: Mentorship Program | ||
nav_order: 2 | ||
--- | ||
|
||
# Project Weekly Status Report | ||
|
||
### Date: | ||
|
||
____ | ||
|
||
|
||
|
||
1. **Project Members (if applicable):** | ||
- Team member 1 | ||
- Team member 2 | ||
|
||
2. **Accomplishments for the week** -- and which team members participated/contributed: | ||
- Accomplishment – Team member: | ||
- Accomplishment – Team member: | ||
|
||
|
||
|
||
3. **List of Milestones to be completed and anticipated date** (indicate which ones are in danger of not being met) | ||
- Milestone – team member – date due: | ||
- Milestone – team member – date due: | ||
|
||
4. **List of issues, problems, or concern(s)**: | ||
|
||
- Issue – team member accountable: | ||
|
||
- Problem – team member accountable: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
--- | ||
title: Project Plan | ||
grand_parent: Programs | ||
parent: Mentorship Program | ||
nav_order: 1 | ||
--- | ||
|
||
# Project Plan | ||
|
||
*(This is a sample template for a Mentorship Project Plan)* | ||
|
||
|
||
**Student's Name:** | ||
|
||
**Mentor:** | ||
|
||
**Project:** | ||
|
||
**Project Description:** | ||
|
||
**Problem Definition:** | ||
|
||
**Deliverables:** | ||
|
||
**Coding Plan:** | ||
|
||
| Week | Tasks | Goals | | ||
|------|-------|-------| | ||
| _Week 1_ | _Task 1_ | _Goal 1_ | | ||
| ... | ... | ... | | ||
| ... | ... | ... | | ||
| ... | ... | ... | | ||
| ... | ... | ... | |