I could be totally wrong, I don&#x27;t read a huge number of CS research papers, but aren&#x27;t most published CS papers fully self-contained? They contain the algorithms or ideas within them. Perhaps in pseudocode, but fully reproducible.<p>The little experience I have is in computer graphics publications and (less) distributed systems publications.  Graphics papers very often have data sets and code that go along with the paper. These are nice, and it would be awesome to have a common and well-known way of publishing all that together with the papers, but they are just examples. Mike Hoye&#x27;s comparison to the loss of greek fire doesn&#x27;t seem applicable to the idea of <i>reproducibility by publishing code and dependencies</i>.  The meat is in the paper!<p>Same with my experience in distributed systems papers. I can implement Paxos at any time using only the Paxos PDFs I&#x27;ve saved. Companion code is nice, and again I&#x27;d be fully supportive of a system which gave permanence to not ony the papers but companion artifacts...  but the paper is the important part, isn&#x27;t it?