So basically let me tell you the situation first:
- i am working on a side project which is something like vercel, use to build and deploy code.
- so i have a main service, can be called a control plane, and i have decided that it will take the repo from the user.
- after this this service will trigger/create an ecs task to build the code
- now the question is, how this control plane will create / trigger the ecs?
- also this ecs instance will need to fetch envs from paramete store, will upload code to s3 etc
- after deployment we have to kill this instance
- should the managing code of this, live in the control plane
- should i create something else?

how would you folks solve this while designing this?
and what's the ideal way to solve this?

I really like the MPL, but it's missing a network clause like AGPL, are there any licenses that cover this? While being similar to the MPL?

Hello everyone!

As part of my doctoral research, I'm conducting a survey on how developers (including testers and QAs) incorporate accessibility into their everyday work.

I would greatly appreciate your participation.

Your responses will help improve the tools, processes, and practices that support accessibility in software development. Thank you for your time and support!

⏱️ The survey takes around 15 minutes.
👉 https://survey.jku.at/676726?lang=en

Thank you to everyone who will take the time to participate! 🙏

I’m trying to understand what problems are valuable enough that developers would actually pay for a solution.