- From: himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Nov 2022 14:28:52 +0000
- To: public-i18n-archive@w3.org
> > • 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. ah, it's for charter, so just stating that was what in my mind. > 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. Yes, and also we can transfer issues from here to jlreq-d repository. Let me take some time to develop 'future' related issues. > > • add a line of license applicable for deliverables? > > Could you do this change? will raise a PR covering all points shortly. -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/jlreq/issues/344#issuecomment-1308850043 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 November 2022 14:28:54 UTC