-
Notifications
You must be signed in to change notification settings - Fork 8
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
I would like to contribute #1
Comments
You've been added. If you're unfamiliar with ReSpec and the specific practices used for JSON-LD specs, we can communicate on a call or offline. Leaving the issue open for more participants. If not a CG member, you can join at https://www.w3.org/community/json-ld/participants. |
@gkellogg already in the json-ld community. Thanks++ |
Yes, I checked before adding you to the YAML-LD Team, the note was for anyone else that wants to join the team. |
@gkellogg Please add me too. I applied for CG membership (I'm in several CGs so that should be able to go through quickly) |
Done. |
@gkellogg I am interested in contributing where I can, so would like to join as well. I just sent a request to join the CG. (This would be the first standardization activity for me.) Thanks to everyone for making this happen! |
Welcome! The next meeting will be in two weeks on July 6th at 18:00 UTC. In the meantime, work proceeds on the existing issues. We're actively looking for new Use Cases, so please generate issues as appropriate. |
Dear folks,
I would be happy to contribute, since I'm working on the YAML media type registration https://ietf-wg-httpapi.github.io/mediatypes/draft-ietf-httpapi-yaml-mediatypes.html
and we already have an issue related to the registration of ld+yaml media type.
cc: @eemeli
The text was updated successfully, but these errors were encountered: