You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been working on a new version of the landscape generating software, landscape2. This new version relies on the same landscape.yml file as the main data source, so nothing changes regarding adding or updating entries to the landscape.
Some landscapes (i.e. CNCF or OSPO) have already been successfully migrated to landscape2, and we'd like to continue migrating some more 🙂
We are already building the LF Networking landscape using landscape2, you can check it out at https://presto.landscape2.io/. It'd be great if you could give it a try when you have a chance and, whenever you are ready, we can proceed with the migration.
The process is very simple and would involve the following steps (we'd be happy to help with them):
Add/update some DNS entries [1]
Update the code used to embed the landscape in other websites (if applicable) [2]
Stop background automated processes that write to this repository (i.e. CNCF bot)
Unlink this repository from Netlify
Update README file and clean up some files no longer needed in this repository
[1] We’d need to know the hostnames you'd like to use to prepare our end to listen on them before switching the DNS (i.e. landscape.prestodb.io). Once we are ready we'll provide you with the destination for the DNS entries so that you can update them.
[2] Landscape2 supports embedding a view with items in a category/subcategory in another website, but it works slightly different than landscape1. If parts of this landscape are embedded using this mechanism on other websites, we'd appreciate if you could let them know about how it works now so that they can prepare in advance.
The text was updated successfully, but these errors were encountered:
Hi! 👋
We've been working on a new version of the landscape generating software, landscape2. This new version relies on the same
landscape.yml
file as the main data source, so nothing changes regarding adding or updating entries to the landscape.Some landscapes (i.e. CNCF or OSPO) have already been successfully migrated to landscape2, and we'd like to continue migrating some more 🙂
We are already building the LF Networking landscape using landscape2, you can check it out at https://presto.landscape2.io/. It'd be great if you could give it a try when you have a chance and, whenever you are ready, we can proceed with the migration.
The process is very simple and would involve the following steps (we'd be happy to help with them):
landscape.yml
file on PRs (optional)Please ping me if you have any question 😉
[1] We’d need to know the hostnames you'd like to use to prepare our end to listen on them before switching the DNS (i.e. landscape.prestodb.io). Once we are ready we'll provide you with the destination for the DNS entries so that you can update them.
[2] Landscape2 supports embedding a view with items in a category/subcategory in another website, but it works slightly different than landscape1. If parts of this landscape are embedded using this mechanism on other websites, we'd appreciate if you could let them know about how it works now so that they can prepare in advance.
The text was updated successfully, but these errors were encountered: