THE LINUX FOUNDATION PROJECTS

QUICK GUIDANCE FOR GRANTEE BLOGS

Use this guide when writing blogs, announcements, or updates about work supported by Alpha-Omega.

How to describe Alpha-Omega

“Alpha-Omega protects society by funding and catalyzing sustainable security improvements across open source software.”

Describe Alpha-Omega as a fund, funding partner, or catalyst for open source security. Keep your team’s work and results at the center of the story.

Do’s and Don’ts

DO

🟢 Explain what Alpha-Omega funding enabled and why it matters.
🟢 Credit the maintainers, engineers, foundations, researchers, and partners doing the work.
🟢 Highlight concrete progress, measurable results, and lasting improvements.
🟢 Use clear, collaborative, factual language.
🟢 Write the name as Alpha-Omega, including the hyphen.

DON’T

❌ Stop at “thanks to our sponsor” without explaining the impact.
❌ Imply Alpha-Omega performed work carried out by your team or other partners.
❌ Claim a project is completely secure or that one grant solves open source security.
❌ Use marketing hype, alarmism, or unsupported claims.
❌ Call it the “Alpha-Omega Foundation.

Optional: Referencing OpenSSF or the Linux Foundation

You do not need to mention OpenSSF or the Linux Foundation. If you choose to include that context, use:

  • OpenSSF: “Alpha-Omega is an associated project of the Open Source Security Foundation (OpenSSF).”
  • Linux Foundation: “Alpha-Omega is a directed fund within the Linux Foundation.”

Avoid using the three names interchangeably when crediting funding.

Blog formatting and style

  • Include an author’s name with every blog.
  • Add an “About the Author” section at the end with the author’s photo and a short bio.
  • Write for easy scanning by readers and AI tools. Use clear H2 headings, phrased as questions when appropriate, and answer each question directly in the text that follows.
  • Keep paragraphs focused and concise. Use bullets when they make results or steps easier to scan.
  • Avoid marketing hype. Focus on the work, results, and impact.
  • Credit AI-generated images. Include a caption beneath the image naming the AI tool and the prompt used. If the prompt is lengthy, provide a clearly labeled summary.
  • Example: “AI-generated image created with ChatGPT. Prompt: ‘Illustrate open source maintainers collaborating to strengthen software security, using a simple blue-and-gold palette.’”

Simple blog structure

Use these questions as H2 headings, adapting them to your project:

  1. What security challenge did the project face? Explain the need and why it matters.
  2. What did Alpha-Omega funding enable? Describe the work and credit those who performed it.
  3. What improved? Share verified results, examples, metrics, or links.
  4. What comes next? Explain how you will sustain or build on this progress.

Finish with an About the Author section, including a photo and short bio.

Copy-and-adapt acknowledgment

“With funding from Alpha-Omega, [project/team] was able to [specific work]. This resulted in [verified outcome], helping [community/ecosystem] improve [security capability]. Our next step is [next milestone].”

Optional prompt for AI-assisted editing

“Edit this grantee blog using the attached Alpha-Omega guidance. Describe Alpha-Omega as a fund and catalyst for sustainable open source security improvements, never as a foundation. Mentioning OpenSSF or the Linux Foundation is optional. If included, describe Alpha-Omega as an associated project of the Open Source Security Foundation (OpenSSF) or a directed fund within the Linux Foundation, respectively.

Preserve the author’s voice, credit those who performed the work, and connect funding to specific outcomes. Use clear H2 headings phrased as questions when appropriate, followed by direct answers. Keep paragraphs concise and avoid marketing hype. Include an author’s name and an ‘About the Author’ section at the end with a photo and short bio. Flag missing author details or photos.

If an AI-generated image is included, add a caption identifying the AI tool and the prompt used, or a clearly labeled prompt summary. Flag missing details rather than inventing them.

Do not invent metrics, quotes, funding amounts, biographical details, or security claims. Flag missing evidence.”