Skip to content

Create MoM-30-10-2023#91

Merged
rartych merged 1 commit intomainfrom
rartych-patch-4
Dec 7, 2023
Merged

Create MoM-30-10-2023#91
rartych merged 1 commit intomainfrom
rartych-patch-4

Conversation

@rartych
Copy link
Contributor

@rartych rartych commented Nov 14, 2023

What type of PR is this?

  • subproject management

What this PR does / why we need it:

MoM-30-10-2023

@rartych rartych changed the title Create MoM-16-10-2023 Create MoM-30-10-2023 Nov 24, 2023
@eric-murray
Copy link
Collaborator

It might be easier to use the CAMARA wiki for meeting minutes in future rather than continue to use github

Copy link
Contributor

@patrice-conil patrice-conil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/LGTM

| Issue<br> [#77](https://github.com/camaraproject/Commonalities/issues/77) | **Response Headers** <br> Eric will rise the PR clarifying use of non-standard headers like X-Correlator. There are different views on presence of header definitions in CAMARA YAML files. More comment expected.|
| Issue<br> [#71](https://github.com/camaraproject/Commonalities/issues/71) | **basePath in servers.url** <br> This issue should be covered within Release Management activity. |
| Issue<br> [#67](https://github.com/camaraproject/Commonalities/issues/67) | **Open points for release management** <br> Presentation prepared by Herbert and Ludovic for TSC discussion is available in [Governance repository](https://github.com/camaraproject/Governance/raw/b62e6214f06f8a88a5870d00584fbf8126f3cd58/documentation/MeetingMinutes/TSC/TSC-2023-10-19-Release-Management.pptx.pptx). All interested in participating in this activity should subscribe to [mailing list](https://lists.camaraproject.org/g/release). Linux Foundation will provide training on Release Management best practices. |
| PR [#43](https://github.com/camaraproject/Commonalities/pull/43) | **Event Notification using CloudEvents specification**<br> Review needed after introduced changes. We should have `application/cloudevents+json` instead of `application/json` as content type for event notifications. This point requires updating the example in the DG and probably adding a note. Rajat highlighted that `cloudevents+json` is not part of IANA registration but agreed that we can move forward. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @rartych,
content-type is already set to application/cloudevents+json
but in the example the datacontenttype which is type of data should remain application/json
Do you agree with that?

@rartych rartych merged commit a93e15a into main Dec 7, 2023
@rartych rartych deleted the rartych-patch-4 branch December 7, 2023 11:41
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.

3 participants