Summary

The GSF is a trusted resource on green software practices, tools, resources, and training to reduce the total change in global carbon emissions associated with software. The content we produce must improve knowledge amongst practitioners, providing deeply researched thought pieces and surfacing practical advice from green software leaders and experts for how to apply green principles to software, and take the conversation on green software forward.

The content we develop has a direct impact on the tooling we make available. This project is part of our communications ecosystem, which includes newsletters, podcasts, perspective pieces, use cases and expert interviews.

Contribute to the Writers Program

The GSF will favor perspective pieces that offer a unique and detailed perspective on the application of green software principles, patterns, and tools across industries to decarbonize software and advance software towards having zero harmful effects on the environment. The GSF welcomes article submissions from all and is committed to introducing more voices and perspectives from the industry.

Editorial Guidelines 

In addition, articles should be: 

• On topic (related to software design, development, operations, and monitoring and measurement to reduce the carbon emissions of software 

• Fresh (in other words, offer a fresh or unique perspective)

• Relevant to the challenges and opportunities that exist for enterprises to reduce software’s environmental impact. 

• Evidence-based (i.e., facts must be backed with supporting research or experience)

• Educational (i.e., the purpose of the content is to inform and offer guidance, not promote or sell any products or services).
  
  

Style Guide 

1. Article length? Be Pithy. 

Generally, we will publish features between 500-1,200 words. 

2. Subheadings? We like them. 

Subheadings are particularly useful when a feature covers multiple points or is guiding a reader through a process or stages of work. Subheadings should summarize the respective section of your article and provide a quick and easy guide to see what an upcoming section is all about. Subheadings should be in lowercase sentence format, with no period at the end. 

3. Link to GSF resources and projects? Please. 

Contributors can refer to our blogs, working group pages, Github Issues, reports, and Use Cases. We encourage individuals to link to previously published GSF material, especially if there is data on our site, or case studies that can offer more insight on the topics covered in your article. We may embed related links throughout the article to link back to previously published material. 

For links, please hyperlink the most relevant word in a phrase or sentence, and cite reputable publications as opposed to blogs when possible. We will remove hyperlinks that, in our view, are self-promotional or distracting. 

4. Include Examples? They will surely help make your point stick. 

Articles that help readers contextualize the problem or opportunity being addressed, relevant to their geography, industry, or field of practice, are helpful. Examples help illustrate the points being made and can help readers grasp the nuances of big ideas. 

Every contributor will have access to GSF’s editorial team to support them in their writing journey. If you’re not comfortable with writing, we hope this program encourages you to start and develop your voice in the field. All perspective pieces will go through a round of editing and approval to ensure the article aligns with the foundation’s mission and meets editorial guidelines. 

If you are interested in submitting a use case, white paper, or research paper, please contact us at news@greensoftware.foundation. 

OKRs

OBJ1: Write engaging content

• KR 1.1: 20K visitors a month reading our articles by the end of 2023

• KR 1.2: 2 min average reading time for our articles by end of 2023

OBJ2: Write high-value content

• KR 2.1: Domain authority increases from 40 to 50 by EOY 23

• KR 2.2: Backlinks increases from 900 to 1500 by EOY 23