Perhaps you misunderstood me. I did not overlook those considerations.Oleg wrote:You are overlooking a couple of important considerations
1. Most people who invest time in phpbb, be that development or support, choose to be here and not somewhere else.
2. phpbb is developed and supported by volunteers. In a company a boss can make their employees work on whatever the boss wants. This totally does not work for volunteer projects.
Each project has their strong points and their weak points. It seems that your needs are met perfectly by another board solution. This is great but mostly irrelevant to those whose needs are met better by phpbb than by other board software.
I hope you're not seriously suggesting that when two projects, companies, whatever, merge that the resulting project should be based on the most popular one at the expense of what is the best one. That does not sound like a sensible approach to me. Surely the better one should not be scrapped just because it's not as popular. Note that I'm not saying (here) that one is better than the other, just that deciding on which product should take over the other based on which is most popular seems to me to be a bad idea.Pony99CA wrote:If there's going to be a takeover/merge, why shouldn't the most popular board system take over the other? phpBB is (supposedly) the most popular and its programmers know how to write more secure code. Why doesn't myBB fold and have its programmers help phpBB implement plug-ins and an excellent migration path?
I'd be happy with either project merging (or being taken over) by the other, IF it resulted in one product that had the features of both, and more importantly, had a good responsive development cycle based on the requests of the users in a transparent manner. I can't see that happening with phpBB, but I can see it happening with myBB.After that, the myBB team can write officially-supported plug-ins (in other words, fully supported by the phpBB staff) to add the other myBB features to phpBB. Officially-supported plug-ins keep the core light, provide functions that admins can easily add while still being guaranteed to work from release to release (unlike the current MOD system). That would keep the myBB developers active, too. Your plan would have the phpBB developers potentially wander away after their tasks were complete.
two answers below ...I think that in light of the known slow progress of phpBB development, and the existence of other very good free open source forums software out there, the best thing that phpBB can do for its users is to merge with another forums project, provide a seamless migration path for the users to the other software, and to add any features in phpBB that don't already exist in that other software.
In my proposal, the other product would retain the name of that other system. phpBB would merely be responsible for making a smooth migration path from phpBB to the other system, and for implementing phpBB features that are not yet in that other system.
That is far from a simple question, as clearly there is differences of opinions. In my opinion, phpBB is the most needy. It needs a plugins system, it needs to become more responsive to user requirements. It needs to improve its development cycle. It needs the features that other forums software has (eg, warning types/values and automatica warning progressing to suspensions and/or bannings, highly configurable). But that's just my opinion.-EnYgmA- wrote:A very simple question, what is the system that needs most of the other in this story ?
I'm not sure that I understand what you're saying here. Are you saying that we should be happy with a slower development cycle, and fewer features if it results in better code (presumably for the sake of better security)?Dévellopement that long or not it should take its time to get the best possible code for our forums, others argue more speeds, yes and ?
That's not a plugin system. That's a modification system. The two things are hardly comparable.-EnYgmA- wrote:For the plugin system => AutoMod
Although it is not perfect
Sounds like a trick question. So that users requirements are met closer to when they want them, and they don't have to wait several years for new features. I thought that would be fairly obvious.Why phpBB should go faster ?
Not sure what you mean.For what other scripts have functions already presents ?
Not at all. And I don't think anybody suggested such a thing.Is it really important to follow the others ?
WHEN. It's been a long time in the making, but apparently it's going to be real soon now. Great.The plugin system is a native of phpBB when his time comes
Seriously?!Why would not NOT want to close phpBB and tell the users to go somewhere else?
what is the difference between a plugin and a mod ?Son of a Beach wrote:That's not a plugin system. That's a modification system. The two things are hardly comparable.-EnYgmA- wrote:For the plugin system => AutoMod
Although it is not perfect
The phpBB developers do take security seriously AFAIK, but I don't think they were ever obsessive about it. Security is something I consider very important though. Security bugs can make a piece of software unpopular very quickly. IMO phpBB3's security is one of the reasons it is so successful. Unfortunately, at least according to various events and mentions on the phpBB blog, phpBB still suffers from the not-as-good security record of phpBB2.Son of a Beach wrote:PS. Top notch security is a great goal worth pursuing. But it should not come at the expense of all else. Eventually there's got to be some compromise where people say that the value of that high security does not outweigh the value of this, that, or the other (whatever else may be of value to them). For me, that line has been reached. The most secure system is one that nobody can access, and is therefore useless. Anything else is a compromise, it's just a matter of how much compromise is acceptable.
Plugins don't require code edits, MODs do.-EnYgmA- wrote:what is the difference between a plugin and a mod ?
Yes, seriously. (and you've quoted me out of context pretty badly). A car company exists to make money. If a care company shuts down, they no longer make money. I'm surprised anybody would think that was a reasonable analogy.callumacrae wrote:Seriously?!Why would not NOT want to close phpBB and tell the users to go somewhere else?
Why would car company X NOT want to shut down and tell their users to go somewhere else?
There are thousands upon thousands of perfectly happy phpBB users. Sure, there are the odd few that want every feature in the world adding (which does make a massive difference, by the way, and I have worked for a hosting company before so I think I'm qualified to say what hits the servers hardest), and ten there are a few more with some valid points (like the need of an events system, which I being added). Unfortunately, phpBB only has limited resources. Suggesting that phpBB shut down to remedy that is a bit of a silly idea, though.
I'm also surprised at this question. The difference is HUGE. A plugin is modular. It doesn't affect the code of any core components. A mod(ification) by definition does modify core components, and is not at all modular (NB: 'mod' in phpBB is modification... in some other systems a 'mod' means a module which is the same as a plugin).-EnYgmA- wrote:what is the difference between a plugin and a mod ?Son of a Beach wrote:That's not a plugin system. That's a modification system. The two things are hardly comparable.-EnYgmA- wrote:For the plugin system => AutoMod
Although it is not perfect