-
-
Notifications
You must be signed in to change notification settings - Fork 681
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into migrate-ts
- Loading branch information
Showing
11 changed files
with
247 additions
and
67 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,47 +1,83 @@ | ||
- companyName: Reiffeisen Bank | ||
useCase: Continuous Integration and Continuous Delivery (CI/CD) pipeline based on GitOps to deploy a topology built on Async API definitions using a Kubernetes operator to an Apache Pulsar cluster. | ||
useCase: Implementing a Continuous Integration and Continuous Delivery (CI/CD) pipeline utilizing GitOps principles to deploy a topology constructed on AsyncAPI definitions using a Kubernetes operator to an Apache Pulsar cluster. | ||
resources: | ||
- title: Video - From an AsyncAPI Definition to a Deployed Pulsar Topology Via GitOps | ||
- title: "Video: From an AsyncAPI Definition to a Deployed Pulsar Topology Via GitOps" | ||
link: https://www.youtube.com/watch?v=_MwzLZMwFN8 | ||
|
||
- companyName: LEGO Group | ||
useCase: Broker management, where developers do not access the management console themselves, but rely on uploading AsyncAPI documents to a self service API that provisions access and topics specified in documents. | ||
useCase: Managing brokers, where developers abstain from direct access to the management console and instead upload AsyncAPI documents to a self-service API, which provisions access and topics specified in the documents. | ||
resources: | ||
- title: Video - Documentation as Configuration for Management of Apache Pulsar | ||
- title: "Video: Documentation as Configuration for Management of Apache Pulsar" | ||
link: https://www.youtube.com/watch?v=m8I0fYjx6Cc | ||
|
||
- companyName: LEGO Group | ||
useCase: Define, document and distribute event-driven APIs. Ensuring consistency and governance | ||
useCase: Defining, documenting, and distributing event-driven APIs while ensuring consistency and governance. | ||
resources: | ||
- title: Video - Cross-Domain Events with AsyncAPI and AWS | ||
- title: "Video: Cross-Domain Events with AsyncAPI and AWS" | ||
link: https://www.youtube.com/watch?v=qjarcJQVLOg | ||
|
||
- companyName: Bank of New Zealand | ||
useCase: Decentralized company-wide governance strategy for API. A self service for publishing APIs and docs. | ||
useCase: Establishing a decentralized company-wide governance strategy for APIs, providing a self-service platform for publishing APIs and documentation. | ||
resources: | ||
- title: "Video - Self-service Events & Decentralised Governance with AsyncAPI: A Real World Example" | ||
- title: "Video: Self-service Events & Decentralised Governance with AsyncAPI: A Real World Example" | ||
link: https://www.confluent.io/events/kafka-summit-apac-2021/self-service-events-and-decentralised-governance-with-asyncapi-a-real-world/ | ||
|
||
- companyName: Zora Robotics | ||
useCase: Documenting lot products public MQTT API and building a developers portal. | ||
useCase: Documenting public MQTT APIs for IoT products and constructing a developer portal. | ||
resources: | ||
- title: Video - Buliding and managing an extensive API for Robotics and loT | ||
- title: "Video: Building and managing an extensive API for Robotics and IoT" | ||
link: https://www.youtube.com/watch?v=yjHgT0n2BtA | ||
- title: Docs - Buliding and managing an extensive API for Robotics and loT | ||
- title: "Docs: Building and managing an extensive API for Robotics and IoT" | ||
link: https://docs.zorabots.be/dev-mqtt-docs/latest/index.html | ||
|
||
- companyName: Walmart | ||
useCase: Managing a central API Hub for internal teams. Using AsyncAPI for events discoverability an visibility in a single place. AsyncAPI also enabled company-wide governance on asynchronous APIs. | ||
useCase: Managing a centralized API Hub for internal teams, enhancing event discoverability and visibility using AsyncAPI. AsyncAPI facilitates company-wide governance on asynchronous APIs. | ||
resources: | ||
- title: Video - Time For AsyncAPI Specification | ||
- title: "Video: Time For AsyncAPI Specification" | ||
link: https://www.youtube.com/watch?v=SxTpGRaNIPo | ||
|
||
- companyName: eBay | ||
useCase: Enabling partners to build with eBay through asynchronous communication. Public AsyncAPI documents enable code generation and faster integration. It also enables governance and standardisation. | ||
useCase: Facilitating partner integration with eBay through asynchronous communication, leveraging public AsyncAPI documents for code generation and rapid integration, while ensuring governance and standardization. | ||
resources: | ||
- title: "Video - AsyncAPI 2.0: Enabling the Event-Driven World" | ||
- title: "Video: AsyncAPI 2.0: Enabling the Event-Driven World" | ||
link: https://www.youtube.com/watch?v=SxTpGRaNIPo | ||
- title: "Article - AsyncAPI 2.0: Enabling the Event-Driven World" | ||
- title: "Article: AsyncAPI 2.0: Enabling the Event-Driven World" | ||
link: https://innovation.ebayinc.com/tech/engineering/asyncapi-2-0-enabling-the-event-driven-world/ | ||
- title: Docs - Overview of Notification API with public AsyncAPI documents | ||
link: https://developer.ebay.com/api-docs/commerce/notification/overview.html | ||
- title: "Docs: Overview of Notification API with public AsyncAPI documents" | ||
link: https://developer.ebay.com/api-docs/commerce/notification/overview.html | ||
|
||
- companyName: Postman | ||
useCase: Enhancing discoverability of information about system events by building a tool called Synapse for provisioning entire event-based infrastructure, with AsyncAPI documents as the source of truth. | ||
resources: | ||
- title: "Video: Turbocharging your Developer Ecosystem with Events Powered by SNS/SQS, Serverless, and AsyncAPI" | ||
link: https://www.youtube.com/watch?v=0_7QZyKLPoE | ||
|
||
- companyName: Adobe | ||
useCase: Providing event documentation to expedite development by generating classes based on message payload information from AsyncAPI documents. | ||
resources: | ||
- title: "Slides: AsyncAPI and Modelina" | ||
link: https://drive.google.com/file/d/1AVCG9_fFtuOtrvZVZWENmU2aDT7C51Jr/view?usp=sharing | ||
|
||
- companyName: Open University of Catalonia and Prodevelop | ||
useCase: Enabling monitoring of ports through a design-first approach, utilizing UML class diagrams to design the entire infrastructure. UML diagrams are source of truth for generated AsyncAPI documents that later are used for models and clients generation. These documents are extended with additional SLA properties to specify runtime quality of service requirements, facilitating real-time monitoring. | ||
resources: | ||
- title: "Video: Leveraging AsyncAPI To Detect Anomalies in Smart Ports Platforms" | ||
link: https://www.youtube.com/watch?v=m4KS6FSeTT4 | ||
|
||
- companyName: Oracle | ||
useCase: Documenting data streaming APIs with AsyncAPI documents for client library generation in various programming languages, reducing development time for applications consuming data. | ||
resources: | ||
- title: "Video: Productizing AsyncAPI for Data Replication" | ||
link: https://www.youtube.com/watch?v=CGLlxYy66LY | ||
|
||
- companyName: TransferGo | ||
useCase: Enhancing discoverability of information about event-driven systems by documenting services with AsyncAPI, rendering documentation, and creating catalogs of events. Legacy services utilize a special library to generate AsyncAPI documents, while new services require AsyncAPI documents for generating PHP classes. | ||
resources: | ||
- title: "Slides: How TransferGo Uses AsyncAPI To Improve Developer Experience" | ||
link: https://drive.google.com/file/d/1t7tYMr8FMRInaZV0lWod1QfDuhhSjwBJ/view?usp=sharing | ||
|
||
- companyName: Kuehne+Nagel | ||
useCase: Implementing a GitOps-based pipeline to enable self-service management of Kafka infrastructure, including access control management. Automation of AsyncAPI document governance ensures consistency in the infrastructure at the pull request level. | ||
resources: | ||
- title: "Slides: AsyncAPI For Platform Self-Service: A GitOps Tale" | ||
link: https://drive.google.com/file/d/1y67PI8NaITPPwZAiDF2Zs7ISfcIpqMV8/view?usp=sharing |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,97 @@ | ||
--- | ||
title: "Community Update: February 2024" | ||
date: 2024-02-29T06:00:00+01:00 | ||
type: Communication | ||
tags: | ||
- Project Status | ||
cover: /img/posts/2024-blog-banner/blog-banner-february.webp | ||
authors: | ||
- name: Thulisile Sibanda | ||
photo: /img/avatars/thulieblack.webp | ||
link: https://www.linkedin.com/in/v-thulisile-sibanda/ | ||
byline: AsyncAPI Community Manager | ||
excerpt: 'Community update for February' | ||
featured: true | ||
--- | ||
|
||
We are starting the year off with a bang as we got accepted to the [Google Summer of Code 2024](https://summerofcode.withgoogle.com/programs/2024/organizations/asyncapi) program after two years of rejections. It is an incredible achievement for the community, and we wouldn't have done it without our Doc's Lead, [Alejandra Quetzalli](https://www.linkedin.com/in/alejandra-quetzalli/), who crafted an excellent proposal, and [Elegbede Azeez](https://twitter.com/_acebuild). We are very excited to have received this opportunity, and you can read [the AsyncAPI Project Ideas Page](https://github.com/asyncapi/community/blob/master/mentorship/summerofcode/2024/asyncapi-gsoc-ideas-page.md) for in-depth details on participating projects. | ||
|
||
## AsyncAPI Conf on Tour 2024 | ||
The planning of AACoT'24 is already underway as we prepare for our first conference in Helsinki on the 28th - 29th of May. We are putting in the final touches to update our conference website with the latest details, and we will soon announce the Call for Speakers. In the meantime, be sure to start crafting those proposals and get ready to share your expertise with the community. | ||
|
||
## Financial Sponsors | ||
We are thrilled to share that the initiative has secured new sponsors who generously paid for the entire year in advance. We welcome [Postman](https://www.postman.com/) as a gold sponsor, who contributed $12,000, and [HiveMQ](https://www.hivemq.com/), our silver sponsor, who gave $6,000. | ||
|
||
<a href='https://www.postman.com/' target='_blank'> | ||
<img src='/img/sponsors/postman.png' alt='postman' width='500px' /> | ||
</a> | ||
|
||
<a href='https://www.hivemq.com/' target='_blank'> | ||
<img src='/img/sponsors/hivemq_logo.png' alt='hivemq' width='500px' /> | ||
</a> | ||
|
||
For more information about our financial budget, please [refer to the 2024 Budget discussion](https://github.com/orgs/asyncapi/discussions/1017). | ||
|
||
## Community Discussions | ||
We have important discussions that require the community's attention: | ||
|
||
- ### Marketing Activities | ||
We need to invest in marketing efforts this year, and as the first initial step, we have secured a budget of $24,000. The next step now is to find a workaround to achieve this goal. If you have experience or have insights on how we can spend and efficiently boost our marketing aspects, please [join the Marketing Activities discussion](https://github.com/orgs/asyncapi/discussions/1062). | ||
- ### Doc's Project Ideas for GSoD'24 | ||
Google Season of Docs 2024 is now open, and we plan to participate again this year. We are currently gathering project proposals for our application, and if you have ideas on areas we should improve or focus on in our documentation, please [propose new docs project ideas in the community discussion](https://github.com/orgs/asyncapi/discussions/1069). | ||
- ### Sovereign Tech Fund Application | ||
The [Sovereign Tech Fund](https://www.sovereigntechfund.de/) is opening its applications for open-source organizations in Q2. We have some ideas and areas we should focus on for the application, such as CI/CD infrastructure. Be sure to [join the Sovereign Tech Fund discussion](https://github.com/orgs/asyncapi/discussions/1073) if you want to collaborate or share application ideas. | ||
- ### Code of Conduct Draft Update | ||
The AsyncAPI Code of Conduct Committee is halfway through updating the current Code of Conduct to the latest version. They have created some documents that explain the procedures and guidelines that the CoC Committee will use to enforce the Code of Conduct. You can glimpse [the updated Code of Conduct draft by checking the work-in-progress pull requests](https://github.com/asyncapi/community/issues/994). | ||
- ### Cupid is Looking For Maintainers | ||
We're on the lookout for maintainers for the AsyncAPI Cupid. The library focuses on finding and analyzing the relationships between AsyncAPI documents. If you're well-versed in Event-Driven Architecture and AsyncAPI, please [join the Cupid repository discussion](https://github.com/asyncapi/cupid/issues/182) and help us drive its development. | ||
- ### AsyncAPI Working Groups | ||
We are finally officializing working groups throughout the AsyncAPI community. A working group will be a community where people share similar interests beyond GitHub repositories. You can read the [Working Groups docs](https://github.com/asyncapi/community/blob/master/WORKING_GROUPS.md) or view the [Working Group public discussion](https://github.com/orgs/asyncapi/discussions/1037) for more comprehensive details. | ||
|
||
## TSC Members x Ambassadors | ||
|
||
We are excited to welcome five new [Technical Steering Committee](https://www.asyncapi.com/community/tsc) (TSC) members. | ||
|
||
<Profile profiles={[ | ||
{ | ||
name: 'Ashish Padhy', | ||
avatar: 'https://avatars.githubusercontent.com/Shurtu-gal', | ||
link: 'https://github.com/Shurtu-gal' | ||
}, | ||
{ | ||
name: 'Ashmit JaiSarita Gupta', | ||
avatar: 'https://avatars.githubusercontent.com/devilkiller-ag', | ||
link: 'https://github.com/devilkiller-ag' | ||
}, | ||
{ | ||
name: 'Prince Rajpoot', | ||
avatar: 'https://avatars.githubusercontent.com/princerajpoot20', | ||
link: 'https://github.com/princerajpoot20' | ||
}, | ||
{ | ||
name: 'Sambhav Gupta', | ||
avatar: 'https://avatars.githubusercontent.com/sambhavgupta0705', | ||
link: 'https://github.com/sambhavgupta0705' | ||
}, | ||
{ | ||
name: 'Samir AMZANI', | ||
avatar: 'https://avatars.githubusercontent.com/Amzani', | ||
link: 'https://github.com/Amzani' | ||
} | ||
]} /> | ||
|
||
Additionally, we have a new addition to the [AsyncAPI Ambassadors](https://www.asyncapi.com/community/ambassadors) team, raising the number to seven. | ||
|
||
<Profile profiles={[ | ||
{ | ||
name: 'Iván García Sainz-Aja', | ||
avatar: 'https://avatars.githubusercontent.com/ivangsa', | ||
link: 'https://github.com/ivangsa' | ||
} | ||
]} /> | ||
|
||
Exciting times for our growing community! | ||
|
||
## Coming in March | ||
- **AACoT'24 Helsinki Call for Speakers** - We will announce our Call for Speakers for AACoT'24 Helsinki by the first week of March. Start crafting those proposals and get ready to submit them. | ||
- **AsyncAPI Community Updates Newsletter** - The March Edition issue will drop on the 6th. Make sure [you're subscribed to the AsyncAPI Newsletter](https://www.asyncapi.com/newsletter); you don't want to miss out! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
--- | ||
title: "Contributing to Open Source as a Product Design and UX Researcher" | ||
date: 2023-11-09T06:00:00+01:00 | ||
type: Communication | ||
tags: | ||
- Project Status | ||
cover: /img/posts/designcover.webp | ||
authors: | ||
- name: Aishat Muibudeen | ||
photo: /img/avatars/maya_picture.webp | ||
link: https://www.linkedin.com/in/aishatmuibudeen/ | ||
byline: Product Designer and UX Researcher | ||
excerpt: 'Design BlogPost' | ||
--- | ||
Every software has a design system, regardless of whether it is free or not. Suppose you are a UX researcher or designer intending to be part of an Open Source community. In that case, you can begin contributing to the research or design program by collaborating with others. This article clarifies what Open Source is and provides tips on how you can start contributing as a UX researcher or designer. In addition, I’ll share some Open Source communities that you can contribute to as a beginner. | ||
|
||
### What is Open Source? | ||
|
||
public/img/posts/oss_image.webp | ||
|
||
Open Source Software (OSS) refers to software shared with its source code, allowing users to access, modify, and distribute. OSS allows everyone to contribute to the source code, make changes, or suggest new features. You can use the code for your purpose or contribute to improving the entire project’s features. | ||
|
||
Some examples of Open Source Software are available, including AsyncAPI, Linux Kernel, Oppia Foundation, VLC Media Player, Mozilla Firefox, Audacity, Blender, and more. These software are free to download, use, and distribute. It’s essential to recognize that some individuals put in much effort to make these projects available to a broad audience. Pursuing a career in Open Source can be beneficial, as it allows you to give back to the community and assist as many users as possible. | ||
|
||
It is worth noting that not all open-source projects are free of charge. To determine whether a project is free, you can check the project’s LICENSE file on GitHub. | ||
|
||
### My Experience as a Product Designer and UX Researcher in Open Source | ||
|
||
If you want to move faster in your career, I suggest getting started contributing to Open Source projects as early as possible. As a UX personnel, working with dummy users without getting feedback can be frustrating. However, Open Source allows you to learn your expertise and receive real-time feedback from users. Additionally, the collaborative nature of Open Source provides real-life working environments. | ||
|
||
In late 2022, I made my first Open Source contribution by designing speaker cards for the AsyncAPI Virtual Conference. When I received a notification that my pull request had been merged, I felt a sense of fulfillment about seeing my work showcased on a global scene. | ||
|
||
My interest in Open Source Communities made me apply for the Outreachy Internship Program. My collaboration and research skills helped me get into the program. I worked on the Foundational Research for Nigeria, a research project created to understand the learning needs and problems associated with technology learning among children between the ages of 7 and 15 in Nigeria. I also conducted usability testing with Oppia users to evaluate the effectiveness and usability of the Oppia application and website platform. | ||
|
||
Since completing my Internship Program in March, I have worked on other open-source projects. | ||
|
||
### Completed Projects | ||
|
||
- Designed the AsyncAPI Conference on Tour 2023 website (AACoT’23). | ||
- Conducted a UX Design Audit on the AsyncAPI Website. | ||
- Designed the AsyncAPI Financial Summary Page. | ||
- Designed the Community Member’s Page for AsyncAPI. | ||
- I worked with my team to design and create content for the Ladder Library as part of She Code Africa HackFest 2022. | ||
|
||
### On-going Projects | ||
|
||
- Working on the Design system for the AsyncAPI website. | ||
- Creating a UX research plan for usability testing. | ||
- Reviewing all design and research-related issues. | ||
|
||
### What are the advantages of contributing? | ||
|
||
There are numerous benefits to contributing to open source. One of the most prominent reasons is collaboration. For beginners and experienced fellows, collaborating using a version control system is an added advantage to your career. Getting hired based on your open-source contribution and contributing to technologies that make your life better and more accessible. | ||
Finally, open source is time-consuming and can become overwhelming if you do not manage your time. | ||
|
||
### Are you ready to start contributing? | ||
|
||
Check if the applications you frequently use are Open Source and consider joining their communities. You can ask questions, solve issues, and offer assistance to others. Many communities offer issues that are suitable for beginners who are new to open source. | ||
|
||
|
||
|
||
|
Oops, something went wrong.