- From: Roy Ran <ran@w3.org>
- Date: Fri, 18 Mar 2022 15:11:58 +0800
- To: "public-apa@w3.org" <public-apa@w3.org>, White, Jason J <jjwhite@ets.org>
- Cc: APA Chairs <group-apa-chairs@w3.org>, Michael Cooper <cooper@w3.org>
- Message-ID: <d26f4a2c-fde9-4b49-b213-52b3ec96beb4@Spark>
Thanks Jason, I will look into those issues. If there is any other issues, please feel free to contact me, or you can also file an issue and assign it to me in GitHub directly. Best, Roy 在 2022年3月18日 +0800 AM1:59,White, Jason J <jjwhite@ets.org>,写道: > Thank you, Roy, for working on it. I noticed some issues with the RQTF repositories migrated so far, which I think I have now fixed. (I apologize for any mistakes I made have made with the fixes.) The “naur” and “saur” repositories weren’t entirely up to date. (I’ve copied the necessary commits over from the APA repository.) References to the bibliography file were failing in all cases except saur (which has its own bibliography file). I’ve imported the bibliography file from the APA repository and corrected the HTML to refer to it. > If anyone notices any remaining issues, I am sure we can address those as well. > When Roy has a chance to work on it, the remote-meetings document will also have the same issue with the bibliography. Recent commits have also been made which modify that document. > > Regards, > > Jason. > > From: Roy Ran <ran@w3.org> > Sent: Thursday, 17 March 2022 5:14 > To: public-apa@w3.org > Cc: APA Chairs <group-apa-chairs@w3.org>; Michael Cooper <cooper@w3.org> > Subject: Fwd: Re: APA GitHub Repository splitting > > Hi all, > > APA GitHub repository starts to be divided into the following repositories [1] according to different work. > > Next step, I will transfer the corresponding Pull Requests and issues to the corresponding repo, and update all the links at the same time. > > It may take me a while to complete all the transfers, during this time, the APA repo will remain unchanged, except that all issues will be transferred to the corresponding repo, other function in APA repo will remain the same, you can continue to use the APA repo to work. > > When all the transfer work is over, I will let everyone know. > > [1] > NAUR: https://github.com/w3c/naur > > XAUR: https://github.com/w3c/xaur > > SAUR: https://github.com/w3c/saur > > RAUR: https://github.com/w3c/raur > > FAST: https://github.com/w3c/fast > > CAPTCHA: https://github.com/w3c/captcha > > media-accessibility-reqs: https://github.com/w3c/media-accessibility-reqs > > payment-accessibility-reqs: https://github.com/w3c/payment-accessibility-reqs > > remote-meetings: https://github.com/w3c/remote-meetings > > maturity-model: https://github.com/w3c/maturity-model > > Thanks, > > Roy > ---------- 转发信息 ---------- > 发件人: Janina Sajka <janina@rednote.net> > 日期: 2022年3月10日 +0800 PM9:03 > 收件人: Roy Ran <ran@w3.org> > 抄送: Matthew Atkinson <matkinson@tpgi.com>, APA Chairs <group-apa-chairs@w3.org> > 主题: Re: APA GitHub Repository splitting > > > > quote_type > > Thanks, Roy. If this is our current preferred scheme, I see no problems; > > but please see a few comments in line below. > > Roy Ran writes: > > > > > Hi Janina, Matthew, > > > > > > I split APA GitHub repo as follow as request, if there is no problem, I will start to transfer all issues into corresponding repositories and archive the APA repo. > > > > > > NAUR: https://github.com/w3c/naur > > This one is in active development, so let's coordinate the move so as > > not to leave pull requests or branches orphaned. > > > > > > > XAUR: https://github.com/w3c/xaur > > This one is a finished Note on TR. So, the TR should be updated to point > > to this location for "Latest Editor's Draft." > > > > > > > SAUR: https://github.com/w3c/saur > > Same as NAUR -- active development and let's coordinate with Josh and > > Jason. > > > > > > > RAUR: https://github.com/w3c/raur > > Same as XAUR, this one is a finished Note on TR so will also need an > > update in the TR copy. > > > > > > > FAST: https://github.com/w3c/fast > > Asking Michael and Josh about this status, please. This is also active, > > afaik. > > > > > > > CAPTCHA: https://github.com/w3c/captcha > > Also active, but OK to move. There is a final Note from 2019 for which > > this will be the latest Editor's Draft, so we need to update TR. > > However, no PR are expected on this one for a week or more. > > > > > > > media-accessibility-reqs: https://github.com/w3c/media-accessibility-reqs > > Also a finished Note (from 2015). Will need to fix Editor's Draft link > > on the TR page. > > > > > > > payment-accessibility-reqs: https://github.com/w3c/payment-accessibility-reqs > > This one is abandoned. Can we ship it to /dev/null? > > > > > > > remote-meetings: https://github.com/w3c/remote-meetings > > This is another recently finished Note on TR. We are creating a cross > > reference in SAUR to it, so please involve Jason White when you move > > this one. > > > > > > > maturity-model: https://github.com/w3c/maturity-model > > > > This is the perfect time to move this one. We hope to resume work on it > > early April. > > > > > > > > > > > > > Best, > > > > Janina > > > > > > > Best, > > > > > > Roy > > > > -- > > > > Janina Sajka > > (she/her/hers) > > https://linkedin.com/in/jsajka > > > > Linux Foundation Fellow > > Executive Chair, Accessibility Workgroup: http://a11y.org > > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > > Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa > > > > This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. > > Thank you for your compliance.
Received on Friday, 18 March 2022 07:12:15 UTC