Skip to content
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.

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

Updating Main from v1.0 to v1.1 #379

Merged
merged 83 commits into from
Apr 18, 2024
Merged

Updating Main from v1.0 to v1.1 #379

merged 83 commits into from
Apr 18, 2024

Conversation

seanmcilroy29
Copy link
Contributor

@seanmcilroy29 seanmcilroy29 commented Apr 10, 2024

WG has agreed to the changes in Dev and has approved to update of the SCI in Main from v1.0 to v1.1

DO NOT MERGE UNTIL APPROVED AFTER REVIEW - 18 APR

Abhishek Gupta and others added 30 commits December 2, 2021 09:10
Co-authored-by: Asim Hussain <asim@codecraft.tv>
Co-authored-by: Asim Hussain <asim@codecraft.tv>
Co-authored-by: Asim Hussain <asim@codecraft.tv>
* Add first pass of text

* Add reference to RFC4122

* Added description of valid requirements

* Added first examples

* Grammar review

* Remove JSON

* Move table structure to appendix

* Remove reporting process

* Changed software boundary reporting requirements

* Removed other references to reports

* updated URLs

* Update Software_Carbon_Intensity/Software_Carbon_Intensity_Specification.md

Co-authored-by: Asim Hussain <asim@codecraft.tv>

* Update Software_Carbon_Intensity/Appendix_A_Further_Information_on_Reporting_Requirements.md

Co-authored-by: Asim Hussain <asim@codecraft.tv>

* Update Software_Carbon_Intensity/Software_Carbon_Intensity_Specification.md

Co-authored-by: Asim Hussain <asim@codecraft.tv>

* Changed baseline preset text

* Made software version mandatory

* Removed the requirement to report C and R baseline comment

Co-authored-by: Asim Hussain <asim@codecraft.tv>
Co-authored-by: Abhishek Gupta <3943612+atg-abhishek@users.noreply.github.com>
1. The software-boundary was not linked correctly.
2. Readability - LCA definition was defined later, moved it to the first reference.
1. Functional Unit was not linked properly
Qualifying that the elements in the SCI equation scale by the same functional unit R
* Add files via upload

* Update issue templates

* adding units

- units added for embodied emissions
- moved units to the bottom of each section 
- reformatted for consistency

Co-authored-by: Abhishek Gupta <3943612+atg-abhishek@users.noreply.github.com>
Co-authored-by: Sean Mcilroy <smcilroy@omaorg.org>
Co-authored-by: Sean Mcilroy <smcilroy@linuxfoundation.org>
Co-authored-by: Henry-WattTime <36998861+Henry-WattTime@users.noreply.github.com>
Included the changes for the Energy and Embodied emissions values for the database server.
Updated the Software Carbon Intensity Standard to include guidance on taking into account data center energy efficiency in the Software Boundary section
…ion.md


Space added

Co-authored-by: Abhishek Gupta <3943612+atg-abhishek@users.noreply.github.com>
Added context for SCI reduction for software roles
1. 'scale' should be first step in the process, as it's the key measure of success
2. 'what' is a bit misleading, and is best defined as a boundary  -> 'bound' is a good verb
3. 'how' is a step that best follows the boundary step -> 'bound' is a verb
WG approved
* Changed wording to highlight elimination

* Change exclusions

WG Approved

* Add space

WG approved

* Restore dev action sentence

WG Approved

Co-authored-by: Henry-WattTime <36998861+Henry-WattTime@users.noreply.github.com>
WG Approved
We've made it explicit in `I` but I believe we also need to make it explicit in `M`.
osamajandali and others added 10 commits September 20, 2023 14:30
So the website has some data to parse and show the current version number being displayed (it's not in the spec)

Signed-off-by: Asim Hussain <asim@codecraft.tv>
Signed-off-by: Sean Mcilroy <smcilroy@linuxfoundation.org>
Signed-off-by: Henry-WattTime <36998861+Henry-WattTime@users.noreply.github.com>
@akshitbatra
Copy link

[Suggestion]

Hey Team,
As we are planning to move from v1.0 to v1.1, could we maintain a Change Log file in the repository so it's easily trackable on what all has been changed from one version to another.

@seanmcilroy29
Copy link
Contributor Author

@akshitbatra - v1.1 and all future version updates will have their own feature release notes

@Henry-WattTime
Copy link
Contributor

Also, Sean very generously made a direct comparison that resolved many of the file name changes so you can see just the text changes: 1.0-comparison...1.1-comparison

Signed-off-by: Sean Mcilroy <smcilroy@linuxfoundation.org>
@seanmcilroy29 seanmcilroy29 merged commit e4081f2 into main Apr 18, 2024
2 checks passed
@seanmcilroy29
Copy link
Contributor Author

No Comments have been submitted during the review period.
WG has now agreed to merge this PR if no submissions are added by 18 Apr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.