From: Todd O. <to...@da...> - 2001-04-30 23:27:20
|
I've been quiet the last few days because I am a principal with IMEC Engineers, an environmental engineering firm. At the request of a local county, we took air samples and tested surface wipes at a local high school of 1200 students. To make a long story short, the superintendent closed the school the day after we gave him the test results, which was last Thursday. Needless to say, the news coverage, angry parents and press conferences have kept me pretty busy. You can read for yourselves (and watch some RealVideo too): http://www.wsls.com http://www.wset.com http://www.wdbj7.com/scripts/heads.htm Anyway, I did get the ear of Bedford County's technology director (who had to run sound for the press conferences). He is really excited about using phpWebSite/2 throughout the county, when it is completed. I am preparing several installments of my phpWS/2 master plan, which I will start releasing tonight or tomorrow. I've collected the input from posts to this group, posts to the sourceforge forums and telephone conversations with others, as well as reviewed MANY other open source packages. I am committed to make phpWS/2 an enterprise level product that is easy to use (not an easy task). I've missed many hours of sleep working on a plan to get the rewrite up and running to keep everyone moving forward. Therefore, I will be presenting specific design proposals for your review. If you have strong objections to a particular point, please raise them here; otherwise, they'll be part of the core. If you haven't already read Brian Brown's phpWebSite/2 Roadmap, please do so now (it's in the list archives). Once these specific design features are decided, I will provide pseudo code, rough class definitions, module API details and db schemas for everyone's review. Once this is OK'd, I believe phpWS/2 will reach critical mass and another freshmeat announcement should be made. I trust other developers will see the master plan and want to join the project. The core coding will then begin simultaneously with some of Jason's module work, since the API will be firm at that point. --Todd Owen |