bitprj / bitproject Goto Github PK

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives
To curate a list of workshop ideas that our developers can draw inspiration from for their upcoming workshops.

• Create and set-up Airtable
• Confirm list of topics
• Compile list of medium articles for each topic

Collaborators and Tasks
@lazyplatypus
@kavuong

Deadline
Saturday, 4/4

Objectives

Checklist

• Week 1 Activities QA'd, in README format
• Week 1 Labs QA'd., in README format
• Week 2 Activities QA'd, in README format
• Week 2 Labs QA'd, in README format
• Week 3 Activities QA'd, in README format
• Week 3 Labs QA'd, in README format
• Week 1 Slides
• Week 2 Slides (have to be QA'd)
• Week 3 Slides

Plan

What still needs to be done later:
Week 1 and 2 completely up on GitHub with NEW FORMATTING
Week 3 Labs Developed and completely up on GitHub WITH NEW FORMATTING
QA of Week 2 Slides
Week 3 Slides

Collaborators and Tasks

Deadline
Week 2 Activities and Labs in README Sun, 4/19
QA Week 2 Slides Sun 4/19
Week 3 TBA

Objectives
To integrate Bit brand slide templates into mdx-deck
Collaborators and Tasks
@kavuong
@lazyplatypus

Deadline
end of next monthly cycle - so April 30th, 2020

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives
To integrate everyone's input and feedback on the documentation on the 4-week process through which new developers will contribute to teams.

Collaborators and Tasks

• Everyone provides initial feedback review of everyone's work on pull request

  • Set-up of overall pull request to master

• Organize meeting on Saturday to discuss entire documentation

• Follow-up work done on the following: (from #45 )

• "Introduction"

  • Summary of how teams will contribute to workshops
  • Why Workshops
  • Workshops are an hour long
  • Explanation of how there are two versions of each workshop: slide version and lab version
  • Summary of role of devs vs role of interns

• Guide on how to pursue an idea for a workshop

• Slide Deliverables

  • Part 1: Idea/Motivation
  • Part 2: Concepts + Interactive Introduction
  • Part 3: Interactive Tutorial + Additional Concepts

• 4-week stage run-through

  • Week 1: Idea Formulated, Proposal Formalized, Slides Part 1
    • Proposal fully fleshed out and finalized
  • Week 2: Code Deliverables for WK 2, Slides Part 2
  • Week 3: Code Deliverables for WK 3, Slides Part 3
  • Week 4: Code Deliverables for WK 4, lab conversion
    • Only summary of lab conversion needed (separate docs will cover it)
  • Role of devs and interns in entire development process

• separate docs needed for lab conversion process

Reviews

• How to conduct Code reviews
• How to conduct PPT/slide reviews
  • how to review each Slide Deliverable "Part"
• Reviews for lab converted from a workshop

Deadline
Final Review by @kavuong Wed, 4/8 of the following:

• Documentation on pursuing an idea for a workshop - Sat 4/4 @ShayanRiyaz

• Documentation on conducting code reviews - Sat 4/4 @ShayanRiyaz

• Documenting process of converting workshop -> lab - Sat 4/4 @sarahg500

• Documenting process of reviewing lab converted from workshop - Sat 4/4 @sarahg500

• PPT/Slide Reviews (by Week) @emily-gui

• Explaining Slide Deliverables @emily-gui

• 4-week Stage Runthrough @alliebailey

• Introduction @alliebailey

Objectives:
To introduce the Airtable/Hubspot flow of work with regards to school emails, and also delegating tasks for getting schools from every team member.
Collaborators:
Iris
Monica
(will fill in GitHubs later)
Deadlines:
Sunday, 3/29

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives
To produce high-quality blogs on case studies on Postman and MongoDB

• Emailed MongoDB for Case Study
• Emailed Postman for CEO's answers
• Interview with @vkxu657 on MongoDB
• Interview with MongoDB folks - @vkxu657
• 1st draft for MongoDB
• Final draft for MongoDB
• 1st draft for Postman
• Final draft for Postman

Collaborators and Tasks
@kavuong - Guidance on what to write, Review
@vkxu657 - Writing
@alliebailey - Postman Case Study

Deadline
MongoDB 1st Draft - TBA
MongoDB Final - TBA
Postman 1st Draft - Thurs, 4/16
Postman Final - Sat, 4/18

Objectives
To fully document the 3 or 5 week workflow, both for developers and managers.

• Developers' Week-by-week Responsibilities, 3 Weeks (choose idea)
• Developers' Week-by-week Responsibilities, 5 Weeks (create own idea)
• Managers' Week-by-week Responsibilities, 3 Weeks (choose idea)
• Managers' Week-by-week Responsibilities, 5 Weeks (create own idea)

Collaborators and Tasks
@kavuong

Deadline
Mon, 4/6

Objectives
To clarify to prospects what roles are available in Bit Project and what each role entails.

Collaborators and Tasks
@kavuong - DevRel Positions

• Head of DevRel
• Content Development Intern
• Content Developer
• Content Development Manager

@shreyagupta98 - People Positions / Marketing Positions

• Director of People

• Learning and Development Manager

• People Experience Associate

• Inclusion and Diversity Associate

• Onboarding Manager

• Recruiter

• Director of Marketing

• Manager of Design

• Illustrator

• Manager of Technical Writing

@wongband - Engineering Positions

• Director of Engineering
• Frontend Architect
• React.js Developer
• Backend Developer

Deadline
April 2nd

Objectives

• Determining time and date for first lecture (drop in call from Suhem)
• Compile addresses to send Twitter swag to

Collaborators and Tasks
@kavuong
Deadline
Will be compiled through an Airtable form after first 15 students are finalized at the end of this first week

Objectives
Documenting a comprehensive checklist for developers to follow when developing. Note that checklist for stages 1-4 have already been created on "Guide to Being a Manager" page, please reference that for this issue.

Please make a variant and only work within your variant. When working, please start pull requests from your variant to the "Developers-Bible" branch. All of your documentation should go in the "Guide to Being a Manager" page for now.

For instructions on how to make a variant, please follow this link.

Guidance on Writing Documentation

• Should not just focus on "what" but also "how" and "why"
  • Example: why is card numbering important? what would an actual length of a card look like?
• Follow the "show not tell" principle
  • Ideas don't fully click unless they see examples to fully comprehend the idea

Old Bible for reference: https://docs.google.com/document/d/1Qa5u1OM2IvsmA54KtoXvHyz5QeCVNVExPH4JIYcF7JI/edit

• General Items Documentation
• Stage 1 Documentation (mostly updating)
• Stage 2 Documentation (mostly updating)
  • Checkpoints need to be documented
  • Concepts need to be documented
• Stage 3 Documentation (creating from scratch using READMEs made by @wongband (Bryan) as inspiration)
  • READMEs should be edited to be more clear
  • Documentation for Test Cases should be edited to be more clear
• Stage 4 Documentation (creating from scratch)
• How this Checklist should be exactly used by Daniel (President), Kevin (or any Head of DevRel), managers and developers

Collaborators
@joeyhuaa - Stage 1 Documentation + Stage 2 Documentation + General Steps Documentation
@atuljayaram - Stage 3 Documentation
@julma1040 - Stage 4 Documentation
@Jmendoza194 - how this checklist should be used by everyone

Deadline
Monday, 3/30

For each module:

Pre-Approval

• 3-4 relevant learning objectives
• 4-5 sample activities with a one-sentence description
• 2-3 sample labs with a one-sentence description
• (if applicable) modules on road map before it and after it

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives

To integrate everyone's feedback on workshops.

Collaborators and Tasks

• Everyone provides initial feedback review of everyone's work on pull request

  • @taimurkashif review of  bitprj/workshops#20
  • @KathyLiu20 review of bitprj/workshops#17

• Follow-up work done on the following: (from #32)

• README on Workshops

• How to contribute to workshops

  • Porting existing workshop into our system
  • Adding workshop in collaboration with a company
  • Developing workshops from existing activities/labs
  • School onboarding workshop (link schools' onboarding)

• Documentation on how to code review a workshop

  • reviewing markdown cards

• Go through entire process of developing markdown cards -> PPT that fits inside of slide template

Deadline
Wednesday, 3/31 initial review by everyone
Follow-up work by Thursday, 4/2

Final Review by @kavuong Wed, 4/8

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives
To organize a Twitter API workshop at April's SacPy.

• Determine who will be presenting
• Determine Twitter API activities to present
• Finalize Workshop to be presented

Collaborators and Tasks
@julma1040 will put finishing touches on workshop, present on Thursday
@kavuong will provide comments, advise the presentation, as well as be available on Thursday

Deadline
Wed, 4/1
(SacPy is Thurs, 4/2 on Zoom)

Objectives

To integrate everyone's feedback on each other's work on the Bible for Developers.

Note that reviews should be conducted within the Developers-Bible branch, and include the following pages:

• Bible for Developers
• General Items Breakdown

• Stage 1 Breakdown
• Stage 2 Breakdown
• Stage 3 Breakdown
• Stage 4 Breakdown

• When making a comment, please find the appropriate page on GitHub's review (under "Files Changed" within the pull request menu)

• Everyone provides initial feedback review of everyone's work on #68

  • Review from @Jmendoza194
  • Review from @joeyhuaa
  • Review from @julma1040
  • Review from @atuljayaram

• Organize meeting on Saturday to discuss entire Bible

• Follow-up work done on the following: (from #30 )

• General Items Documentation

• Stage 1 Documentation (mostly updating)

• Stage 2 Documentation (mostly updating)

  • Checkpoints need to be documented
  • Concepts need to be documented

• Stage 3 Documentation (creating from scratch using READMEs made by @wongband (Bryan) as inspiration)

  • READMEs should be edited to be more clear
  • Documentation for Test Cases should be edited to be more clear

• Stage 4 Documentation (creating from scratch)

• How this Checklist should be exactly used by Daniel (President), Kevin (or any Head of DevRel), managers and developers

Collaborators and Tasks
@kavuong - initial review of everyone's work, organize meeting
All collaborators from #30:
@joeyhuaa - Stage 1 Documentation + Stage 2 Documentation + General Steps Documentation
@atuljayaram - Stage 3 Documentation
@julma1040 - Stage 4 Documentation
@Jmendoza194 - how this checklist should be used by everyone

Deadline
Wednesday, 3/31 initial review by everyone
Follow-up work by everyone by Friday, 4/3

Final Review by @kavuong Wed, 4/8

Objectives

To update our organizational structure here: https://about.bitproject.org/organization/organizational-structure/untitled

Have managers update their team vacancies.

This issue will be fully tackled after the transition from BitCamps to workshops.
Collaborators and Tasks
@kavuong
Deadline

Fri, 4/24

Objectives
Based on https://about.bitproject.org/teams/people,

Collaborators and Tasks
@vkxu657 -writing
@kavuong -direction

Deadline
Fri, 4/24

Objectives

• Assign devs to emails
• Notify devs of task
• Ensure devs do fill in emails

Collaborators and Tasks
@shreyagupta98 - assigning devs to emails, notifying devs of task
@kavuong - following up with all managers to ensure task gets done

Deadline
Wed, 4/1 (emails will be sent Thursday)

Objectives
To document a comprehensive and clear guide for reviewers' responsibilities: quality assurance, code reviews, pull requests, etc.

Please start pull requests to the "Managers-Bible" branch. Also do start by making a variant and then making a pull request to the Managers-Bible branch.

• Receiving module assignments documentation

  • Based on "Pre-approval" and "Post-approval" Checklists
  • Sections (or info that should be covered)
    • Pre-approval: What To Do
    • Explanation of Role of Epics + Assigning Epic Points
      • Module epic points = activity epic points + lab epic points + workshop epic points
    • Explanation of Role of Issues (curriculum issues)
      • issues should be made constantly
    • Explanation of Role of Milestones
    • Adding Issues to Epics (Modules + Activities + Labs)
      • point of discussion: should there be epic points on curriculum issues?
    • Long-term Plan with examples
    • Zenhub Calendar

• Weekly Manager's Tasks documentation (directions on what manager should complete every week)

  • Based on "Weekly Manager Checklist"
  • Sections (or what info should be provided)
    • Fri/Sun/Tues Timeline + "first draft" explanation + "final draft" explanation
    • Explanation of issues to be set-up each week (long-term plan) and first-timer issues
      • emphasis that issues have to fully address the long-term plan
    • Setting up Milestones
    • Adjusting long-term plan and epic points for each activity + lab epic based on activity last week + feedback

• Role of GitHub Projects

• Weekly Code Review Documentation (directions on reviewing devs' pull requests)

  • How to start a code review
  • Should include "Pull Request Checklist" in review for each pull request
    • Explanation of each part - why is each part important?
  • Process of commenting based on devs' issues addressed and where code is added/subtracted

• Documentation on Specific QA procedures for managers and developers (

  • Goal: Complete projects as swiftly as possible while incorporating developers' and managers' input into and throughout the entirety of the project.
  • Preliminary idea
    • Managers and I (Kevin) must conduct code reviews on GitHub
      • Checking issues and contributions
        • In every pull request, there needs to be a list of checkboxes addressed
        • Managers: Need to make sure all assigned issues in milestone were completed and that checkbox contributions match the assigned issues
      • Every PR must have comments that address checkboxes
        • Every checkbox needs to be addressed with a comment
          • Comments can be positive or constructive

• Documentation on Specific QA for Kevin and Daniel

• Kevin will audit a random PR from dev to manager to ensure comments are being left.
• Overall similar to code reviews
  • Kevin: Need to make sure that all assigned issues and checkbox contributions are connected with the long-term plan
  • Daniel: checking after Kevin
  • Daniel's Code Review
  • Daniel will audit a random one of Kevin's code reviews, Kevin will audit a random one of each manager's code reviews

• Role of Writing Team (Victoria Xu right now)
  • Essentially when all curriculum is merged to master after Kevin and Daniel's QA there needs to be a procedure for proofreading

Collaborators
@ismaildude - Module Assignments Documentation (first task)
@ojgao - Weekly Manager Checklist and GitHub projects (second and third tasks)
@mxthu313 - Weekly Code Review Documentation (fourth task)
@JasonL24 - Documentation on Specific QA procedures for managers and developers (fifth task)
@jeffchhen - Documentation on Specific QA procedures for Kevin and Daniel (sixth task)

Deadlines
Monday, 3/30
Tuesday, 3/31 @mxthu313

Objectives:

• Setting dedicated hours towards Bit
• Documenting the following on GitBooks
  • follow-ups in communication in the channel 1 day before, and then daily follow-ups via DM after the due date, as well as a video call discussing problems
  • setting deadlines
  • documenting admin task issues (template, process, adding deadlines to issues)

Collaborators:
@kavuong

Deadlines:
documenting should be done Tuesday, 3/31

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

When working, please place the documentation associated with each bullet point of work in a new markdown file.

Also please set up pull requests for your work.

Guidance on Writing Documentation

• Should not just focus on "what" but also "how" and "why"
  • Example: why is card numbering important? what would an actual length of a card look like?
• Follow the "show not tell" principle
  • Ideas don't fully click unless they see examples to fully comprehend the idea

Objectives

• README on Workshops

• How to contribute to workshops

  • Porting existing workshop into our system
  • Adding workshop in collaboration with a company
  • Developing workshops from existing activities/labs
  • School onboarding workshop (link schools' onboarding)

• Documentation on how to code review an activity version of a workshop

  • reviewing markdown cards

• Go through entire process of developing markdown cards -> PPT that fits inside of slide template

Collaborators
@taimurkashif - README On workshops + how to contribute to workshops

• 1st and 2nd bullet points above

@KathyLiu20 - Docs on how to code review a workshop (in .md format) + Developing markdown cards -> PPT + documentation

• 3rd and 4th bullet points above

Deadline
Monday, 3/30

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

• Checklist
• Documentation for each Item of the checklist

Objectives
To put together documentation on the 4-week process through which new developers will contribute to teams.

Instructions

Please put all of your work in the "future-workshop-plan" variant. All of your documentation should go in the "Future Workshop Plan" page for now.

The Future Workshop Plan page is right under the section "Developer Relations".

For instructions on how to make a variant, please follow this link.

General Info

• "Introduction"
  • Summary of how teams will contribute to workshops
  • Why Workshops
  • Explanation of how there are two versions of each workshop: slide version and lab version
  • Summary of role of devs vs role of interns (change the name)
• Guide on how to pursue an idea for a workshop
• Slide Deliverables
  • Part 1: Idea/Motivation
  • Part 2: Concepts + Interactive Introduction
  • Part 3: Interactive Tutorial + Additional Concepts
• 4-week stage run-through
  • Week 1: Idea Formulated, Proposal Formalized, Slides Part 1
    • Proposal fully fleshed out and finalized
  • Week 2: Code Deliverables for WK 2, Slides Part 2
  • Week 3: Code Deliverables for WK 3, Slides Part 3
  • Week 4: Code Deliverables for WK 4, lab conversion
    • Only summary of lab conversion needed (separate docs will cover it)
  • Role of devs and interns in entire development process
• separate docs needed for lab conversion process

Reviews

• How to conduct Code reviews
• How to conduct PPT/slide reviews
  • how to review each Slide Deliverable "Part"
• Reviews for lab converted from a workshop

Collaborators and Tasks
@sarahg500

• Documenting process of converting workshop -> lab (dev point of view)
• Documenting process of reviewing lab converted from workshop (manager point of view)

@ShayanRiyaz

• Documentation on pursuing an idea for a workshop
• Documentation on conducting code reviews

@emily-gui

• PPT/Slide Reviews (by Week)
• Explaining Slide Deliverables

@alliebailey

• Introduction
• 4-week Stage Runthrough

Deadline
Documentation on pursuing an idea for a workshop - Sat 4/4 @ShayanRiyaz
Documentation on conducting code reviews - Sat 4/4 @ShayanRiyaz
Documenting process of converting workshop -> lab - Sat 4/4 @sarahg500
Documenting process of reviewing lab converted from workshop - Sat 4/4 @sarahg500

Documenting PPT/Slide Reviews (by Week) - Thurs, 4/2 @emily-gui
Explaining Slide Deliverables - Thurs 4/2 @emily-gui
4-week Stage Runthrough - Thurs 4/2 @alliebailey
Introduction - Thurs 4/2 @alliebailey

Objectives
To demonstrate how a dev should use GitBooks, and explain how to use variants

• Role of GitBooks
• Explanation of how to make Variants
• Pull Requests and GitBooks

Collaborators and Tasks
@kavuong

Deadline
TBA

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives:
To send emails to all communications professors previously contacted, advertising the BitCamp.

• Lecture Time Confirmed
• Airtable Form Set-Up
• Emails Composed
• Emails Sent Out

Collaborators:
@ojgao @ismaildude - Lecture time confirmed
@minhtumn - Airtable form set-up
@kavuong - emails composed and sent

Deadlines:
Sunday, 3/29

Objectives:
To document the development and review process from start to end on GitBooks, all in one place with stages.

• Descriptions of Development
• Descriptions of Weekly Manager Review
• Descriptions of Review by Kevin
• Descriptions of Review by Daniel
• All descriptions highlighted with stages

Collaborators:

• @lazyplatypus
• @kavuong

Deadlines:

Objectives
Document how non-Davis students will enter our team

• #form-duos procedure => Airtable

Collaborators and Tasks
@kavuong
Deadline
Sun 4/19

Objectives

To integrate everyone's feedback on the Bible for Reviewers.

Follow-up work should be done directly on the managers-bible branch/variant.

• Everyone provides initial feedback review of everyone's work on pull request #73

  • Set-up of overall pull request to master

• Organize meeting on Saturday to discuss entire Bible

• Follow-up work done on the following: (from #29)

• Receiving module assignments documentation

  • Based on "Pre-approval" and "Post-approval" Checklists
  • Sections (or info that should be covered)
    • Pre-approval: What To Do
    • Explanation of Role of Epics + Assigning Epic Points
      • Module epic points = activity epic points + lab epic points + workshop epic points
    • Explanation of Role of Issues (curriculum issues)
      • issues should be made constantly
    • Explanation of Role of Milestones
    • Adding Issues to Epics (Modules + Activities + Labs)
      • point of discussion: should there be epic points on curriculum issues?
    • Long-term Plan with examples
    • Zenhub Calendar

• Weekly Manager's Tasks documentation (directions on what manager should complete every week)

  • Based on "Weekly Manager Checklist"
  • Sections (or what info should be provided)
    • Fri/Sun/Tues Timeline + "first draft" explanation + "final draft" explanation
    • Explanation of issues to be set-up each week (long-term plan) and first-timer issues
      • emphasis that issues have to fully address the long-term plan
    • Setting up Milestones
    • Adjusting long-term plan and epic points for each activity + lab epic based on activity last week + feedback

• Role of GitHub Projects

• Weekly Code Review Documentation (directions on reviewing devs' pull requests)

  • Based on "First Draft Pull Request Checklist"
    • Explanation of each part - why is each part important?
    • point of discussion: project labels and what should the naming and overall format of this PR be?

• Weekly Pull Request Documentation (directions on sending pull requests to master)

  • Complete "Final Draft Checklist"
    • Each part to be documented - why is each part important?
  • point of discussion: is a final draft pull request even necessary?

• Documentation on Specific QA procedures for managers and developers (

  • Goal: Complete projects as swiftly as possible while incorporating developers' and managers' input into and throughout the entirety of the project.
  • Preliminary idea
    • Managers and I (Kevin) must conduct code reviews on GitHub
      • Checking issues and contributions
        • In every pull request, there needs to be a list of checkboxes addressed
        • Managers: Need to make sure all assigned issues in milestone were completed and that checkbox contributions match the assigned issues
      • Every PR must have comments that address checkboxes
        • Every checkbox needs to be addressed with a comment
          • Comments can be positive or constructive

• Documentation on Specific QA for Kevin and Daniel

• Kevin will audit a random PR from dev to manager to ensure comments are being left.
• Overall similar to code reviews
  • Kevin: Need to make sure that all assigned issues and checkbox contributions are connected with the long-term plan
  • Daniel: checking after Kevin
  • Daniel's Code Review
  • Daniel will audit a random one of Kevin's code reviews, Kevin will audit a random one of each manager's code reviews

• Role of Writing Team (Victoria Xu right now)
  • Essentially when all curriculum is merged to master after Kevin and Daniel's QA there needs to be a procedure for proofreading

Collaborators and Tasks
@kavuong - initial review of everyone's work, organize meeting
All collaborators from #29:

• @ismaildude - Module Assignments Documentation (first task)
• @ojgao - Weekly Manager Checklist and GitHub projects (second and third tasks)
• @mxthu313 - Weekly Code Review Documentation (fourth task)
• @JasonL24 - Documentation on Specific QA procedures for managers and developers (fifth task)
• @jeffchhen - Documentation on Specific QA procedures for Kevin and Daniel (sixth task)

Deadline
Thursday, 4/2 initial review by everyone
Follow-up work by Friday, 4/3

Final Review by @kavuong Wed, 4/8

Under Stage 2: Slides and Component, step 1 and step 2 are repeated twice.

Objectives
To make it clear to developers how they should contribute their slides and labs during the workshop development process. Also to make the lab conversion process smoother.

• How to start off with MDX-Deck
• Branching process (branching off of manager's branch)
• Where to place their .mdx decks
• Where to place their lab work
  • Set up sample lab, with empty READMEs and card templates that just have to be copied
  • Must have specific instructions

Collaborators and Tasks
@kavuong
Deadline
Fri, 4/24

Objectives
Record DevRel welcome webinar with documentation
Collaborators and Tasks
@kavuong
Deadline
Thurs, 4/9

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives
Get Documentation for MDX Deck.

• Code Surfer
• MDX Deck Documentation for All Slides Formats
• MDX Deck Documentation in MDX Deck
• Restyling Slides with Input from Rochelle

Collaborators and Tasks
@atuljayaram

Deadline
Monday, 04/06/20

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Pre-Approval

• Asked a head (Kevin) to give you write access to GitBooks
• For each module:
  • 3-4 relevant learning objectives
  • 4-5 sample activities with a one-sentence description
  • 2-3 sample labs with a one-sentence description
  • (if applicable) modules on road map before it and after it
• GitBook Variant/GitHub branch set up with your modifications in the page "Roadmap Topic Breakdown"
• Content all correctly formatted

Post-Approval

• Placing modules appropriately within the Lucidchart road-map

Please consult our handbook here for any clarifications or questions!

Objectives

• Finalize time and date with managers
• Presentation slides on plan for workshops (#45)
  • Prepare set of general announcements
  • Process of transition for teams
  • Determine project options for interns and devs
  • Set up system for gathering input
  • Zoom link from @lazyplatypus
• Advertise meeting to developers
  • Ensure everyone will attend

Collaborators and Tasks
@kavuong
@minhtumn - make sure everyone will attend
Deadline
Saturday, 4/4
(Sunday is Meeting)

• Road Map Meetings/DevRel town halls
  • Procedures need to be documented
• Internal feedback system