Raul Miller <[EMAIL PROTECTED]> writes: > On Fri, Mar 12, 2004 at 07:27:53PM -0800, Thomas Bushnell, BSG wrote: > > That is, the tech-ctty seems to have taken its role to be only a very > > last resort when everything is breaking in some situation, but that > > can be way too late to get involved. I think a little gentle, and > > carefully worded, persuasion can be valuable. We need a group whose > > job is thinking about general interoperability issues on a more than > > one-package-at-a-time basis, and especially when such issues are being > > ignored by the developers, or handled with very dragged feet, it would > > be nice to see the tech-ctty apply a little encouragement. > > Committees don't lead. > > Individuals lead.
Ok, then we need an individual to do it. I filed bug reports against the packages in question, and I was told "feh, why would you want more than one display manager anyway?" It took a *lot* of prodding before the maintainers really decided it was a problem, and then a long time to find a solution, and then a long time to implement it. It's easy to say "the committee can't do it", but then let's drop the Technical Committee entirely, and appoint a Technical Tsar who can. The job needs to get done, and things fall through the cracks right now or take too long in part because there is nobody doing them. We need someone who has the official job of saying "this is a real interoperability problem, fix it". That would, I believe, move things along in many cases. It won't solve all problems, but it would solve some. For example, it could happen that people mail the technical committee, somebody on the committee handles it, and begins working to try to solve the problem. Right now, who does a random Debian user or developer contact when this is necessary? Thomas
