Re: Re: priorities for PEAR project as a whole

Bertrand Mansion wrote:

Ian Warner wrote:

Im not beating a massive WIKI drum here but collaboration and communication are the basis of any successful project, it seems to me

from my short time in PEAR that this is what is missing.

I personally have always disliked mailing lists as a method - especially primary of communicating with a team, or community, a forum to me is just more elegant. http://forum.joomla.org/ except maybe Joomlas is a little large :) Joomla also monetise this area with google ads even though they are open sourece too. what i suggested was to immitate then evolve what http://framework.zend.com/ are doing, there front site is glamourous, has the necessary content and tools. I know that Zend and PEAR are different but the concepts are similar. PEAR is a long way ahead of Zend lets keep it that way. Fed up of rewriting all my code to move onto new platforms also :) I suggest writing a http://framework.zend.com/roadmap PEAR needs one of these, no-one knows where PEAR is going - sure it lurks deep it BeebleX somewhere, which list I am not sure :) What I really like is this though - http://framework.zend.com/wiki/dashboard.action - its impressive and will aid collaboration from not just core members but all PEAR community. Zend dont seem to offer a Mailist .. http://www.joomla.org/ is also one of my favourites To get proffesional design help - plan: I suggest an Official Wiki, I reckon a good introductory comment may be to run a competition to design the new logo (want this - http://www.joomla.org/content/view/259/70/) and front end design and concepts for PEARweb, with a prize 1. a link from the front page to the designers site, with PEARS PR and visitor count this is indeed a nice prize to win. A few marketing emails will generate a little buzz for that i think. Just something I think will aid in categorisation: I also suggest splitting PEAR up into two sections - CORE and COMPONENTS with the idea of getting developers focused on developing the real building blocks of PEAR. CORE being packages like MDB2 DATA_OBJECTS DATA_STRUCTURES etc COMPONENTS DB (I put this here as it is superseded by MDB2 I think?) PAGER NET_SMS etc ..... Also what happened to Google summer of code entrants http://php.net/ideas.php - did PEAR get any students to do these ideas? Sorry I do RANT sometimes - so take please forgive me if that pisses some people off, but once I start writing I cant stop..

Please make a pause. It's true that we need hosting and hardware for PEAR, but we can't use a company like yours for this because we don't know you. PEAR is useful for lots of people, companies depend on its availability, we can't take the risk to have it hosted by someone we don't know, I think you can understand that. I as a company depend on its availiabilty also, this is why I was suprised to hear it was on such an old machine with a flaky HD and MySQL. Anyway the offers there, but please dont be patronising and state 'a company like yours' you have no idea what I do or where my talents lie.

Now, about your ideas for pearweb, I think we would all be happy to read them, Lukas was already nice enough to setup a wiki for this. You can post on it, this way important things won't be forgotten: <http://oss.backendmedia.com/PEARThinkTank/> TIA Im sorry but I look at that wiki and think what a dull and boring lot PEAR is. What I was stating is that PEAR needs an official forum / wiki, branded and more importantly actually used - there is nothing up there, yes I dont mind creating entries but will anybody read it and contribute to it - it needs someone in the PEAR group to make a mandate for this kind of thing, I wish I could but you "dont know me".

time for a pause..