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] A scorecard for processes and features. #104

Open
12 tasks
NAMRATA-WOKE opened this issue May 9, 2023 · 2 comments
Open
12 tasks

[Article] A scorecard for processes and features. #104

NAMRATA-WOKE opened this issue May 9, 2023 · 2 comments
Assignees
Labels
articles blocked Issue needs attention before it can be worked on

Comments

@NAMRATA-WOKE
Copy link
Contributor

Article Details

Please enter the details here

Proposer: Asim Hussain | Exec. Dir. & Chair | @jawache )
Abstract: Energy rating is commonplace for household appliances, cars and even houses. Why not software? Emissions depend on a number of factors, e.g. the 'ls' command is going to be incredibly efficient and perhaps scores an A, how would you score windows explorer? A D? But it does a lot more. How would you solve this objectively without bringing a human opinion into it.
Why: (Why is this article an important topic to discuss and how is it related to the work/mission/theory of change of the GSF)
Audience: (Which audience is most going to connect to the content in this article)
Timeline: (Should this article come out before or after an important date)

Important Information

To be filled out later

Author: (Who is assigned to write this article)
Other contributors: (Experts, Reviewers)
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

Discussed here.

@jawache notes:

Do you have a process to monitor the SCI score of your application in production?
Has your team completed the green software training?

If you answer yes to 100% you get an A, 90% you get a B etc...

IMO we should be scoring the "development process" not "a specific version of an application", ls and windows explorer can both score A, even if they have wildly different feature sets as long as they have strong process's in place to ensure all future versions of the software emit the least carbon possible.

@NAMRATA-WOKE
Copy link
Contributor Author

Bench until we can write a conversation piece.
@jawache sees this more as a project right now that we need to perhaps focus on/create. Punting for a couple of months.

@NAMRATA-WOKE NAMRATA-WOKE added the blocked Issue needs attention before it can be worked on label May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
articles blocked Issue needs attention before it can be worked on
Projects
None yet
Development

No branches or pull requests

2 participants