# Slicer Hackathon hosted by Kitware: January 24th, 2025

**URL:** <https://discourse.slicer.org/t/slicer-hackathon-hosted-by-kitware-january-24th-2025/41096>\
**Category:** Events\
**Created:** [January 15, 2025, 3:16pm UTC](https://discourse.slicer.org/t/slicer-hackathon-hosted-by-kitware-january-24th-2025/41096 "2025-01-15T15:16:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [January 15, 2025, 3:16pm UTC](https://discourse.slicer.org/t/slicer-hackathon-hosted-by-kitware-january-24th-2025/41096/1 "2025-01-15T15:16:29Z")

</div>

The upcoming **Slicer Hackathon** is an **in-person event** at the **Kitware North Carolina office**. While we expect only Kitwareans to attend in person, remote participants are welcome to join via **Google Meet** (link will be shared with registered attendees).

The main goal of this hackathon is to **collaboratively address issues** , with the expectation that each participant will contribute at least **one pull request** that is either:

- **Reviewed & integrated** , or
- **Ready to be reviewed & integrated.**

## 🚀 Why Attend?

- **Learn** : Get hands-on experience contributing to Slicer, receive guidance, and improve your development skills.
- **Contribute** : Make meaningful contributions to an open-source medical imaging community.
- **Connect** : Collaborate with fellow Slicer developers, discuss ideas, and gain insights from experienced contributors.

## 📅 Mark Your Calendar

- **📆 Date** : Friday, January 24th, 2025
- **🕗 Time** : 9:00 AM - 6:00 PM ET
- **📍 Location** : Hybrid - Kitware North Carolina Office & Google Meet (link will be shared with registered attendees)
- **👥 Who** : Open to all Slicer developers!

## 🔧 Prepare for the Hackathon

To ensure a productive session, please complete the following beforehand:

✅ **[Register](https://forms.gle/F1jjfPxcLJ9f4Ys17)** by Monday, January 20th  
✅ **Create a GitHub account** and fork the Slicer repository.  
✅ **Set up your development environment** : Follow the [Slicer Build Instructions](https://slicer.readthedocs.io/en/latest/developer_guide/build_instructions/index.html).  
✅ **Review issues** : Look through the [Good First Issues](https://github.com/Slicer/Slicer/labels/good%20first%20issue) to identify potential tasks.  
✅ **Get in touch** with @Sam_Horvath and @jcfr if you have another issue in mind.  
✅ **Join the discussion** : Participate in pre-event discussions to clarify objectives and get feedback.

## 🔥 During the Hackathon

- Engage with other participants to exchange knowledge and ideas.
- Work on your assigned task and collaborate with peers.
- **Adhere to** [Slicer’s Code of Conduct](https://github.com/Slicer/Slicer?tab=coc-ov-file#readme).
- **(Recommended) Have fun!** 🎉

## 📝 Assign Yourself a Task

To select an issue to work on, review the list of [Good First Issues](https://github.com/Slicer/Slicer/labels/good%20first%20issue) or discuss with @Sam_Horvath and @jcfr if you have another issue in mind.

📌 Once you start working on an issue, assign it to yourself if you can (Slicer developers) or add a comment stating `I am looking into this` or something similar.

💡 If you decide you don’t want to take it, write so in another comment. **Extra points:** write any findings which might help someone tackling the issue in the future.

## Acknowledgments

This hackathon is supported by Kitware. Kitware provides advanced technical computing, state-of-the-art AI, and tailored software solutions to our customers. Read more on Kitware’s [about page](https://www.kitware.com/about/).

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [January 17, 2025, 5:54pm UTC](https://discourse.slicer.org/t/slicer-hackathon-hosted-by-kitware-january-24th-2025/41096/2 "2025-01-17T17:54:05Z")

</div>

Reminder: registration deadline is **Monday** , and hackathon takes place on **Friday**.
