-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Category Request: Abstractions #243
Comments
Yes! This is a great idea for a category. I'm not sure about the name Abstractions. |
I think "abstractions" is exactly what this is. My first thought was "higher-level abstraction", but that would imply that things like tekton are "low level", which is weird. Other ideas:
|
Brought this up to the CDF Interoperability SIG. The general consensus was that it would be very good to add this category and in the first instance label it Abstractions. The name can evolve should that be needed/desired later. 🥳 🎉 |
To start visualising the new category on the landscape, I've made a very hacky first iteration. The final placement should look very different, but we can start to discuss where the category should fit within the current landscape, either on this thread or on the WIP PR. Notes:
|
I think it also is related to stuff like: https://cd.foundation/blog/2022/07/13/help-wanted-intent-based-pipelines/. We also think it's related to the intent-based pipelines that folks are opining on as well. |
Ploigos is another tool that is being written around a similar sort of problem: https://github.com/ploigos |
Would Kubevela https://kubevela.io/ fit in this category as well? It has been suggested that the new Abstractions category would be better over next to Tracing/Messaging and so: |
Hi @trmiller and @mlieberman85, Do you have an SVG for FRSCA's logo? |
We currently have a ticket open with the Linux Foundation on getting us a logo. We're hoping to have one in the next few weeks :). |
Category request:
I was wondering if there was any interest in adding a higher level category to the landscape. There are projects like FRSCA, or Dagger.io which aim to either configure multiple landscape tools together, or act as a way to work between them with a higher level API.
My initial thought was a category called Abstractions, but would love other thoughts, or feedback on if what I'm suggesting fits within the landscape or not.
Thanks!
The text was updated successfully, but these errors were encountered: