Automated deployment to update events 2021-07-05 (#323)

Co-authored-by: github-actions <github-actions@users.noreply.github.com>

docs/_events/2021-07-04-rseng-software-PushEvent-17028516873.md

@@ -0,0 +1,17 @@
+---
+event_type: PushEvent
+avatar: "https://avatars.githubusercontent.com/u/814322?"
+user: vsoch
+date: 2021-07-04
+repo_name: rseng/software
+html_url: https://github.com/rseng/software/commit/0da3d778ba0e9ead7913a6365939cf0559b49e81
+repo_url: https://github.com/rseng/software
+---
+
+<a href='https://github.com/vsoch' target='_blank'>vsoch</a> pushed to <a href='https://github.com/rseng/software' target='_blank'>rseng/software</a>
+
+<small>Automated deployment to update software database 2021-07-04 (#227)
+
+Co-authored-by: github-actions <github-actions@users.noreply.github.com></small>
+
+<a href='https://github.com/rseng/software/commit/0da3d778ba0e9ead7913a6365939cf0559b49e81' target='_blank'>View Commit</a>

docs/_events/2021-07-04-spack-spack-IssueCommentEvent-17031768457.md

@@ -0,0 +1,15 @@
+---
+event_type: IssueCommentEvent
+avatar: "https://avatars.githubusercontent.com/u/814322?"
+user: vsoch
+date: 2021-07-04
+repo_name: spack/spack
+html_url: https://github.com/spack/spack/pull/24690
+repo_url: https://github.com/spack/spack
+---
+
+<a href='https://github.com/vsoch' target='_blank'>vsoch</a> commented on issue <a href='https://github.com/spack/spack/pull/24690' target='_blank'>spack/spack#24690</a>.
+
+<small>A `sphinx>=someversion` could possibly avoid a lot of issues to not use really old versions, and the CI would still install latest, if that if of concern....</small>
+
+<a href='https://github.com/spack/spack/pull/24690' target='_blank'>View Comment</a>

docs/_events/2021-07-04-vsoch-opensource-heartbeat-PullRequestEvent-17028374351.md

@@ -0,0 +1,13 @@
+---
+event_type: PullRequestEvent
+avatar: "https://avatars.githubusercontent.com/u/814322?"
+user: vsoch
+date: 2021-07-04
+repo_name: vsoch/opensource-heartbeat
+html_url: https://github.com/vsoch/opensource-heartbeat/pull/322
+repo_url: https://github.com/vsoch/opensource-heartbeat
+---
+
+<a href='https://github.com/vsoch' target='_blank'>vsoch</a> merged a pull request to <a href='https://github.com/vsoch/opensource-heartbeat' target='_blank'>vsoch/opensource-heartbeat</a>
+
+<a href='https://github.com/vsoch/opensource-heartbeat/pull/322' target='_blank'>View Pull Request</a>

docs/_events/2021-07-05-buildsi-drift-server-PushEvent-17033047291.md

@@ -0,0 +1,17 @@
+---
+event_type: PushEvent
+avatar: "https://avatars.githubusercontent.com/u/814322?"
+user: vsoch
+date: 2021-07-05
+repo_name: buildsi/drift-server
+html_url: https://github.com/buildsi/drift-server/commit/58ef2448c78992521db57e26cd64538f93a4ca69
+repo_url: https://github.com/buildsi/drift-server
+---
+
+<a href='https://github.com/vsoch' target='_blank'>vsoch</a> pushed to <a href='https://github.com/buildsi/drift-server' target='_blank'>buildsi/drift-server</a>
+
+<small>start of third attempt
+
+Signed-off-by: vsoch <vsoch@users.noreply.github.com></small>
+
+<a href='https://github.com/buildsi/drift-server/commit/58ef2448c78992521db57e26cd64538f93a4ca69' target='_blank'>View Commit</a>

docs/_events/2021-07-05-opencontainers-distribution-spec-IssuesEvent-17033079576.md

@@ -0,0 +1,13 @@
+---
+event_type: IssuesEvent
+avatar: "https://avatars.githubusercontent.com/u/814322?"
+user: vsoch
+date: 2021-07-05
+repo_name: opencontainers/distribution-spec
+html_url: https://github.com/opencontainers/distribution-spec/issues/289
+repo_url: https://github.com/opencontainers/distribution-spec
+---
+
+<a href='https://github.com/vsoch' target='_blank'>vsoch</a> open issue <a href='https://github.com/opencontainers/distribution-spec/issues/289' target='_blank'>opencontainers/distribution-spec#289</a>.
+
+<p>Content Length Required</p><small>I wanted to open up some discussion about the `Content-Length` header. Currently the spec does not say that all responses are required to have it, and this possibly makes sense because we could look it up, say, in the manifest, but since Content-Length is sort of bread and butter when it comes to communicating about requests/responses, is there any reason to not have it? Many libraries can find this field useful, so we are proposing to have it added to all registry responses that make sense for a future release:...</small><a href='https://github.com/opencontainers/distribution-spec/issues/289' target='_blank'>View Comment</a>

docs/_events/2021-07-05-vsoch-chonker-awards-PushEvent-17033936490.md

@@ -0,0 +1,17 @@
+---
+event_type: PushEvent
+avatar: "https://avatars.githubusercontent.com/u/814322?"
+user: vsoch
+date: 2021-07-05
+repo_name: vsoch/chonker-awards
+html_url: https://github.com/vsoch/chonker-awards/commit/817ac48e334df9c7280cbc8aceedc51cf68dd991
+repo_url: https://github.com/vsoch/chonker-awards
+---
+
+<a href='https://github.com/vsoch' target='_blank'>vsoch</a> pushed to <a href='https://github.com/vsoch/chonker-awards' target='_blank'>vsoch/chonker-awards</a>
+
+<small>Merge pull request #155 from vsoch/chonkers/update-2021-07-05
+
+[chonkers] chonkers/update-2021-07-05</small>
+
+<a href='https://github.com/vsoch/chonker-awards/commit/817ac48e334df9c7280cbc8aceedc51cf68dd991' target='_blank'>View Commit</a>