55
Quote:
phppp wrote:
Quote:
Vahrokh wrote:
About WF-Section
In easier words: WF-Section needs at one dedicated guy just for maintaining itself, which is a no go for busy people like the XOOPS Devs.
I had been the lead developer of wfsection sincehttp://www.wf-projects.com was established.
For wfsection 2.x series, I felt that it would take too much effort for me considering its codebase and my knowledge on it so after the wfsection 2.05(I even did not remember whether it was released or not) I left it to other developers.
Since then I had been working on wfsection 3, which is re-designed from ground.
I have to say that management is much more important to a large project than expected, WF-projects is yet another example.
I am glad to see that Mr catzwolf has been back to wf-projects and he asked the developers to leave so that he will take over wf modules, again.
I ever said "catzwolf was not willing to leave XOOPS". Actually it is not the first time for him to come back to wfprojects since he left wfsection.xoops2.com and wf-projects.com was then established by Bender and other wf guys.
Anyway, wf projects will move on and the modules labelled with "WF" that we are working on are also progressing.
The article management, which I have been worked on for 6 months almost as full time and was planned to be released as wfsection 3, now is for internal test.
And a stable (former) WFsection 2.08 will be released by a former WFsection developer with a new name, in early June.
phppp -
As I hope you know, I have the utmost respect for you. You have always replied to my inquires to your modules and assited when I posted issues to you.
I wish others here would learn from you example, but thats not here nor there right now.
I hope you understand why I and many others are fustrated right now. Honestly, I dont care about this new version or that fork of wf-sections. I would be COMPLEATLY happy with just a patch to fix the currect public version or a upgrade script to go to the newer beta.
I am NOT voicing concern about the delay in the new version(s). Frankly, I couldnt give a rats fat arse about them. For my needs the current version is fine IF a patch was issued to just correct the major outstanding bugs/security problems.
As a former developer, last I knew you fixed the currect code before you moved on to the next version. You did not leave your customer base hanging. Perhaps things have changed since I was in s/w development... *shrugs*
None the less, I hope you can see where my fustration is coming from on this topic.
