Add 2020 Methodology in Simplified Chinese #1422
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tunetheweb
commented
Nov 5, 2020
Comment on lines
+126
to
+128
| <!-- To be translated <p> | ||
| There was was a 20-30% growth on websites analysed compared to the <a href="../2019/methodology#websites">number of sites analysed for the 2019 Web Almanac</a>. This increase has been analysed by <a href="{{ url_for('contributors', year=year, lang=lang, _anchor='paulcalvano') }}">Paul Calvano</a> in his <a href="https://paulcalvano.com/2020-09-29-growth-of-the-web-in-2020/">Growth of the Web in 2020</a> post. | ||
| </p> --> |
There was a problem hiding this comment.
Can you translate this whole section and remove the <!-- and --> marks when you are done?
Comment on lines
+371
to
+397
| <!-- To be translated <section> | ||
| <h3 id="brainstorming"><a href="#brainstorming" class="anchor-link">ブレインストーミング</a></h3> | ||
|
|
||
| <p> | ||
| The 2020 Web Almanac kicked off in June 2020 as a <a href="https://twitter.com/rick_viscomi/status/1273135952848977920?s=20">request for new authors</a>. After a round of brainstorming, 22 chapters were solidified and we began <a href="https://github.com/HTTPArchive/almanac.httparchive.org/issues/876">assigning subject matter experts and peer reviewers to each chapter</a>. This process had some inherent bias because of the challenge of getting volunteers to commit to a project of this scale. Thus, many of the contributors are members of the same professional circles. One explicit goal for future editions of the Web Almanac is to encourage even more inclusion of underrepresented and heterogeneous voices as authors and peer reviewers. | ||
| </p> | ||
|
|
||
| <p> | ||
| We spent July 2020 pairing people with chapters and getting their input to finalize the individual metrics that will make up each chapter. | ||
| </p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h3 id="analysis"><a href="#analysis" class="anchor-link">Analysis</a></h3> | ||
|
|
||
| <p> | ||
| In July and August 2020, with the stable list of metrics and chapters, data analysts triaged the metrics for feasibility. In some cases, <a href="https://github.com/HTTPArchive/legacy.httparchive.org/tree/master/custom_metrics">custom metrics</a> needed to be created to fill gaps in our analytic capabilities. | ||
| </p> | ||
|
|
||
| <p> | ||
| Throughout August 2020, the HTTP Archive data pipeline crawled several million websites, gathering the metadata to be used in the Web Almanac. | ||
| </p> | ||
|
|
||
| <p> | ||
| The data analysts began writing queries to extract the results for each metric. In total, <strong>TBC queries</strong> were written by hand! You can browse all of the queries by chapter in the <a href="https://github.com/HTTPArchive/almanac.httparchive.org/tree/main/sql/2020">sql/2020</a> directory of the project's GitHub repository. | ||
| </p> | ||
| </section>--> |
There was a problem hiding this comment.
Can you translate this whole section and remove the <!-- and --> marks when you are done?
Suggested change
| <!-- To be translated <section> | |
| <h3 id="brainstorming"><a href="#brainstorming" class="anchor-link">ブレインストーミング</a></h3> | |
| <p> | |
| The 2020 Web Almanac kicked off in June 2020 as a <a href="https://twitter.com/rick_viscomi/status/1273135952848977920?s=20">request for new authors</a>. After a round of brainstorming, 22 chapters were solidified and we began <a href="https://github.com/HTTPArchive/almanac.httparchive.org/issues/876">assigning subject matter experts and peer reviewers to each chapter</a>. This process had some inherent bias because of the challenge of getting volunteers to commit to a project of this scale. Thus, many of the contributors are members of the same professional circles. One explicit goal for future editions of the Web Almanac is to encourage even more inclusion of underrepresented and heterogeneous voices as authors and peer reviewers. | |
| </p> | |
| <p> | |
| We spent July 2020 pairing people with chapters and getting their input to finalize the individual metrics that will make up each chapter. | |
| </p> | |
| </section> | |
| <section> | |
| <h3 id="analysis"><a href="#analysis" class="anchor-link">Analysis</a></h3> | |
| <p> | |
| In July and August 2020, with the stable list of metrics and chapters, data analysts triaged the metrics for feasibility. In some cases, <a href="https://github.com/HTTPArchive/legacy.httparchive.org/tree/master/custom_metrics">custom metrics</a> needed to be created to fill gaps in our analytic capabilities. | |
| </p> | |
| <p> | |
| Throughout August 2020, the HTTP Archive data pipeline crawled several million websites, gathering the metadata to be used in the Web Almanac. | |
| </p> | |
| <p> | |
| The data analysts began writing queries to extract the results for each metric. In total, <strong>TBC queries</strong> were written by hand! You can browse all of the queries by chapter in the <a href="https://github.com/HTTPArchive/almanac.httparchive.org/tree/main/sql/2020">sql/2020</a> directory of the project's GitHub repository. | |
| </p> | |
| </section>--> | |
| <section> | |
| <h3 id="brainstorming"><a href="#brainstorming" class="anchor-link">ブレインストーミング</a></h3> | |
| <p> | |
| The 2020 Web Almanac kicked off in June 2020 as a <a href="https://twitter.com/rick_viscomi/status/1273135952848977920?s=20">request for new authors</a>. After a round of brainstorming, 22 chapters were solidified and we began <a href="https://github.com/HTTPArchive/almanac.httparchive.org/issues/876">assigning subject matter experts and peer reviewers to each chapter</a>. This process had some inherent bias because of the challenge of getting volunteers to commit to a project of this scale. Thus, many of the contributors are members of the same professional circles. One explicit goal for future editions of the Web Almanac is to encourage even more inclusion of underrepresented and heterogeneous voices as authors and peer reviewers. | |
| </p> | |
| <p> | |
| We spent July 2020 pairing people with chapters and getting their input to finalize the individual metrics that will make up each chapter. | |
| </p> | |
| </section> | |
| <section> | |
| <h3 id="analysis"><a href="#analysis" class="anchor-link">Analysis</a></h3> | |
| <p> | |
| In July and August 2020, with the stable list of metrics and chapters, data analysts triaged the metrics for feasibility. In some cases, <a href="https://github.com/HTTPArchive/legacy.httparchive.org/tree/master/custom_metrics">custom metrics</a> needed to be created to fill gaps in our analytic capabilities. | |
| </p> | |
| <p> | |
| Throughout August 2020, the HTTP Archive data pipeline crawled several million websites, gathering the metadata to be used in the Web Almanac. | |
| </p> | |
| <p> | |
| The data analysts began writing queries to extract the results for each metric. In total, <strong>TBC queries</strong> were written by hand! You can browse all of the queries by chapter in the <a href="https://github.com/HTTPArchive/almanac.httparchive.org/tree/main/sql/2020">sql/2020</a> directory of the project's GitHub repository. | |
| </p> | |
| </section> |
tunetheweb
commented
Nov 5, 2020
| <h2 id="looking-ahead"><a href="#looking-ahead" class="anchor-link">展望未来</a></h2> | ||
|
|
||
| <p> | ||
| WebAlmanac的2020年版是网络社区内省和致力于积极变革的年度传统中的第二版。我们付出了巨大的努力才走到今日，这多亏了许多有奉献精神的 <a href="{{ url_for('contributors', year=year, lang=lang) }}">贡献者</a>。 我们希望尽可能多地利用这些工作，使未来的版本更加精简。 |
There was a problem hiding this comment.
This line could do with a review.
|
There's also some extra changes that need to happen here as well. You can see these changes here: https://github.com/HTTPArchive/almanac.httparchive.org/pull/1449/files Feel free to commit any changes directly to this branch. |
|
Closing this as a few other changes so will handle in the translation task. |
|
I'm back, will work on this and 2020 capabilities chapter. |
|
Cool. Feel free to work on this branch (I left it in place in case we needed it), and to translate the missing pieces and also the changes from https://github.com/HTTPArchive/almanac.httparchive.org/pull/1449/files |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is liable to change some more but at the moment it's very similar to 2019 and we've committed in English to think we can do the same in the other languages if you're willing to review @chengxicn ?
Will point out paragraphs that need particular review