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

[Article] Do emission challenges vary across types of software? #229

Open
12 tasks
NAMRATA-WOKE opened this issue May 2, 2024 · 1 comment
Open
12 tasks
Assignees
Labels

Comments

@NAMRATA-WOKE
Copy link
Contributor

Article Details

Please enter the details here

Proposer: Namrata Narayan | Dir. Communications & Member Relations | @NAMRATA-WOKE
Abstract: Addressing the question if emission output concerns and considerations vary across types of software, and highlighting what developers might need to consider to decarbonize their software effectively
Why: Introduce how the GSF categorizes software and build understanding that can be more commonly considered
Audience: Software developers, heads of product and solution architects
Timeline: June 2024

Important Information

To be filled out later

Author: TBC
Other contributors: @NAMRATA-WOKE, TOSS team
Article Link: (Link to the doc, must be in our official GSF drive)
Graphics Link: (Link to the design assets for this article, must be in our official GSF drive)
Published Link: (The link the article was published to for memory)

Checklist

  • Idea discussed and selected for writing. After checking this box, set Status to "Todo" under "Articles" project
  • Author identified. After checking this box Assign issue to the Author
  • Scheduled in calendar
  • Google doc link created in GSF drive.
  • In progress. After checking this box, set Status to "In Progress" under "Articles" project
  • Draft created. After checking this box, set Status to "In Review" under "Articles" project. Assign issue to Reviewer/Author during the back-and-forth
  • Draft reviewed. After checking this box, set Status to "In Publishing" under "Articles" project. Assign issue to Graphic Designer and add "Graphic Design" to issue's Projects
  • Graphics created. After checking this box, assign to TBC for approval.
  • Approved. After checking this box, assign to TBC for publishing.
  • Published. After checking this box, set Status to "Ready" under "Articles" project. Assign to Marketing and add "D: Marketing" to issue's Projects
  • Shared on socials
  • Shared on newsletter. After checking this box, set Status to "Done" under "Articles" project and close issue.
@NAMRATA-WOKE
Copy link
Contributor Author

NAMRATA-WOKE commented May 2, 2024

From TOSS Miro:

Types of Software: 

  1. consumer-based
  2. operational
  3. web-based
  4. transactional
  5. Simulation/modelling
  6. Network streaming

@NAMRATA-WOKE NAMRATA-WOKE self-assigned this May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant