Dev Diary: Beta 14

luceos

Hari I understand everyone's hopes to see their personal favorite features added to stable. We've also made a decision to underpromise and overdeliver.

No new features will be added to core before stable, because we need to focus on stabilizing the extension api. This will reduce the likelihood of extensions breaking on new releases after stable.

Our goal is to create an extensible forum framework allowing extensions to shape it to your every need.

That your features are possible with an extension is very likely, so do keep an eye out for that.

Turgut

We call it only a forum, but the features are not over.

luceos

For those of you who missed it, last weekend I decided to step down from being an active core developer in order to focus completely on leading Flarum to its future.

luceos I have stepped down as active core contributor to focus on my other duties in the project. For a while I haven't been able to live up to my own expectations of the core position.

The new badge has replaced a badge which holds significant meaning and well deserved respect. Especially to me, I literally pursued the position for a very long time. But it's time to take charge of the flarum future as my sole responsibility instead. Something I have been doing since the foundation adopted the software, but with stable on our irises, it's now an even more pressing priority.

samus14

luceos Excellent!

luceos

It's time for an update.

🤓 What I did:

For the past few weeks I've been working on a redo of our flarum.org website. Something that I'm hoping we can deploy somewhere before the stable release. The day before yesterday I moved the docs out of our main domain (flarum.org/docs) to its own subdomain (https://docs.flarum.org) to improve SEO of our main domain on non technical terminology and to prepare for the new website by simplifying the deployment script.
With more time on my hands I've been looking at our strategic positioning again. So that we're not completely unprepared for whatever hits us around and after stable.
Respond to inquiries from differently sized companies, including a multi billion enterprise from Australia. Interest in Flarum is increasing, that much is clear 👏 !

🖥️ About development:

The core team has been extremely active. A great pace has been set by the core team to rewrite the frontend. It requires a lot of discussion; pull requests are openly and privately scrutinized in order to achieve the best results.

I do think, seeing how much work is still left ahead of us, that our targeted deadline of August might need to be pushed back slightly in order to get to a stable and reliable fourteenth beta. In addition we'd hate to break extensions twice in rapid succession. I know this is disappointing, seeing that beta 14 already was given one month of extra time. Sometimes we need to lose a battle to win the war. In software development you sometimes have to sacrifice delivery times, to guarantee the best product. Especially because we know you love Flarum, therefor to us the only viable release is a great one!

At the end of this week, we'll know for sure whether delaying beta 14 to September is necessary.

We will keep you up to date about any news related to our project and beta 14 specifically. Thanks for your patience and understanding.

luceos

luceos Sometimes we need to lose a battle to win the war.

With quite some regret but with increased determination we've decide to postpone the release of 0.1.0-beta.14 with one month. We hope on your support in our challenges towards stable, thanks for your understanding.

neptronix

Awesome to hear, Keep up the great work, guys!

MikeJones

luceos no worries, keep up the great work!

luceos

One of the ways to guarantee stable is by paying for 👨‍💻 developer time. @Franz has been investing every Friday since January in propelling our releases forward 🚀. Sadly we've seen a few of our GitHub sponsors withdraw their pledge and as such this arrangement is at risk 😞.

🙏 Please help us, by pitching in! Every small donation supports our goal in delivering awesome, free community software.

Ping here or privately if you pledged and haven't received a forum badge automagically.

Wadera

luceos Ping here or privately if you pledged and haven't received a forum badge automagically.

How it working? Match by username? Or e-mail? How long it usually take to get it working?

mekici

Hello luceos . I am happy to sponsor Flarum Github. Github username is flarumtr.

Flarum Turkey Community

Wadera

Which one is preferred (less fee or something)? GitHub or Open Collective?

luceos

Wadera GitHub pays for the transaction costs, so that one returns the best net result for us. Open Collective is more transparent in where funds come from and go to.

luceos

Wadera it ought to match on email address. Let me verify the cron runs.

Edit: Seems they were disabled, they are now running hourly.

luceos

Wadera your mail address on github is not public, so the api won't share it with us. I've handed out the badge manually 👍️

tankerkiller125

It's been awhile since I've given any updates, I've been pretty busy with work and life, however I have done the following:

Started a topic about UTF-8 (non-english) support for community feedback
Started brainstorming solutions to the challenges UTF-8 presents flarum/core2230

I intend to start working on the solution here in the coming days once I summarize the community feedback, It's important to note however that this feature will NOT make it to Beta 14, but I do intend to have it ready before stable. Our international communities are just as important as our English speaking ones and hopefully this will help close the gap in terms of long standing UTF-8 issues.

luceos

mekici thank you 🥳

photonics

Is it possible to support svelte framework in extension parts? I am familiar with React, and need to use Svelte in the next project. According to the trends, Svelte is very possible the mainstream front end framework in near future. I mean it is good bet to let Flarum support both Mithril and Svelte for the extension parts.

luceos

photonics we decided to stick with mithril after careful deliberation. So don't expect support for a framework that we do not use. However, mithril and svelte - in the end - both generate to raw javascript. So there might be a way to generate Svelte code that compiles to JS that interacts with our frontend; I think one of the other core developers might provide a better answer to that (cc @datitisev).

matteocontrini

photonics Svelte is very possible the mainstream front end framework in near future

Until the next one... 😄

datitisev

luceos I'm not sure, but Svelte might not create a virtual DOM like mithril Ford - and even if It did, it'd probably be structured differently (diff API).

You could perhaps try using svelte and custom HTML elements? Not sure if that'd work, but raw HTML is possible with mithril m.trust(...) and I use custom web elements in reflar/inject-mithril-components (or a similar repo name, I can't remember).

« Previous Page Next Page »