archiving WebVR related repositories (and so on) (was: Re: Immersive Web Community Group Teleconference - 2026-04-07)

   hi IWCG (cc to IWWG for info share)



On 2026/04/07 3:41, Ada Rose Cannon wrote:
> 
>       Call Agenda
> 
> This agenda can be viewed and updated on _Github_ <https://github.com/immersive-web/administrivia/blob/main/meetings/2026/2026-04-07-Immersive_Web_Community_Group_Teleconference-agenda.md>.
> 
> If you would like to add an item to the agenda or volunteer to scribe please open a pull request against this agenda.
> 
>   *
> 
>     _administrivia#239 Archive WebVR related repositories_ <https://github.com/immersive-web/administrivia/issues/239>_requested by AdaRoseCannon_ <https://github.com/immersive-web/administrivia/issues/239#issuecomment-4157092562>
> 
>     lets let the CG know at least before we archive them.



   As mentioned during the latest IW Group call, we (me as staff contact for IWWG, sorry but no role in CG;
and CG co-chairs) would turn following repositories as archived per github meaning:
https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories
   Please note, archiving does not affect to any content at the repository URL nor github.io. So you could
access to any content already on the web including git history or issues, just archived as read only content.
Also we can revert archiving any repository once we decided to resume activity in future.

   If there is no objection by end of this week (e.g. 11 April), I will update README.md (via PR or direct
commit) and archive them.
   Please note that decision is already made during group call for CG at 7 April, and this email is just
for info-share.
# by the end of this week, just means, I don't think I could take action before that...


   Please see details at following issue, and also please comment to the issue if you think any of listed one
shall not be archived (by means you are willing to actively update or work on issues). And you can find text
to be included in README at the top of target repositories for stating clause and information of archiving.
https://github.com/immersive-web/administrivia/issues/239

WebVR related repositories:
     webvr https://github.com/immersive-web/webvr
     webvr-polyfill https://github.com/immersive-web/webvr-polyfill
     cardboard-vr-display https://github.com/immersive-web/cardboard-vr-display
     webvr-polyfill-dpdb https://github.com/immersive-web/webvr-polyfill-dpdb
     webvrrocks https://github.com/immersive-web/webvrrocks

also stalled repositories in CG space (with clause):
     community-resources https://github.com/immersive-web/community-resources
         one issue added with no comment. no commit after created by toji at 2018.
         discussions could go to proposals repository. and resources like logo or images could go homepage repository or something.
     ar-common https://github.com/immersive-web/ar-common
         created for cross-API on AR at 2019, but no issue,PR raised after that. even if we need something, we could use proposals or webxr-ar-module for hosting such discussion?
     performance-improvements https://github.com/immersive-web/performance-improvements
         last issue was 2019-Jan, no update from 2020. Incubation could go proposals repository, and no dedicated one is required for now.
     detached-elements https://github.com/immersive-web/detached-elements
         no issue,PR raised. only initial commits exist, made at 2020.
     immersive-web-weekly https://github.com/immersive-web/immersive-web-weekly
         host of ImmersiveWebWeekly.com, domain exists but server disappeared?
     privacy-and-security https://github.com/immersive-web/privacy-and-security
         open issue kept left (w/o activity) since 2020, and also we develop more in webxr repository including horizontal reviews on our specifications. Do we want to keep this one, or merge into webxr one and archive this repository?
     occlusion ref: issue exists to merge depth-sensing into this : Should depth-sensing be merged into this? occlusion#2

Received on Thursday, 9 April 2026 00:03:47 UTC