On Thu, Aug 12, 2010 at 13:13, Felix Miata <mrmazda@xxxxxxxxxxxxx> wrote: > On 2010/08/12 11:55 (GMT-0700) Adam Williamson composed: > >> if you want to maintain s-c-d, I'm sure ajax would be more than >> happy to hand over ownership. > > Being a non-programmer I'm confident there's little likelihood I'd be > competent to attempt such an endeavor. Nevertheless, my complaints are not > unique to Fedora. Other distros have the same problem. Before announcement > that SaX2 was to be dropped from the openSUSE 11.3 development tree, > maintenance takeover was invited, and no one stepped up. > > For the benefit of those few, and there will likely always be some, for whom > automatic isn't, some tool is needed upstream in Xorg, possibly SaX2 or SCD > at least as a starting point. A wider call for a maintainer of SaX2 or SCD or > some equivalent is needed. But how and where? I would look for people who are interested in older hardware and keeping it running. HAM groups used to be the place but these days I am not sure. The larger issue is that Fedora can only keep maintaining for older hardware when there are enough people who want to scratch the itch versus expect that it will continue to work. -- Stephen J Smoogen. “The core skill of innovators is error recovery, not failure avoidance.” Randy Nelson, President of Pixar University. "We have a strategic plan. It's called doing things."" — Herb Kelleher, founder Southwest Airlines -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
