PyOrb Team

[YHordijk]

Project Lead: Tori Gijzen, Yuman Hordijk, Trevor A. Hamlin

Mentor: Nadine Spychala

Welcome to OLS-8! 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 Life Science program :tada:.

---

Week 1: Meet your mentor!

• [x] Meet mentor for 30 minutes
• [x] Create an account on GitHub
• [x] Check if you have access to the HackMD notes set up for your meetings with your mentor
• [x] Prepare to meet your mentor(s) by completing a short homework provided in your shared notes
• [x] Complete your own copy of the open leadership self-assessment and share it to your mentor 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.
• [x] Make sure you know when and how you'll be meeting with your mentor.

Before Week 2: Cohort Call (Welcome to Open Life Science!)

• [x] Attend call or catch up via YouTube

• [x] Create an issue on the OLS-8 GitHub repository for your OLS work and share the link to your mentor.

• [x] Draft a brief vision statement using your goals

  This lesson from the Open Leadership Training Series (OLTS) might be helpful

• [x] Leave a comment on this issue with your draft vision statement & be ready to share this on the call

• [x] Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3: Meet your mentor!

• [x] Meet mentor
• [x] Look up two other projects and comment on their issues with feedback on their vision statement
• [x] Complete this compare and contrast assignment about current and desired community interactions and value exchanges
• [x] Complete your Open Canvas (instructions, canvas)
• [x] Share a link to your Open Canvas in your GitHub issue
• [x] Start your Roadmap
• [x] Comment on your issue with your draft Roadmap
• [x] Suggest a cohort name at the bottom of the shared notes and vote on your favorite with a +1

Before Week 4: Cohort Call (Tooling and roadmapping for Open projects)

• [x] Attend call or catch up via YouTube
• [ ] Look up two other projects and comment on their issues with feedback on their open canvas.

Week 5 and later

• [x] Meet mentor
• [x] Create a GitHub repository for your project
• [x] Add the link to your repository in your issue
• [x] Use your canvas to start writing a README.md file, or landing page, for your project
• [ ] Link to your README in a comment on this issue
• [x] Add an open license to your repository as a file called LICENSE.md
• [x] Add a Code of Conduct to your repository as a file called CODE_OF_CONDUCT.md
• [x] Invite new contributors to into your work!

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

Week 6

• [x] Attend call or catch up via YouTube

Week 7

• [x] Meet mentor

Week 8

• [ ] Attend call or catch up via YouTube

Week 9

• [ ] Meet mentor

Week 10

• [ ] Attend call or catch up via YouTube

Week 11

• [ ] Meet mentor

Week 12

• [ ] Attend call or catch up via YouTube

Week 13

• [ ] Meet mentor

Week 14

• [ ] Attend call or catch up via YouTube

Week 15

• [ ] Meet mentor

[YHordijk]

Vision statement

Our group aims to empower chemists with state-of-the-art quantum-chemical analysis tools. The latest project is PyOrb, used for the automated analysis of complex molecular orbital interactions. PyOrb makes expert orbital analysis available to all chemists, regardless of their theoretical background, ensuring that knowledge knows no bounds!

[ToriGijzen]

Our Roadmap:

[ToriGijzen]

Our Open Canvas:

[paulmaxus]

Very detailed roadmap, nice! Can you add a link to your repo as well? I'm curious about your project and the codebase you start developing later this year :)

[ToriGijzen]

Thanks @paulmaxus Max!
Unfortunately, we can not make our code public yet due to confidentiality. But later this year, we will make the code public!