Plus the whole device is 100% open
I'm very interested why decision about publishing Eagle project files isn't a sure thing? If it depends on something, then what it is, any particular reasons for not doing it, *if* the project comes to fruition, eventually? It seems to me, that it would nicely play along with "FOSH(ardware)" spirit of the project.
With all due respect, you've avoided answering the question. The fact that Mr. Nikolaus owns PCB layout, doesn't expand why you couldn't not want to release it. In my understanding, "We might consider making it one", means that you have some reasons/arguments against it. I'm sincerely interested in what those are. Of course, if you just don't know, or is it the (typical in hardware production business) memento of "it's better to own something exclusively that don't, even if we don't know why, yet", I'll accept that as answer. I would just like to hear it, officially, from the Neo900, this or other way. Believe it or not, but there are people, that consider eventual FOSW of the project as very important factor, before making pre-order/support decision*. Even if it can't be guaranteed now, knowing the reasoning of project Creators is useful when deciding if one want to "take the risk" of jumping into the bandwagon now, before releasing/not releasing those files in some Free license is confirmed/denied. Respect, love, and pink chocolate flowers /Estel *Including two people, that I'm personally trying to convince into pre-ordering - well, at least as soon as the new donation method is up, as it's not quite reasonable to do so now and get refund, losing on conversion/transfer fees...
please read the quote in your question, it has the answer to your question already. Also: And no, this is not exactly a FOSH project in the sense you use the word. Never been. We might consider making it one, eventually. When we agree that we all want to do that.
what in "we might consider making it one, eventually" you failed to grok? We didn't care about that detail yet. period. You're free to consider this a negligance but it's not relevant for us right now. It's not a product property requirement spec. Please stop pestering.