Skip to content

Commit be9342d

Browse files
constraints update v1
1 parent 4a4e6de commit be9342d

File tree

2 files changed

+10
-54
lines changed

2 files changed

+10
-54
lines changed

collaboration/communication.md

Lines changed: 0 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -1,54 +0,0 @@
1-
<!--
2-
this template is for inspiration, feel free to change it however you like!
3-
4-
Careful! be sure to protect your privacy when filling out this document
5-
everything you write here will be public
6-
so share only what you are comfortable sharing online
7-
you can share the rest in confidence with you group by another channel
8-
-->
9-
10-
# Communication
11-
12-
---
13-
14-
## Communication Schedule
15-
16-
| Day | How | The topic of discussion | | --- | :-: | ----------------------- |
17-
| | | |
18-
19-
## Communication Channels
20-
21-
how often will we get in touch on each channel, and what we will discuss there:
22-
23-
- **Issues**:
24-
- **Pull Requests**:
25-
- **Slack/Discord**:
26-
- **Video Calls**:
27-
28-
---
29-
30-
## Availability
31-
32-
### Availability for calling/messaging
33-
34-
| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday |
35-
| ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: |
36-
| _name_ | | | | | | | |
37-
38-
### How many hours everyone has per day
39-
40-
- name: _5h_;
41-
- name: _6h_;
42-
- name: _5h_;
43-
- name: _4h_;
44-
- name: _3h_;
45-
46-
## Asking for Help
47-
48-
There's a fine line between confidently learning from your mistakes, and
49-
stubbornly getting no where. Here is a general guide for when to ask for help
50-
based on how long you've been stuck on the same problem:
51-
52-
1. _0 -> 30 min_: Try on your own
53-
1. _30 -> 60 min_: Ask your group for help
54-
1. _60+ min_: Tag your coaches in Slack or GitHub

collaboration/constraints.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,16 @@ to allow for reviews and backups.
4242
- We will only include tools and code we understand and can explain clearly.
4343
- We will prioritize clarity over complexity in both data and code.
4444

45+
📨 Communication
46+
47+
- Communication will primarily be asynchronous via Slack and GitHub,
48+
with task tracking managed using GitHub issues and project boards.💬
49+
50+
🕒 Scheduling and Deadlines
51+
52+
Each team member should allocate specific working hours within their schedule
53+
to ensure milestones are delivered on time while maintaining productivity and well-being.⏱️'
54+
4555
---
4656

4757
> Defining clear constraints helps us commit to achievable goals and encourages

0 commit comments

Comments
 (0)