chore(blog): add article with summary of 2nd half of 2021 at asyncapi

pages/blog/events2021.md

@@ -12,7 +12,6 @@ authors:
     link: https://twitter.com/derberq
     byline: AsyncAPI Maintainer and Dev Comm Keeper
 excerpt: It is official! October is an AsyncAPI Hacking Fest! and November 16-18 a 2nd online AsyncAPI Conference
-featured: true
 ---
 
 AsyncAPI Community organizes two important events in the second half of 2021:

pages/blog/hackathon-faq.md

@@ -12,7 +12,6 @@ authors:
     link: https://twitter.com/derberq
     byline: AsyncAPI Maintainer and Community Guardian
 excerpt: Answers to all the questions you ever wanted to ask about the AsyncAPI Hackathon 2021
-featured: true
 ---
 
 Last year was the first time we hosted the AsyncAPI Conference. This year, we're going to host our first AsyncAPI Hackathon. This article tries to address the many questions coming from our community. 😀

pages/blog/july-december-2021-at-asyncapi.md

@@ -0,0 +1,171 @@
+---
+title: 2nd half of 2021 at AsyncAPI
+date: 2021-12-17T06:00:00+01:00
+type: Communication
+tags:
+  - Project Status
+cover: /img/posts/july-december-2021-at-asyncapi/cover.webp
+authors:
+  - name: Lukasz Gornicki
+    photo: /img/avatars/lpgornicki.webp
+    link: https://twitter.com/derberq
+    byline: AsyncAPI Maintainer and Community Guardian
+excerpt: It has been a while since the last update on the things at AsyncAPI Initiative. Lots of things have happened since June. You better have a read or listen to the podcast. 
+featured: true
+---
+
+Around August, I communicated that because vacation is a dead season (in Poland we call it cucumber time) I will not do my monthly updates and write a single vacation summary.
+
+Well, the thing is that vacations were not as quiet as I expected. In September, a carousel started that was impossible to stop.
+
+I started writing status updates bi-weekly in early 2020. These were about simple improvements in specific libraries, very detailed on libraries release level. Back then, I basically knew every single new thing happening in the initiative. This year I switched to monthly updates as there was simply too much happening, and I could not really do those bi-weekly. I also started picking the most important news as there were too many things happening.
+
+I submit my official apologies to those awaiting my update-related articles. Honestly, looking at the size of the community and the growth that we are noticing, I don't know how I'll manage to publish these regularly in 2022. Maybe we should start writing those as a collective. 
+
+What I can promise for sure is that in January 2022 I will write a summary article about AsyncAPI growth in 2021. 
+
+## More regular live-streams
+
+We started two live streams under the AsyncAPI brand:
+- **Thinking Out Loud** is hosted by AsyncAPI Founder (Fran Mendez). He invites different community members to talk about AsyncAPI specification. All recordings are available [in the official YouTube playlist](https://www.youtube.com/playlist?list=PLbi1gRlP7pigPxRRylHGCvpdppYLmSKfJ). Fran plans to continue doing them in 2022 as well,
+- **Contributor-first** is strictly targeted at new or existing contributors. Any AsyncAPI Technical Steering Committee member can volunteer as a host and talk about specific contribution-related topics. We aim to have it as frequently as possible, at least once a week. All recordings are available [in the official YouTube playlist](https://www.youtube.com/playlist?list=PLbi1gRlP7pigPBrBMaNQhUeniR1pdDMiY). Basing on the community feedback, live stream will be renamed to **Let's talk about contributing** in 2022.
+
+Hosting these live streams is all possible thanks to great support from [Restream.io](https://restream.io/) folks who gave us free access to the tool that enables us to live stream directly all our social media channels.
+
+All official meetings are always listed:
+- in [our Community repository](https://github.com/asyncapi/community/labels/meeting)
+- in [our official Google Calendar](https://calendar.google.com/calendar/u/0/[email protected])
+
+The best way to learn about a new event is to join [our official Google Group](https://groups.google.com/u/1/g/asyncapi-users) that we use as a mailing list for invites.
+
+## Solving publish/subscribe confusion aka possible AsyncAPI 3.0 release in 2022
+
+It is hard to find someone in the community that was not confused by semantics related to **publish** and **subscribe** operations when learning about the AsyncAPI specification. Many people are asking in Slack. People are opening pull requests to fix our documentation, assuming we mixed things up by accident.
+
+There are cases where education is not enough. You can have great docs and education materials. Still, some stuff just needs to be improved and cannot be fixed by documentation.
+
+At the beginning of my tech career, I've learned one sentence from an experienced developer: "documented bug becomes a feature". Sometimes you do not have a chance to learn from the bests :sweat_smile:
+
+This is causing too much confusion and needs to be solved in 2022. It is probably not possible without a breaking change in the specification. 
+
+Please join us and help us improve not only the specification but also update tooling:
+- [Proposal to solve publish/subscribe confusion](https://github.com/asyncapi/spec/issues/618)
+- [The many meanings of an AsyncAPI file](https://github.com/asyncapi/spec/issues/628)
+
+## Google Summer of Code Summary
+
+We closed holidays 2021 with massive success of the [Google Summer of Code](https://www.asyncapi.com/blog/march-2021-at-asyncapi#google-summer-of-code) participants. All participants not only finished their projects, but they also became members of AsyncAPI Technical Steering Committee and also got a chance to present their work at AsyncAPI Conference.
+
+- [Aayush Sahu](https://www.linkedin.com/in/aayushmau5) created [Diff](https://github.com/asyncapi/diff)
+  <YouTube id="yILtksZriqA" /> 
+- [Khuda Dad Nomani](https://www.linkedin.com/in/khudadadnomani) created [Optimizer](https://github.com/asyncapi/optimizer)
+  <YouTube id="wHBfRheAero" /> 
+- [Arjun Garg](https://www.linkedin.com/in/arjungarg17) created [Cupid](https://github.com/asyncapi/cupid)
+  <YouTube id="V5H4pmz6yq8" /> 
+- [Elegbede Azeez Wahab aka Ace](https://www.twitter.com/_acebuild) created [Chatbot](https://github.com/asyncapi/chatbot)
+  <YouTube id="pxOrJl2c_DQ" /> 
+- [Nektarios Fifes](https://www.linkedin.com/in/nektarios-fifes-372740220) created [Simulator](https://github.com/asyncapi/simulator). He could not unfortunately join us at the AsyncAPI Conference to talk about his work, but I'm sure he will be open to answer any of your questions asked through GitHub Issues.
+
+It was a pleasure to work with these folks and see them staying with us after GSoC ends. I, therefore [proposed we do it again in 2022 on a larger scale](https://github.com/asyncapi/community/discussions/193).
+
+## Technical Steering Committee members setup
+
+After joining [Linux Foundation (LF)](https://www.asyncapi.com/blog/asyncapi-joins-linux-foundation) and applying the [open governance model](https://github.com/asyncapi/community/blob/master/CHARTER.md) it was a time for us to start setting up a Technical Steering Committee. 
+
+So here we are, 9 months after joining LF, we already have 23 members. Check out [complete list of all the members](https://www.asyncapi.com/community/tsc). Pay attention to those that are marked as **Available for hire**. Don't let folks work for free. Pay them to work on open source. Be good humans.
+
+Do you want to be on that list? Watch :point_down: presentation.
+
+<YouTube id="uG_aLF9Z1F0" /> 
+
+There are lots of things yet missing, like TSC list synchronization, voting process automation, and other things that need lots of work, so if you want to contribute to the project and you are a fan of automation, this is the right topic to help with.
+
+## Welcome Studio and Good Bye Playground
+
+We released a new application that you can use to work on your AsyncAPI files. 
+
+Before, you could use [AsyncAPI Playground](https://playground.asyncapi.com/) but soon we'll start redirecting traffic to new, beautiful :point_right: [AsyncAPI Studio](https://studio.asyncapi.com/) :point_left:
+
+The new Studio has a bright future, and you should expect lots of new features coming there. I definitely recommend checking out [Studio's GitHub repository](https://github.com/asyncapi/studio/).
+
+The cool stuff is that it is also integrated with [AsyncAPI CLI](https://www.asyncapi.com/tools/cli):
+```bash
+#install CLI
+npm install -g @asyncapi/cli
+#create new file using an example
+asyncapi new --file-name=asyncapi.yml --example=default-example.yaml --no-tty
+#start studio that picks up asyncapi.yml file from the context it runs in
+asyncapi start studio
+```
+
+Repository with [Playground source code](https://github.com/asyncapi/playground) will most probably be archived and moved to [organization with old archived projects](https://github.com/asyncapi-archived-repos). 
+
+## Hackathon
+
+This year, we hosted our first [AsyncAPI Hackathon](https://www.asyncapi.com/blog/hackathon-faq). Even though we did not have a dedicated marketing campaign, and even though AsyncAPI is not trivial and requires experience to build tools for it, we received 9 submissions.
+
+[Souvik De](https://www.linkedin.com/in/souvik-de-a2b941169) won first prize with [AsyncAPI Bundler](https://github.com/asyncapi/community/discussions/128). Check out Souvik talking about the AsyncAPI Bundler at AsyncAPI Conference.
+
+<YouTube id="j_KLiCRW3t0" /> 
+
+We also had 2 folks that got into the 2nd place:
+- [Ace](https://www.twitter.com/_acebuild) submitted [AsyncAPI Blocks](https://github.com/asyncapi/community/discussions/149)
+- [Greg Meldrum](https://www.linkedin.com/in/greg-meldrum-8b15a03/) submitted [Event Discovery Agent](https://github.com/asyncapi/community/discussions/147)
+
+Congrats to all of you folks!
+
+Check [this discussion to get more details on the voting process](https://github.com/asyncapi/community/discussions/165).
+
+PS. During Hackathon we also had lots of people engaging with us because of Hacktoberfest. We got [30 issues resolved and merged](https://docs.google.com/spreadsheets/d/17YYe-ZompcuUACfCGa8Pc3XunFfWRBrNllIBChJ0yWw/edit#gid=0).
+
+## Conference
+
+COVID19 is still here. Thus, we decided that we will have another AsyncAPI Conference this year only in online mode. It was a three-day event with lots of great content, and most importantly, with 1st day dedicated to contributors only.
+
+The conference was live-streamed. Full-day recordings were released immediately, and individual talks recordings will follow. All listed under [dedicated Conference playlist](https://www.youtube.com/playlist?list=PLbi1gRlP7pijq9F5eYsJomWc7Zf6EYVTZ).
+
+Till today this is how many people watched it during the conference and after as recordings:
+- Day 1:
+  - YouTube: 1119
+  - Twitch: 89 (during event only, later Twitch removes old videos)
+  - LinkedIn: 148
+  - Twitter: 692
+
+  Total: **2048**
+- Day 2:
+  - YouTube: 737 
+  - Twitch: 56 (during event only, later Twitch removes old videos)
+  - LinkedIn: 49
+  - Twitter: 283
+
+  Total: **1125**
+- Day 3:
+  - YouTube: 521
+  - Twitch: 26 (during event only, later Twitch removes old videos)
+  - LinkedIn: 29
+  - Twitter: 312
+
+  Total: **888**
+
+These numbers are great if we compare them with a total of 600 registrations!
+
+Personally, the best number was that I discovered when I started listing names of all the people who helped during hackathon and conference organization. I think 62 is now my favorite number :heart:
+
+<Figure
+  src="/img/posts/july-december-2021-at-asyncapi/conf_contrib.webp"
+  caption="Picture showing names of all people that helped in event organization."
+  className="text-center"
+/>
+
+What about 2022? People during the conference voted for hybrid approach:
+
+<Figure
+  src="/img/posts/july-december-2021-at-asyncapi/asyncapi_conf.webp"
+  caption="Picture showing that out of 25 voters, 18 (72%) voted for conference that is at the same time online and in person."
+  className="text-center"
+/>
+
+Join [related discussion and help organize it](https://github.com/asyncapi/community/discussions/193).
+
+> Photo by <a href="https://unsplash.com/@goian?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Ian Schneider</a> on <a href="https://unsplash.com/s/photos/end-of-the-year-ahead?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a>
+

pages/blog/openapi-vs-asyncapi-burning-questions.md

@@ -3,7 +3,6 @@ type: Engineering
 cover: /img/posts/openapi-vs-asyncapi-burning-questions/asyncapi-openapi-post_pic-15.webp
 title: "AsyncAPI vs OpenAPI: Answers to Your Burning Questions About Two Leading API Specs"
 date: 2021-09-08T06:00:00+01:00
-featured: true
 tags:
    - Specification
    - OpenAPI

pages/blog/release-notes-2.2.0.md

@@ -12,7 +12,6 @@ authors:
     link: https://twitter.com/derberq
     byline: AsyncAPI Maintainer and Community Guardian
 excerpt: '2.2 release of AsyncAPI specification is here. The long-awaited feature for assigning channels to servers is finally here.'
-featured: true
 ---
 
 I'm happy to share that AsyncAPI specification 2.2.0 is here. Check out all the goodies that it brings.