# ParaView hackathon
**URL:** https://discourse.paraview.org/t/paraview-hackathon/11907
**Category:** Development
**Tags:** hackathon
**Created:** [April 17, 2023, 2:27pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907 "2023-04-17T14:27:03Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [April 17, 2023, 2:27pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/1 "2023-04-17T14:27:03Z")
It’s been a while since we have had a ParaView hackathon - let’s plan one for early June 2023.
Possible topics are:
- issue cleanup in GitLab
- documentation
- Catalyst, emphasizing documentation
Since likely participants are spread out over many time zones, we can make this a “rolling” hackathon where people join and leave at normal working hours as available.
Please reply with other ideas for a hackathon!
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 2, 2023, 7:05am UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/2 "2023-05-02T07:05:30Z")
Awesome, I’d be glad to work on the issue cleanup !
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [May 2, 2023, 12:34pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/3 "2023-05-02T12:34:42Z")
I think focusing on issue _triage_ is important. This means just classifying and categorizing issues. I’d avoid actually fixing anything but instead labeling them with `triage:confirmed` or closing them if they’re no longer relevant. Also checking for missing data or instructions (`triage:needs-info`). Finding duplicates is also very useful.
Doing the same categorization on MRs would also be a good idea.
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 2, 2023, 2:27pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/4 "2023-05-02T14:27:57Z")
Currently I’m planning on having Phil and me work the day verifying or closing bugs, and looking for (and closing) duplicates. Ben describes exactly what I had in mind. We won’t be touching MRs.
@phismith
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 4, 2023, 7:49am UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/5 "2023-05-04T07:49:24Z")
> let’s plan one for early June 2023.
Could the date be fixed soon ?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 4, 2023, 10:51pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/6 "2023-05-04T22:51:32Z")
Let’s have an issue triage hackathon on June 15, 2023. What time would you like to start in France? You could get started and then on the US side, we can join you as the workday begins in our various timezones.
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 5, 2023, 3:36am UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/7 "2023-05-05T03:36:07Z")
Perfect, I can make it, and will encourage Phil to do so also.
One question. For whomever closes bugs, should we have them mark them as “needs verification”? Get a second set of eyes on the issue? I would suggest doing so. Phil and I could take the task of verifying bugs are really fixed needed. (I believe this is what happened last time, and {groan} I ended up resolving something like 200 bugs. It was still the right thing to do, as I found a few incorrect closures).
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 15, 2023, 12:54pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/8 "2023-05-15T12:54:03Z")
> [@cory.quammen](#):
>
> What time would you like to start in France?
KEU will probably work on the hackathon during the afternoon
> should we have them mark them as “needs verification”?
I second that.
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 15, 2023, 6:44pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/9 "2023-05-15T18:44:14Z")
Phil and I will make it a priority to work on resolving “Needs Verification” issues. Second, we will work on closing old Sandia issues.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 2, 2023, 12:10pm UTC](https://discourse.paraview.org/t/paraview-hackathon/11907/10 "2023-06-02T12:10:04Z")
Details: [ParaView Issue Hackathon - June 15, 2023](https://discourse.paraview.org/t/paraview-issue-hackathon-june-15-2023/12215)