CodeBuddies

[lpatmo]

Project Lead: @lpatmo

Mentor: @acgetchell

Welcome to OL7, Cohort C! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training 🎉.

---

Before Week 1 (Jan 30): Your first mentorship call

• Complete the OLF self-assessment (online, printable). If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
• Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Feb 6): First Cohort Call (Open by Design)

• Complete Assignment 'Write Your Vision or Mission Statement'. Leave a comment on this issue with your draft vision statement & be ready to share this on the call.
• Watch 'Mozilla & Working Open'.
• Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Feb 13): Mentorship call

• Look up two other projects and comment on their issues with feedback on their vision statement.
• Complete your Open Canvas (instructions, canvas). Comment on this issue with a link to your canvas.
• Start your Roadmap. Comment on this issue with your draft Roadmap.

Before Week 4 (Feb 20): Cohort Call (Build for Understanding)

• Look up two other projects and comment on their issues with feedback on their open canvas.
• Pick an open license for the work you're doing during the program.
• Use your canvas to start writing a README, or landing page, for your project. Link to your README in a comment on this issue.

Week 5 and more

• Create a repository for your project. New to GitHub? You can fork our templates.
• Add Contributing Guidlines
• Add a Code of Conduct
• Submit your project to Mozilla Pulse, add the tag #mozsprint
• Invite new contributors to into your work!

This issue is here to help you keep track of work as you start Open Leaders. Please refer to the OL7 Syllabus for more detailed weekly notes and assignments past week 4.

[lpatmo]

Mission of CB Connect: In a community of people helping each other become better at software development, connect mentees with people who want to teach/mentor, connect accountability with each other, and connect open source projects with potential new contributors.

[lpatmo]

Canvas: https://docs.google.com/presentation/d/1QjVW5UPnyfCQaLCvM-Lqne87a1xYsHS763UEK6D5pTQ/edit#slide=id.p

[lpatmo]

Roadmap/Github README: https://github.com/codebuddies/cb-connect/blob/staging/README.md

[BhuvanaMeenakshiK]

Mission of CB Connect: In a community of people helping each other become better at software development, connect mentees with people who want to teach/mentor, connect accountability with each other, and connect open source projects with potential new contributors.

Hey this is cool. Curious to know how do you match the skills and connect them accordingly?

[abhayrjoshi]

Hello Ipatmo, How do you ensure that the platform doesn't become the way "mainstream" are, and keep serving the "shy"?

[belengimenezcic]

Mission of CB Connect: In a community of people helping each other become better at software development, connect mentees with people who want to teach/mentor, connect accountability with each other, and connect open source projects with potential new contributors.

I like this! Do you have a specific community you are focusing on first?

[lpatmo]

Hello Ipatmo, How do you ensure that the platform doesn't become the way "mainstream" are, and keep serving the "shy"?

Good question! So when all the applications are submitted, they're kept anonymous. :) It's not a social network, but an anonymous connecting platform.

I like this! Do you have a specific community you are focusing on first?

This will serve the CodeBuddies community (people who've already joined codebuddies.org).

Hey this is cool. Curious to know how do you match the skills and connect them accordingly?

There will be 7 categories:

• I want a mentor
• I want to help teach/mentor
• I want an accountability or coding partner
• I want feedback/advice
• I want an open source project to contribute to
• I am looking for contributors to my open source project
• Other

The moderator will try to connect someone in the mentor category with someone in the "I want to help teach/mentor" category, and someone in the "I want to contribute to an open source project" category with someone in the "I am looking for contributors" category, etc.

[nor-mn]

Very interesting! It can become more ambitious in the long term. Successes! 😄
La LIBREría #47

[samu-workopen]

Really great idea, thank you for sharing. I have some questions:
Did you figure out why the people are "shy"?
What kind of policy's to have in mind to get sure that you have a good learning environment between the coding partners?
How do you get sure that the coding pairs are also working in the long term together and not just for one or two months?

[lpatmo]

Thanks for the questions!

Did you figure out why the people are "shy"?

People have told me that it feels intimidating to see that e.g. a thousand people are in a Slack channel, and to post their question in the channel, even if it says something like #javascript (and therefore is the right place to ask).

What kind of policy's to have in mind to get sure that you have a good

learning environment between the coding partners? Good question -- we expect people to follow the Code of Conduct while learning together. How they learn together is up to them, though (e.g. it could be via chat, or in a Zoom screenshare)

How do you get sure that the coding pairs are also working in the long

term together and not just for one or two months? I actually don't expect that the pairs should be working together long term, but they can if they want to. The expectation is one-off 1-hour meetings, but if say it's a long-term open sourced project that both partners want to work on, then that would be great. I'm hesitant to put too much responsibility on the people volunteering to teach or mentor.

…

On Sun, Feb 17, 2019 at 2:49 AM samu-wmde ***@***.***> wrote: Really great idea, thank you for sharing. I have some questions: Did you figure out why the people are "shy"? What kind of policy's to have in mind to get sure that you have a good learning environment between the coding partners? How do you get sure that the coding pairs are also working in the long term together and not just for one or two months? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#102 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AETbu3wevp7g351B2Qt7BbCyU6qjrTsKks5vOTPNgaJpZM4aT2_m> .

[lpatmo]

(Btw, thanks for asking these questions -- I will keep track of them for the FAQ)

…

On Sun, Feb 17, 2019 at 3:14 PM Linda Peng ***@***.***> wrote: Thanks for the questions! > Did you figure out why the people are "shy"? People have told me that it feels intimidating to see that e.g. a thousand people are in a Slack channel, and to post their question in the channel, even if it says something like #javascript (and therefore is the right place to ask). > What kind of policy's to have in mind to get sure that you have a good learning environment between the coding partners? Good question -- we expect people to follow the Code of Conduct while learning together. How they learn together is up to them, though (e.g. it could be via chat, or in a Zoom screenshare) > How do you get sure that the coding pairs are also working in the long term together and not just for one or two months? I actually don't expect that the pairs should be working together long term, but they can if they want to. The expectation is one-off 1-hour meetings, but if say it's a long-term open sourced project that both partners want to work on, then that would be great. I'm hesitant to put too much responsibility on the people volunteering to teach or mentor. On Sun, Feb 17, 2019 at 2:49 AM samu-wmde ***@***.***> wrote: > Really great idea, thank you for sharing. I have some questions: > Did you figure out why the people are "shy"? > What kind of policy's to have in mind to get sure that you have a good > learning environment between the coding partners? > How do you get sure that the coding pairs are also working in the long > term together and not just for one or two months? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#102 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AETbu3wevp7g351B2Qt7BbCyU6qjrTsKks5vOTPNgaJpZM4aT2_m> > . >

[scottkildall]

I just read the ReadMe, it's very clear! I like the idea a lot as it helps build community by serving those who aren't chatting in the forums. As someone who does some software development (mostly solo), I'm wondering if there is a type of "software development" that you're targeting. Are these other open source projects, inside companies, etc? What are the types of environments that CodeBuddies might be used in? I'd love to some specific examples. Thanks!