Prepare hack.commit.push

[nipafx]

Things we need to do before hack.commit.push:

• short video introduction of the project
• link to a guide on how to create JUnit 5 extensions
• make sure the good first issue and up for grabs labels are properly applied

Things we could do:

• rename master to main ~> Evaluate to rename master branch to main #331
• update dependency on JUnit to prevent problems if updating becomes necessary during the event
• add existing extension ideas (e.g. from JUnit 5's issues) as issues

[nipafx]

Regarding the JUnit 5 version we depend on:

We usually want to depend on the lowest minor version (newest patch of that) that supports our feature set. Generally speaking, that's still the case, but the upcoming hack.commit.push event required an exception. Updating from Jupiter 5.6 to 5.7 requires some changes to our test code, which means it's a bit disruptive. In case some contributors need to update during the event, they would also need to make these changes in our test code, which would be an unnecessary burden. To preempt that, I decided to update to 5.7 now.

[Bukama]

Just to note it: We discussed the update in team call and we all were fine to update it.

[nipafx]

We should probably discuss how to best provide support during the event. I'll definitely be live-streaming my side of it, so coming to Twitch is one way to get in touch. Then there are the issues and pull requests here on GitHub that we can monitor and reply to. The question is, do we need more?

• We could offer a Jitsi room for people to come into and have a high-fidelity conversation with a maintainer.
• We could activate GitHub discussions for this project.

It might also be helpful to define one place where we expect contributors to check in occasionally in case we need to broadcast to all of them. Not sure why we'd want to do that, but it may be a good idea to at least have the option.

Other ideas or concerns regarding this?

[fbiville]

FYI, we're going to use https://workadventu.re/ (+ dedicated Slack) for the event (it may change if we face any unexpected difficulties but that's the current plan). Every group is of course free to use its own tooling.

[nipafx]

I think that will be fine, thanks @fbiville!

[nipafx]

HCP is over now, so we've obviously done everything. 😊