Re: PEAR a way forward

--On October 4, 2006 12:58:50 PM -0700 Joshua Eichorn <josh@bluga.net> wrote: > I think pear can accomplish a rejuvenation - both in the code and in the > mind of the community - by focusing on several aspects I agree (and that was an insightful list of things to work on.) Joshua's list is excellent, but there are larger issues to tackle... I believe we have a race condition: How do we make decisions, resolve issues and move forward, when we clearly have trouble making decisions, resolving issues and moving forward? --Organizational documentation We need one place which holds all the official documentation. This would be the library holding all of PEAR's goals, guidelines, CS, organizational standards and RFCs. Most of this raw material already exists; There are documents in the QA area of pearweb, there are RFCs in PEPr, there are mailing list archives, there are IRC conversations, and I'll bet there are other places we could also mine. --Organizational procedures Clear, well known procedures, rules and systems(software) for working on all the organizational and steering things. This enables us to build knowledge and wisdom to be stored in the library. Neiter of those need to be "complexity for complexity's sake". The actual systems (software and conceptual) could be relatively simple, and implemented relatively easily. Should we rally around these two ideas? Could we rally around these two ideas? If we did, would we be able to move forward and address the myriad of things everyone has on their minds? -craig ---- PEAR web/CVS: cconstantine cconstantine@php.net / craig.blurfl.com