Nicholai/jan
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: capitalize title with chicago style

Browse Source
This commit is contained in:
Ho Duc Hieu 2024-01-12 13:58:07 +07:00
parent 2e31e52607
commit fd8ff27ba5
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/handbook/04-core-contributors/01-how-we-hire.mdx
View File

@ -19,7 +19,7 @@ keywords:
_The purpose - To conduct fair, unbiased interviews that focus on identifying candidates with initiative, scrappiness, and a good fit for a core contributor role at Jan._ _The purpose - To conduct fair, unbiased interviews that focus on identifying candidates with initiative, scrappiness, and a good fit for a core contributor role at Jan._
## Our key principles ## Our Key Principles
### Avoiding Bias ### Avoiding Bias
@ -38,7 +38,7 @@ Value alignment isn’t something that’s often spoken about when hiring for a
![Value Alignment](./assets/01-value-alignment.png) ![Value Alignment](./assets/01-value-alignment.png)
## We care about ## We Care About
### Initiative and Scrappiness ### Initiative and Scrappiness

6
docs/docs/handbook/04-core-contributors/02-embracing-pod-structure.mdx
View File

@ -31,7 +31,7 @@ How do we decide what gets prioritized when there are so many potentials?
[Our product handbook](https://jan.ai/handbook/product/) is not just a document; it makes up part of our larger open company handbook. The aim is for everything to be outlined - from our high-level roadmap, which is used for strategic alignment and reflects our engineering implementation cycles, to our Standup Kanban, the go-to view for our daily standups. [Our product handbook](https://jan.ai/handbook/product/) is not just a document; it makes up part of our larger open company handbook. The aim is for everything to be outlined - from our high-level roadmap, which is used for strategic alignment and reflects our engineering implementation cycles, to our Standup Kanban, the go-to view for our daily standups.
### How we label ### How We Label
We use Roadmap Labels to tag large, long-term projects that often span multiple teams and sprints. For example, a label like 'roadmap: Jan has Mobile' signifies a significant strategic initiative. We use Roadmap Labels to tag large, long-term projects that often span multiple teams and sprints. For example, a label like 'roadmap: Jan has Mobile' signifies a significant strategic initiative.
@ -41,11 +41,11 @@ These roadmaps contain epics – large stories that typically span 1-2 weeks, co
Our milestones, aligned with semantic versioning, track release versions and fit neatly into our 2-week sprint cycles. Tasks, whether they're features, bugs, or chores, are designed to be completed within a few days. They always belong to an epic, tying back to our larger roadmap. Our milestones, aligned with semantic versioning, track release versions and fit neatly into our 2-week sprint cycles. Tasks, whether they're features, bugs, or chores, are designed to be completed within a few days. They always belong to an epic, tying back to our larger roadmap.
### Kanban- Because a cluttered brain doesn’t make decisions ### Kanban - Because a Cluttered Brain Doesn’t Make Decisions
Our Kanban board is a dynamic snapshot of our workflow. It ranges from 'no status' for issues needing triage, to 'done' for completed tasks. This system helps us efficiently manage our workflow and ensures that every team member is aware of their responsibilities and the current state of our projects. Our Kanban board is a dynamic snapshot of our workflow. It ranges from 'no status' for issues needing triage, to 'done' for completed tasks. This system helps us efficiently manage our workflow and ensures that every team member is aware of their responsibilities and the current state of our projects.
### How we triage bugs ### How We Triage Bugs
Our Triage Standard Operating Procedure (SOP) is crucial for handling urgent bugs by assigning them to an owner and tagging them to the current sprint and milestone. For all other tasks, we assign the correct roadmap label(s) and owner. Determining what fires we let burn is a continuous learning and practice to build. Our Triage Standard Operating Procedure (SOP) is crucial for handling urgent bugs by assigning them to an owner and tagging them to the current sprint and milestone. For all other tasks, we assign the correct roadmap label(s) and owner. Determining what fires we let burn is a continuous learning and practice to build.