Perfectly on schedule, yesterday our QA team started testing the upcoming beta 16 release. @katos @Ralkage @Deebug and @IanM have since already completed over half of the testing tasks!

Since most of our open issues for stable have been completed in this release we are hoping to tag the release as 0.1.0-rc.1 meaning this will be a release candidate!

If all goes well, by the end of next week we will be shipping this new version 🚀

Feel free to give this new version a spin on https://nightly.flarum.site (running php 8).

One thing that might hurt is that making Flarum compatible with PHP 8 made us drop support for PHP 7.2. So if you can upgrade your PHP version to at least 7.3 (7.4 preferred) right away; the current Flarum version is compatible with that and so is RC 1.

    luceos is there anything special that was introduced with PHP 8? I mean, is upgrading mostly painless or is there the risk that some extensions break?

        We are looking for someone to join our staff team in the role of Assistant Verified Community Coordinator. Currently @Kyrne and I work with our Verified Community Leaders to onboard them, help them and see whether they still adhere to their agreement. With the increasing number of these wonderful communities to be part of our ecosystem and both our responsibilities it would be great having someone assist us.

        What would you do?

        • Keep in touch with each Community Leader, pinging them on occasion on how things are going. Building a relationship and gathering feedback for our own community, but also for our product.
        • Do a periodic screening of each community to look for any breach of agreement (sounds sad but it's a matter of principle not necessity).
        • Report back to Charlie and the Foundation Board about anything that we should now about.
        • Onboard new Verified Communities, including preparing the Agreement (template with a couple of fields).
        • Help us further increase the value of these communities in our ecosystem, for instance by writing about them, by offering more (ideas for) tooling etc.

        What I think is required?

        • A friendly nature, even in tense situations you have to keep your cool.
        • Excellent communication skills in at least English.
        • Availability, let's roughly say half an hour every day (meaning regular involvement is necessary).

        Feel free to ping me on Discord luceos#0001.

        Just so that this is clear: this is non-paid position, like everyone else in the Flarum organisation (including the board).

        Reading from the current progress and everything being said, plus the new job posting... Is Flarum moving into a paid product in the future? It sounds like that is the path you are aiming for.

          ICANN Absolutely not. Being free and completely open source is an important part of Flarum's mission: the official entity backing us is a foundation, not a for-profit company. The core product is, and will always be, free and open source.

          The "verified community" program (described on our site) is designed to provide non-english-speaking communities for Flarum users and developers. Note that one of the requirements is not being able to sell commercial products as the community.

          The recent progress and momentum is the result of a LOT of procedural changes (described here) and many, many hours of volunteer work put in by our amazing team, contributors, extension developers, and ecosystem. (on an quick tangent, we could always be going faster! If you, whoever is reading this at the moment, has development experience/interest and is interested in contributing, we have a list of good first issues and documentation on how to get started)

          I will note that one of our goals is to increase commercial activity around Flarum by unaffiliated entities. More and larger groups using Flarum means more money in the ecosystem for paid services / support / products, means more developers and contributors to Flarum. That in turn results in more extensions, faster core development, and better long-term stability. This includes:

          Among others. Note that none of these are "official" or formally tied to the Flarum Foundation, and all of these are products and services around Flarum, not anything to do with core itself.

            Looks like the team did a ton of preparation for the release 😍

            So, I'm currently going over our release checklist to get everything in order, because it is release week for beta 16.

              • [deleted]

              • Post #80

              luceos Will there be any extension breaking changes for Beta 16 ? I expect this to be the case, but though I'd ask 🙂

              Thanks