I personally think that phpBB should stay independent of phpPP (or whatever it's name will be). Although I do agree with pso and with what he says below.
I did not say phpBB 2.x will not change to accommodate something the portal may require. I clearly said more than once that it will not change if that change is detrimental to the forum. Now common sense suggests that if a change is detrimental to one thing, and in this case the major component of the project, then it's a 'bad idea' anyway and should be re-assessed to find an alternative, superior solution.
I know that I wouldn't want to see all the work done by the phpBB2 team be so integrated that they can't concentrate on just the forum. That's not what they started out doing (making a protal that is). They started out to make the best forum on the net (and they have done a damn good job IMO and it's only getting better). I wouldn't want to interfere with their work because of a portal. However, I am glad to hear that the phpBB team might be willing to work with the portal team in smaller issues. I know that I don't want to see the two become dependant on each other. That would be bad. That's why I voted to keep the two separate but at the same time we could package them together as one big web community all in one (WCAO as a name? or OBWC? hmmm).
Like I've said before I can see the portal using some of the same code as phpBB (it would be dumb not too IMO). As log as the code of phpBB doesn't change as far as what functions take in and what they return it shouldn't be a problem. That's where the two teams will need to talk about things. If a function that is used by both the portal and phpBB change in that respect then the portal (IMO) should rewrite the function for it's software since it's a sub project of phpBB (rewriting a function shouldn't be hard anyway).
Anyway, if the phpBB team is going to be so gracious as to take this under their wing etc. the least we can do is let them continue work on what they started and not have to worry about the portal.