# ParaView hackathon Wednesday, May 6.
**URL:** https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172
**Category:** Announcements
**Created:** [April 24, 2020, 10:30am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172 "2020-04-24T10:30:58Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 24, 2020, 10:30am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/1 "2020-04-24T10:30:58Z")
Kitware will be holding a ParaView hackathon on Wednesday, may 6, from 8am EST (2pm GMT+2) to late.
It is open to anyone willing to contribute, with or without coding skills.
Here are the objectives of this hackathon :
- Cleaning up any warnings or issues on the dashboards.
- Fix simple outstanding issues.
- Implement simple life-improving features.
- Do a pass on the issues to close all the old ones that should be closed.
- Do a pass on open merge request in order to finish some up and close others.
This hackathon will, of course, be only virtual.
A Google Meet meeting will be accessible here [https://meet.google.com/axt-xjak-anw](https://meet.google.com/axt-xjak-anw).
It will NOT be used for extensive communications and discussions, but only for short questions, greetings and cheering up 🙂
A slack channel will also be accessible, technical questions and discussions will surely take places there : [Slack](https://app.slack.com/client/T0128R76PD5/C012VNKKYVA)
If you are not a kitwarean, please make sure to send me a private message here or a mail at [mathieu.westphal@kitware.com](mailto:mathieu.westphal@kitware.com) to be able to gain access.
If you are a kitwarean, please make sure to accept the event you have been invited to, you will then be invited to the slack.
Before the hackathon, Issues and MRs will be tagged with the `hackathon` tag.
It means they have been identified to be addressable in some forms during the hackthon.
- [Issues](https://gitlab.kitware.com/paraview/paraview/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=triage%3Ahackathon)
- [Merge Requests](https://gitlab.kitware.com/paraview/paraview/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=triage%3Ahackathon)
Certain issues will also have been tagged with the `needs-testing` tag.
It means these issues should be tested to see if they can still be reproduced or can be closed.
Once tested, they may or may not be fixed during the hackathon.
[Those issues](https://gitlab.kitware.com/paraview/paraview/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=triage%3Ahackathon&label_name%5B%5D=triage%3A%20needs-testing)
Certain issues will also have been tagged with the `documentation` tag.
These types of issues generally do not require any kind of Programming knowledge.
[Those issues](https://gitlab.kitware.com/paraview/paraview/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=triage%3Ahackathon&label_name%5B%5D=area%3Adoc)
Certain issues will also have been tagged with the `easy` tag.
It means these issues would be perfect for a ParaView beginner to try and fix them.
[Those issues](https://gitlab.kitware.com/paraview/paraview/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=triage%3Ahackathon&label_name%5B%5D=triage%3Aeasy)
When taking over an issue or a merge request, make sure to assign it to yourself or to ask myself (@mwestphal on gitlab) to assign it to you. Please mention it also on the slack channel to make sure a single issue is not being worked on by multiple person.
When closing an issue, either by a fix or because issue is not present anymore, make sure to add the `needs-verifications` tag and to remove the `needs-testing` tag.
Please make sure to read our [develop guide](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/git/develop.md)
Q&A :
> I want to contribute but I’m only a ParaView user and I’d rather not use git.
You can absolutely contribute by testing the issues with the `needs-testing` tag, see above.
> I want to contribute and I know how to use git, but am not a programmer.
You can absolutely contribute by improving ParaView documentation, see above.
> I want to contribute and am a Programmer, but never touched ParaView code before.
This hackathon is the perfect time to start ! You may want to try to fix an `easy` tagged issue.
> I have an idea for a feature for ParaView !
Awesome ! Keep in mind that this feature should requires only a small amount of work to be able to be finished in the scope of the hackathon. If that is not the case, that’s okay as well, this hackathon can be just a good way to start working on it. Make sure to create an issue and tag it as `hackathon` and `feature`.
> I don’t know what to do, how to merge, what is the next step, unsure about anything.
Either tag me in the slack or on gitlab 🙂.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 24, 2020, 10:42am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/3 "2020-04-24T10:42:58Z")
_Poll ([view on site](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/3))_
This vote will stay up until Monday, April 27. Be sure to vote quickly.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 28, 2020, 5:07am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/4 "2020-04-28T05:07:44Z")
The date of Wednesday, May 6 was chosen.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 28, 2020, 7:12am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/5 "2020-04-28T07:12:02Z")
The post have been updated.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 29, 2020, 2:34am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/6 "2020-04-29T02:34:47Z")
The post have been updated and is now complete.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 5, 2020, 1:27am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/7 "2020-05-05T01:27:35Z")
Invitation to the slack has been sent. Please contact me if you have not receive yours.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 6, 2020, 9:48am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/8 "2020-05-06T09:48:19Z")
All issues and merge request have been tagged. Feel free to tag other issues if any seems fitting.
Of course, all these issues will not be addressed in a single hackathon.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 6, 2020, 12:19pm UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/9 "2020-05-06T12:19:59Z")
The hackathon is starting !
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 7, 2020, 3:05am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/10 "2020-05-07T03:05:56Z")
The hackathon is over, thanks to all the participants !
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 2, 2020, 2:57am UTC](https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172/11 "2020-06-02T02:57:34Z")
A blog about the hackathon was published !
> **[ParaView Hackathon still happening ! Last one was on may 6. - Kitware Blog](https://blog.kitware.com/paraview-hackathon-still-happening-last-one-was-on-may-6/)**
>
> On Wednesday May 6, Kitware organized an (online only) ParaView Hackathon. It was open to anyone, Kitwarean or not, programmer or not.