Open Design (OSD forum version) (Transparency movements (Open... (Science…
(OSD forum version)
(especially self-taught beginners)
Pioneer for designers
Give more opportunities to work for good: non-profits and FOSS.
Beginner designers do work for free for commercial projects by participating in design contests (spec work).
Beginner designers create fictional work and don't get real-world experience.
Open the design process further: write more detailed case-studies, research reports and guidelines.
Create more educational content that focuses on design process.
In particular, they look at “pretty pictures” on Behance and Dribbble and don't see the real thought process behind them.
Beginner designers may have a distorted view on design, because they are exposed to limited amount of parts of it and don't see the whole picture.
Create a technology that would allow open design collaboration.
Designers who can't code can't contribute to the open
A lot of open source products are designed by developers thus they don't feature well-thought-out user experience (not usable).
Give designers the ability to collaborate with open source developers.
Open Design System
Show open source software UI-s to designers and ask for help.
Match designers who want to help/need portfolio with open source projects that would benefit from the design help.
Open notebook science
To scientific literature
Currently most of the scientific researches are behind the paywall
Specifically: research outputs
OS Schools of thought
The public misunderstanding
Difficult discovery verification
Getting overwhelmed by unsorted information
Funded publicly therefore should be public
Allows rigorous peer review
Makes science more reproducible and transparent
Will help answer uniquely complex questions
Open Peer Review
Open science taxonomy
Peer & Public review
Online & Offline
Software: API, SDK
Contributors can extend product's functionality
Introducing a partially-completed product
Collaborative product design and development
Idea competitions (hackathons)
Between a firm and a knowledge-based partner
(e.g. a research institution)
Knowledge Transfer Partnerships
Open Source vs.
(They are not mutually exclusive)
Might conflict on patent issues
Example: “Is it acceptable to withhold information that could save the world’s poorest people from suffering and death?”
Open Source Design
Open Source Design agency
Helps open source projects with usability studies, UX, visual design and illustrations
Designed style guides for Tor and other open source projects
Patreon — $77/mo
Commissions by OTF Usability Lab
6-person team, each passionate about open movements
Open Technology Fund
Specifically aimed at reducing users' false sense of security
OTF sponsors agencies and teams to conduct usability studies for open source projects and improve their UX.
Any open source project can apply and ask for help
Open Source Design Foundation
Jobs & Projects
Open up the design process
Improve developer-designer communication
Connect the existing open source community
Funding for open source design
Improve the design of open source projects
Showcase existing open source design
Make designers contributors
Targeted at developers and designers interested in working and designing in open source
Open Design Foundation
Open Source Design Manifesto
find time for meaningful projects
openly participate in design discussions
work with other designers by choice
improve my toolbox
share my design experiences; both the good and the bad
find opportunities to design in the open
Difficulties of design in Open Source
Everyone has an opinion on design
Designers have to fight for their opinions
Solution: set clear goals, discourage “taste talk”
Current decision foundation
Difficulty of implementation
Should be: alignment to goals, impact & effort
Autochecks — automatic decisions for developers
Design is not as quantifiable as code
Decision makers are developers
Usability vs unit tests
4 more items...
Usability tests require preparation and people
Solution: educate developers, give designers more voice
Solutions: bring more designers to open source
Not many people who can provide feedback
Solution: bring more designers to open source
Usually a designer is working alone on one project
Necessary designer traits
Play long-term game
Willing to put a lot of time into OS
Familiarity with open source
Knows politics and ideologies of OS
Share OS values
Solution: find connection between ethical concerns of designers and FOSS
Want to create value, not money
OS cultural assumptions
Copyright is positive in design
But everything is a remix
Culture can be toxic
Code of conduct
Design work is not valued
“Settings and options are great”
Linux is for power users who want choice
Integration testing is valued, usability testing is not.
Nature of design
3 more items...
Benefits of open source
3 more items...
Projects are developed as scratching own itches
Designers can't do it due to nature of design
(“you are not your user”)
OS is best at text interfaces, simple tools
2 more items...
2 more items...
Engineering and design cultures
1 more item...
1 more item...
More design work = more work for devs
Cannot be opened by default on Mac and Windows
Standard for readmes and documentation
File limit of 100MB
Doesn't count comments towards the log
No support for Creative Commons licenses
No “drag & drop” on GH Desktop
GitHub says “Built for developers”
GitLab's Kubernetes & CI
Licenses are confusing, too many of them
Solution: Creative Commons
Universities teach “industry standard”
Not very accessible
Solution: SVG or other shareable formats
Tools are difficult to use
Git is hard
Language is confusing
No website source code
No easy way to find source files
No design contribution docs
Solution: Design contribution page
SVG can be diffed but it's not widely used in design
Instead proprietary tool formats are used
“The Cathedral and the Bazaar”
WIP is closed
Releases are public
Code is developed in the view of the public
Open source appropriate technology
Currently — engineering design / design of physical products
Zoybar: open source 3D printed guitar
Uzebox: open-design video game console
RepRap: general-purpose 3D printer that can print itself
Advanced projects that are too hard for single company
High-tech local solutions for sustainable development
Developing technologies for common good
More eyes and hands can notice and improve more flaws
Everybody can contribute and improve the work or build upon it
Free access for developing countries
Mass access to knowledge
Higher development productivity
Early customers — in the development process
Higher accuracy for marketing research
Synergism between internal and external innovations
Reduced cost of research and development
Potential for viral marketing
Maximizing author or content impact or reach
Challenges for open models
Limited time (e.g. 6 mo. embargo on articles)
How it can work
Compiled code/prepared product is not
Example 1: Dumplings company shows how it makes its products. Still not everybody is ready to cook them, so they buy the prepared ones.
Example 2: a tool is open source, but only the development version. User has to download a bunch of development tools and compile the code to avoid paying the money. And they will have to do it with every update, which is not as convenient as buying the product.
Source materials (instructions/code) are open
Constant (e.g. paid software)
Freemium (e.g. FontAwesome icons)
Separate line of non-open material
Selling physical products
Advertisements, subscriptions and other regular business models
Funds, grants and government support
Individual's savings/passive income/wage
Part of the revenue of a company/corporation
Paying contributors (non-profit)
Getting profit (company)
Paying by contribution amount
Failed due to not having the “open-source spirit”.
No monetary incentive (volunteers)
The users of the tool who want to make it better
Beginners who are learning and trying to gain professional experience
Paying for features that were implemented (no matter whether employee did that or not).
Employees are paid to contribute to open source software used by their employer.
Some people believe that open source projects are of low quality
“Open source software is that it's not sturdy enough for the enterprise.”
“Open source software full of bugs and is unsafe”
Peer review system
May be biased in some models (e.g. author-pays-for-publication)
Revealing intellectual property and losing competitive advantage
Potential for revealing information not intended for sharing
And regulating how contributors affect a project
Complexity of controlling the development/innovation process
Developers + designers
Figma Developer Handoff
(only invited people can view and participate)
Paper and a pen
(everyone can view & contribute)
They are only accessible to developers
You can invite people or open them for everyone to edit
Principle, Flinto, Origami etc.
Kaktus (VCS for Sketch)
Adobe PS, AI etc.
Slack, Twist, Discord
Forums, Q&A (Stack Exchange)
Going to art school
Thoughts, concepts, essays, etc.
Design lessons (theory)
Analyze others' work
Individuals' and agencies' portfolios
Freely shared design assets
News, tool reviews
Tutorials & how-tos
Tips and tricks
Basics of design (theory)
Business of design
Things that are currently adding to the transparency in design and related fields
Everyone who paid money (or contributed in other way)
Everyone with a link
Public — everyone with an account
Public — no need to sign up (anonymous)
Only invited users
Only the creator
Contributors can edit the master, don't need to create copies
Example: Open for
Figma and Google Docs files
Little to no moderation
Contributors can duplicate the master and edit their copy
Example: Open for
Figma and Google Docs files
If necessary, changes can be added to the master manually
Contributors can edit the copy, then add your edits back to master
Example: GitHub repositories (fork –> commit –> pull)
Final result only
Viewing and Sharing
Open to anyone, anonymous
Can be found freely on the web
Graph-like structure: fork –> commit –> pull
Moderated by privileged users
Discussions: issues, comments on pull requests
Open to everyone with an account
Branches of commits
Project stages — commits/releases
Commit — a freeze-frame shot of the file at a given time; a saved version in a backup.
Figma file open for editing
Viewing and sharing
Open to anyone with the link, anonymous
Linear — anyone can change any element, even project name
No moderation, everyone has access to everything in a file
Discussions in the form of comments
Or tree-like, if someone decides to duplicate given project
Real-time, even the cursor movement is visible
Version history is linear
There are a lot of
ways to get involved
in this project
A great example of an extremely transparent project is Wikipedia. They've developed a platform called Phabricator that helps everyone manage the Wikipedia-related work.
“Phabricator is a collaboration platform open to all Wikimedia contributors. It is mostly used for managing work related to software projects. Non-technical initiatives are welcome as well.”
Assets (mocks and designs)
Tasks & Bugs
Projects & Tags
(Kanban style boards)
Boards with tasks, backlog
Members & Watchers
A group devoted to the design research of Wikipedia. They share a backlog of things that need to be researched. During the work, they give presentations, recruit participants and conduct user research.
All tasks are open to the public so everyone could contribute by conducting a research or finding some design solutions and sharing them with the team.
Sponsoring the creative open source contributions
A fully open-source game
What kind of design?
Physical Product Design
Hardware and software
Interior, exterior, landscape, architecture
“Design of business” (branding, identity, marketing, etc.)
Software Product Design
Who is involved?
Prototype & Test
What is it?
Set of tools?
Made by Gleb Sabirzyanov