Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Assign subject matter experts and peer reviewers to each chapter #2

Closed
rviscomi opened this issue Apr 25, 2019 · 19 comments
Closed

Assign subject matter experts and peer reviewers to each chapter #2

rviscomi opened this issue Apr 25, 2019 · 19 comments
Assignees
@rviscomi
Milestone
Chapter planning ...

Comments

@rviscomi
Copy link
Member

rviscomi commented Apr 25, 2019 •
edited by ahmadawais
Loading

Part Chapter Authors Reviewers Tracking Issue
I. Page Content 1. JavaScript @addyosmani @housseindjirdeh @mathiasbynens @rwaldron @RReverser #3
I. Page Content 2. CSS @una @argyleink @meyerweb @huijing #4
I. Page Content 3. Markup @bkardell @zcorpan #5
I. Page Content 4. Media @dougsillars @colinbendell @Yonet @ahmadawais @kornelski #6
I. Page Content 5. Third Parties @patrickhulce @simonhearne @flowlabs @jasti @zeman #8
I. Page Content 6. Fonts @davelab6 @zachleat @HyperPress @AymenLoukil #7
II. User Experience 7. Performance @rviscomi @zeman @JMPerez @OBTo @sergeychernyshev #9
II. User Experience 8. Security @arturjanc @ScottHelme @paulcalvano @bazzadp @ghedo @ndrnmnn #10
II. User Experience 9. Accessibility Nektarios Paisios, @nadinarama, @OBTo @rachellcostello, @kleinab #11
II. User Experience 10. SEO @rachellcostello @ymschaap @AVGP @clarkeclark @andylimn @voltek62 #12
II. User Experience 11. PWA @tomayac @jeffposnick @HyperPress @ahmadawais #13
II. User Experience 12. Mobile web @slightlyoff @OBTo @HyperPress @AymenLoukil #14
III. Content Publishing 13. Ecommerce @samdutton @alankent @voltek62 @wizardlyhel #15
III. Content Publishing 14. CMS @amedina @westonruter @mor10 @sirjonathan #16
IV. Content Distribution 15. Compression @paulcalvano @yoavweiss @colinbendell #17
IV. Content Distribution 16. Caching @paulcalvano @yoavweiss @colinbendell #18
IV. Content Distribution 17. CDN @andydavies @colinbendell @yoavweiss @paulcalvano @pmeenan #19
IV. Content Distribution 18. Page Weight @khempenius @henrisGH @tammyeverts @paulcalvano @flowlabs #20
IV. Content Distribution 19. Resource Hints @khempenius @yoavweiss @andydavies @addyosmani #21
IV. Content Distribution 20. HTTP/2 @bazzadp @bagder @rmarx @dotjs #22

Reference sheet

For more context about the Almanac project and how you can help, see this post.
@bkardell
Copy link
Contributor

I think I should be attached to 3, not 4 above... typo?

@rviscomi
Copy link
Member Author

Ah, fixed!

@nadinarama
Copy link

Hi Rick, switching companies, I had to create another account, so here it is... Am okay with contributing to 9. Accessibility

@rviscomi
Copy link
Member Author

@nadinarama I don't have your email address so here's a direct link to the planning doc for the Accessibility chapter. Your coauthor, Nektarios, is unable to use GitHub so we'll do the planning in the doc instead.

@rviscomi rviscomi self-assigned this May 21, 2019
@rviscomi rviscomi transferred this issue from HTTPArchive/httparchive.org May 21, 2019
@rviscomi rviscomi changed the title [Web Almanac] Assign subject matter experts and peer reviewers to each chapter Assign subject matter experts and peer reviewers to each chapter May 21, 2019
@rviscomi rviscomi pinned this issue May 22, 2019
@Yonet
Copy link

Yonet commented May 22, 2019

Should we add WebXR to the content topics? I am happy to help.

@rviscomi
Copy link
Member Author

Good idea! Yeah this could fit in with the Media chapter. Are you interested in writing or reviewing?

@Yonet
Copy link

Yonet commented May 22, 2019

@rviscomi I am happy to help as author or reviewer.

@foxdavidj
Copy link
Contributor

I'd love to help author and/or review 9 and 12 as well. Just let me know 😃

@rviscomi
Copy link
Member Author

Thanks @OBTo! Do you have a preference for author/reviewer for either chapter?

@foxdavidj
Copy link
Contributor

I'd like to help author both if possible

@rviscomi
Copy link
Member Author

Great, just added you!

@flowlabs
Copy link

@rviscomi Happy to peer review 1 or 2 from this list if you need any support?

  1. Third Parties
  2. Performance
  3. Compression
  4. Caching
  5. CDN
  6. Page Weight

@rviscomi
Copy link
Member Author

@flowlabs that would be great! The ones most in need of reviewers are Third Parties and Page Weight. I'll put you down for those. Thanks!

@flowlabs
Copy link

@rviscomi Cool! Looking forward to helping :)

@rviscomi rviscomi closed this as completed Jun 4, 2019
@rviscomi rviscomi added this to the Chapter planning complete milestone Jun 4, 2019
@rviscomi rviscomi unpinned this issue Jun 7, 2019
@MSakamaki MSakamaki mentioned this issue Jun 12, 2019
Closed
2 tasks
@AymenLoukil
Copy link
Contributor

Hello @rviscomi i had already expressed my interest to contribute but i was in a rush period. Is that stills possible ? Please tell me on which part(s) could i help ? Thanks !

@rviscomi
Copy link
Member Author

👋 Hi @AymenLoukil, it'd be great to have your help! We could use additional reviewers on the Markup, Fonts, PWA, and Mobile Web chapters. Do any of these sound like a good fit for you?

@AymenLoukil
Copy link
Contributor

Hi @rviscomi :) Great ! I could review #7 Fonts and #14 Mobile

@rviscomi
Copy link
Member Author

Thanks @AymenLoukil! I've assigned you as a reviewer for those chapters and sent you an invitation to the Reviewers team. You can accept it via email or visit https://github.com/HTTPArchive.

We're currently in the data analysis phase, so there won't be much work for you to do until ~August. You can learn more about our timeline here. Meanwhile you can look over the list of metrics that have been agreed on for those chapters to become familiar with their contents. Let us know if anything is glaringly missing/wrong.

@AymenLoukil
Copy link
Contributor

Super @rviscomi ! Thanks.

allemas added a commit that referenced this issue Mar 6, 2020
@allemas @borisschapira @tunetheweb
Translation of caching chapter to French (#669)
b19af35 
* start traduction

* process trad

* # This is a combination of 9 commits.
# This is the 1st commit message:

update

# The commit message #2 will be skipped:

# review

# The commit message #3 will be skipped:

# review #2

# The commit message #4 will be skipped:

# advance

# The commit message #5 will be skipped:

# update

# The commit message #6 will be skipped:

# update translation

# The commit message #7 will be skipped:

# update

# The commit message #8 will be skipped:

# update
#
# update

# The commit message #9 will be skipped:

# update

* First quick review

(typofixes, translating alternatives)

* Preserve original line numbers

    To facilitate the review of original text vs. translation side-by-side.

Also: microtypo fixes.

* Review => l338

* End of fine review

* Adding @allemas to translators

* Rename mise-en-cache to caching

* final updates

* update accessibility

* merge line

* Update src/content/fr/2019/caching.md

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

* Update src/content/fr/2019/caching.md

If it's not too much effort, could you also fix this in the English version as part of this PR as looks wrong there:

6% of requests have a time to time (TTL)

should be:

6% of requests have a Time to Live (TTL)

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

* Update src/content/fr/2019/caching.md

Do we need to state that all the directives are English language terms or is that overkill? If so need to check this doesn't mess up the markdown->HTML script.

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

Co-authored-by: Boris SCHAPIRA <borisschapira@gmail.com>
Co-authored-by: Barry Pollard <barry_pollard@hotmail.com>
tunetheweb added a commit that referenced this issue Mar 6, 2020
@allemas @borisschapira @tunetheweb
Translation of Caching chapter to French (#679)
4c164bb 
* start traduction

* process trad

* # This is a combination of 9 commits.
# This is the 1st commit message:

update

# The commit message #2 will be skipped:

# review

# The commit message #3 will be skipped:

# review #2

# The commit message #4 will be skipped:

# advance

# The commit message #5 will be skipped:

# update

# The commit message #6 will be skipped:

# update translation

# The commit message #7 will be skipped:

# update

# The commit message #8 will be skipped:

# update
#
# update

# The commit message #9 will be skipped:

# update

* First quick review

(typofixes, translating alternatives)

* Preserve original line numbers

    To facilitate the review of original text vs. translation side-by-side.

Also: microtypo fixes.

* Review => l338

* End of fine review

* Adding @allemas to translators

* Rename mise-en-cache to caching

* final updates

* update accessibility

* merge line

* Update src/content/fr/2019/caching.md

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

* Update src/content/fr/2019/caching.md

If it's not too much effort, could you also fix this in the English version as part of this PR as looks wrong there:

6% of requests have a time to time (TTL)

should be:

6% of requests have a Time to Live (TTL)

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

* Update src/content/fr/2019/caching.md

Do we need to state that all the directives are English language terms or is that overkill? If so need to check this doesn't mess up the markdown->HTML script.

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

* generate caching content in french

* Update src/content/fr/2019/caching.md

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

* Update src/content/fr/2019/caching.md

Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com>

Co-authored-by: Boris SCHAPIRA <borisschapira@gmail.com>
Co-authored-by: Barry Pollard <barry_pollard@hotmail.com>
@gregorywolf gregorywolf mentioned this issue Sep 12, 2020
Merged
17 tasks
This was referenced Jul 19, 2021
Closed
Closed
rviscomi pushed a commit that referenced this issue Nov 24, 2021
@eeeps
Merge pull request #2 from akshay-ranganath/main
2fe4cfc 
Adding queries from past year
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rviscomi rviscomi

Labels
None yet
Projects
None yet
Milestone
Chapter planning complete
Development

No branches or pull requests
7 participants
@foxdavidj @bkardell @flowlabs @rviscomi @Yonet @AymenLoukil @nadinarama