Philippe Le Hégaret | @[email protected]

[Philippe Le Hégaret | @[email protected] @plhw3org]

fyi, https://t.co/LnjuuiWvhJ

[Philippe Le Hégaret | @[email protected] @plhw3org]

@christianliebel @w3c They used to have a meaning in a past TPAC. For TPAC 2022. Orange is staff, and other colors are simply "others"

[Philippe Le Hégaret | @[email protected] @plhw3org]

Getting ready for W3C TPAC 2022. @w3c

[Philippe Le Hégaret | @[email protected] @plhw3org]

@marcosc @WHATWG @w3c if I have time before the flight, I'll stop by the office and see if I can find some

[Philippe Le Hégaret | @[email protected] @plhw3org]

@marcosc @WHATWG @w3c We did W3C pins a while back. I probably have one or two of them in the bottom of a drawer...

[Philippe Le Hégaret | @[email protected] @plhw3org]

[TPAC 2022] Video recording on Trainings for hybrid meeting facilitators:
https://t.co/scCrFSNx8Y

[Philippe Le Hégaret | @[email protected] @plhw3org]

@danbri @TzviyaSiegman @davidbaron @jyasskin @w3c I don't see how yet another review will help here. One can easily argue that IDs https://t.co/XLiJId9uDj and proofs https://t.co/NppvIQCqyq are defined as needed in the spec.

[Philippe Le Hégaret | @[email protected] @plhw3org]

Since October 7, the horizontal system is tracking over 100k specifications issues (including 17,5k open issues) @w3c

[Philippe Le Hégaret | @[email protected] @plhw3org]

The different classes of documents published by @w3c and their formal standings: https://t.co/nR7I4a3Mrm

[Philippe Le Hégaret | @[email protected] @plhw3org]

@davidbaron @Google @googlechrome Congrats David!

[Philippe Le Hégaret | @[email protected] @plhw3org]

Automatic Publishing of W3C technical reports (2021-03-18, 13:00 UTC) See https://t.co/ZcAMRckXO5

[Philippe Le Hégaret | @[email protected] @plhw3org]

"All new features should be supported by at least two intents to implement before being incorporated in the specification"
https://t.co/mhVicROwOu @w3c

[Philippe Le Hégaret | @[email protected] @plhw3org]

We're late in the winter for a migration, but nevertheless: Renaming the master branches: https://t.co/3MSpMnFcZC

[Philippe Le Hégaret | @[email protected] @plhw3org]

@jorydotcom @w3cdevs amusingly, I did not put this on https://t.co/rPJdgb0QyZ and I got the question this week :)

[Philippe Le Hégaret | @[email protected] @plhw3org]

Happy new Year 2021! One of my objectives for this year to rethink how we differentiate technical documents within the spectrum from proposals to standards. @w3c

[Philippe Le Hégaret | @[email protected] @plhw3org]

@annevk @GangMan_ @w3c @WHATWG @thedomstandard @htmlstandard Looking back at https://t.co/YSn2kAp965 , I wasn't sure back then if we can retire safely. I'd welcome feedback on this front.

[Philippe Le Hégaret | @[email protected] @plhw3org]

https://t.co/4wSLYtWlGx is now owned by WICG

[Philippe Le Hégaret | @[email protected] @plhw3org]

Work is progressing on W3C Groups calendar, so make sure to send feedback https://t.co/0dTt7dmlLO

[World Wide Web Foundation @webfoundation]

"We can not forget that the web, for all its faults, is at its best an incredible force for good. We must keep fighting for the kind of web we want, for everyone." - @markdavies67 https://t.co/EoJfa0WjCV

[Philippe Le Hégaret | @[email protected] @plhw3org]

If you are a Working Group participant and want to adopt the latest W3C Patent Policy, make sure your Working Group chair(s) answer the survey this month!