Menu
▾
▴
|
From: <joo...@bt...> - 2003-01-14 14:05:01
|
First of all - I *really* like phpWebSite. I highly appreciate the effort and dedication of all involved. Above all, the concept is great. Also, it's the university's project, and I respect their right to take the project forward in whichever way they see fit. I would like to express some concerns, though. For several months I have been following the development of phpWebsite. When I asked back in September/October (don't remember exactly) when it would be ready The reply was <<whenever there are no more bugs>> which seemed fair enough. I started to test the RC's as I would with an RC of any other piece of software. To my surprise, I have seen complete rewrites of large parts of phpWebSite between RC's -another major rewrite announced a few days ago - it seems there is no intention to actually go in <release mode> - just fix bugs and create a stable version - not add functionality for a while. In my experience, when you don't do a feature freeze you will add each week the same amount of bugs as you are solving - and there will never be a release. For me the moment of truth is near for phpWebSite - I have to make a decision this week. My options are: 1. Wait without an idea of a release date. You can see the difficulty of that. 2. Take RC3, fix a few bugs, and go with that. It will certainly work but I will find myself on a 'mod island' - my mod's won't work for anyone else, and I cannot share my mods with anyone. 3. Go for some other CMS. I had a quick look at some others already. None has the modular structure done properly like you guys have. Again I am really appreciating the effort and I am in no way trying to upset you (please don't be!) but I am facing a real challenge here and I thought the right thing for me to do was to raise the issue rather than silently create a fork or bail out altogether. That would be so sad. Any thoughts or advise would be helpful. Thanks! Joost |
|
From: Don S. <do...@se...> - 2003-01-14 15:43:52
|
This is pretty much the sentiment I was trying to carry in my earlier email. I have no intention of going to another CMS, but I do need a doc management system and I sold my boss on PageMaster. Obviously now I have to play the waiting game. I hate to appear ungrateful since you guys are doing all the work, and a lot of the changes are for the better. From a software development point-of-view, just wondering if we'll see a feature freeze and only go into bug-fix mode. It would probably allow us to find bugs more reliably if new features weren't coming in every day (as Joost said). My 2 cents, Don. On Tue, 14 Jan 2003 joo...@bt... wrote: > First of all - I *really* like phpWebSite. I highly appreciate the effort and dedication of all involved. Above all, the concept is great. > Also, it's the university's project, and I respect their right to take the project forward in whichever way they see fit. > > I would like to express some concerns, though. > > For several months I have been following the development of phpWebsite. When I asked back in September/October (don't remember exactly) when it would be ready The reply was <<whenever there are no more bugs>> which seemed fair enough. > > I started to test the RC's as I would with an RC of any other piece of software. > > To my surprise, I have seen complete rewrites of large parts of phpWebSite between RC's -another major rewrite announced a few days ago - it seems there is no intention to actually go in <release mode> - just fix bugs and create a stable version - > not add functionality for a while. In my experience, when you don't do a feature freeze you will add each week the same amount of bugs as you are solving - and there will never be a release. > > For me the moment of truth is near for phpWebSite - I have to make a decision this week. My options are: > 1. Wait without an idea of a release date. You can see the difficulty of that. > 2. Take RC3, fix a few bugs, and go with that. It will certainly work but I will find myself on a 'mod island' - my mod's won't work for anyone else, and I cannot share my mods with anyone. > 3. Go for some other CMS. I had a quick look at some others already. None has the modular structure done properly like you guys have. > > Again I am really appreciating the effort and I am in no way trying to upset you (please don't be!) but I am facing a real challenge here and I thought the right thing for me to do was to raise the issue rather than silently create a fork or bail out altogether. That would be so sad. > > > Any thoughts or advise would be helpful. > > > Thanks! > > Joost > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
|
From: Matthew M. <ma...@tu...> - 2003-01-14 15:57:23
|
Joost, Much of the rewriting is done because once we say it is a FINAL release, we are severely limited in what we can change. In all cases it was warranted. For example, layout needed restructuring. It has been the same code for over a year. I have learned a lot since then and I want to apply that to the code. It was missing key components and the interface was sloppy. The location change for the layout.php file was something approved by the developers. As for approval, it had bugs and was kludgey. The new format doesn't require registration and should be easier to manage. Other than that, I would say we are very close to a final release. However, until we release the final code, I would not recommend those with tight deadlines to depend upon its delivery. I don't with to discourage you however. Remember that for every change, I have alter all my modules as well. So far, none have been very time consuming. Best regards, Matt ---- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
