Re: Package proposal: Mail_Mime (alternative)

On 19 Aug 2003 at 13:29, Greg Beaver wrote: > Pierre-Alain Joye wrote: > > >On Tue, 19 Aug 2003 02:10:01 -0400 > >Greg Beaver <greg@chiaraquartet.net> wrote: > > > > > > > >>you've been around PEAR long enough to know that none of the core > >>developers care about fairness > >> > >> > > > >you are wrong (and I remember you are part of the core PEAR > >developers now ;) ). > > > :) > > >For the rest, you are right to remember that a package can fit > >somewhere else than PEAR. > > > This was the main point of the email, yes. > > >But you are wrong to think we should accept a package > >only because it is well done and/or usefull. There are cases where we > >should not have more than 1 package, especially for such features (or > >DB and MDB). > > > I do understand this policy, and I have respect for what works, even > if I express a little annoyance now and then :). I do think there > needs to be a home for the other projects that are still well-written > and useful. No offense to the other repositories out there, but > nothing approaches the ease of finding packages and installation that > pear and Horde have. I think a repository that uses the pear > installer but has more relaxed rules about acceptance (i.e., only > requiring quality code and documentation) would complement PEAR quite > well, and possibly reduce the length and acid content of threads on > pear-dev when a package is not accepted. Then there would be the > official repository, and another place to search if you need a > specific solution that isn't quite implemented by a pear package. Wouldn't this by design cause that packages aren't submitted to pear but to this "other" repository. I can remember some proposals that just weren't taken care of but not really rejected or maybe also accepted at the end. These packages would be submitted to the "other" repository since it needs less hard work than to convince us sometimes narrow-minded devs :-) There is pear, there is Horde - and maybe another repository will open / is already there we don't know about. But I don't think that we should "force" the branch-off of a new repository from the pear- people (directly). Stefan