search

whatwg / participant-data

How we track participants in the WHATWG
https://participate.whatwg.org/agreement
Other
32 stars 52 forks source link

Verify Keio University #29

Closed foolip closed 4 years ago

foolip commented 4 years ago

Also fix Mike's GitHub ID.

foolip commented 4 years ago

@sideshowbarker it's great that you were finally able to get this approved, and I'm so sorry that you had to in the first place.

@annevk @domenic have you done anything in particular when verifying entities? I see there are other unverified entities in the file, and wonder if there is a process?

annevk commented 4 years ago

Verification is triggered by a corresponding contribution.

And yeah, very happy this got resolved.

sideshowbarker commented 4 years ago

I think https://github.com/whatwg/participant-data#maintenance is where the process is documented:

Whenever an individual or entity signs the agreement, an entry is added to the respective JSON file with the verified field set to false. When they then make a contribution, the respective editor will check everything is in order and set the verified field to true or escalate as appropriate. If they do not end up contributing their verified field likely is not changed.

The good news is, I already have PRs that’ve been waiting til we could get the participant-agreement situation unblocked:

I need to look back at each of them and see if they’re still relevant to the current spec (rather than having been superseded by other changes in the meantime), and need to rebase them. But in parallel to that, any of the HTML spec editors can also be reviewing them see. If any of them are still relevant, then after rebasing, we can apply the normal process steps (cited above) to get the participant data updated. (I don’t know, though, if that happens before a PR is merged, or after…)

foolip commented 4 years ago

Thanks for pointing out the docs. It sounds like there's no issue at all verifying before one comes across a PR blocked on it, which in this care there already are though. I see that we don't have branch protection for this repo, but if someone wants to approve it, that'd be great.

annevk commented 4 years ago

In fact, we usually commit directly to master. 😊

foolip commented 4 years ago

I see. Maybe next time I'll feel daring :)