@soto.mariochr :
Apologies if any of this post sounds rude, or offensive - it is not my intention to offend. I just wish to offer some (hopefully) constructive feedback and reply to some of the comments you have made:
First up, I must say that your "white-paper" and the other articles on github are a very difficult, uncomfortable and uneasy read.
And by that, I don't mean that I didn't understand some of the big words - I assure you that my vocabulary, reading abilities and comprehension are fine. I actually meant that it was difficult to read because the overall tone of the documents made me physically and mentally uncomfortable.
From the way they are written, the articles come across more like a wishlist for a new operating system written by a mentally ill person, or at the very least - someone with a very chaotic mind.
Now, I'm not accusing you of being mentally ill here - it is just the impression I got from the structure of the documents and the mental tone that the documents presented to me when I was reading them. And if you do have any mental health issues - I sincerely hope that you are getting all of the help and support you need with them.
But it seems like you have a lot of ideas. Some of them may even be good ideas. It just seems like you are having difficulty expressing them clearly, accurately and logically.
It is evident from the articles that you have some technical background with Computer Science. But your depth of knowledge is hard to gauge accurately, because as Ryan has pointed out - a lot of the material tends to turn into vague, pseudo-technical gobbledygook rather than anything that resembles a technical discussion, or an actual plausible design.
As an aside - even your reply to ryanvade contains nonsense:
What? You aren't making the GPU "a more efficient RAM" at all.
For the benefit of any non-techies here - ASIC chips (Application Specific Integrated Circuits) are basically an entire system on a chip that is used to run a single, specific task.
Most notably they are used in Bitcoin mining rigs to perform hashing algorithms - which they can do much faster than other methods. And yes - you can port code that is ran on ASIC chips to run on a graphics card.
But by doing this you are NOT creating a "more efficient RAM".
What you are doing is using the graphics card (or an ASIC chip) to perform calculations INSTEAD of doing them in the CPU/RAM because it is more efficient.
Graphics cards and ASIC chips are designed to crunch numbers quickly - so it makes sense to farm out computationally intensive tasks to them. That way there is more CPU time and RAM available to your main application and other programs/processes that are running.
It may seem like I'm nit-picking by pointing out your error, but by stating technically misleading/inaccurate things like that - your posts and documents lose a lot of credibility.
Going back to your documents:
There is nowhere near enough technical detail in any of them for you to be able to call them a "design" for a new operating system. And certainly not enough detail for a developer to implement anything concrete.
It's all very well having these grand, yet vague ideas, but developers will need a
lot more detail.
Rather than a collection of ideas, there needs to be a technically feasible design and a strong rationale for its development!
The only thing that got any real detail was your description of the logo at the start of the whitepaper - which, for all intents and purposes is really a secondary consideration at this point in time isn't it?!
And why are you opening the whitepaper with a description of the logo anyway?
This is the part of the document where you should be introducing your project and making a strong case for it.
Wouldn't it make more sense to introduce the aims of the project and the proposed features of your OS?
How will it be better than other OSes?
What different modules/components will the OS be composed of?
How will the different components of the system interact with each other?
What technical challenges does it pose for would be developers?
etc. etc.
Starting a whitepaper with your requirements for the logo is just too abrupt and simply doesn't make sense!
It's great that you've thought about how the logo should look, but that is something that could be specified later in the document.
OK, I get that you are too lazy to try writing the code yourself. That's fair enough. I have my own share of project ideas that I can't be arsed to code too. And more than a few that I've completely neglected and/or abandoned. But if you want others to get interested, you'll need to do a
lot more work on these documents.
But if you are too lazy to come up with a coherent, technical set of design documents to clearly illustrate your ideas for this new operating system AND provide some compelling reasons for developing it - you aren't going to attract
any developers.
As things currently stand - as a free software enthusiast and as a developer - I don't see any reason to take any of this project seriously.
I don't want you to think that I'm picking on you here. I really don't enjoy criticising other peoples work. It seems like something you are fairly serious about and have put a lot of time and thought into. And if you are that serious, I hope that you will take some of these points onboard and take the time to improve your documents.
Going forward, I think it is most important for you to put more thought into the structure of the documents and more clearly,
accurately and logically express your ideas. Also you need to start to formalise the design for this OS. At the moment, it's too chaotic. It sounds more like a collection of vague ideas - a pipe-dream, rather than a formal design (or even an informal one).
Also, a huge project like this is going to need some serious direction and organisation. This ball isn't going to get itself rolling. You're going to have to put in a
lot more work and be the catalyst to successfully get people interested and actively involved. After all
you are the person who came up with this idea. So if you want this project to get off the ground and to succeed,
you are going to have to get things started. Which may also involve getting your hands dirty and writing some of the initial code.
After all, if you aren't willing to put any time or effort into making this idea of yours a reality, what makes you think that other people will bother?
Finally, apologies if any of this has upset or offended you. It is definitely
NOT my intention. I just wanted to offer you some detailed and honest feedback.
Good luck with this extremely ambitious project. I hope you eventually manage to get it off the ground.
+1 for creativity. 
