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

Open Community Working Meeting 2023-06-12 - 14:00 PT #400

Closed
2 tasks done
benjagm opened this issue Jun 6, 2023 · 3 comments
Closed
2 tasks done

Open Community Working Meeting 2023-06-12 - 14:00 PT #400

benjagm opened this issue Jun 6, 2023 · 3 comments
Labels
Working Meeting Identify working meetings

Comments

@benjagm
Copy link
Collaborator

benjagm commented Jun 6, 2023

Open Community Working Meeting 2023-06-12 - 14:00 PT

📺 See Recording

Go To Previous Meeting

Agenda:

Topic Owner Decision/NextStep
Review last call's action items [facilitator]
As we discussed in the las summit I'd like to help in the spec discussions with some project management. As starting point it will be great to discuss the current status, scope and blockers. @benjagm Create an Issue to allow everyone to share their thoughts
PR #9 - Add header to Github organization's readme @benjagm Modify the banner to make it more similar to the design of the new website
Issue #408 - Identify a list of critical interfaces that implementations should have and empower implementers with better resources @Relequestual Continue the collaboration in the issue.

Action items:

  • @benjagm To discuss with the Design Team to change the banner and make it more alike to the new website landing page.
  • @benjagm To create a discussion to identify together what is in scope for the next Spec Release.

Notes:

  • The group discussed about the issue Identify a list of critical interfaces that implementations should have and empower implementers with better resources #408 . Everyone agreed that it was a good start and that further breakdowns into smaller issues would be necessary for easier tracking and delegation.
  • @benjagm showed the [PR #9 - Add header to Github organization's readme] to add a banner in the top of the org's README to improve the look and feel. @gregsdennis pointed out that there was a subtle fade on the website that needed updating and the text was not vertically centered inside the box. The team suggested to provide a design more similar to the hero section of the new website. @benjagm acknowledged and share with Paul Waller.
  • Benjamin gave an update on the progress of the new website, mentioning that it was almost done, with some minor issues to be solved. He also showed a preview of the documentation view and discussed changes for the mobile version.
  • The last point of the agenda was kickoff the discussion to identify what is in scope for the next Spec Release with the objective of start doing some project management to ease the progress. The conversation started in this session but the team agreed on creating an Issue to allow everyone to share their thoughts. Find below some of the topics discussed:
    • The need for stable and unique URIs for releases.
    • The implications of changing the default for a $ schema.
    • They also talked about the possibility of introducing a new stable URI for big changes in the future.

Attendees

Account
@jdesrosiers
@Relequestual
@benjagm
@gregsdennis
@Julian
@jviotti
@AgniveshChaubey
@benjagm benjagm added the Working Meeting Identify working meetings label Jun 6, 2023
@benjagm
Copy link
Collaborator Author

benjagm commented Jun 20, 2023

Marking as completed the action item related #9 because the Contributing banner has been updated with the feedback provided.

@benjagm
Copy link
Collaborator Author

benjagm commented Jun 20, 2023

Marking as completed the action item "create a discussion to identify together what is in scope for the next Spec Release". The related issue is #415 .

@benjagm
Copy link
Collaborator Author

benjagm commented Jun 20, 2023

Closed with all actions completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Working Meeting Identify working meetings
Projects
None yet
Development

No branches or pull requests

1 participant