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

Create 2020.12.01_meeting-notes.md #118

Merged
merged 1 commit into from
Mar 11, 2021
Merged

Create 2020.12.01_meeting-notes.md #118

merged 1 commit into from
Mar 11, 2021

Conversation

jorydotcom
Copy link
Contributor

Adds notes for our brainstorming session

Adds notes for our brainstorming session
Base automatically changed from master to main February 2, 2021 19:39
@christian-bromann
Copy link
Member

Love the direction ❤️

From the WebdriverIO perspective I would love to collaborate with other OpenJS projects e.g. AMP when it comes to testing. This particular aligns to the idea of "filling the cracks". For example: let's say AMP develops a new component to their framework which has certain requirements for automated testing. AMP folks then can say: "Hey we need WebDriver to do that to test our component" and I can help facilitate adding this new automation capability to the WebDriver protocol. We see this already in other working groups, e.g. WHATWG where changes to the spec that require certain automation requirements trigger the creation of additional capabilities in the WebDriver spec. While this example is on a standard level I don't see a reason why this process wouldn't work on an application level.

For that it would be interesting to find out which WG members participate in which standards WG. Extending the format of the MEMBER_REPRESENTATION.md could be a solution to that.

I would love to see this working group help OpenJS project members support their endeavours into the standards world. It can start with just providing materials to certain topics and go as far as hosting workshops to specific areas (e.g. note taking, spec editing etc.).

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

Successfully merging this pull request may close these issues.

4 participants