Captain's Log for the ipfs/archives endeavor

[flyingzumwalt]

Captains Log - Initial Entry

@flyingzumwalt is the captain for this endeavor until we find a long-term captain. We're still trying to define the purpose of this repository, which grew organically over the past 18 months.

[flyingzumwalt]

Captain's Log 30 Jan 2017

What is happening

Meanwhile, we wrapped up the IPFS engineers' 2-week data.gov Sprint. The collaborators on that sprint will start replicating datasets very soon. See the report from the sprint for more info.

Where is the help needed

• The data.gov collaborators will start Main data.gov Epic: Replicate 350 TB of Data Between 3 Peers (and then the World) #104 soon. They might need help/support.
• Help test the benefits of various chunking algorithms Test the benefits of Rabin Fingerprinting vs normal chunking #137
• Help @flyingzumwalt clarify the purpose of this ipfs/archives repository. See Clarify purpose of this repository and archives.ipfs.io #89

Thank-yous

Thank you to @mejackreed for inspiring this sprint

Thank you to @20zinnm for enthusiastically experimenting with using IPFS for distributed archiving

Thanks to the people and organizations who responded to the Call for Participants, especially Matt and Michelle at EDGI and Mek, Jefferson & Wendy at Internet Archive.

Thanks to the IPFS contributors who worked on this sprint @whyrusleeping @Kubuxu @kevina @jbenet @flyingzumwalt

[rht]

To whom it may concern: I have already proposed that the repository should contain build scripts for public datasets being published to ipfs (#86). So that the archival method can be reused -- existing examples > documentations.