I will not be able to attend the TSC call in the morning but here is my proposal for the slack archive.

As Hyperledger already has an AWS account, we could create an S3 bucket to hold the content of github[0] for indexing and display. It would need a host name - I have no good proposal for this. slack-archive.hyperledger.org perhaps?

I would still like to have the contents of github[1] hosted in my previously proposed repo in Gerrit. The gist that I used to generate the HTML is available[2]. Arnaud found some mangled characters - pull requests to fix the gist accepted.

We could host the initial version[0] until enough fixes are in to [2] to warrant a republication, or we could wait until people were generally happy with the formatting of the content.

Ry

[0] https://github.com/rjones-lf/hyperledger-slack-archive/tree/master/html

[1] https://github.com/rjones-lf/hyperledger-slack-archive

[2] https://gist.github.com/rjones-lf/f8f4f9e4008567fa6ba9a03234316a33

On Thu, Feb 23, 2017 at 8:26 AM, Todd Benzies via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:

• VOTE:  slack-archive repo
  

• https://lists.hyperledger.org/pipermail/hyperledger-tsc/2017-February/000605.html

• Ry is exploring best way to host/format -- but, it sounds like people are generally in favor.

• Vote next week based on Ry’s findings.