Skip to content

Curriculum Review Committee: Overview

Jump to bottom
simon edited this page Feb 26, 2021 · 2 revisions

This describes the overall premise of a group of folks wanting to review the curriculum for Ada Developer Academy's core program.

This committee should be a group of individuals from different backgrounds committed to the quality and practicality of this curriculum, the program it supports (Ada Developer Academy's core program), and the mission it supports.

Code of Conduct

We operate with a Code of Conduct based on the Contributor Covenant v2.0.

Extending our CoC, we also explicitly prioritize the voices of underrepresented people in tech, and their contributions, suggestions, feedback, comments, safety, health, and well-being in this committee.

Curriculum Philosophy

Work done through the Core Curriculum Review Committee should reflect the mission, values, guides, rules, patterns, and alignment outlined in the rest of the core wiki.

Something to explicitly name is that the learning goals for the curriculum has currently largely been determined through a combination of research with alum, company partners, educators, hiring managers, and other curricula. Suggestions for topics to teach is discouraged.

OSS and Free Always

As much as possible and is respectful, we should treat this as an open-source software project.

Commitment

This committee is a volunteer committee.

As part of this committee, the expectation is that each member:

  • Participates in the primary work and responsibilities reliably and with prompt communication per month
    • As a baseline, ideally each member will review at least 5 lessons per month
  • Commits to being part of the committee for at least 2 months at a time, ideally longer

Primary Work and Responsibilities

The primary responsibility of this committee is to provide feedback, comments, and suggestions to the curriculum development through PR reviews and communication through GitHub.

  • Each committee member will join The Curriculum Review Committee GitHub Team with their GH account
  • PR Reviews will be requested to the team
  • Our goal is for each lesson should have 2 reviews
  • Each lesson will finish with a list of contributors to that lesson. Each reviewer is encouraged to optionally include their name/username and date to this list

Reviews

Again, reviews on lessons are meant to serve our unified goal: committing to elevating the quality and practicality of this curriculum, the program it supports (Ada Developer Academy's core program), and the mission it supports.

In general, most comments can fit in one of these categories:

  1. Proofreading: grammar, spelling, readability, clarity, structure of a paragraph or two
  2. Accuracy: Is this code correct? Is this definition correct enough?
  3. Suggestions on lesson structure

Reviewers and curriculum developers should prioritize feedback on proofreading and accuracy.

  • Each PR comment should reflect one thought
  • Each PR comment should try to be clear about what it observes, why it can improve, and a suggestion for how to improve it if possible

Meetings

  • To get aligned and in sync, we will aim to have a monthly meeting.

Communication & Resources

Ada Core Repos (Blocks):

Contributing to Curriculum:

Teaching and Learning at Ada:

Curriculum Review Committee:

Clone this wiki locally