As a matter of interest, would it be ok to open a new thread for those questions which have not been chosen for your blog, so that any candidates who wish can also answer them?

Absolutely! We are all on equal footing here. What I've found is that some candidates are more responsive than others, so be patient, and ymmv !

there are capacitive and resistive candidates...
sorry, couldn't resist

Please publish on maemo.org as well.

My blog is aggregated on planet maemo, so it will appear on maemo.org.

Well, maybe someone will cut and paste it onto talk or wiki as well.

Due to certain remarks made here and on the email list I'll go ahead and move my answering posts elsewhere, so don't be confused at the upcoming editing.

I honestly thought EIPI was through with the question assembling process, sorry

The blog post containing the 10 Q&A with candidates is now up on my blog:

http://mobiletablets.blogspot.com

Enjoy!

I will have to see about publishing the 3 community questions on the blog, as I only received a few responses to those. If no more materialize before voting starts, I will post those responses in this thread.

Thank you very much to the candidates for their participation and patience. Collaborating with 10 people in such a short time-frame is a first for me, and there were lots of lessons learned on my part. Thanks again!

What merge? What's taking place is not really a merge, but the creation of a whole new community. So, really, nothing much will happen to maemo.org it will remain online for the foreseeable future and support those users who can't or don't wish to move to MeeGo.

Of course the specifics of that future are dependent on Nokia. If no viable upgrade path is provided for existing owners then maemo.org's position must be much larger moving forward than if users have an easy way to migrate to MeeGo.

Good QA is a balancing act that's never going to be perfect. It will always be inconvenient for everybody involved in the process. Developers have to suffer longer deployment times, testers have to work harder and users have to wait longer for new software. Ideally good QA will leave everybody better off in the end when they don't have to deal with a lot of buggy, low-quality software.

I think the Extras QA process currently has two majors problems: an often slow and still unpolished front-end, and QA requirements that have, as yet, not been completely refined.

The software will improve with time and good bug reporting, of course, but the process requirements themselves require tweaking. Specifically, I'd like to see accommodations made for minor point releases (currently the process treats all releases the same, which encourages developers not to release minor fixes) and I'd like to see the burden for basic, easily automated testing moved into the infrastructure as much as possible.

Technical barriers to entry, of course, need to be reduced, processes need to be transparent, and everything needs to be well documented.

maemo.org being what it is (and that's not a support site for end-users, but the home of the enthusiast community for Maemo), the hurdles of active participation are never going to go away and all content is never going to be completely easy to understand. The best that can be done is to make sure the tools are approachable (making Bugzilla easier to use is one of my pet projects), the documentation is good, and that there are always people available to answer whatever questions arise.

Yeah, I've been reprogramming myself to use words like "migration" instead of "merge".