[haiku-development] Re: R1 (Final) General Interest poll closed. Results posted. ...
- From: Simon Taylor <simontaylor1@xxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 13 Dec 2010 10:48:53 +0000
Am 12.12.2010 22:27, schrieb Matt Madia:
There were over 1600 results on
http://www.haiku-os.org/r1-final-features-poll.
That Google document is no longer accepting responses.
The results have been individually attached as images to
http://dev.haiku-os.org/wiki/FutureHaikuFeatures
I'd like to keep the FutureHaikuFeatures open until Wed. Dec 15th, as
there's a good number of active committers, who have not posted on
that page.
Thanks for collating the results Matt. I read the community poll a
little differently from Stephan, in that the feeling I got was that most
tasks were "only if ready" - ie people generally would like to see as
few blockers for R1 as possible. I've separated the items that received
more votes for must-have than only-if-ready into a few categories:
===R1 Blockers, IMHO===
WiFi WPA - definite blocker, being worked on
WiFi config tools - also a definite blocker
Web+ certificate management - could be hacked into the cURL backend to
save rewriting lots of code?
Upgrade management - some way to push updates cleanly to "core Haiku"
would probably be worthwhile.
===Unsure on===
Package management - many of the votes are probably from Linux users
where package management is essential. The more unified Haiku philosophy
makes it less important for us, IMHO.
Finalize new driver architecture - would be nice to have I suppose but
given the BeOS binary compatibility drop is to come later that seems
like one we can postpone until then.
===Driver/Hardware Support===
When the question is "should Haiku support more hardware" the answer is
obviously going to be yes. I think that effect explains the results for
the following items:
Driver issues (gfx, audio)
Boot failure issues
IRQ routing
Perhaps it would be useful to have a specific alpha/beta with the goal
of testing on as much hardware as possible and fixing bugs. It might be
an idea to have a time-limit on this phase, 100% compatibility would
probably block R1 forever. IRQ routing seems responsible for many of the
failures though, so that should be implemented first.
===Confusing questions===
Bootman multiple drives - perhaps people were confused as to the
limitations this causes. Those who care likely have another boot manager
already installed and Haiku can always be booted by that. A temporary
solution could be to try to detect the case and warn the user.
Networked FS integration - I'm surprised by the size of the vote here -
maybe the title containing FTP and SSH made people think Haiku doesn't
have those currently?
Video mode setting drivers - I find that one very confusing, as I
thought we already had drivers for most of the listed vendors. The small
size of the "don't know" vote suggests most people thought they
understood the question, but I wonder if they really knew what they were
voting for.
----
Read like that, R1 might not be so far away - finish up WiFi, add a
rudimentary update mechanism, add IRQ routing, push out a beta with a
focus on hardware support, have a couple of months of bug squashing and
then release R1. Simple, right?!
Simon
Other related posts:
