Menu
▾
▴
Re: [phpesp-dev] updated version
|
From: Bishop B. <ph...@id...> - 2008-04-21 15:02:01
|
Quoting Matthew Gregg <mat...@gm...>: > Joel may be correct with projects the size of mozilla, but I'm not so > sure with something as small as ESP. Especially since I would hope a > great deal of what is currently custom in the code-base would be > provided out of the box in most modern frameworks. To an outsider (me), phpESP looks pretty big, though that is probably a mirage: I have had no problem digging into it, nor have I encountered any feelings of "how deep does this rabbit hole go?" I also don't know how many people/organizations use phpESP, so I'm not sure what kind of upgrade resistance the community would offer. When you say "framework," what do you mean? When I hear "a great deal of what is currently custom ... would be provided .. in [a] modern framework", that makes me think that phpESP wouldn't add much value over the framework. > As for as a space for collaboration. I can enable the wiki on the > Sourceforge site or drop an instance of Trac on our hosting service. > > IRC is available here: irc://irc.freenode.net/phpesp/ > Or if you would rather have a Jabber/XMPP conference room I can have > that available in a few seconds. I would think we'd want a wiki (or static repository of some kind), to keep the documentation around for a longer period than afforded by communication groups. bishop > On Sun, 2008-04-20 at 19:38 -0400, Bishop Bettini wrote: >> While I agree the code is horrendous in many places, I caution against >> a wholesale rewrite, for the reasons Joel gives here: >> http://www.joelonsoftware.com/articles/fog0000000069.html >> >> But, if that is the tack taken for v3, we should define the >> requirements, write the functional specification, identify re-use and >> re-factor candidates, decide on the platform tools, draw the road map, >> and declare milestones. In other words, do it right and try not to >> make the same mistakes. >> >> On that note, is there a wiki or some other collaboration space where >> this information (requirements, specifications, etc) can be maintained? >> >> bishop >> >> Quoting Franky Van Liedekerke <lie...@te...>: >> >> > On Sat, 19 Apr 2008 20:21:28 -0400 >> > Matthew Gregg <mat...@gm...> wrote: >> > >> >> So many things need to be redone in the current code base: >> >> * Permission system >> >> * User management >> >> * The admin UI <-biggie >> >> * Survey results export >> >> * Survey question storage export/interchange >> >> * etc... >> >> and it's already in a pretty ugly state, that I have had "flip the >> >> switch and start over" in my head for a long time. I have worked >> >> privately on a few proof of concepts for this, but never pushed to >> >> have something usable. Current code could be put into maintenance >> >> mode and new dev only on this "branch". >> > >> > well, I agree here: the current code is ugly and I sometimes thought >> > about beginning from scratch again also. So I'm in favour of starting >> > over also. >> > >> > Franky >> > >> > ------------------------------------------------------------------------- >> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> > Don't miss this year's exciting event. There's still time to save $100. >> > Use priority code J8TL2D2. >> > >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> > _______________________________________________ >> > phpESP-devel mailing list >> > php...@li... >> > https://lists.sourceforge.net/lists/listinfo/phpesp-devel >> > >> >> >> > -- > Matthew Gregg <mat...@gm...> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel > -- Bishop Bettini ideacode, Inc. (main) +1 919 341 5170 / (fax) +1 919 521 4100 Visit us on the web at: ideacode.com Professional software research and development reviewmysoftware.com Improve sales! Review your software before you release bytejar.com Solutions to those annoying development problems |
