Re: priorities for PEAR project as a whole

That's how I see it. Well yes it is important to make the site good first, but we have to establish what we need for the site first.. I mean, do we need a total new architecture ? do we need only couples packages changing, we need to establish some ground rules (ideas) I think we should first decide who will be the teams in charge of differnent tasks, then we can start doing other things, otherwise it will cause confusion and frustration (again), which we should (imho) try to avoid so we do not loose other members of the team. I would classify the priorities this way: 1. Teams & tasks (How we decide that? votes? Then we won't have enough votes ?) Well if anyone has good ideas would be time to suggest them. 2. Site imho we can start on the site once the web team has be defined 3. Other politicals & perosnal That can wait, but not forever, we'll loose too many users.