Title: Theory / Unimportant / Compagnie considérée / Open Craft

Question: How many people are in a cell
Answer: At most 12
Page: https://handbook.opencraft.com/en/latest/organization/
Context: Open Craft

Name: Cell
Definition: The smaller group to which a contributor belong
Page: https://handbook.opencraft.com/en/latest/organization/
Context: Open Craft

Name: Mitosis
Definition: when a cell of 12 recruit a member, it splits into two smaller cells
Page: https://handbook.opencraft.com/en/latest/organization/
Context: Open Craft

Name: Ocim
Definition: Hosting automation software
Page: https://handbook.opencraft.com/en/latest/organization/
Context: Open Craft

Question: where can an employee work from ?
Answer: Anywhere with high-bandwith internet connection
Page: https://handbook.opencraft.com/en/latest/roles/#what-is-expected-from-everyone

Question: Constraint on schedules
Answer: Remaining available for question
Page: https://handbook.opencraft.com/en/latest/roles/#what-is-expected-from-everyone
Answer2: Not expecting others to be available on week-end
Answer3: Going to Open edX conf' every year
Answer4: 40hours/week on average each month
Answer5: Colleagues needs to know about it
Answer6: Available for srint meeting on monday

Question: Clients must be answered in how much time
Answer: At most 24 hours.
Page: https://handbook.opencraft.com/en/latest/roles/#what-is-expected-from-everyone

Question: What to do when answering clients?
Answer: help@opencraft.com in copy
Page: https://handbook.opencraft.com/en/latest/roles/#what-is-expected-from-everyone
Context: Open craft

Question: How much time to answer pings on github/gitlab
Answer: 24 hours
Page: https://handbook.opencraft.com/en/latest/roles/#what-is-expected-from-everyone

Question: How much time to answer pings/email in chat
Answer: At most 24 hours, preferrably less
Page: https://handbook.opencraft.com/en/latest/roles/#what-is-expected-from-everyone

Question: Where to have discussion
Answer: Always in public, so that other can see what people are working on
Page: https://handbook.opencraft.com/en/latest/roles/#what-is-expected-from-everyone
Context: open craft

Question: How to take a decision affecting only oneself
Answer: Take it and communicate to anyone potentially interested
Page: https://handbook.opencraft.com/en/latest/decisions/
Context: Open craft

Question: How to take a decision affecting others
Answer: - It's often better to start with the problem and ask for advice or potential solutions from those with expertise or who would be affected.
Page: https://handbook.opencraft.com/en/latest/decisions/
Context: Open craft
Answer2: - Then prepare the proposal itself, e.g. a pull request for code, or for changes to the handbook's rules;
Answer3: - For a trivial decision, a comment in one of OpenCraft's tools (if it happens on a synchronous tool like the chat though, make sure to document this discussion and link to it from an asynchronous tool);
Answer4: - For any other matter, describe the decision to take and the options in a Google Doc on the shared folder, and post it on an asynchronous discussion tool, such as the forum or Jira, pinging anyone who you think could be affected by or interested in the change. Also err on the side of over-communicating on this.

Question: When to open a PR
Answer: Early, even if it is not ready to merge
Page: https://handbook.opencraft.com/en/latest/pull_request_process/

Question: Why to open a PR
Answer: - Pull requests send an email notification to anyone "watching" the repository, so they can stay informed about new developments.
Page: https://handbook.opencraft.com/en/latest/pull_request_process/
Answer2: - Pull requests will usually trigger an automated build, to ensure tests are passing, provision a test environment, or even to deploy the changes when you merge them.
Answer3: - Pull requests provide a way to associate the changes with a particular JIRA ticket (this can also be done via the git commit message, but a PR title/description can be edited by anyone with admin access to the repo, and a git commit message cannot.)
Answer4: - Pull requests provide a public place to give context for the changes, as opposed to JIRA tickets which are often private.