We should ask around renowed universities what courses they have for freshmen in CS and then what books they recommend for those courses.
If a book comes up often, it should go into the gentoomenv2 library into /basics/
If its a book like Cormen which is used everywhere in intrduction to algorithm class, yet is pretty difficult, we could include an easier version (like algortihms for dummies.pdf or headfirstAlgorithms.pdf) into /prebasics/.
In /meta/ we could put all the classics that are not about a particular concept or technique but about the field of CS in itself: The tao of programming, The mythical man month, Code complete...
Then /algortihms/ all books about algorithms that go beyond the basics. Could include Encyclopedias of algorithms, research papers on rarely used but brilliant algorithms...
Of course following this principle there would be /os/. While there should be 1-3 books about OSes in /basic/ in /os/ there would be the more advanced concepts or books about exotic OSes like Lisp Machines.
Same for /db/: Database books beyond basic level or nonSQL database systems or even distributed databases.
I think you get the structure I have in mind.
Perhaps we could structure the folder structure in the torrent hierarchically, making it easier for users to navigate it. /basics/ and /meta/ would be toplevel with /basics/ holding both the book files about basic concepts as well as the folders like /db/ /os/...
The user, even with no CS experience could then navigate down the tree, reading along ever book (assuming infinite time) and be ready for the next "level" once he has read at least one book at the current level.