Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tool to extract session chair contact information #18

Closed
ianbjacobs opened this issue May 19, 2023 · 3 comments
Closed

Tool to extract session chair contact information #18

ianbjacobs opened this issue May 19, 2023 · 3 comments

Comments

@ianbjacobs
Copy link
Contributor

For communications before and after TPAC with session chairs, it would be handy to be able to extract the contact information for email.

@ianbjacobs ianbjacobs changed the title Tool to extra session chair contact information Tool to extract session chair contact information May 19, 2023
@ianbjacobs
Copy link
Contributor Author

Proposal:

  • By default, person who raised the issue is (at least one of) the session proposals for the purposes of communications.
  • The person who raised the issue can identify additional proponents through a form field. They identify proponents via their GitHub labels.
  • In case we need to merge sessions, we will do so manually, possibly by creating a new issue. So in some cases (like this), the proposer of the session will not be relevant for ongoing communications.
  • Internally, we will map GitHub identities to W3C identities (where there is a binding) to extract contact information.

@ianbjacobs
Copy link
Contributor Author

Solution: We will get info from W3C database via link with W3C accounts. When there is no link to a W3C account, we will work around the situation (e.g., by reaching out to the GitHub account owner).

@tidoust
Copy link
Member

tidoust commented Jun 21, 2023

Local mapping done through a CHAIR_W3CID environment (and GitHub repo) variable. What remains is a documentation effort, tracked in #27.

@tidoust tidoust closed this as completed Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants