RE: [PEAR-DEV] Solution: secondary maintainer

> From: LIMBOURG Arnaud [mailto:arnaud.limbourg.prestataire@cegetel.fr] > Sent: Thursday, August 14, 2003 5:38 PM > > Saying that people should reply within a week is totally > > unreasonable. > > It's not like people get paid for this. All those stupid > > rules make it > > less an open source project, and more a commercial entity. Of course > > there should be something done when a maintainer/developer doesn't > > respond for-a-long-time. But one week... come on. > > Where do you read one week ? ;) > From: Greg Beaver [mailto:greg@chiaraquartet.net] > Sent: Wednesday, August 13, 2003 10:52 PM > If you are a maintainer, and you know that you will be out of contact > for more than a few days (I don't mean unable to fix, I mean mute), you > must assign a secondary maintainer who has both power to fix bugs and to > do releases. This can be arbitrated by pear-group. I would suggest > that a week of no reply should result in a hostile takeover by ^^^^ > pear-group to fix a critical bug with a known fix and do a snapshot > release as suggested by Tomas. All disputes of whether a bugfix works > or not should be settled by pear-group. If the pear-group people don't > have time or technical knowledge of a package, they must delegate > someone else to make the decision, and that person's decision must be > final, or more blood will spill. Regards, Lukas