search

w3c / web-performance

W3C Web Performance Working Group repo
https://www.w3.org/webperf/
Other
411 stars 69 forks source link

Autopublish specs #34

Open marcoscaceres opened 3 years ago

marcoscaceres commented 3 years ago

It would be great to work out a plan for us to auto publish all the Web Perf specs. We could use spec-prod to make that happen: https://github.com/w3c/spec-prod

@caribouW3, would be great for us to work on this together.

caribouW3 commented 3 years ago

The WG had a CfC on this recently: https://lists.w3.org/Archives/Public/public-web-perf/2021Apr/0005.html A number of specs are set to auto-publish. Which one specifically are you looking at?

marcoscaceres commented 3 years ago

Here is what we can copy to auto-publish any BikeShed specs (updating the various keys, of course): https://github.com/w3c/clipboard-apis/pull/145/files

Similarly, for ReSpec specs: https://github.com/w3c/manifest/blob/gh-pages/.github/workflows/action.yml

marcoscaceres commented 3 years ago

To get a token:

To save that token:

marcoscaceres commented 3 years ago

Updated list of specs above based on charter.

marcoscaceres commented 3 years ago

For the W3C_WG_DECISION_URL, we've used use the following in the past: https://www.w3.org/2015/06/24-webperf-minutes.html#item01 ....

However, that one is not super great (though suitable)... it might be worth sending another email to the mailing list.

marcoscaceres commented 3 years ago

Ah whoops! @caribouW3, just remembered/saw you posted https://github.com/w3c/web-performance/issues/34#issuecomment-832672839 above... that link is perfect for W3C_WG_DECISION_URL! thank you.

marcoscaceres commented 3 years ago

@caribouW3, wrote

A number of specs are set to auto-publish. Which one specifically are you looking at?

I'm thinking all of them. I added the list of all the specs above.

If they are still using travisci, we should move off that. Similarly, we should move off using the various scripts for bikeshed and just use spec-prod.

marcoscaceres commented 3 years ago

@caribouW3, could you identify the specs where we can drop the levels (probably all of them)? And if so, what we need to do (e.g., if we need to request a new short name?). Then we can plan out a bit more how we approach all these.

marcoscaceres commented 3 years ago

Ok, Page Visibility should hopefully be good with: https://github.com/w3c/page-visibility/pull/71

@caribouW3, I also sent: https://github.com/w3c/spec-prod/pull/69

Which will hopefully help a bit with getting started. Would appreciate your feedback!

Let me know how you want to proceed with the rest!

marcoscaceres commented 3 years ago

@caribouW3, for the rest, we can probably copy what I did for each of:

  1. clean up the repository's root
  2. If ReSpec spec, tidy up spec + add tidy.yml workflow
  3. If ReSpec spec, clean up ReSpec config
  4. Setup auto-publish
  5. If groups agrees, Add PULL_REQUEST_TEMPLATE
  6. General xref usage cleanup. - https://respec.org/docs/#Shorthands-Guide

Let me know of you want to do a few together!