search

seamusocionnaigh / DeveloperCarbonDashboard

BSD 3-Clause "New" or "Revised" License
4 stars 0 forks source link

Scope 3 inclusion #2

Open Marksbutcher opened 11 months ago

Marksbutcher commented 11 months ago

Can you please confirm if you are including the scope 3 emissions from the supply chain and if so which sub categories and how has this data been validated.

scope 3 from your context for AWS will be substantial

Also, do you include emissions other than server related?

tysonread-salesforce commented 10 months ago

Hi Mark, these numbers don't include Scope 3 emissions right now. Just curious, how would scope three emissions be helpful for a developer building with Salesforce features?

On Mon, Oct 23, 2023 at 5:54 AM Mark Butcher @.***> wrote:

Can you please confirm if you are including the scope 3 emissions from the supply chain and if so which sub categories and how has this data been validated.

scope 3 from your context for AWS will be substantial

Also, do you include emissions other than server related?

— Reply to this email directly, view it on GitHub https://github.com/seamusocionnaigh/DeveloperCarbonDashboard/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARUWOVYHHHARUXWDX5MWSATYAZSIXAVCNFSM6AAAAAA6MA2UQ2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TOMJQGEZTGNY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Marksbutcher commented 10 months ago

Hi, building in scope 3 is critical as without that the numbers are under reporting by anything up to 99%

Also, excluding scope 3 means that developers are only seeing a tiny part of the problem they are trying to solve. The scope 3 are the key component that showcase to a developer the true impact of their decisions