-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add LF Energy and Open Mainframe landscapes (#58)
Signed-off-by: Sergio Castaño Arteaga <[email protected]> Signed-off-by: Cintia Sanchez Garcia <[email protected]> Co-authored-by: Sergio Castaño Arteaga <[email protected]> Co-authored-by: Cintia Sanchez Garcia <[email protected]>
- Loading branch information
1 parent
47a4ca7
commit 5424550
Showing
7 changed files
with
587 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
name: LFEnergy build and deploy | ||
|
||
on: | ||
schedule: | ||
- cron: "0 21 * * *" | ||
workflow_dispatch: | ||
|
||
jobs: | ||
build-landscape: | ||
uses: cncf/landscape2-sites/.github/workflows/build-and-deploy.yml@main | ||
with: | ||
foundation: lfenergy | ||
repository: lf-energy/lfenergy-landscape | ||
secrets: inherit |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
name: LFEnergy validate settings | ||
|
||
on: | ||
pull_request: | ||
branches: | ||
- main | ||
paths: | ||
- lfenergy/settings.yml | ||
|
||
jobs: | ||
validate-landscape-settings: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- uses: cncf/landscape2-validate-action@v2 | ||
with: | ||
target_kind: settings | ||
target_path: lfenergy/settings.yml |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
name: OMP build and deploy | ||
|
||
on: | ||
schedule: | ||
- cron: "0 20 * * *" | ||
workflow_dispatch: | ||
|
||
jobs: | ||
build-landscape: | ||
uses: cncf/landscape2-sites/.github/workflows/build-and-deploy.yml@main | ||
with: | ||
foundation: omp | ||
repository: openmainframeproject/omp-landscape | ||
secrets: inherit |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
name: OMP validate settings | ||
|
||
on: | ||
pull_request: | ||
branches: | ||
- main | ||
paths: | ||
- omp/settings.yml | ||
|
||
jobs: | ||
validate-landscape-settings: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- uses: cncf/landscape2-validate-action@v2 | ||
with: | ||
target_kind: settings | ||
target_path: omp/settings.yml |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,263 @@ | ||
# 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_NAME> | ||
# | ||
foundation: LFEnergy | ||
|
||
# Images (required) | ||
# | ||
# Urls some images used in the landscape UI. | ||
# | ||
# images: | ||
# favicon: <FAVICON_URL> | ||
# footer_logo: <FOOTER_LOGO_URL> | ||
# header_logo: <HEADER_LOGO_URL> | ||
# open_graph: <OPEN_GRAPH_IMAGE_URL> | ||
# | ||
images: | ||
favicon: "https://raw.githubusercontent.com/lf-energy/lfenergy-landscape/main/images/favicon.png" | ||
footer_logo: "https://raw.githubusercontent.com/lf-energy/artwork/main/other/lf-energy/horizontal/white/lf-energy-horizontal-white.svg" | ||
header_logo: "https://raw.githubusercontent.com/lf-energy/lfenergy-landscape/main/images/left-logo.svg" | ||
open_graph: "https://raw.githubusercontent.com/lf-energy/lfenergy-landscape/main/images/favicon.png" | ||
|
||
# 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: <CATEGORY_NAME> | ||
# subcategories: | ||
# - <SUBCATEGORY1_NAME> | ||
# - <SUBCATEGORY2_NAME> | ||
# | ||
categories: | ||
- name: LF Energy Member | ||
subcategories: | ||
- Strategic | ||
- General | ||
- Associate | ||
|
||
# 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(<RED>, <GREEN>, <BLUE>, <ALPHA>)". | ||
# | ||
# colors: | ||
# color1: <COLOR1> # Buttons, groups, links | ||
# color2: <COLOR2> # Some highlighted items like filters button, search icon | ||
# color3: <COLOR3> # Participation stats bars, spinners, modal titles | ||
# color4: <COLOR4> # Categories titles in filters, fieldset in filters modal | ||
# color4: <COLOR5> # Categories and subcategories frames (odd) | ||
# color5: <COLOR6> # Categories and subcategories frames (even) | ||
# | ||
colors: | ||
color1: "rgba(0, 55, 100, 1)" | ||
color2: "rgba(0, 143, 101, 1)" | ||
color3: "rgba(0, 55, 100, 1)" | ||
color4: "rgba(0, 55, 100, 0.7)" | ||
color5: "rgba(0, 154, 222, 0.9)" | ||
color6: "rgba(0, 55, 100, 0.9)" | ||
|
||
# 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: <SUBCATEGORY1_NAME> | ||
# - value: <SUBCATEGORY2_NAME> | ||
# | ||
featured_items: | ||
- field: maturity | ||
options: | ||
- value: graduated | ||
order: 1 | ||
label: Graduated | ||
- value: earlyadoption | ||
order: 2 | ||
label: Early Adoption | ||
- value: incubation | ||
order: 3 | ||
label: Incubation | ||
- value: sandbox | ||
order: 4 | ||
label: Sandbox | ||
- value: emeritus | ||
order: 5 | ||
label: Emeritus | ||
- value: lfess | ||
order: 6 | ||
label: Standards and Specs | ||
- value: working-group | ||
order: 7 | ||
label: Working Group | ||
- field: subcategory | ||
options: | ||
- value: Strategic | ||
|
||
# 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: <small|medium|large> | ||
# | ||
grid_items_size: small | ||
|
||
# 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: <GROUP_NAME> | ||
# categories: | ||
# - <CATEGORY1_NAME> | ||
# - <CATEGORY2_NAME> | ||
# | ||
groups: | ||
- name: Projects and products | ||
categories: | ||
- Renewable Energy | ||
- Energy Storage | ||
- Energy Systems | ||
- Consumption of Energy and Resources | ||
- Emissions | ||
- Industrial Ecology | ||
- Earth Systems | ||
- Climate and Earth Science | ||
- Natural Resources | ||
- Sustainable Development | ||
- Asset Management | ||
- Acquisition and Control | ||
- Customer and Market | ||
- Shared | ||
- System Management | ||
- Generation | ||
- Transmission | ||
- Distribution | ||
- DER | ||
- Customer Premises | ||
- name: Members | ||
categories: | ||
- LF Energy Member | ||
|
||
# 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: <CATEGORY_NAME> | ||
# | ||
members_category: LF Energy Member | ||
|
||
# QR code configuration (optional) | ||
# | ||
# Defines the configuration of the QR code that will be displayed on the UI as | ||
# well as on the downloadable landscape in PDF and PNG formats. | ||
# | ||
# qr_code: | ||
# url: <URL> | ||
# | ||
qr_code: | ||
url: https://lfenergy.landscape2.io | ||
|
||
# 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: <WIDTH_IN_PIXELS> | ||
# | ||
screenshot_width: 3000 | ||
|
||
# Social networks urls (optional) | ||
# | ||
# List of social networks urls that will be used to create some links in the | ||
# landscape web application. | ||
# | ||
# social_networks: | ||
# facebook: <FACEBOOK_URL> | ||
# flickr: <FLICKR_URL> | ||
# github: <GITHUB_URL> | ||
# instagram: <INSTAGRAM_URL> | ||
# linkedin: <LINKEDIN_URL> | ||
# slack: <SLACK_URL> | ||
# twitch: <TWITCH_URL> | ||
# twitter: <TWITTER_URL> | ||
# wechat: <WECHAT_URL> | ||
# youtube: <YOUTUBE_URL> | ||
# | ||
social_networks: | ||
facebook: "https://www.facebook.com/LFEnergyFoundation/" | ||
github: "https://github.com/lf-energy" | ||
linkedin: "https://www.linkedin.com/company/lf-energy-foundation" | ||
slack: "https://join.slack.com/t/lfenergy/shared_invite/zt-f9z7c305-SYbhNb2ffXJ~8jGd_gpwWQ" | ||
twitter: "https://twitter.com/LFE_Foundation" | ||
youtube: "https://www.youtube.com/channel/UCW2V5Sj6cme8na9BkTqfoJA" | ||
|
||
# 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 <CATEGORY1> are | ||
# owned by <TAG1>. 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: | ||
# <TAG1>: | ||
# - category: <CATEGORY1> | ||
# subcategories: | ||
# - <SUBCATEGORY1> | ||
# - <SUBCATEGORY2> | ||
# <TAG2>: | ||
# - category: <CATEGORY2> | ||
# |
Oops, something went wrong.