惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
Microsoft Security Blog
Microsoft Security Blog
Recent Announcements
Recent Announcements
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Last Week in AI
Last Week in AI
罗磊的独立博客
腾讯CDC
云风的 BLOG
云风的 BLOG
月光博客
月光博客
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 三生石上(FineUI控件)
宝玉的分享
宝玉的分享
U
Unit 42
I
InfoQ
D
DataBreaches.Net
Blog — PlanetScale
Blog — PlanetScale
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
V
V2EX
美团技术团队
IT之家
IT之家
Stack Overflow Blog
Stack Overflow Blog
F
Fortinet All Blogs
GbyAI
GbyAI
S
SegmentFault 最新的问题

Ubuntu blog

Bring Zenoh to ROS 2 with snaps | Ubuntu Evolution of the RISC-V ISA. What next after RVA23? | Ubuntu Cut bloat, not features | Ubuntu Ubuntu now certified on Qualcomm Dragonwing™ IQ-8275 | Ubuntu Grace on the currents: Stonking Stingray | Ubuntu How we create a Canonical Academy exam | Ubuntu Surviving the uncharted: when dedicated OpenStack expertise is your best ally in disaster recovery  | Ubuntu Canonical joins the Open Secure AI Alliance | Ubuntu AI harnesses for telco autonomous networks | Ubuntu Arduino® VENTUNO™ Q is available for pre-order with Ubuntu pre-installed | Ubuntu Advantech AOM-2721 is now Ubuntu Certified | Ubuntu Canonical integrates NVIDIA Nemotron 3.5 Lightning with Ubuntu for always-on AI agents | Ubuntu Ubuntu’s virtualization hardware enablement (HWE) stack: a new model for confidential computing enablement | Ubuntu Confidential computing and the new regulatory focus on data in use | Ubuntu A day in the life of an Android developer with Anbox Cloud | Ubuntu Canonical announces the Enterprise Store as part of Ubuntu Pro | Ubuntu Tracing a memory leak bug in PID 1 and contributing an upstream fix: a Linux support story | Ubuntu MAAS installation: bare metal provisioning is easier than ever | Ubuntu Januscape vulnerability CVE-2026-53359 mitigations available | Ubuntu Managing Ubuntu on bare metal at scale | Ubuntu Ubuntu Server: a platform made for enterprise scale | Ubuntu Building an open source chain of trust: new research uncovers key blockers and ways forward | Ubuntu Beyond safety and security: Why automotive open source demands dependability  | Ubuntu DirtyClone Linux kernel local privilege escalation vulnerability fixes available | Ubuntu pedit COW kernel local privilege escalation vulnerability mitigations | Ubuntu Canonical becomes Gold Sponsor of Trifecta Tech Foundation | Ubuntu Challenges designers face in open source (and how to fix them) | Ubuntu Hunting a 16-year-old SQLite bug with TLA+: is dqlite affected? | Ubuntu Anbox Cloud on C4A metal: Android, at scale, without friction | Ubuntu Canonical announces live kernel patching for Arm64 | Ubuntu
Template: Streamlining open source design contributions |...
Nina Rojc (N · 2026-06-16 · via Ubuntu blog

As designers working at Canonical, we’re always thinking about open source. We believe that encouraging more designers to contribute to open source  benefits everyone, from the project maintainers to the end users themselves.  

In the 2025 edition of FOSSBackstage conference, we presented our research findings on  why designers don’t get involved in open source projects and found a particular breakdown between designers and project maintainers. 

The truth is that designers often struggle to find projects they can contribute to. When they do find a project, the design requirements often are unclear or very limited. Meanwhile, project maintainers struggle to articulate their design needs or may not even know when to ask for design support. 

To bridge this gap, we created a template for a design contribution brief for open source projects. This template will help maintainers to clearly articulate their needs and give designers the essential information they need to contribute. 

What’s in the contribution brief?

The brief has 5 sections, one for each area that can cause friction when maintainers try to onboard a designer to a project. The brief includes questions and examples that help maintainers add context to their contribution requirements, so a designer can pick up a project more easily. Here’s what each section covers:

  1. About the project: enables maintainers to get designers up to speed with a project overview, vision, target audience, and progress tracking. This section ensures everyone is on the same page about the project’s goals and context.
  2. About the design contribution needed: here’s where you detail the specific design contributions – from UX and UI, to graphic design and accessibility audits. Explain why you need the contribution, what user needs are, and what design skills are essential.
  3. Logistics: outline deadlines, priority levels, and timelines to keep everyone organized and on track.
  4. Team: introduce the project team and their roles, highlight any existing designers or contributors.
  5. Communications: specify how the team communicates (for example, asynchronously, synchronously), preferred communication platforms, preferred language, and any support for onboarding contributors.

Why use the contribution brief?

Benefits for project maintainers:

  1. Set clear expectations: the template breaks down project expectations to help maintainers articulate what they’re really looking for, and help designers understand the expectations. This makes it easier to communicate design needs and expectations to potential contributors.
  2. Streamline your process: adding all the information to a centralized place makes it easy to reference and saves time and effort. The template addresses the most commonly asked questions, which reduces the need to repeat the same things in different channels. 
  3. Attract the right contributors: clearly articulating design needs helps attract people with the right skills and experience. Maintainers can tag their issues with specific labels and maximize their chance to reach the right audience.

Benefits for designers:

  1. Understand the project: designers can quickly grasp the project’s vision, goals, and target audience, without getting in touch or looking for information in more than one place.
  2. Know your requirements: a specific scope makes it easier to know where to start and how much work will need to be done. The template helps clarify what design contributions are required and the expected outcomes.
  3. Streamline your onboarding: the template makes it easier to understand how the team communicates and where designers can get support quickly.

How to use the template


Join the Canonical design team

We’re looking for designers who care about craft and how systems work under the hood. At Canonical, design sits at the intersection of UX, engineering, and open source where we shape cohesive, accessible experiences across cloud, desktop, and IoT products.

If you enjoy solving complex problems and turning technical depth into clarity, explore our open roles: canonical.com/careers