Skip to content
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

Open
trmiller opened this issue Aug 4, 2022 · 9 comments
Open

Category Request: Abstractions #243

trmiller opened this issue Aug 4, 2022 · 9 comments

Comments

@trmiller
Copy link

trmiller commented Aug 4, 2022

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!

@MarckK
Copy link
Member

MarckK commented Aug 17, 2022

Yes! This is a great idea for a category.

I'm not sure about the name Abstractions.

@justinabrahms
Copy link

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:

  • interoperable interface
  • portability tools

@MarckK
Copy link
Member

MarckK commented Aug 18, 2022

Brought this up to the CDF Interoperability SIG.
There was much agreement that this was a great category to add to the landscape and an immediate understanding of what this is -- and the best name considered was Abstractions!

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.

🥳 🎉

@MarckK
Copy link
Member

MarckK commented Aug 18, 2022

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.
You can see the preview here: https://deploy-preview-253--cdf-landscape.netlify.app/

Screenshot 2022-08-18 at 16 02 25

Notes:

  • We don't need to have a top sub-heading (or could have a different one)
  • Perhaps Abstractions could be a sub-heading in a different main category? If so, where would this fit best, and/or how would current categories need to be reconfigured/reconceptualized?
  • The one item card in the WIP Abstraction category is for FRSCA. The information on the card for FRSCA likely needs to be amended.
  • The logo on that card is currently Tekton's as a card must have an svg logo. To have a card on the CDF landscape FRSCA will need to provide an svg logo. Please note that stacked logos look best.

@mlieberman85
Copy link

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.

@mlieberman85
Copy link

Ploigos is another tool that is being written around a similar sort of problem: https://github.com/ploigos

@MarckK
Copy link
Member

MarckK commented Aug 24, 2022

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:
Screenshot 2022-08-24 at 17 18 54

@MarckK
Copy link
Member

MarckK commented Sep 8, 2022

Hi @trmiller and @mlieberman85, Do you have an SVG for FRSCA's logo?
Then I can add this category with FRSCA and we can build it out from there. 😄

@mlieberman85
Copy link

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 :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants