-
Notifications
You must be signed in to change notification settings - Fork 40
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
Update contact information for Team page #402
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jennaswa !
I will opt out of including myself in community engagement, but will opt in for project organization.
Re: the build failure, I suspect the autogeneration from yaml might not like the links so much. @lilyminium would be best suited to weigh in on this.
Re: github failure -- yup, I hadn't included Markdown support in the teams pages. I've opened #403 to include this so that should fix it. However, the caveat is that the initial YAML still has to be valid, so all the team member links should be encapsulated in quotes to tell YAML it's a string and not a list. (i.e. |
Added non-blocking comments for quotes. Otherwise LGTM -- thanks for this @jennaswa! |
Co-authored-by: Irfan Alibay <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
…tting Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
Co-authored-by: Lily Wang <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for the delayed response! I’ve added myself to the teams now.
Per the discussion in #397, the main purpose of this PR is to:
In addition, this would provide a good opportunity to update team members in preparation for our first upcoming R&R review, as decided in the Aug 20 business meeting. Namely:
Thanks!