Create Hardware documentation and resource group

[stargatefan]

Instead of having the developers waste time chasing down hardware specs, I propose a alternate system. Create a sub system where dev's can post info requests and 5-10-20-100 people who are not capable of generating code, can go and find the documents, code etc from the various sources to assist the dev's.Plus manufacturers tend to give in a bit when they get hammered with 400 phone calls asking for the same doc's. trust me this works "sometimes" when dealing with a obstenant vendor.

I see this as helpful in a number of ways.

1. it reduces the number of feature requests comming from users, it free dev's to work on important task like coding and testing.

2. it give alot of folks who could contribute but can't code something to do.

3. it creates a way to check driver development and a unified hardware list.

mostly it helps development along a great deal by removing work other people could be doing.

I dunno. How do dev's feel about this ?We could also start a pretty serious hardware manual by defualt.

[tangobravo]

The problem really is not lack of documentation, it's a lack of developers to write the drivers. It's an unfortunate fact that the developers tend to only be motivated to make something work when it's their own hardware. Also it's pretty much impossible to write the drivers without having the hardware.

Still, I can imagine it would be very useful to have someone with contacts in the industry (such as yourself) involved in order to chase down specs.

(I'm not a Haiku dev, btw, just throwing out a personal opinion)

[stargatefan]

Well its alot easier to write drivers if you have the information. Group could also get driver code to.

There are a ton of things that could be done to assist.

As for hardware testing. setting a up a host system similar to logmein.com would be a good idea. Dev could take control of machine remotely and fix problem and get info.

[luroh]

Can't see this one going anywhere, unfortunately. Closing.