Pali, could You contact Council (for example using "contact us" form) and point them to this problem? I thought about doing that myself, but it seems much more proper, when done by You.

It's completely unacceptable that kernel-power will stay in dev forever, cause one maintainer disappeared and don't give a duck about transferring maintainer's right, and another one "feel that it's not fair to grant You [rights], because Titan was main maintainer".

Not to mention little duckish behavior of last contactable maintainer (sorry, I must write that - forced myself to not comment when we received that info 1st time, but now it's too much), I agree that council or community shall have a way to deal with such counter-productive situations. What if main maintainer get hit by a bus one day? Project R.I.P, even thought many people contributed/co-dev'ed it, and still want to continue?

---

Pali, what about removing faulty bq module from next release? As for now, this is only 1 not working (as it should, in kp47) thing, that was 110% confirmed. Still, somehow I feel that You deny to acknowledge it as fact. Sorry if I'm wrong - I don't mean to sound harsh - but for me that is conclusion from Your short discussion with original bug reporter (ended by him blacklisting module as for joerg-rw suggestion)