Reflecting on // foss.events

Verfasst von

in

While your favorite FOSS calendar continues as usual and, thanks to your help, keeps you up to date on the latest FOSS events in Europe, it’s been quiet on this blog for a while. It’s time to change that and bring you the latest news about // foss.events. After all, there’s a lot to share, and some changes are on the horizon. That’s why we’re going to revive this blog and provide you with background information and an outlook for the future of // foss.events over the next few weeks.

What to expect

To start, we’ll take a peek behind the scenes: How did it all begin? What decisions were made, what paths have we taken since then, and what milestones have we reached? Wherever possible—and where it’s of interest—we’ll also try to illustrate this story with some figures and statistics.

Following that, we want to update you on the project’s current status: Where does the project stand, and how is the community doing? What are the next planned milestones, and what changes will they bring? We’d like to take you on a journey and share our long-term vision for // foss.events. Some of these goals are realistic, others will require your support, and some are ultimately beyond our direct control.

Why

Of course, we aren’t doing this without a reason. Two major, transformative changes are on the horizon; we can already reveal that our project will be merging with another, as we share common goals and will be much better positioned by joining forces. It feels right, therefore, to capture the original spirit of // foss.events before we take this step.

We can also share that, by outlining the project’s current state and presenting a long-term vision, we are looking for new contributors. The project has grown significantly, and we are currently understaffed. So, if you can imagine getting involved with // foss.events—whether in a technical, organizational, or content-related capacity—now is the perfect time to jump in! 🙂

That’s all for today. With the next post, as mentioned, we’ll dive into the history of // foss.events.