From 7e2e606ef2aed84bb90a81bba94cb051f55cc1bb Mon Sep 17 00:00:00 2001 From: jmertic <296737+jmertic@users.noreply.github.com> Date: Fri, 26 Apr 2024 04:13:53 +0000 Subject: [PATCH] Update members --- landscape.yml | 15 +- ..._sunvega_information_technology_co_ltd.svg | 1 + settings.yml | 276 ++---------------- 3 files changed, 33 insertions(+), 259 deletions(-) create mode 100644 logos/guangdong_sunvega_information_technology_co_ltd.svg diff --git a/landscape.yml b/landscape.yml index 92df880..c2ff9e0 100644 --- a/landscape.yml +++ b/landscape.yml @@ -9,22 +9,27 @@ landscape: name: Adobe Inc. homepage_url: https://adobe.com/ logo: adobe_inc.svg + twitter: https://twitter.com/Adobe crunchbase: https://www.crunchbase.com/organization/adobe-systems + joined: '2022-10-13' - item: name: Apple Inc. homepage_url: https://apple.com/ logo: apple_inc.svg twitter: https://twitter.com/Apple crunchbase: https://www.crunchbase.com/organization/apple + joined: '2019-05-01' - item: name: Autodesk homepage_url: https://autodesk.com/ logo: autodesk.svg + twitter: https://twitter.com/autodesk crunchbase: https://www.crunchbase.com/organization/autodesk - item: name: NVIDIA Corporation homepage_url: https://nvidia.com/ logo: nvidia_corporation.svg + twitter: https://twitter.com/nvidia crunchbase: https://www.crunchbase.com/organization/nvidia - item: name: The Walt Disney Studios @@ -72,11 +77,11 @@ landscape: twitter: https://twitter.com/EpicGames crunchbase: https://www.crunchbase.com/organization/epic-games-2 - item: - name: Guangdong Sanweijia Information Technology Co., Ltd + name: Guangdong Sunvega Information Technology Co., Ltd homepage_url: https://3vjia.com/ - logo: guangdong_sanweijia_information_technology_co_ltd.svg + logo: guangdong_sunvega_information_technology_co_ltd.svg organization: - name: Guangdong Sanweijia Information Technology Co., Ltd + name: Guangdong Sunvega Information Technology Co., Ltd - item: name: Hexagon AB homepage_url: https://hexagon.com/ @@ -104,16 +109,19 @@ landscape: name: OTOY, Inc. homepage_url: https://otoy.com/ logo: otoy_inc.svg + twitter: https://twitter.com/OTOY crunchbase: https://www.crunchbase.com/organization/otoy - item: name: SideFX (Side Effects Software Inc) homepage_url: https://sidefx.com/ logo: sidefx_side_effects_software_inc.svg + twitter: https://twitter.com/sidefx crunchbase: https://www.crunchbase.com/organization/side-effects-software-inc - item: name: Siemens AG homepage_url: https://siemens.com/ logo: siemens_ag.svg + twitter: https://twitter.com/Siemens crunchbase: https://www.crunchbase.com/organization/siemens - item: name: Sony Group Corporation @@ -137,6 +145,7 @@ landscape: name: Trimble Inc. homepage_url: https://trimble.com/ logo: trimble_inc.svg + twitter: https://twitter.com/TrimbleCorpNews crunchbase: https://www.crunchbase.com/organization/trimble - item: name: Worley Limited diff --git a/logos/guangdong_sunvega_information_technology_co_ltd.svg b/logos/guangdong_sunvega_information_technology_co_ltd.svg new file mode 100644 index 0000000..2ef9ac1 --- /dev/null +++ b/logos/guangdong_sunvega_information_technology_co_ltd.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/settings.yml b/settings.yml index 8a739e1..8638cf3 100644 --- a/settings.yml +++ b/settings.yml @@ -1,271 +1,35 @@ -# Landscape2 settings -# -# This settings file allows customizing some aspects of the landscape. - -# Foundation (required) -# -# Name of the foundation. This value is used in some labels, so we recommended -# to keep it as short as possible. -# -# foundation: -# foundation: Alliance for OpenUSD (AOUSD) - -# Url (required) -# -# Url where the landscape will be hosted. -# -# url: -# url: http://127.0.0.1:8000 - -# Analytics (optional) -# -# Analytics providers configuration. When an analytics provider is set up, some -# additional code from the provider will be injected into the web application. -# -# analytics: -# gtm: # Google Tag Manager configuration -# container_id: # Landscape web application container ID -# - -# Base path (optional) -# -# Base path where the landscape will be hosted. By default the generated -# landscape is prepared to be hosted at the root of the domain. However, if the -# landscape will be hosted in a subpath, this value must be set accordingly. -# -# base_path: / -# - -# Categories (optional) -# -# Categories information is read from the `landscape.yml` data file. The way -# categories are displayed in the web application is computed dynamically based -# on the number of categories and subcategories, as well as the number of items -# on each. Sometimes, however, we may want subcategories to be displayed in a -# specific order within a category (this happens often in the Members category). -# In those cases, it is possible to define that order by overriding a category. -# -# This option can also be used to not display one or more subcategories in the -# landscape. To achieve that, we only need to exclude the subcategory from the -# subcategories list when overriding a category. -# -# categories: -# - name: -# subcategories: -# - -# - -# - -# Colors (optional) -# -# Colors used across the landscape UI. The colors section is optional but, when -# provided, *all colors must be provided*. Colors must be specified using the -# following format: "rgba(, , , )". -# -# colors: -# color1: # Buttons, groups, links -# color2: # Some highlighted items like filters button, search icon -# color3: # Participation stats bars, spinners, modal titles -# color4: # Categories titles in filters, fieldset in filters modal -# color4: # Categories and subcategories frames (odd) -# color5: # Categories and subcategories frames (even) -# colors: - color1: "rgba(0, 107, 204, 1)" - color2: "rgba(255, 0, 170, 1)" - color3: "rgba(96, 149, 214, 1)" - color4: "rgba(0, 42, 81, 0.7)" - color5: "rgba(1, 107, 204, 0.7)" - color6: "rgba(0, 42, 81, 0.7)" - -# Featured items (optional) -# -# This section allows highlighting items that match certain criteria. You can -# define a list of rules and the matching items will be featured in a special -# way in the landscape. -# -# Each rule must define a field for the check as well as the values that will -# trigger a match. At the moment the fields supported are: -# -# - maturity -# - subcategory -# -# When a given item's field matches any of the values provided, it will be -# considered a featured item. For each option, it is possible to also define an -# order (which item would be displayed first) and a label for the item. -# -# featured_items: -# - field: subcategory -# options: -# - value: -# - value: -# + color1: rgba(0, 107, 204, 1) + color2: rgba(255, 0, 170, 1) + color3: rgba(96, 149, 214, 1) + color4: rgba(0, 42, 81, 0.7) + color5: rgba(1, 107, 204, 0.7) + color6: rgba(0, 42, 81, 0.7) featured_items: - field: maturity options: - value: graduated order: 1 label: Graduated - -# Footer (optional) -# -# This section allows customizing some aspects of the footer. -# -# footer: -# links: -# facebook: -# flickr: -# github: -# homepage: -# instagram: -# linkedin: -# slack: -# twitch: -# twitter: -# wechat: -# youtube: -# logo: # Foundation logo featured on the footer -# text: # Copyright notice, for example -# footer: links: - facebook: "https://www.facebook.com/CloudNativeComputingFoundation/" - flickr: "https://www.flickr.com/photos/143247548@N03/albums" - github: "https://github.com/cncf" - homepage: "https://cncf.io" - instagram: "https://www.instagram.com/humans.of.cloudnative/" - linkedin: "https://www.linkedin.com/company/cloud-native-computing-foundation/" - slack: "https://slack.cncf.io/" - twitch: "https://www.twitch.tv/cloudnativefdn" - twitter: "https://twitter.com/cloudnativefdn" - wechat: "https://www.cncf.io/wechat/" - youtube: "https://www.youtube.com/c/cloudnativefdn" - logo: "https://raw.githubusercontent.com/cncf/artwork/master/other/cncf/horizontal/white/cncf-white.svg" - -# Grid items size (optional) -# -# Defines the preferred size of the landscape items in the grid mode. When the -# landscape contains many items, it is recommended to use the `small` size. -# However, if there aren't many items, choosing `medium` or `large` may make -# the landscape look nicer. Users will still be able to adjust the items size -# from the UI using the zoom controls. -# -# grid_items_size: -# + facebook: https://www.facebook.com/CloudNativeComputingFoundation/ + flickr: https://www.flickr.com/photos/143247548@N03/albums + github: https://github.com/cncf + homepage: https://cncf.io + instagram: https://www.instagram.com/humans.of.cloudnative/ + linkedin: https://www.linkedin.com/company/cloud-native-computing-foundation/ + slack: https://slack.cncf.io/ + twitch: https://www.twitch.tv/cloudnativefdn + twitter: https://twitter.com/cloudnativefdn + wechat: https://www.cncf.io/wechat/ + youtube: https://www.youtube.com/c/cloudnativefdn + logo: https://raw.githubusercontent.com/cncf/artwork/master/other/cncf/horizontal/white/cncf-white.svg grid_items_size: large - -# Groups (optional) -# -# In some cases, specially when a landscape contains lots of items, it may be -# interesting to organize them in groups. Each group will be displayed on a -# different tab in the landscape web application. Each entry must contain the -# name of the group (it will be displayed as is) and a list with the categories -# (as defined in the landscape.yml data file) that will be part of this group. -# -# groups: -# - name: -# categories: -# - -# - -# - -# Header (optional) -# -# This section allows customizing some aspects of the header. -# -# header: -# links: -# github: -# logo: # Foundation logo featured on the header -# header: links: - github: "https://github.com/cncf/landscape2" - logo: "https://raw.githubusercontent.com/cncf/artwork/master/other/cncf-landscape/horizontal/color/cncf-landscape-horizontal-color.svg" - -# Images (optional) -# -# Urls of some images used in the landscape UI. -# -# images: -# favicon: -# open_graph: -# - -# Name of the members category (optional) -# -# Landscapes usually have a special category dedicated to the members of the -# corresponding foundation. It is possible to use any name for that category, -# but it is important that we define it here as there are some special -# operations that depend on it. -# -# members_category: -# - -# Osano (optional) -# -# Osano cookies consent form configuration. When the Osano configuration is -# provided, some additional code will be injected into the web application. -# -# The `customer_id` and `customer_configuration_id` fields values can be -# obtained from the url in the configuration script code available on the Osano -# site: -# -# https://cmp.osano.com///osano.js -# -# osano: -# customer_id: -# customer_configuration_id: -# - -# Screenshot width (optional) -# -# Width of the landscape screenshots automatically generated (in pixels). -# Screenshots won't be taken if this value is not provided. -# -# screenshot_width: -# + github: https://github.com/cncf/landscape2 + logo: https://raw.githubusercontent.com/cncf/artwork/master/other/cncf-landscape/horizontal/color/cncf-landscape-horizontal-color.svg screenshot_width: 1500 - -# TAGs (optional) -# -# Projects items can specify which TAG owns them in the `landscape.yml` file -# (by using the `tag` field in the `extra` item's section). However, sometimes -# this information is not available at the item level. This configuration -# section provides a mechanism to automatically asign a TAG to projects items -# based on the categories and subcategories they belong to. -# -# For example, we can define that all projects in the category are -# owned by . When the items are processed, the corresponding TAG will be -# set in the items that match the rule defined. The TAG defined at the item -# level always takes precedence, so when it's present it won't be replaced. -# -# NOTE: TAGs names should only use lowercase case letters and hyphens (no -# spaces or other characters), and should not be prefixed with "tag". The -# subcategories field is optional and, when omitted, all of them will be -# included. -# -# tags: -# : -# - category: -# subcategories: -# - -# - -# : -# - category: -# - -# Upcoming event (optional) -# -# This section allows configuring an upcoming event that will be featured on -# the landscape web application. Expired events won't be displayed. -# -# upcoming_event: -# name: # Event name (required) -# start: # Start date: (required, format: YYYY-MM-DD) -# end: # End date: (required, format: YYYY-MM-DD) -# banner_url: # Event banner image url (required, recommended dimensions: 2400x300) -# details_url: # Event details URL (required) -#