Forums

I don't think 2.0 is going to be finished in several years: I would be surprised if it took more than one year to write. I think once 1.4 is tested and released, planning for 2.0 can start in earnest. I think there are more people "on the team" working to plan and develop the software than ever before. I think having a clear roadmap beforehand will lead to better written software that is finished more quickly.

It is a release [1.4] meant to fill a void that formed when all the development efforts focused around 1.3, while 1.2 was left neglected for no good reason.

...don't assume because they are official PunBB extensions that they are secure or good quality code

I am also disappointed that FluxBB is still not ready. I don't think the problem is that the development is too slow, or that there isn't enough work being done, or anything like that. I think the project bit off more than it could chew when it decided on making huge changes this late in the game. We've had two beta releases, and a beta release is supposed to be of a virtually finished product. So to decide to go back and completely rework elements of the project after it was in Beta 2, so close to being finished, was a big mistake. Large modifications could have been saved for 1.4.

Yes, FluxBB is a free project put together by volunteer effort, and the developers can do anything they want. But the longer it takes, the less useful it becomes. By developing it in the public eye, having this discussion forum, having a downloadable Beta, and saying that there isn't much work left, you are stringing along potential users--and what is the point of that if it's going to be an eternity before a real release? And tossing around the "it will be done when it's done so don't ask" line only alienates people.  If you keep going down this road, you will have no users, and all of the effort put into this will have been wasted.

I think the project needs a real leader to stand up, make decisions, and keep the project going...kind of like what Rickard was to the PunBB 1.2 branch.

I think they have decided giving up the compatibility between FluxBB & PunBB. They've also waited for FluxBB for long time.

THIS makes me sad

In any case, thank you for developing an alternative to the commercial PunBB.

Even if we did want to do this, I'm not sure we can just agree to it and it be OK under GPL

also PunBB is still taking code from FluxBB, so I don't see how we can agree to let PunBB do that in the future as we don't know what is going to happen.

Also this isn't something for the community to decide, the copyright is nothing to do with the community.

This should be emailed to the dev team really as its not a community discussion really

Just curious. Is there a specific reason why the avatar code still loops through checking for several filetypes on disk and generating the code if found rather than just entering the complete img tag in the user db when the avatar is uploaded? It's always struck me as a tad weird doing file_exists, getimagesize and such several times when the info could be pulled directly from the db during existing queries, negating the need for all the extra checks. Plus, the filemtime cache setup thing wouldn't be needed due to being able to generate a time prefix or suchlike for the image when it is uploaded.

I've always thought the first partly because of pruning but also because somebody could come up with a way of archiving old posts possibly as an extension. You cold of course change the labels to "Total posts made: 1000" and "Posts found available to view: 900" to avoid confusion.

Literally 99.9% of users would prefer more concise error messages than a single ambiguous one.

the page should explain that the topic (post, etc.) he tried to access is private and he is not authorized to read it