Staff Diary: v2.0 Cycle
serdo you can find this information over in the docs, see: https://docs.flarum.org/install#installing
If you use any of the archives, the extension manager will be installed by default.
- Edited
luceos https://nightly.flarum.site now runs 2.x
Currently offline, Sire.
What about multi-language Tags officialy?
HasanMerkit What do you mean? Please elaborate.
European Union to abolish NGI funds
Flarum 2.0 is funded entirely by a grant organized through NLnet; feel free to read about that history here.
@SychO, @IanM and myself have been able to dedicate our time to building the next version of our community software while being compensated through this grant. The European Union is now no longer interested in funding open source. For an institute that should have all our interests clear as day, we seem to head into the direction of unsustainable open source projects. In the meantime the xkcd meme is only gaining in importance with countless projects facing maintainer burnout, financial burden, or other various reasons causing massive issues around the globe:
- log4j 2021: https://www.ncsc.gov.uk/information/log4j-vulnerability-what-everyone-needs-to-know
- colors.js and faker.js 2022: https://www.theverge.com/2022/1/9/22874949/developer-corrupts-open-source-libraries-projects-affected
- xz 2024: https://en.wikipedia.org/wiki/XZ_Utils_backdoor
And these are the projects we are aware of. Supply chain attacks are more common than ever, the bigger the project, the weightier the burden of maintenance and doubling when actually progressively developing for the future.
Please, I ask all of you to stand with us to prevent open source projects from losing a fundamental investment to the benefit of the project and maintainers' health.
Share with us, speak up and help us
Ref: https://kde.org/announcements/2024_ngi_openletter/
PS I will be signing the letter on behalf of our project.
Hello ,
Apologies for the late update, the current task/milestone that I have been working on is the most time consuming one (though perhaps the most fun).
Since the last update, we have merged the following changes:
- The JSON:API refactor (references to old posts: https://discuss.flarum.org/d/32901-staff-diary-v20-cycle/122, https://discuss.flarum.org/d/32901-staff-diary-v20-cycle/111).
- Support for PgSQL and SQLite (references to old posts: https://discuss.flarum.org/d/32901-staff-diary-v20-cycle/149).
- More reliance on Vanilla CSS which allows for more flexible Dark/Light mode changes (including per-user preference). In addition to new high contrast Dark/Light modes: flarum/framework3996.
I am currently working on a CLI tool that will enormously help extension developers upgrade their extensions to be compatible with Flarum 2.0, here is a sneak peak on how that works:
Till the next update.
An amazing contribution to the community, there isn't always enough free time to update extensions to keep the code up to date, and once Flarum 2.0 is released, a lot of work will be needed overall to be able to maintain the working ecosystem and the great collection of extensions that are currently available. Thanks!
Just saying: I heard Switzerland plans to use Open Source for their government platforms. I wonder if any money is to be found from them somehow.
- Edited
Hey everyone!
Following up on my previous update (https://discuss.flarum.org/d/32901-staff-diary-v20-cycle/115), I'm excited to share two new features that will be part of the Flarum 2.0 release. These additions weren't part of our initial roadmap, but we believe they'll add significant value to your Flarum experience.
Managing an ever-growing list of extensions can be a bit challenging. To make navigation easier, we're introducing a redesigned admin search.
While we already have an admin search feature, its current functionality is quite limited, allowing only for extension searches. We're enhancing it to be much more comprehensive and extendable, making it a more powerful tool for Flarum administrators.
You can review the design proposal and join the conversation here!
Private messaging has been one of the most requested features, as highlighted in various discussions over the years and a recent community proposal (https://discuss.flarum.org/d/30933-who-could-fix-pm-for-flarum). We're pleased to announce that it will be included in Flarum 2.0.
This feature will streamline communication within the community and help in keeping private messages and private discussions (FoF Byōbu) distinct, which should facilitate message migrations to Flarum (from another software).
Here's what you can expect from the initial implementation:
- A dedicated /messages page
- A new button in the header-secondary for message notifications
- User-to-user messaging
- A "Send message" button in the UserCard/UserHero dropdown
- Message/conversation info
- User settings for notifications and privacy options (like "Prevent users from messaging me")
While this initial rollout covers the basics, there are plenty of opportunities for future enhancements, such as group messaging. These could be added through community proposals or future updates.
You can review the design proposal and join the discussion here!
I look forward to hearing your thoughts on these new features. I hope you're as excited about them as I am
See you around!
Wow, I really didn't think y'all would be bringing a messaging system any time soon, that drives the value of Flarum so much higher. Can't wait!
- Edited
Darkle Wow, very nice, thank you for your work!
Now only 2 features (or rather, the lack of them) prevent me from moving all my forums to Flarum from other software:
- Lack of official built-in WYSIWYG,
- Lack of official built-in attachment uploading.
Once these two are implemented, I'll finally be able to move to Flarum and start recommending it to other community owners.
Curious: When is V2.0 expected to be released?