While proof development shares A LOT of traits with software development, it is not the same. For example, proof development also shares A LOT of traits with wr

While proof development shares A LOT of traits with software development, it is not the same. For example, proof development also shares A LOT of traits with writing an academic paper. I think Github + package manager is definitely the baseline to beat, but I believe something much better is possible when focusing on the particular case of a collaborative theorem proving system. It might even turn out that this particular case is not that particular at all. :-)