Day 1
We started with brainstorming and discussing the options for the project. This was more difficult than originally thought, since some members of the team had limited knowledge of some of the concepts currently in use. There were many diagrams and tonnes of flipchart pages used (see our gallery!).
We approached this project from a number of different angles. We looked at current systems that offer events and started evaluating the features that we liked about them and/or wanted in the new system. Some examples are:
- Ability (or lack thereof) to see attendee emails or subscribers of our organization/group;
- Waitlist maintenance; and
- Dashboards for both organizers and attendees.
Once we came up with these features, we filtered out anything that wasn’t “network” related versus “server” or node specific. Things like viewing events by location, for example, cannot exist without the network component.
At this point, we realized that we needed to determine the classes of users to better evaluate what our system should or shouldn’t do. We shifted to defining user stories of the various users. This included:
- An Attendee of an event or many events;
- An Organizer of an event or many events;
- An Operator of a server which can host multiple events; and
- A Developer who needs documentation on how to use the system.
The end result that we aimed for was whether we should use and enhance existing technologies or build something new. Tomorrow, we are going to break into groups to evaluate some of the existing technologies and document our findings.
Day 2
We started Day 2 by breaking up into different teams:
- Website (which you are viewing right now)
- Presentation
- Documentation
- Find Events Near Me
- Mobilizon
- User Stories
- WordPress
The website and presentation teams were working constantly throughout the day getting updates from the individual teams.
The Mobilizon team put together a setup that would make it easier for users to set up and operate their instances.
The WordPress team worked on making it easy for WordPress users, or more importantly, organizers of events that use WordPress to publish and manage their own events, to share those events to the Fediverse. The main focus for this was the ActivityPub plugin.
Originally, we had a Federation Relay Team, that pivoted to creating a working model to geolocate events in the Fediverse.
The User Stories that were identified the day before on chart paper were organized on the repository as well and categorized accordingly.
Day 3
On the third day, we continued collaborating in our working groups, building on the progress made on Day 2. Each team focused on refining their ideas, finalizing key aspects of their work, and preparing to showcase their achievements.
We created a Live Demo of “find events near me”.
At 12:00 PM, we presented our results, sharing insights, challenges, and solutions developed throughout the hackathon. It was an inspiring moment to see the collective effort and creativity that had gone into each project, highlighting the power of teamwork and innovation.
Fedivents 