Re: [Phpwebsite-developers] Easing into 1.x

[Shaun M. <sh...@ae...>]

The 1.x roadmap seems fine (that's British for 'good').

I've got quite a few sites in production using branches and even a  
couple in development now so branches are crucial before I can even  
contemplate 1.x on some sites. And one set of sites is using Andrew  
Patterson's Single Sign On hack so that's going to be an interesting  
upgrade. I'm usually pretty conservative with hacks but I just needed  
that functionality.

I'd voice again that we should be eating our own dog food so if  
there's any new forum then we should use phpwsBB and I'll volunteer  
for moderation duties if you need the extra help there. I'd also hope  
that that one module is where a lot of effort is made to keep  
compatibility as a lot of content gets shoved through forums. I don't  
think a conversion script will be ok here for many people so I'd  
imagine getting phpwsBB 1.03 (the latest) running on fallout with as  
few changes as need be for now would be the way forward, even if we  
have to drop stuff from phpwsBB that is problematic (eg. the avatar  
code).

I don't know how far away we are with getting the wiki module  
functional enough that it takes over duties for the -comm wiki but  
that would be useful too. Perhaps Greg or Mike might like to say.

Otherwise, giving the community more of a role than they've had in  
the past would seem to me to be crucial through this change. More  
reliance on -comm is good but I'd suggest we can go further once 1.0  
has been hot-housed enough at appstate.

Perhaps some of the in-house modules could be moved over to -comm for  
us to work on them rather than submitting patches.

I'd also like to ask now what is to become of the 0.10.x code?

Could this be released into the community now so that we can support  
that? CVS transferred to sourceforge?


Shaun
aegis design - http://www.aegisdesign.co.uk
aegis hosting - http://www.aegishosting.co.uk