Then fork the project and add OpenID support if you're so convinced it's a good idea.
Mind you, the current version doesn't support any customer login aside from ticket ID/email so OpenID support at this time would be even more pointless.
There's a difference between leading and wasting time implementing features that will be of practically no use outside of a very small set of users.
There are a lot of things to take into consideration when adding a new feature to any piece of software and, quite frankly, most people who suggest new features don't consider those things at all. If we added every feature that someone thought was a "good idea" then the system would be bloated and full of "features" that only confused, got in the way, and made the system harder to use.
I don't care if someone's 76 year old grandmother adopts a new technology. I do care if she's able to open a support ticket and find out why the toy train set she orderd for her grandson for Christmas hasn't shown up yet.
I'm an early adopter, a big fan of new technology when it's good and shows promise. I like seeing progress move forward as much as anybody, but those all come secondary to meeting the needs of the users who actually depend on the software.
I'm sorry your bright idea doesn't make the feature list, but for now, OpenID, which still has a lot of problems in its own right, stays on the cutting room floor.
(I never said Facebook Connect was a good idea. I was using it as an example of a centralized login, much as OpenID is.)
