clean up Flarum discuss !

KazeroG

i want to help flarum staff by bring the idea of creating a group who will really clean up the forum and help the somehow the mederator !

like puting the unworkable extension in a TRASH CAN tag !

by doing this i concluded that the installation and compatibility error will be solved by 50% like the 404 error and 500 error and more
i heard adn read that the 1.8beta will be very clean but the paradoxe of the story is why the forum is such a mix of what is happen there and i dont understand how to

lets say from now to the release of the 1.8beta lets make the forum beter place ? XD

PS: i dont want to take the place/work of staff who really good for helping people .... but juste wanna take a somehow the hard work and give them a lot of time to help in the good place !

Prosperous

It's quite comforting that you have offered to help with something like this @KazeroG and we always encourage everyone to engage as much as they can to improve not only Flarum, but its community as well.

At this time and as advised before, the next update will bring along quite a few significant changes. As discussed in the Community Update - 2017 Year in Review discussion, Toby mentions that beta.8 will basically break all extensions that have been created for Flarum to date. Based on your suggestion it would mean that all extensions would be added to this 'trash can' tag. ? We just do not have the manpower to manually test each and every extension so we leave that up to the community to provide the feedback.

I think the best way to tackle this is to leave things the way they are and give the extension creators a chance to update their extensions to work on the new update.

This will avoid an increase in admin work as we would have something else to add to our schedules. The last thing we want to be is counterproductive. Perhaps some sort of 'notify the creator' feature could be included to inform creators that their extension may be outdated? That's just me thinking out aloud. We also have Guidelines for Posting Your Extension which advises creators to keep their extensions up to date otherwise it will be added to the Abandoned tag which essentially works similar to your suggestion anyway.

Again, thanks for your enthusiasm and please do not hesitate to give us more ideas on ways that can improve our service to you and Flarum as a whole. ?

clarkwinkelmann

This makes me think...

What about adding a "beta7" subtag under "Extensions", then when beta8 is out add "beta8".

Then add those subtags to extensions. We could start by having every extension having "beta7" (or 6,5,... or none)

When an existing extension is made compatible with beta8, the developer can ask a moderator to change the tag.

On an extension discussion either keep only the most recent tag (this gives an idea of whether the extension is active or not) or leave all beta tags this extension ever supported to show history.

This could be a great way for non-tech people who don't want to go to Packagist/Flagrow and just want a rough idea of the list of active extensions.

Technically of course this could somehow be automated if you can link discussions with their packagist entries then use a script too look at the Flarum version requirement. Problem is, only a handful of extensions use the "Flagrow" standard to link discussions with Packagist so doing it by hand is probably the easiest at this point.

Instead of a trash can, this doesn't throw non-updated extensions away in a corner, this just makes it easier to find extensions for the latest Flarum while leaving a change for the others to update.

What do you think ?

luceos

clarkwinkelmann another issue is that the composer.json of most extensions mention only a lower boundary: ^0.1.0-beta.5 which makes them technically compliant with any upcoming version, including the stable 1.0.0. Flagrow.io/bazaar - as you know - is able to filter through the existing list, but that wouldn't work with simply processing the packagist list.

Ralkage

clarkwinkelmann I suggested that too not too long ago, right @luceos? ?

Super Needed Edit: To add, it would be rather tricky to keep adding secondary tags for each release the extension is compatible up to, but that's how other forum software platforms do similarly in their respective extension/modification ecosystem and community.