json-schema-org / json-schema-org/community

Ben Hutton's (@relequestual) 2021 Q4 Key Results

Open
#72 1 comment 0 reactions 1 assignee View on GitHub

@Relequestual is already working on this.

Since Oct 25, 2021.

Staff OKRs
Dominant language
No language data
Stars
135
Forks
77
No merged PRs in 30d

Description

These are my personal "key results" for 2021 Q4.
I'm putting them here and testing how easy it is to use GitHub Projects and Issues to manage them.
The method for this is using Objective Key Results (OKRs) loosely as defined in the Atlassian playbook.

  • json-schema-org/community#73
  • json-schema-org/json-schema-spec#1191
  • json-schema-org/community#76
  • json-schema-org/community#75
  • json-schema-org/community#77
  • json-schema-org/website#316
  • json-schema-org/website#317
  • json-schema-org/community#80
  • json-schema-org/community#81
  • json-schema-org/community#82
  • json-schema-org/community#83
  • json-schema-org/community#84
  • json-schema-org/community#85
  • json-schema-org/community#86

You can also now see this list as a public project: https://github.com/orgs/json-schema-org/projects/3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.