We have several options. a) Implement the "thingapt" API in terms of `thing.el' so that programs just work. This would be in the spirit of fsf-compat. (Although the analogy doesn't fully hold water. It's listed just for completeness.) b) Proclaim `thing.el' obsolete and replace it with `thingapt.el'. This has the problem of losing backward compatibility in a way that would set Kyle on your shoulders, clawing at your spine. c) Proclaim `thing.el' obsolete and `thingapt.el' its follower. Provide clear instructions on how to change all programs, and keep `thing.el' in a "compatibility" package (not `fsf-compat', but `old-compat'.) This is an option only if FSF's `thingapt.el' really is better than `thing.el'. d) The same as c), but implement `thing.el' API in terms of `thingapt.el' for compatibility. Which one do you think should apply?