You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enrich project docs with video content, peer review images, and cross-links
Add content from the "DTC Zoomcamp projects" Loom video to the platform
projects page: project attempts, plagiarism rules, commit checking,
certificate name vs display name, reproducing peer projects, and past
office hours. Embed the Loom video at the top of the page.
Add peer review assignment and evaluation screenshots to the peer review
page. Add submission and technology choice sections to DE Zoomcamp and
ML Zoomcamp project pages with links back to the platform docs.
@@ -28,6 +30,8 @@ Peer review is a mandatory part of the project. After submitting your project, r
28
30
29
31
Each course has its own evaluation criteria. The platform will display the specific rubric when reviewing. Criteria typically assess project quality, documentation, and reproducibility.
30
32
33
+
<imgsrc="{{ '/assets/images/course-management-platform/peer-review-evaluation.jpg' | relative_url }}"alt="Peer review evaluation form with criteria"width="80%">
34
+
31
35
## Tips for Good Reviews
32
36
33
37
- Submit before the deadline even if you're not 100% confident in your evaluation
For most courses, you need to complete one project and you get two attempts:
20
+
21
+
- Data Engineering Zoomcamp - 1 project, 2 attempts
22
+
- MLOps Zoomcamp - 1 project, 2 attempts
23
+
- LLM Zoomcamp - 1 project, 2 attempts
24
+
- ML Zoomcamp - 2 projects, 3 attempts (you must complete 2 out of 3)
25
+
26
+
You only need to use one attempt. If you fail the first attempt, you still have a second chance. The second attempt also provides flexibility if you started the course late or are still catching up with the modules.
27
+
28
+
If you have extra time, you can submit different projects for both attempts and earn points for each - but they must be different projects. You cannot submit the same project twice.
29
+
13
30
## Project Gallery
14
31
15
32
The projects page displays a gallery of student projects from your cohort. Each project card shows:
@@ -44,11 +61,16 @@ The project submission form includes:
Your certificate name and display name are separate. The display name appears on the leaderboard - you can keep it anonymous if you prefer. The certificate name is what will be printed on your certificate. Make sure to set your certificate name before submitting - otherwise, you may end up with a placeholder instead of your real name.
67
+
47
68
### Tips
48
69
49
70
- Submit before the deadline even if your project isn't perfect
50
71
- Make sure your GitHub repository is public
51
-
- Use a specific commit ID to match what reviewers will see
72
+
- Use a specific commit ID (first seven characters of the commit hash) to match what reviewers will see
73
+
- If you keep committing after submission, update the commit ID in the form
52
74
- Share your work publicly to earn extra points
53
75
54
76
## Peer Review
@@ -65,3 +87,33 @@ Through peer review, you:
65
87
- Earn extra points for each review
66
88
67
89
Click on any project card to view details and submit your evaluation.
90
+
91
+
### Checking a Specific Commit on GitHub
92
+
93
+
When reviewing, you need to evaluate the project at the exact commit the author submitted. To see the repository at that commit, use this URL pattern:
94
+
95
+
```
96
+
https://github.com/user/repo/tree/COMMIT_ID
97
+
```
98
+
99
+
The author may have continued pushing changes after submission, but you should evaluate using the commit ID they provided.
100
+
101
+
To clone and run the project at that commit locally, clone the repository and then run `git checkout COMMIT_ID`.
102
+
103
+
### Reproducing Peer Projects
104
+
105
+
Try to reproduce the projects you review - clone them, run the code, deploy if possible. This is a great opportunity to learn from different approaches. However, sometimes full reproduction is not possible (for example, you might need cloud credentials you don't have). Use your own judgment on how thorough your review is. You can evaluate all the criteria without running the code, but running it helps you learn more.
106
+
107
+
## Plagiarism
108
+
109
+
Plagiarism is not permitted. You must not copy the work of others and present it as your own. If you notice plagiarism while reviewing a peer's project, give them zero points for everything and note it in the review comments.
110
+
111
+
Self-plagiarism is also not allowed:
112
+
113
+
- You cannot reuse a project from another course without changes
114
+
- If you passed project attempt one, you cannot submit the same project as attempt two - even if you improved it - because you would get double the points
115
+
- If you failed attempt one, you can improve and resubmit for attempt two
116
+
117
+
## Past Office Hours
118
+
119
+
For courses that have been running for some time, past office hours recordings contain useful information about projects. Typically, the last office hours of a cohort focus on project-related questions. Check the course playlist for these recordings.
Copy file name to clipboardExpand all lines: courses/data-engineering-zoomcamp/logistics/projects.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,12 @@ You decide:
33
33
34
34
Create a dashboard with at least two visualizations. Use Looker Studio, Streamlit, or any BI tool.
35
35
36
+
## Submission
37
+
38
+
You get 2 attempts to submit your project. If you fail the first attempt or need more time, you can use the second attempt. See the [project submission guide]({{ '/courses/course-management-platform/projects/' | relative_url }}) for details on how to submit, commit IDs, certificate name, and other platform mechanics.
39
+
40
+
You are not restricted to the technologies covered in the course. If the course uses GCP, you are free to use AWS, Azure, or anything else. If you use tools outside the course content, make sure to document everything in detail so your peer reviewers can understand your choices.
41
+
36
42
## Evaluation
37
43
38
44
Peer review is mandatory to pass the project. After submitting, you must review 3 projects from your cohort. See the [peer review guide]({{ '/courses/course-management-platform/peer-review/' | relative_url }}) for evaluation tips and process details.
Copy file name to clipboardExpand all lines: courses/ml-zoomcamp/certification.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,3 +35,9 @@ The **earliest you can receive your certificate is January 2025**, which comes a
35
35
To clarify expectations, only two elements are strictly **required for certification**: completing 2 out of 3 projects with deployments, and conducting peer reviews (3 reviews per project you submit).
36
36
37
37
However, several activities are **optional but highly recommended** for your learning success. [Homework assignments](assignments-and-scoring.html) provide excellent practice and help solidify concepts, even though they don't directly impact certification. Learning in public activities and active community participation, while optional, significantly enhance your learning experience and can lead to career opportunities.
38
+
39
+
## 4. Project Submission and Technology Choices
40
+
41
+
See the [project submission guide]({{ '/courses/course-management-platform/projects/' | relative_url }}) for details on how to submit your project, commit IDs, certificate name settings, and other platform mechanics.
42
+
43
+
You are not restricted to the technologies covered in the course. If the course uses a specific framework or cloud provider, you can use alternatives. However, if you use something outside the course content, describe everything with as many details as possible - your peer reviewers need full context to evaluate technologies they may not know.
0 commit comments