camera-preview VS http-add-on

Looking for Swift, Android and Typescript developers to help with camera-preview, an open source cross-platform embedded camera for Capacitor and Ionic.

I recently got involved and my goal is to add frame processing so you can run object detection and models on the preview frames. But first the project needs to stabilise.

We're a welcoming community and all contributions are very gratefully received. I take care of the project admin so contributors can focus on what they enjoy.

https://github.com/capacitor-community/camera-preview

I recently took over maintaining https://github.com/capacitor-community/camera-preview because lots of people find embedding a camera in their apps useful and it hadn't been updated for ages.

I'm not a Swift programmer, or Kotlin, and haven't touched Java in a decade. I would love to collaborate with people on this project. I can offer lots of enthusiasm, I'll handle all the user-facing stuff and managing GitHub issues and support requests, project admin and writing documentation :)

There is much to do and I've plenty of ideas, but not got the coding skills to know where to start.

KEDA ships with an HTTP add-on to enable HTTP scaling.

KEDA has a special scaler that creates an HTTP proxy that measures and buffers requests before they reach the app.

I am a core maintainer on the KEDA HTTP Addon project (https://github.com/kedacore/http-add-on). It's 100% written in Go and we are a small group looking for additional contributors. I believe there are interesting challenges ahead of us that will be enjoyable to solve.

If you're interested, please reach out. My username here is the same as my username on the Gophers and Kubernetes slack groups.

(You're of course welcome to just go pick up an issue in the repo if you'd prefer)

The KEDA HTTP Addon project contains three major components: the operator, scaler and interceptor.

Hacking on the KEDA HTTP Addon, I found myself having to do something familiar:

First, we need to finish the minimal infrastructure. The components and supporting artifacts (Helm charts, CI scripts, etc...) are being built in PR #2, and once we have them completed, we will merge it [5]. Second, we need to establish a roadmap. We're beginning to outline it now and will finish it shortly after merging.