chore: update and consolidate cli tool meta configs and add README/release notes examples

data/readmes/act-v0283.md

@@ -0,0 +1,48 @@
+# act - README (v0.2.83)
+
+**Repository**: https://github.com/nektos/act
+**Version**: v0.2.83
+
+---
+
+![act-logo](https://raw.githubusercontent.com/wiki/nektos/act/img/logo-150.png)
+
+# Overview [![push](https://github.com/nektos/act/workflows/push/badge.svg?branch=master&event=push)](https://github.com/nektos/act/actions) [![Go Report Card](https://goreportcard.com/badge/github.com/nektos/act)](https://goreportcard.com/report/github.com/nektos/act) [![awesome-runners](https://img.shields.io/badge/listed%20on-awesome--runners-blue.svg)](https://github.com/jonico/awesome-runners)
+
+> "Think globally, `act` locally"
+
+Run your [GitHub Actions](https://developer.github.com/actions/) locally! Why would you want to do this? Two reasons:
+
+- **Fast Feedback** - Rather than having to commit/push every time you want to test out the changes you are making to your `.github/workflows/` files (or for any changes to embedded GitHub actions), you can use `act` to run the actions locally. The [environment variables](https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) and [filesystem](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#filesystems-on-github-hosted-runners) are all configured to match what GitHub provides.
+- **Local Task Runner** - I love [make](<https://en.wikipedia.org/wiki/Make_(software)>). However, I also hate repeating myself. With `act`, you can use the GitHub Actions defined in your `.github/workflows/` to replace your `Makefile`!
+
+> [!TIP]
+> **Now Manage and Run Act Directly From VS Code!**<br/>
+> Check out the [GitHub Local Actions](https://sanjulaganepola.github.io/github-local-actions-docs/) Visual Studio Code extension which allows you to leverage the power of `act` to run and test workflows locally without leaving your editor.
+
+# How Does It Work?
+
+When you run `act` it reads in your GitHub Actions from `.github/workflows/` and determines the set of actions that need to be run. It uses the Docker API to either pull or build the necessary images, as defined in your workflow files and finally determines the execution path based on the dependencies that were defined. Once it has the execution path, it then uses the Docker API to run containers for each action based on the images prepared earlier. The [environment variables](https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) and [filesystem](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#file-systems) are all configured to match what GitHub provides.
+
+Let's see it in action with a [sample repo](https://github.com/cplee/github-actions-demo)!
+
+![Demo](https://raw.githubusercontent.com/wiki/nektos/act/quickstart/act-quickstart-2.gif)
+
+# Act User Guide
+
+Please look at the [act user guide](https://nektosact.com) for more documentation.
+
+# Support
+
+Need help? Ask in [discussions](https://github.com/nektos/act/discussions)!
+
+# Contributing
+
+Want to contribute to act? Awesome! Check out the [contributing guidelines](CONTRIBUTING.md) to get involved.
+
+## Manually building from source
+
+- Install Go tools 1.20+ - (<https://golang.org/doc/install>)
+- Clone this repo `git clone git@github.com:nektos/act.git`
+- Run unit tests with `make test`
+- Build and install: `make install`

data/readmes/activemq-activemq-parent-551.md

@@ -0,0 +1,82 @@
+# Activemq - README (activemq-parent-5.5.1)
+
+**Repository**: https://github.com/apache/activemq
+**Version**: activemq-parent-5.5.1
+
+---
+
+Welcome to Apache ActiveMQ 
+=======================================================================
+Apache ActiveMQ is a high performance Apache 2.0 licensed
+Message Broker.
+ActiveMQ supports several API and protocols:
+- Jakarta Messaging 3.1.0, JMS 2.0 and JMS 1.1.
+- AMQP
+- MQTT
+- HTTP/WS
+
+ActiveMQ also provides advanced features like:
+- network of brokers
+- scheduling
+- and much more!
+
+Getting Started
+===============
+To help you get started, try the following links:
+
+Getting Started
+- You need JDK17+ to run Apache ActiveMQ
+- After having extracted ActiveMQ binary distribution, you can start ActiveMQ with `./bin/activemq console` (foreground) or `./bin/activemq start`
+- Docker images are also available on Docker Hub (https://hub.docker.com/r/apache/activemq-classic)
+
+Building
+- You can build (fast) using Apache Maven: `mvn clean install -DskipTests`
+- You can build (including all tests) using Apache Maven: `mvn clean install`
+
+Examples
+- https://activemq.apache.org/examples.html
+
+We welcome contributions of all kinds, for details of how you can help
+https://activemq.apache.org/contributing.html
+
+Please refer to the website for details of finding the issue tracker, 
+email lists, wiki or IRC channel at https://activemq.apache.org/
+
+Please help us make Apache ActiveMQ better - we appreciate any feedback 
+you may have.
+
+Enjoy!
+
+Licensing
+=======================================================================
+
+   This software is licensed under the terms you may find in the file 
+   named "[LICENSE](./LICENSE)" in this directory.
+
+   This distribution includes cryptographic software.  The country in 
+   which you currently reside may have restrictions on the import, 
+   possession, use, and/or re-export to another country, of 
+   encryption software.  BEFORE using any encryption software, please 
+   check your country's laws, regulations and policies concerning the
+   import, possession, or use, and re-export of encryption software, to 
+   see if this is permitted.  See <https://www.wassenaar.org/> for more
+   information.
+
+   The U.S. Government Department of Commerce, Bureau of Industry and
+   Security (BIS), has classified this software as Export Commodity 
+   Control Number (ECCN) 5D002.C.1, which includes information security
+   software using or performing cryptographic functions with asymmetric
+   algorithms.  The form and manner of this Apache Software Foundation
+   distribution makes it eligible for export under the License Exception
+   ENC Technology Software Unrestricted (TSU) exception (see the BIS 
+   Export Administration Regulations, Section 740.13) for both object 
+   code and source code.
+
+   The following provides more details on the included cryptographic
+   software:
+
+   ActiveMQ supports the use of SSL TCP connections when used with 
+   with a JVM supporting the Java Cryptography extensions
+   <https://www.oracle.com/java/technologies/javase/javase-tech-security.html>.
+   ActiveMQ does not include these libraries itself, but is designed to use them.
+

data/readmes/aeraki-mesh-141.md

@@ -0,0 +1,197 @@
+# Aeraki Mesh - README (1.4.1)
+
+**Repository**: https://github.com/aeraki-mesh/aeraki
+**Version**: 1.4.1
+
+---
+
+<!--
+# Copyright Aeraki Authors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+
+[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Faeraki-mesh%2Faeraki.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2Faeraki-mesh%2Faeraki?ref=badge_large)
+
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+-->
+
+# Aeraki （[中文](./README.zh-CN.md)）
+
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://github.com/aeraki-mesh/aeraki/blob/master/LICENSE)
+[![Go Report Card](https://goreportcard.com/badge/github.com/aeraki-mesh/aeraki)](https://goreportcard.com/report/github.com/aeraki-mesh/aeraki)
+[![CI Tests](https://github.com/aeraki-mesh/aeraki/workflows/ci/badge.svg?branch=master)](https://github.com/aeraki-mesh/aeraki/actions?query=branch%3Amaster+event%3Apush+workflow%3A%22ci%22)
+[![E2E Tests](https://github.com/aeraki-mesh/aeraki/workflows/e2e-metaprotocol/badge.svg?branch=master)](https://github.com/aeraki-mesh/aeraki/actions?query=branch%3Amaster+event%3Apush+workflow%3A%22e2e-metaprotocol%22)
+[![E2E Tests](https://github.com/aeraki-mesh/aeraki/workflows/e2e-dubbo/badge.svg?branch=master)](https://github.com/aeraki-mesh/aeraki/actions?query=branch%3Amaster+event%3Apush+workflow%3A%22e2e-dubbo%22)
+[![E2E Tests](https://github.com/aeraki-mesh/aeraki/workflows/e2e-thrift/badge.svg?branch=master)](https://github.com/aeraki-mesh/aeraki/actions?query=branch%3Amaster+event%3Apush+workflow%3A%22e2e-thrift%22)
+[![E2E Tests](https://github.com/aeraki-mesh/aeraki/workflows/e2e-kafka-zookeeper/badge.svg?branch=master)](https://github.com/aeraki-mesh/aeraki/actions?query=branch%3Amaster+event%3Apush+workflow%3A%22e2e-kafka-zookeeper%22)
+[![E2E Tests](https://github.com/aeraki-mesh/aeraki/workflows/e2e-redis/badge.svg?branch=master)](https://github.com/aeraki-mesh/aeraki/actions?query=branch%3Amaster+event%3Apush+workflow%3A%22e2e-redis%22)
+[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Faeraki-mesh%2Faeraki.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2Faeraki-mesh%2Faeraki?ref=badge_shield)
+
+<a href="https://aeraki.net/">
+    <img src="docs/aeraki-log.png"
+         width="130"
+         alt="Aeraki logo" title="Istio" />
+</a>
+
+---
+# Manage **any** layer-7 traffic in a service mesh!
+
+**Aeraki** [Air-rah-ki] is the Greek word for 'breeze'. While service mesh becomes an important infrastructure for microservices, many(if not all) service mesh implementations mainly focus on HTTP protocols and treat other protocols as plain TCP traffic. Aeraki Mesh is created to provide a non-intrusive, highly extendable way to manage any layer-7 traffic in a service mesh.
+
+Note: Aeraki only handles non-HTTP layer-7 traffic in a service mesh, and leaves the HTTP traffic to other existing service mesh projects. (As they have already done a very good job on it, and we don't want to reinvent the wheel! )
+Aeraki currently can be integrated with Istio, and it may support other service mesh projects in the future.
+
+## Problems to solve
+
+We are facing some challenges in service meshes:
+* Istio and other popular service mesh implementations have very limited support for layer-7 protocols other than HTTP and gRPC.
+* Envoy RDS(Route Discovery Service) is solely designed for HTTP. Other protocols such as Dubbo and Thrift can only use listener in-line routes for traffic management, which breaks existing connections when routes change.
+* It takes a lot of effort to introduce a proprietary protocol into a service mesh. You’ll need to write an Envoy filter to handle the traffic in the data plane, and a control plane to manage those Envoy proxies.
+
+Those obstacles make it very hard, if not impossible, for users to manage the traffic of other widely-used layer-7 protocols in microservices. For example, in a microservices application, we may have the below protocols:
+
+* RPC: HTTP, gRPC, Thrift, Dubbo, Proprietary RPC Protocol …
+* Messaging: Kafka, RabbitMQ …
+* Cache: Redis, Memcached …
+* Database: MySQL, PostgreSQL, MongoDB …
+
+![ Common Layer 7 Protocols Used in Microservices ](docs/protocols.png)
+
+If you have already invested a lot of effort in migrating to a service mesh, of course, you want to get the most out of it — managing the traffic of all the protocols in your microservices.
+
+## Aeraki's approach
+
+To address these problems, Aeraki Mesh provides a non-intrusive, extendable way to manage any layer-7 traffic in a service mesh.
+![ Aeraki ](docs/aeraki-architecture.png)
+
+As this diagram shows, Aeraki Mesh consists of the following components:
+
+* Aeraki: [Aeraki](https://github.com/aeraki-mesh/aeraki) provides high-level, user-friendly traffic management rules to operations, translates the rules to envoy filter configurations, and leverages Istio’s `EnvoyFilter` API to push the configurations to the sidecar proxies. Aeraki also serves as the RDS server for MetaProtocol proxies in the data plane. Contrary to Envoy RDS, which focuses on HTTP, Aeraki RDS is aimed to provide a general dynamic route capability for all layer-7 protocols.
+* MetaProtocol Proxy: [MetaProtocol Proxy](https://github.com/aeraki-mesh/meta-protocol-proxy) provides common capabilities for Layer-7 protocols, such as load balancing, circuit breaker, routing, rate limiting, fault injection, and auth. Layer-7 protocols can be built on top of MetaProtocol. To add a new protocol into the service mesh, the only thing you need to do is to implement the [codec interface](https://github.com/aeraki-mesh/meta-protocol-proxy/blob/ac788327239bd794e745ce18b382da858ddf3355/src/meta_protocol_proxy/codec/codec.h#L118) and a couple of lines of configuration. If you have special requirements which can’t be accommodated by the built-in capabilities, MetaProtocol Proxy also has an application-level filter chain mechanism, allowing users to write their own layer-7 filters to add custom logic into MetaProtocol Proxy.
+
+[Dubbo](https://github.com/aeraki-mesh/meta-protocol-proxy/tree/master/src/application_protocols/dubbo) 
+, [Thrift](https://github.com/aeraki-mesh/meta-protocol-proxy/tree/master/src/application_protocols/thrift) 
+, [bRPC](https://github.com/aeraki-mesh/meta-protocol-proxy/tree/master/src/application_protocols/brpc)
+and [a number of other protocols](https://github.com/aeraki-mesh/aeraki/issues/105) have been implemented based on MetaProtocol. More protocols are on the way. 
+If you're using a close-source, proprietary protocol, you can also manage it in your service mesh simply by 
+[writing a MetaProtocol codec](https://www.aeraki.net/docs/v1.x/tutorials/implement-a-custom-protocol/) for it.
+
+Most request/response style, stateless protocols can be built on top of the MetaProtocol Proxy. However, some protocols' routing policies are too "special" to be normalized in MetaProtocol. For example, the Redis proxy uses a slot number to map a client query to a specific Redis server node, and the slot number is computed by the key in the request. Aeraki can still manage those protocols as long as there's an available Envoy Filter in the Envoy proxy side. Currently, for protocols in this category, [Redis](https://github.com/aeraki-mesh/aeraki/blob/master/docs/zh/redis.md) and Kafka are supported in Aeraki.
+
+## Supported protocols:
+Aeraki can manage the below protocols in a service mesh：
+* Dubbo (Envoy native filter）
+* Thrift (Envoy native filter)
+* Kafka (Envoy native filter)
+* Redis (Envoy native filter)
+* MetaProtocol-Dubbo
+* MetaProtocol-Thrift
+* MetaProtocol-bRPC (A RPC protocol open-source by Baidu)
+* MetaProtocol-tRPC (A proprietary RPC protocol used in Tencent）
+* MetaProtocol-qza (A proprietary protocol used in Tencent Music)
+* MetaProtocol-videoPacket (A proprietary protocol used in Tencent Media Data Platform)
+* MetaProtocol-Others: Alauda, Tencent iGame...
+* MetaProtocol-Private protocols: Have a private protocol? No problem, any layer-7 protocols built on top of the [MetaProtocol](https://github.com/aeraki-mesh/meta-protocol-proxy) can be managed by Aeraki
+
+## Supported Features:
+  * Traffic Management
+    * [x] Request Level Load Balancing/Locality Load Balancing (Supports Consistent Hash/Sticky Session)
+    * [x] Circuit breaking
+    * [x] Flexible Route Match Conditions (any properties can be exacted from layer-7 packets and used as match conditions)
+    * [x] Dynamic route update through Aeraki MetaRDS
+    * [x] Version Based Routing
+    * [x] Traffic Splitting
+    * [x] Local Rate Limit
+    * [x] Global Rate Limit
+    * [x] Message mutation
+    * [x] Traffic Mirroring
+  * Observability
+    * [x] Request level Metrics (Request latency, count, error, etc)
+    * [x] Distributed Tracing
+    * [x] Access log
+  * Security 
+    * [x] Peer Authorization on Interface/Method
+    * [ ] Request Authorization
+
+> Note: Protocols built on top of MetaProtocol support all the above features in Aeraki Mesh, Envoy native filters only support some of the above features, depending on the capacities of the native filters.
+
+## Demo
+
+https://www.aeraki.net/docs/v1.x/quickstart/
+
+## Install
+
+https://www.aeraki.net/docs/v1.x/install/
+
+## Build
+
+### Pre-requirements:
+* Golang Version >= 1.16, and related golang tools installed like `goimports`, `gofmt`, etc.
+* Docker and Docker-Compose installed
+
+### Build Aeraki Binary
+
+```bash
+# build aeraki binary on Linux
+make build
+
+# build aeraki binary on darwin
+make build IMAGE_OS=darwin
+```
+
+### Build Aeraki Image
+
+```bash
+# build aeraki docker image with the default latest tag
+make docker-build
+
+# build aeraki docker image with xxx tag
+make docker-build IMAGE_TAG=xxx
+
+# build aeraki e2e docker image
+make docker-build-e2e
+```
+
+## Contribute to Aeraki
+
+If you're interested in contributing to this project, please read [Contributing to Aeraki](CONTRIBUTING.md).
+
+## Talks
+
+* IstioCon 2022: [Tencent Music’s service mesh practice with Istio and Aeraki](https://events.istio.io/istiocon-2022/sessions/tencent-music-aeraki/)
+* Istio meetup China(中文): [全栈服务网格 - Aeraki 助你在 Istio 服务网格中管理任何七层流量](https://www.youtube.com/watch?v=Bq5T3OR3iTM) 
+* IstioCon 2021: [How to Manage Any Layer-7 Traffic in an Istio Service Mesh?](https://www.youtube.com/watch?v=sBS4utF68d8)
+
+## Who is using Aeraki?
+
+Sincerely thank everyone for choosing, contributing, and using Aeraki. We created this issue to collect the use cases so we can drive the Aeraki community to evolve in the right direction and better serve your real-world scenarios. We encourage you to submit a comment on this issue to include your use case：https://github.com/aeraki-mesh/aeraki/issues/105
+
+## Contact
+* WeChat Group: Please contact Wechat ID: zhao_huabing to join the Aeraki Wechat group
+* Slack Channel: Join [our slack channel](https://cloud-native.slack.com/messages/aeraki-mesh)
+* Community meetings: [Meetings and recordings](https://www.aeraki.net/community/#community-meetings)
+
+## License
+
+This project is licensed under [Apache 2.0 License](LICENSE)
+
+## Conduct
+
+We follow the [CNCF Code of Conduct](CODE_OF_CONDUCT.md)
+
+## Landscapes
+
+<p align="center">
+<img src="https://landscape.cncf.io/images/cncf-landscape-horizontal-color.svg" width="300"/>
+<br/><br/>
+Aeraki Mesh is a <a href="https://landscape.cncf.io/?selected=aeraki-mesh&item=orchestration-management--service-mesh--aeraki-mesh">CNCF sandbox project.</a>
+</p>