Merge pull request #14 from MIT-Emerging-Talent/collaboration/learning_goals

Add learning goals for Milestone 0

Author: CaesarGhazi

collaboration/communication.md

@@ -0,0 +1,48 @@
+# 📡 Communication Plan
+
+This document outlines how we stay in touch, when we meet,
+and how we ask for help. This is a living document and will evolve with our team.
+
+---
+
+## 💬 Communication Channels
+
+We’ll use the following tools with clear purposes:
+
+- **Issues**: Daily, for asking for help, setting a meeting agenda, creating a
+new challenge, and asking questions asynchronously.
+- **Pull Requests**: As needed, for code reviews and for other contributions in general.
+- **Discord/Slack**: Daily, for quick questions and discussions.
+- **Live Calls Zoom / Google Meet**: Weekly, for detailed discussions and planning.
+
+## Availability
+
+### Availability for calling/messaging (TIMEZONE: EET - UTC +2)
+
+| Day    | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday |
+|--------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:|
+| Caesar | x-x PM | x-x PM  | x-x PM    | x-x PM   | x-x PM | x-x PM   | x-x PM |
+| Fahed  | 6-8 PM | 7-9 PM  | 6-8 PM    | 5-7 PM   | 8-9 PM | 8-9 PM   | 6-8 PM |
+| Maria | x-x PM | x-x PM  | x-x PM    | x-x PM   | x-x PM | x-x PM   | x-x PM |
+| Mohammad | x-x PM | x-x PM  | x-x PM    | x-x PM   | x-x PM | x-x PM   | x-x PM|
+| Terry | x-x PM | x-x PM  | x-x PM    | x-x PM   | x-x PM | x-x PM   | x-x PM |
+| Tomas | x-x PM | x-x PM  | x-x PM    | x-x PM   | x-x PM | x-x PM   | x-x PM |
+
+### How many hours everyone has per day
+
+- Fahed: 1 ~ 2 hours
+- Caesar:
+- Maria:
+- Mohammad:
+- Terry:
+- Tomas:
+
+## Asking for Help
+
+There's a fine line between confidently learning from your mistakes, and
+stubbornly getting nowhere. Here is a general guide for when to ask for help
+based on how long you've been stuck on the same problem:
+
+1. _0 -> 30 min_: Try on your own
+2. _30 -> 60 min_: Ask your group for help
+3. _60+ min_: Tag your coaches in Slack or GitHub

collaboration/learning_goals.md

@@ -1,5 +1,66 @@
-# Learning Goals
+# 🎯 Learning Goals
 
-## Collective
+This document outlines both our shared and individual learning
+objectives for this project. While each member may have different goals,
+aligning expectations early ensures stronger collaboration and more meaningful outcomes.
 
-## Individual
+---
+
+## 🤝 Collective Goals
+
+As a team, we aim to:
+
+- Strengthen our collaborative skills in a remote, cross-cultural setting.
+- Apply the data science lifecycle to a real-world problem
+from domain exploration to final communication.
+- Improve project planning and task ownership using
+GitHub tools (Issues, Projects, PRs).
+- Produce clean, reproducible, and well-documented code and analyses.
+- Deliver clear, impactful results through visualizations and
+stakeholder-oriented communication.
+- Build confidence in reviewing and giving feedback on technical work.
+
+---
+
+## 👤 Individual Goals
+
+### **Fahed**
+
+- Improve GitHub fluency: project boards, CI/CD, and PR workflows.
+- Gain confidence in collaborative writing and documentation.
+- Practice clean Python code and code review habits.
+- Strengthen data visualization and storytelling skills.
+- Deepen understanding of exploratory data analysis (EDA) techniques.
+- Learn how to design and document a data pipeline collaboratively.
+- Gain confidence in managing raw datasets ethically and responsibly.
+- Improve research and domain framing skills.
+- Get familiar with reproducibility tools and Jupyter workflows.
+- Practice writing readable, reusable Python functions.
+- Focus on time management and structured task planning.
+- Strengthen understanding of data ethics and licensing.
+- Learn how to structure CI/CD for data science–oriented projects.
+
+---
+
+### **Caesar**
+
+---
+
+### **Maria**
+
+---
+
+### **Mohammad**
+
+---
+
+### **Terry**
+
+---
+
+### **Tomas**
+
+---
+
+> *"Learning is not attained by chance, it must be sought for with ardor."*  
+> *— Abigail Adams (adapted)*