# ParaView Issue Hackathon - June 15, 2023
**URL:** https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215
**Category:** Announcements
**Tags:** hackathon
**Created:** [June 2, 2023, 12:09pm UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215 "2023-06-02T12:09:18Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 2, 2023, 12:09pm UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/1 "2023-06-02T12:09:19Z")
## What
[ParaView’s issue tracker](https://gitlab.kitware.com/paraview/paraview/-/issues/) has many issues that may be no longer relevant or solved during the course of development. A clean issue tracker helps the ParaView community stay informed about current problems and concerns with the software. This hackathon will aim to clean up the issue tracker by confirming that issues persist and closing issues that no longer apply.
Example ways to participate:
- Triage an issue. Given the information in the issue, see if it can be reproduced in the latest version of ParaView ([download](http://www.paraview.org/download)). Mark it with an appropriate triage label.
- Request more information from the reporter if the issue is not clear.
- Close the issue if it is no longer reproducible.
## Who
Participation is open to the public. Anyone interested in ParaView as a user or as a developer is welcome, and so is anyone who wants to take part in an open source project. A computer is needed to access the [ParaView issue tracker](https://gitlab.kitware.com/paraview/paraview/-/issues/) during the hackathon. If you plan to join, please let us know in the replies to this topic.
## When
Date: **June 15, 2023**
**3PM - 11PM** Central European Summer Time (UTC+02:00)
**9AM - 5PM** Eastern Daylight Time (UTC−04:00)
## Where
**Location:** This will be a virtual hackathon, though participants at the same location are welcome to join from a shared video conference link. Connection information is below.
ParaView Issue Hackathon
Thursday, June 15 · 9:00am – 4:50pm
Time zone: America/New\_York
Google Meet joining info
Video call link: [https://meet.google.com/sxr-tqqv-myo](https://meet.google.com/sxr-tqqv-myo)
Or dial: (US) +1 774-369-0053 PIN: 876 431 899#
More phone numbers: [https://tel.meet/sxr-tqqv-myo?pin=4587244485348](https://tel.meet/sxr-tqqv-myo?pin=4587244485348)
---
### Author:  [@Ayat\_Mohammed](https://discourse.paraview.org/u/Ayat_Mohammed)
#### Post date: [June 5, 2023, 5:20pm UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/2 "2023-06-05T17:20:24Z")
I’m planning to join.
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [June 6, 2023, 5:54pm UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/3 "2023-06-06T17:54:37Z")
@phismith and I (@wascott ) will join. Thanks to Kitware for holding this.
Alan
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [June 7, 2023, 12:11am UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/4 "2023-06-07T00:11:15Z")
> [@cory.quammen](#):
>
> Request more information from the reporter if the issue is not clear.
There is the `triage:needs-info` label for this.
> [@cory.quammen](#):
>
> Close the issue if it is no longer reproducible.
Please add the `workflow:needs-verification` label when closing issues.
If anyone needs access to manage labels, feel free to ask. For those granting permissions, the `Reporter` level is sufficient for label editing.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 15, 2023, 7:49am UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/5 "2023-06-15T07:49:15Z")
> [@cory.quammen](#):
>
> Triage an issue. Given the information in the issue, see if it can be reproduced in the latest version of ParaView ([download](http://www.paraview.org/download)). Mark it with an appropriate triage label.
Can I suggest working with the last nightly release as well ? Issue fixed in master can be closed too.
> Close the issue if it is no longer reproducible.
No need to add the “needs-verification” label ? I think so but just checking.
---
### Author:  [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [June 15, 2023, 12:27pm UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/6 "2023-06-15T12:27:10Z")
I plan to join for the morning.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 15, 2023, 1:47pm UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/7 "2023-06-15T13:47:22Z")
Please join the ParaView Issue Hackathon, which is happening now!
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 16, 2023, 1:45am UTC](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215/8 "2023-06-16T01:45:20Z")
A big thank you to all who attended a very successful ParaView Issue Hackathon! About 12 ParaView developers and community members from around the world joined at various times throughout the day.
Together, we examined a total of 234 open issues. Of those 138 were determined to have been fixed or no longer relevant. We started with 2037 issues and ended the day with 1899.
Additionally, we confirmed a number of issues and tagged them as such. Where issues weren’t clear we requested from the reporter.
Thank you to all who contributed today, and I look forward to seeing you at the next one!