In the OP's question, he wondered whether promoting great developers into a non-technical role was a good idea. It's the same age-old question about developers becoming managers. And the answer is? Almost always a horrible idea. Hire the skills. Find someone who wants to learn it. Don't do automatic promotions. In other words, THINK!
No pro sports player would try to play their sport without a coach, but developers try to pick up new techniques all the time by ourselves. Sometimes it works... sometimes, you need an expert to help you figure it out as quickly as possible. Team-wide (and company wide!) process changes are the times you always need a coach. Bring in an expert and solve these problems before you run into them.
The UI is set up for small screens and it's quite fast.
But I still get better battery life from OS X and XP (on the same hardware). But I like Linux better.
Then use the 'pomodoro' technique. Work for 25 minutes (no interruptions, like email or
Tell someone else what you'll get done today.
Two things to consider. Posting to the open source project gets your name out in a big way. Your next job, or your next 5 jobs, very well may come your way because of that exposure and enhanced reputation.
Also, pitch it to the company as getting the community to maintain your changes. Unless this is their core business (and it sounds like it might be), it's in their best interests to get the community to pick up the changes and keep them moving forward in future releases.
Finally, have you asked them if this was intentional? Often contacts are just boilerplate from the lawyers and they never intended to put you in this position.
The number of computer scientists in a room is inversely proportional to the number of bugs in their code.