Re: Re: [ANNOUNCEMENT] DTD-0.3 (alpha) Released.

Hi Tomas, > I would like to add this to the Package Proposal Text: "any PEAR Group > Member may add or remove packages in benefit of the PEAR community". Remember, removing a package is _never_ a good idea. I recall a plan to create a "Siberia" for unmaintained packages. PEAR isn't a "I hope it's still there" repository, which will make it ultimately unpopular for end developers (our users). PEAR needs to have stability, and _all_ releases must be available. Imho, a security flaw isn't sufficient to remove a release, but it should expedite a bugfix release, or should be moved to "Siberia" so that it is not as readily available. As an active contributer, if the core group suddenly is allowed to remove my packages simply because they don't like them, I'll be upset and you bet I won't want to contribute at all. In fact, it will stigmatize PEAR. I fully support the voting system, and PEAR Group members shouldn't be above the law. As to subpackages... I really don't see why we can't have subpackages that are visible _only_ on the package page (or when the main package is installed), so that we don't have clutter in the package listing. For example, why not have the DB drivers as subpackages? For example, *DB - DB_MySql - DB_MsSql - DB_SqlLite ... Or whatever, so that it is not necessary to pack all the drivers in with it. In this case, pure subpackages should not be subject to a vote because they are within the package namespace and directory structure, and if they would not be subpackages, they'd be included in the package. Just my two cents, Klaus > -- > Tomas V.V.Cox mailto:cox@idecnet.com > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >