From 0cfcf5d8d978fd6efa7d32d19722ffe4b624ebbd Mon Sep 17 00:00:00 2001 From: Ace <40604284+AceTheCreator@users.noreply.github.com> Date: Mon, 5 Dec 2022 16:23:48 +0100 Subject: [PATCH 1/6] Update docs/README.md Co-authored-by: Alejandra Quetzalli --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index be78b3aee..117cf44fa 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,3 +1,3 @@ # Community Documetation -The community documentation directory helps the community maintains collaboratively a collection of helpful community-related documentations from how to start contributing to AsyncAPI to how it leverages other technologies to build and enhance it's software. \ No newline at end of file +The community documentation directory helps the community collaboratively maintain a collection of helpful community-related documentation, from how to start contributing to AsyncAPI to how it leverages other technologies to build and enhance its software. \ No newline at end of file From 614911c0d54e435e0a3a188e56c786fa77ade64d Mon Sep 17 00:00:00 2001 From: Ace <40604284+AceTheCreator@users.noreply.github.com> Date: Mon, 12 Dec 2022 14:34:07 +0100 Subject: [PATCH 2/6] Update docs/README.md Co-authored-by: Alejandra Quetzalli --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 117cf44fa..3cd776b35 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,3 +1,3 @@ -# Community Documetation +## Community Documentation The community documentation directory helps the community collaboratively maintain a collection of helpful community-related documentation, from how to start contributing to AsyncAPI to how it leverages other technologies to build and enhance its software. \ No newline at end of file From 32a340d95123bd7d2205a8e531ada2865f5957ca Mon Sep 17 00:00:00 2001 From: Ace <40604284+AceTheCreator@users.noreply.github.com> Date: Mon, 12 Dec 2022 14:35:03 +0100 Subject: [PATCH 3/6] Update docs/README.md Co-authored-by: Alejandra Quetzalli --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 3cd776b35..6e1ab147d 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,3 +1,3 @@ ## Community Documentation -The community documentation directory helps the community collaboratively maintain a collection of helpful community-related documentation, from how to start contributing to AsyncAPI to how it leverages other technologies to build and enhance its software. \ No newline at end of file +The community documentation directory helps the community collaboratively maintain a collection of helpful community-related documentation. From becoming an AsyncAPI contributor to becoming a TSC member, and beyond. \ No newline at end of file From 8e8874e0b84e7c5310ef23d380b4057d6fbe4f34 Mon Sep 17 00:00:00 2001 From: Ace <40604284+AceTheCreator@users.noreply.github.com> Date: Mon, 12 Dec 2022 14:35:18 +0100 Subject: [PATCH 4/6] Update docs/how-changes-in-the-spec-are-introduced.md Co-authored-by: Alejandra Quetzalli --- docs/how-changes-in-the-spec-are-introduced.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-changes-in-the-spec-are-introduced.md b/docs/how-changes-in-the-spec-are-introduced.md index eec7cdb16..b12b17e63 100644 --- a/docs/how-changes-in-the-spec-are-introduced.md +++ b/docs/how-changes-in-the-spec-are-introduced.md @@ -1,6 +1,6 @@ ** -# How spec changes are introduced +## How spec changes are introduced AsyncAPI Initiative always concentrates on the problems rather than the solution. This is because you are generally rather single-minded when you already have a solution in mind to a problem instead of fully diving into the issue, seeing alternatives, and finding the best solution.  ### RFCs & champions From cccd4b82d88c878c3380c23171179f3ed8e5ff58 Mon Sep 17 00:00:00 2001 From: Ace <40604284+AceTheCreator@users.noreply.github.com> Date: Mon, 12 Dec 2022 14:35:36 +0100 Subject: [PATCH 5/6] Update docs/how-changes-in-the-spec-are-introduced.md Co-authored-by: Alejandra Quetzalli --- docs/how-changes-in-the-spec-are-introduced.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-changes-in-the-spec-are-introduced.md b/docs/how-changes-in-the-spec-are-introduced.md index b12b17e63..199786fa7 100644 --- a/docs/how-changes-in-the-spec-are-introduced.md +++ b/docs/how-changes-in-the-spec-are-introduced.md @@ -49,7 +49,7 @@ This part of the lifecycle aims to describe all details of the process so that a - The coordinator keeps a closed watch on what is merged, documents it in release notes, and engages contributors and maintainers of the spec to collaborate on a release. - Maintainers trigger release when ready, release notes are published, and the world of open source won again. -You can learn more about the release process [here](https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md#what). +Learn more about the [release process](https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md#what). ### Release process visual The image below visualizes the whole process of how changes are introduced to the spec in a single glance. From 68df1b4a4308620dfc96560cb2bfb93108064c3e Mon Sep 17 00:00:00 2001 From: Ace <40604284+AceTheCreator@users.noreply.github.com> Date: Mon, 12 Dec 2022 14:40:42 +0100 Subject: [PATCH 6/6] Update docs/how-changes-in-the-spec-are-introduced.md Co-authored-by: Alejandra Quetzalli --- docs/how-changes-in-the-spec-are-introduced.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/how-changes-in-the-spec-are-introduced.md b/docs/how-changes-in-the-spec-are-introduced.md index 199786fa7..f523dc997 100644 --- a/docs/how-changes-in-the-spec-are-introduced.md +++ b/docs/how-changes-in-the-spec-are-introduced.md @@ -1,4 +1,3 @@ -** ## How spec changes are introduced AsyncAPI Initiative always concentrates on the problems rather than the solution. This is because you are generally rather single-minded when you already have a solution in mind to a problem instead of fully diving into the issue, seeing alternatives, and finding the best solution.