Today’s meeting was about the current state of things regarding all existing Pluginkollektiv plugins.
Development on Antispam Bee and Statify reached a standstill over the last few months.

Attending: Florian Brinkmann, Bernhard Kau, Matze Kittsteiner, Justin Kostka, Dennis Ploetner, Stefan Kalscheuer, Andreas Spoo, Matthias Pfefferle, Thomas Brühl, Simon Kraft

Short term measures
We have volunteers for our three big plugins – Antispam Bee, Statify, and Cachify.
For Antispam Bee, Florian will give an introduction to the current state of development of the v3 alpha. Matze, Matthias, and Bernhard will help with outstanding changes to help the plugin enter a beta phase.
I (Simon 🙋‍♂️) will start polls for both the intro meeting and our new timeslot for our weekly.

Statify lacks some features and a clear, consistent vision. A team around Stefan will sort out the different – and in some places conflicting – open issues and ideas for Statify.
We’ll also be opening a poll to find a time slot for this kick-off.

Cachify was agreed to remain a helpful tool worth keeping in our portfolio. Version 2.4 seems achievable, but similar to Antispam Bee and Statify, we must define a roadmap to align features and further development.

Long term measures
Bernhard suggested planning for the depreciation of our other plugins in multiple stages and with enough time for users to move to other plugins (or maybe adopt one of ours).

The topic of fundraising to pay contributors received mixed feedback during the call. Some see benefits in bringing the (volunteer) work on Pluginkollektiv projects to the same level as paid projects, while others doubt that this would impact their personal choices.

We can use this p2 to keep some meeting minutes, document internal processes (eg. how to release a new plugin update or member onboarding). All things pluginkollektiv, without a proper place in GitHub issues or our plugin documentations be put right here. ✨