Skip to content

Commit eefca53

Browse files
authored
Added a post with updates; highlighted work in progress is ok. (#8)
* Added a post with updates; highlighted work in progress is ok. * Move image so it's not messing up the index page.
1 parent a155428 commit eefca53

File tree

4 files changed

+27
-1
lines changed

4 files changed

+27
-1
lines changed

_posts/2025-02-19-updates.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
layout: post
3+
title: "Updates from the Working Group!"
4+
date: 2025-02-19 09:00:00 -0400
5+
categories: jekyll update
6+
---
7+
8+
9+
2024 was a busy year for the Code Review Working Group! We completed [four reviews](/recent-reviews.html), switched to quarterly submission deadlines, and presented our work at DHTech's mini-conference ["DH Inside Out" at DH2024](https://dh-tech.github.io/blog/2024/06/14/dh-inside-out-dh2024-program/).
10+
11+
12+
We plan 2025 to be just as exciting and succesful but we need your help! Do you have code that could benefit from being reviewed? Maybe you plan on writing a paper about it but want to make sure there are no bugs in the code you might have missed? Or maybe you would like a second opinion on how you architected your code? Or maybe you are still learning and are wondering if you approach is right! All of these motivations (and more!) are valid reasons to submit your code for review. Your code does not have to be finished and polished. Take a look at our [submission page](submit-code.html) and submit your code for review!
13+
14+
If you don't have any code at the moment you would like to have reviewed but would like to get involved, you can also sign up to be a facilitator. Facilitators organize the code review process by organizing meetings and getting everyone on the same page. It’s low effort but a really important job! You’ll be recognized as a facilitator on our website afterwards and will have everyone’s deep gratitude. You can sign up using our [facilitator application form](https://forms.gle/GPzv3wzuB5WXq24V9).
15+
16+
<center><img src="/assets/imgs/geekpoke-codereview.jpeg" width="600px" ></center>
17+
18+
19+
20+
909 KB
Loading

index.html

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,9 @@ <h2>Our Process</h2>
3939
<hr class="col-3 col-md-2 mb-5">
4040

4141
<h2>Submission Deadlines</h2>
42-
42+
<div class="alert alert-warning" role="alert">
43+
Please note that you do not need a finish product to be able to submit your code for review! You are welcome to <b>submit code that is work in progress</b>. All we ask that you select a piece of code that can be reviewed in about an hour.
44+
</div>
4345
<p>
4446
Our quarterly deadlines to submit code for review are as follows:
4547
</p>

submit-code.html

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,10 @@ <h2>General requirements</h2>
2222
<li>Example data is available.</li>
2323
</ul>
2424

25+
<div class="alert alert-warning" role="alert">
26+
Especially if you are submitting code in progress, we understand that the above requirements might not be met. <b>Please submit your code anyways</b> and make a note in your submission that you could not meet the requirements. We will take a look and let you know if there is anything we believe is needed to effectively review your code.
27+
</div>
28+
2529
<h2>How to submit a review request?</h2>
2630
<p>
2731
When getting ready to submit code for a review, please make sure to have the following information available (you will need them for the submission form):

0 commit comments

Comments
 (0)