Skip to content

typo fixes #359

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

typo fixes #359

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cdbb0ec
typo fixes
jessLryan May 11, 2025
cc02061
DCO Remediation Commit for Jess <[email protected]…
jessLryan May 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ For the longest time, the feedback we've received is that people need actionable

The catalog of green software patterns is an online open-source database of software patterns reviewed and curated by the Green Software Foundation across a wide range of categories. Any software practitioner can find the patterns related to their field, technology, or domain. Anyone can submit a pattern that triggers a detailed review process by the Foundation. You can be confident that applying any patterns that have completed that process will reduce your software emissions.

The intention is that patterns are vendor agnostic, for instance there should not be Azure, AWS and GCP patterns. There should be generic cloud patterns which could be applied to specific vendors, but the patterns themselves are vendor agnostic. We encourage specific platforms/vendors to create vendor-specific versions of these patterns for their specific products on their platforms.
The intention is that patterns are vendor-agnostic, for instance there should not be Azure, AWS and GCP patterns. There should be generic cloud patterns which could be applied to specific vendors, but the patterns themselves are vendor-agnostic. We encourage specific platforms/vendors to create vendor-specific versions of these patterns for their specific products on their platforms.

To use the patterns, head to https://patterns.greensoftware.foundation and search for your field or technology. Each pattern is atomic and applicable to real-world situations and applications.

Expand All @@ -26,7 +26,7 @@ The project is led by:
* **Tag Category**: Select the most appropriate category from: Artificial Intelligence, Cloud, or Web which might apply to this pattern
* **Tags**: A [pre-defined list of additional tags](https://patterns.greensoftware.foundation/tags/) which might apply to the pattern (e.g. Machine Learning, Gaming, Mobile).
* **Description**: A full description of what problem this pattern is solving
* **Solution**: How will this patter solve the problem
* **Solution**: How will this pattern solve the problem
* **SCI Impact**: How will this pattern affect an SCI score of an application and why
* **Assumptions**: What are the assumptions being made
* **Considerations**: Discussion section anything that should be taken into consideration when implementing this pattern
Expand Down Expand Up @@ -60,7 +60,7 @@ The pattern is merged into dev but is not published on our website.


### Consistency Review
Every quarter the dev branch is merged to the main branch and this triggers a consistency review where anyone in the Foundation has 2 weeks to comment or object. We need GSF wide consensus for the patterns to be published.
Every quarter the dev branch is merged to the main branch and this triggers a consistency review where anyone in the Foundation has 2 weeks to comment or object. We need GSF-wide consensus for the patterns to be published.

This is done in batches every quarter to reduce the noise to the rest of the Foundation.

Expand Down