Forums

I happend to be seriously interested in its faults. If they are so obvious and not being fixed I'd be interested to know what they are.

What are you talking about? Final Release? Good software continously evolves. And most bug reports are related to extensions. And everytime a bug is fixed PunBB moves one step ahead.

If you think what gets produced here as a final release will be immune to that: Very funny.

Name what is not up to the task if you can.

But why bother? And who's going to do it all the time? All the updates, revision to extensions? Why would I go to the trouble? Both are GPL but PunBB is actively putting things out like pun_attachment (v. popular) , pun_poll (pretty popular I believe) - you'd just copy that? change hooks etc? (don't forget they've got more hooks and are upgrading regularly)

If PunBB was not GPL I'd maybe understand better. But Flux 1.3 is like something being dragged along against its will

I happen to believe in what Flux stands for. But common sense seems to fly in the face of using Flux 1.3 (WHEN it even is even finally released?). Ergo: Better make PunBB 1.3 (future users of flux 2.0 if it's good) stronger for community instead of loosing everyone new to Vbulletin and PhpBB (my opinion)

PS: Not even quick quote is possible here

EDIT: As you have devs here saying: "Don't use it in production" - might as well go the whole mile and do the decent thing and give those people the best deal I reckon (i.e. pun 1.3). If the decision to not support it ongoing-basis has been made: Then proper thing is to give those people who wanted it a proper solution.

would like to see that feature on 2.0 here (extension)

It does. Alrighty then. Thanks again for effort you're all putting in.

Looking on the bright side. Thanks for clarifying. It's appreciated.

When are we expecting more color on what exactely 1.4 is improving? What features? Or Security issues? Would have liked to understand better....

RE: 1.3 - Wouldn't the proper way of deciding not to support 1.3 have been the open way for an open source forum?

Will/would 1.3 even require much support from flux side? Seems to be generating some decent interest.

I think the hassle you'll have with saying YES, we support 1.3 and the feedback and interest generated by it will by far outweigh the limbo you seem to be putting the extension system in by saying NO.

Plus I don't really like how that could happen that we have that decision without debate beforehand

If I speak to a json or ajax or xxx coder who might be willing to incorp a tool / app into flux - do you think he's going to like working in such an environment?
An environment where a fairly small group of people is deciding things behind closed doors?

I don't

Seriously: How hard can it be to get a core-dev to start
1. a blog or
2. topic (where he puts in two phrases what's going on a daily or very frequent basis)
with or without comment function. just so ALL people know what's happening?

@Lu:
What you're saying about not needing extension system is covering the needs of a VERY small coder world I think.
I'm using extensions and if you can tell me how that is negatively affecting speed or other I'll be more than interested to know!

You're just thinking of extensions.
I'm looking at the bigger picture of when people help someone code / answer etc something.

I agree that should be added ASWELL to extensions manifest.xml.

Plus I come across this issue at any forum. If someone is usefull - you may wanna show it in another way (money <- paypal).

EDIT: or take styles and mods - how to integrate it there? I reckon it's of general  interest. But time will tell.

No, not for the base. Indeed. That's why I proposed a seperate list in the prior posts.

Interest will indicate to a Ext/Mod Dev (notice I am talking about devs not on core team) where he can satisfy a high demand. If he wants to monetize that or not I'll leave out.

and if that % increased due to frequent additions - that couldn't hurt.
getting feedback and whatnot

Agree.

But what is the best way to do so? (i.e. find person willing to code it)
Judging by user/guest numbers it's probably not a given that someone picks up on a sensible wish.
Take for example that rating with stars idea.

I'd like there to be a list with description of what requirements are being set-out and making it clear that there is £ to be made if successfully completed. (and if possible to have users be able to 'second motion' it - i.e. support it, co-finance)
Now if there were a list like that, and it were clearly visible to eager coders, then I'd get my requirements fullfilled faster and probably at best price.
(always talking about MY in the sense: one would...)

That's just my tuppence worth on the matter.