public-geolocation@w3.org from March 2022 by author

Anssi Kostiainen via GitHub

• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Wednesday, 9 March)
• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Tuesday, 8 March)
• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Monday, 7 March)

Fuqiao Xue via GitHub

• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Monday, 7 March)

Marcos Cáceres via GitHub

• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Wednesday, 9 March)
• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Wednesday, 9 March)
• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Tuesday, 8 March)
• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Monday, 7 March)
• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Monday, 7 March)

Mike Taylor via GitHub

• [geolocation-api] Pull Request: Editorial: use associated Document in place of responsible document (Monday, 14 March)

Reilly Grant via GitHub

• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Tuesday, 8 March)
• Re: [geolocation-api] Transition to Proposed Recommendation (#121) (Tuesday, 8 March)

Last message date: Monday, 14 March 2022 20:10:07 UTC