Clint Priest wrote:
I was thinking more along the lines of a collaborative wiki with
inline-threaded comments...
Actually just using the wiki better would work, but it tends to get even more
messy without someone moderating everything.
I know people don't like my stance, but when one is supporting 15+ year old
systems that people just expect to work, strange messages popping up because
someone has upgraded a machine cause panic. 'Mailing list' with it's parallel
news feed is a good stable archaic method that just works, and forums that do
not provide a PROPER mail link are an utter pain. I'm on a few lists where
things have been improved by 'moving to a forum' ... and the majority of the
users are still on the mailing list!
github's issues area is another backward step 'improvement', trying to track
bugs across several repos ( pear, php-src and the like ) are just impossible and
when the repos are modules of the one project ...
In the case of the current discussions, a LOT of edge cases have been pointed
out, and yes it is difficult to track them in the discussions. SO what is needed
is a wiki page which lists them all? I seem to recall a list of several items
that were being proposed as the skeleton for a new rework, some of which were
disputed, at which point a separate wiki page would be appropriate. Stas listed
some 11 points which marry up with that list but the answers get messy and
disjointed.
Given the nature of the problem, several pages on the wiki does not seem
inappropriate and will make discussions more focused.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
