profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/dontcallmedom/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

darobin/webref 2

References for Web Specifications (http://webref.herokuapp.com/)

dontcallmedom/api-design-cookbook 2

A cookbook for Web API design

dontcallmedom/canon-singing 2

A node-based Web app to record and play a distributed canon song (Frère Jacques for now)

darobin/vision-old 1

Web Vision

dontcallmedom/adoption-monitor 1

https://dontcallmedom.github.io/adoption-monitor/

dontcallmedom/bikeshed 1

:bike: A preprocessor for anyone writing specifications that converts source files into actual specs.

dontcallmedom/code-talks 1

An HTML-based code displayer, that allows to talk through the creation of a piece of a code (e.g. for a tutorial)

dontcallmedom/android 0

The ownCloud Android App

dontcallmedom/apa 0

Accessible Platform Architectures WG deliverables

create barnchw3c/webrtc-pc

branch : respec-26.9.4

created branch time in 2 days

PR opened w3c/webrtc-pc

Update to latest ReSpec version

Automated changes by create-pull-request GitHub action

+204 -198

0 comment

1 changed file

pr created time in 2 days

delete branch w3c/webrtc-pc

delete branch : respec-26.9.4

delete time in 9 days

PR closed w3c/webrtc-pc

Update to latest ReSpec version Editorial

Automated changes by create-pull-request GitHub action

+204 -198

1 comment

1 changed file

dontcallmedom

pr closed time in 9 days

pull request commentw3c/webrtc-pc

Update to latest ReSpec version

needs the changes in #2663, so closing without merging

dontcallmedom

comment created time in 9 days

delete branch w3c/mediacapture-main

delete branch : respec-26.9.4

delete time in 9 days

push eventw3c/mediacapture-main

dontcallmedom

commit sha 66835270e230ce54b750ec17f5bda355d05bddb1

Update to latest ReSpec version

view details

Dominique Hazael-Massieux

commit sha 3037fc11efeaeca17653de0e83469f55d9b2d35a

Merge pull request #807 from w3c/respec-26.9.4 Update to latest ReSpec version

view details

push time in 9 days

PR merged w3c/mediacapture-main

Update to latest ReSpec version editorial

Automated changes by create-pull-request GitHub action

+187 -183

0 comment

1 changed file

dontcallmedom

pr closed time in 9 days

pull request commentw3c/browser-specs

Monitor MathML 4 spec

given that it's unlikely to be browser targeting, is there any reason not to put it in the ignore list?

tidoust

comment created time in 9 days

PullRequestReviewEvent

create barnchw3c/webrtc-pc

branch : respec-26.9.4

created branch time in 9 days

PR opened w3c/webrtc-pc

Update to latest ReSpec version

Automated changes by create-pull-request GitHub action

+204 -198

0 comment

1 changed file

pr created time in 9 days

create barnchw3c/mediacapture-main

branch : respec-26.9.4

created branch time in 9 days

PR opened w3c/mediacapture-main

Update to latest ReSpec version

Automated changes by create-pull-request GitHub action

+187 -183

0 comment

1 changed file

pr created time in 9 days

issue commentw3c/ash-nazg

Work jointly done by a CG & a WG

no work needed in ash-nazg on this, closing the issue

dontcallmedom

comment created time in 12 days

issue closedw3c/ash-nazg

Work jointly done by a CG & a WG

There are at least two reasonably clear cases of WGs that want to operate their repositories under the joint aegis of a WG and a CG: WebAssembly and WebGPU.

Right now, the IPR manager isn't able to handle this case, and requires joint work to be under groups of the same type (either several WGs, or several CGs).

A possible model for an IPR check on joint CG/WG work would be:

  • if contributor is covered by WG IPR commitment, OK
  • if contributor is covered by CG IPR commitment (but not WG), flag the need to obtain an FSA commitment
  • otherwise, flag as needing action

@wseltzer thoughts?

closed time in 12 days

dontcallmedom

issue commentmdn/browser-compat-data

Issue with "KeyboardEvent.metaKey": I don't think this works on Firefox but is marked as compatible

Would it be worth documenting in the BCD section itself (and thus in the data) the fact that the Windows key is no longer considered the metaKey since FF48?

KibiH

comment created time in 12 days

PullRequestReviewEvent

delete branch w3c/webrtc-identity

delete branch : upgrade-infra

delete time in 13 days

pull request commentw3c/webrtc-identity

Upgrade respec version to deal with latest WebIDL support

The error linked to [[IsClosed]] is a combination of waiting for a respec upgrade in WebRTC, and then the WebRTC spec needing to mark the said internal slot as exported.

Since the current spec is more broken than this, I'll merge with error pending.

dontcallmedom

comment created time in 13 days

push eventw3c/webrtc-identity

Dominique Hazael-Massieux

commit sha e6b246d087e7145dcd5a4216315a568fdb0ac521

Use reference to internal slot for IsClosed

view details

push time in 13 days

PR opened w3c/webrtc-identity

Upgrade respec version to deal with latest WebIDL support

close #34

+1281 -883

0 comment

10 changed files

pr created time in 13 days

create barnchw3c/webrtc-identity

branch : upgrade-infra

created branch time in 13 days

issue closedw3c/ash-nazg

Metaverse Interoperability Community Group missing from list

I'm trying to import a repository in to the repo manager, but our community group isn't on the list of groups. Could add the metaverse-interop community group? I'm trying to add the IPR bot, w3c.json, etc. Thanks!

closed time in 13 days

robertlong
PullRequestReviewEvent
PullRequestReviewEvent

issue openedw3c/ash-nazg

Report operational errors

There are at least two ways the checker can fail to process a pull request:

  • it doesn't recognize the repo (e.g. after a name change #64)
  • the secret used to verify the origin of the check is wrong (which has happened a number of times, although I'm not sure how)

… and probably more. Right now, these failures are simply logged as a webook failure - useful for debugging, not for noticing there is a configuration issue.

These should instead be reported - either on the pull request itself, or on this repo (probably both - e.g. it could stay in "pending" state on the pull request status with an appropriate message, while reporting the issue here).

created time in 13 days

PullRequestReviewEvent

issue commentw3c/ash-nazg

Metaverse Interoperability Community Group missing from list

group now added - let us know if you encounter any other hiccup in the process

robertlong

comment created time in 13 days