Re: [jlreq] build JL-TF charter for next period from 2023/Jan/01 (#344)

Thank you @himorin for the heads up. All proposals sound good. I will send the note to the list to solicit feedback.

> • mark as jlreq just for errata, and moving a11y improvements into jlreq-d
How do we add the mark? I would appreciate it if you could do the mass move of a11y issues.

There might be other gh issues that should be moved over to jlreq-d. I can't spend much time rght now until spring but let's plan reviewing all remaining issues in jlreq.

> • add a line of license applicable for deliverables?
Could you do this change?

thanks.

-- 
GitHub Notification of comment by kidayasuo
Please view or discuss this issue at https://github.com/w3c/jlreq/issues/344#issuecomment-1306715316 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 8 November 2022 06:50:21 UTC