An important part of hackathon participation, much like GitHub's "Hacktoberfest" or soliciting an intern, is to prepare a coherent project scope for folks to participate in a constructive way. Otherwise, it can cause much miscommunication that is a net detriment. I'm personally not ready, at this time, to provide that level of guidance to multiple developers attempting to make small-but-intense contributions to the project, but that is the ultimate goal of the documentation and structure I've been working on as I have time.

Could we define a few not too large contributions we could provide guidance for?

I'd love to make this work, but I agree we need serious coordination up front. I have unfortunately limited time and experience with this, but if you think we can do it, let's do it :)

Some ideas:

*  Fediverse integration: https://github.com/agorakit/agorakit/issues/271

* accessibility: an interesting challenge, but we have to make sure it is solvable, therefore we have to solve it first, I fear!

* documentation

* some of the features here https://app.agorakit.org/groups/2014/discussions/18470 : maybe maps?

In any case, we need some well-enclosed, independant task or group of tasks. The sessions have limited time. Which also means that we must make ourselves available, also, for a limited time, ~ 20 hours, hence something like 2-3 days.

I think it would be a big service to simply use PHPStan to do static analysis and submit fixes based on it as they increase the levels. That's tiny scope, can be bounded to any time box, and doesn't require aligning with project vision or studying how it works.