Create Onboarding Guide #25
Merged
Conversation
This file contains hidden or 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
|
@Henry-WattTime to change introductions to first meeting of every month. Fix links. |
Henry-WattTime
commented
Nov 10, 2022
|
|
||
| ## Read the Specification | ||
| The specification forms the foundation of everything that this working group focuses on. We suggest that you read the SCI specification cover to cover (don't worry, it's not that long!). Not only will you be intimately familiar with this key document, but your fresh eyes will help identify gaps and limitations in the current specification. If there are areas that you have questions about and want to dig deeper, we suggest looking at the FAQ (forthcoming). If questions remain or there are ambiguities, this may be a perfect area that you can help us improve the specification. The most recent version of the specificaiton can be found here <link> (it might be wise to view the 'dev' branch to see the current draft version as well). |
There was a problem hiding this comment.
Suggested change
| The specification forms the foundation of everything that this working group focuses on. We suggest that you read the SCI specification cover to cover (don't worry, it's not that long!). Not only will you be intimately familiar with this key document, but your fresh eyes will help identify gaps and limitations in the current specification. If there are areas that you have questions about and want to dig deeper, we suggest looking at the FAQ (forthcoming). If questions remain or there are ambiguities, this may be a perfect area that you can help us improve the specification. The most recent version of the specificaiton can be found here <link> (it might be wise to view the 'dev' branch to see the current draft version as well). | |
| The specification forms the foundation of everything that this working group focuses on. We suggest that you read the SCI specification cover to cover (don't worry, it's not that long!). Not only will you be intimately familiar with this key document, but your fresh eyes will help identify gaps and limitations in the current specification. If there are areas that you have questions about and want to dig deeper, we suggest looking at the FAQ (forthcoming). If questions remain or there are ambiguities, this may be a perfect area that you can help us improve the specification. The most recent version of the specificaiton can be found [here](https://github.com/Green-Software-Foundation/software_carbon_intensity) (it might be wise to view the 'dev' branch to see the current draft version as well). |
Henry-WattTime
commented
Nov 10, 2022
|
|
||
| ## Read the Specification | ||
| The specification forms the foundation of everything that this working group focuses on. We suggest that you read the SCI specification cover to cover (don't worry, it's not that long!). Not only will you be intimately familiar with this key document, but your fresh eyes will help identify gaps and limitations in the current specification. If there are areas that you have questions about and want to dig deeper, we suggest looking at the FAQ (forthcoming). If questions remain or there are ambiguities, this may be a perfect area that you can help us improve the specification. The most recent version of the specificaiton can be found here <link> (it might be wise to view the 'dev' branch to see the current draft version as well). |
There was a problem hiding this comment.
Suggested change
| The specification forms the foundation of everything that this working group focuses on. We suggest that you read the SCI specification cover to cover (don't worry, it's not that long!). Not only will you be intimately familiar with this key document, but your fresh eyes will help identify gaps and limitations in the current specification. If there are areas that you have questions about and want to dig deeper, we suggest looking at the FAQ (forthcoming). If questions remain or there are ambiguities, this may be a perfect area that you can help us improve the specification. The most recent version of the specificaiton can be found here <link> (it might be wise to view the 'dev' branch to see the current draft version as well). | |
| The specification forms the foundation of everything that this working group focuses on. We suggest that you read the SCI specification cover to cover (don't worry, it's not that long!). Not only will you be intimately familiar with this key document, but your fresh eyes will help identify gaps and limitations in the current specification. If there are areas that you have questions about and want to dig deeper, we suggest looking at the FAQ (forthcoming). If questions remain or there are ambiguities, this may be a perfect area that you can help us improve the specification. The most recent version of the specification can be found here <link> (it might be wise to view the 'dev' branch to see the current draft version as well). |
Henry-WattTime
commented
Nov 10, 2022
| The specification forms the foundation of everything that this working group focuses on. We suggest that you read the SCI specification cover to cover (don't worry, it's not that long!). Not only will you be intimately familiar with this key document, but your fresh eyes will help identify gaps and limitations in the current specification. If there are areas that you have questions about and want to dig deeper, we suggest looking at the FAQ (forthcoming). If questions remain or there are ambiguities, this may be a perfect area that you can help us improve the specification. The most recent version of the specificaiton can be found here <link> (it might be wise to view the 'dev' branch to see the current draft version as well). | ||
|
|
||
| ## Onboarding Session | ||
| Once a month the working group asks all new members to briefly introduce themselves and explain their interest in the Standards Working group at the beginning of the regularly scheduled working group call. This is a great time to raise any questions about the specification or indicate areas of expertise that you can contribute to. |
There was a problem hiding this comment.
Suggested change
| Once a month the working group asks all new members to briefly introduce themselves and explain their interest in the Standards Working group at the beginning of the regularly scheduled working group call. This is a great time to raise any questions about the specification or indicate areas of expertise that you can contribute to. | |
| At the first working group meeting of the month we ask all new members to briefly introduce themselves and explain their interest in the Standards Working group at the beginning of the regularly scheduled working group call. This is a great time to raise any questions about the specification or indicate areas of expertise that you can contribute to. |
Henry-WattTime
commented
Nov 10, 2022
| We assign a 'buddy' to new members who can answer questions, orient you to key topics, and generally support getting you up to speed so that you can meaningfully contribute to the working group. You and the mentor should work out the most effective way for you to communicate, whether by call, email, or other messaging platform. | ||
|
|
||
| ## Operations | ||
| The 'How We Work' <link> section explains how we work by consensus, when we meet, what projects we are working on, and some other details of how to contribute. |
There was a problem hiding this comment.
Suggested change
| The 'How We Work' <link> section explains how we work by consensus, when we meet, what projects we are working on, and some other details of how to contribute. | |
| The ['How We Work'](https://standards.greensoftware.foundation/#how-we-work) section explains how we work by consensus, when we meet, what projects we are working on, and some other details of how to contribute. |
Henry-WattTime
commented
Nov 11, 2022
|
|
||
| ## Mentor for New Members | ||
| We assign a 'buddy' to new members who can answer questions, orient you to key topics, and generally support getting you up to speed so that you can meaningfully contribute to the working group. You and the mentor should work out the most effective way for you to communicate, whether by call, email, or other messaging platform. | ||
|
|
There was a problem hiding this comment.
Suggested change
| ## Time Commitment | |
| We expect working group member to attend the weekly hourlong meetings as well as contribute to the the specification between meetings. There may be other project specific work that the working group may engage on as well. |
Henry-WattTime
added a commit
that referenced
this pull request
Nov 18, 2022
This reverts commit 9b8b3aa.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.