Non-responsive maintainer fast track procedure for libsndfile

[Chris Jones]

This seems to be happening a lot lately regarding maintainers and/or
co-maintainers losing interest in their projects somewhere along the
line and just stopping development without any warning and
notification to other members who may be interested.

I am wondering, is the process efficient enough for other willing
developers to take over development of unplanned orphaned and
unmaintained code from unresponsive developers/maintainers and
co-maintainers?

Regards


--
Chris Jones
Photographic Imaging Professional and Graphic Designer
ABN: 98 317 740 240

Photo Resolutions - Photo Printing, Editing and Restorations
Web: http://photoresolutions.freehostia.com
Email: <chrisjones at comcen.com.au> or <ubuntu_cj at comcen.com.au>

Fedora Design Suite Developer and Co-Maintainer
Email: <foxmulder881 at fedoraproject.org>
--
GnuPG v1.4.10 (GNU/Linux)
Public Key Fingerprint:
6915 0761 5754 D091 99F4
5384 BA37 FD5D 34F9 F115