Sort
7. Improve stability
As the plugin will interact with multiple WordPress event plugins as well as multiple Fediverse
applications, an automated testing setup would greatly help in detecting interoperability issues
between our (new versions of) plugin and (new versions of) those other applications.
6. Release
The plugin will be released in the official WordPress Plugin repository at wordpress.org.
5. Release Candidate
This release should be enhanced by the evaluation process and be ready to be reviewed externally.
4. Evaluation
Using of a small diverse trial group of event organizers, the evaluation will take place whether the goals of the plugin are made clear in the documentation, whether there are hurdles in the configuration, and on whether there are sufficient and understandable FAQs and automatic feedback/help messages in the admin interface for potential/likely pitfalls.
3. Beta State
This release should include all major functionality desired and be ready to be evaluated in conjunction with real-life event organizers of different types.
2. Alpha Phase
The parts of the plugin that are easiest and most straightforward should be implemented to achieve a prototype of the plugin that makes it possible to follow/unfollow an actor on the WordPress site and send new events to followers.
1. Architecture decisions & plugin skeleton
The most major decision is whether the plugin should work stand-alone, or as a child plugin of the existing ActivityPub-Plugin followed by a technical design draft: most API endpoints and the structure of the code should be sketched.