Please enable JavaScript.
Coggle requires JavaScript to display documents.
Open Design (OSD forum version) (Transparency movements (Open... (Science…
Open Design
(OSD forum version)
Problems
Designers
(especially self-taught beginners)
Problem #2
Solution
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.
Problem #1
Solution
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.
Open Source
Problem #3
Solution
Create a technology that would allow open design collaboration.
Designers who can't code can't contribute to the open
source projects.
Problem #4
A lot of open source products are designed by developers thus they don't feature well-thought-out user experience (not usable).
Solution
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.
Unifying solution
Match designers who want to help/need portfolio with open source projects that would benefit from the design help.
Transparency movements
Open...
Science
Open Access
Open Science
Open notebook science
To scientific literature
Currently most of the scientific researches are behind the paywall
Specifically: research outputs
Open Research
Articles
https://en.wikipedia.org/wiki/Science_2.0
https://en.wikipedia.org/wiki/Open_research
https://en.wikipedia.org/wiki/Open_access
https://en.wikipedia.org/wiki/Open_science
OS Schools of thought
Infrastructure
Measurement
Public
Democratic
Pragmatic
Arguments
Against
The public misunderstanding
Low-quality science
Difficult discovery verification
Potential misuse
Getting overwhelmed by unsorted information
For
Funded publicly therefore should be public
Allows rigorous peer review
Makes science more reproducible and transparent
Will help answer uniquely complex questions
More impact
Open Peer Review
Open Data
Open Methodology
Science 2.0
Open science taxonomy
Education
Flexible learning
Agile
Reduced cost
Peer & Public review
Time efficient/
Time flexible
Accessible
Example: MOOCs
Related:
http://manifesto.edutainme.ru/en
Online & Offline
Innovation
Models
Product platforming
Software: API, SDK
Contributors can extend product's functionality
Introducing a partially-completed product
Collaborative product design and development
Customer immersion
Innovation networks
Idea competitions (hackathons)
Government-driven
Between a firm and a knowledge-based partner
(e.g. a research institution)
Knowledge Transfer Partnerships
Open Source vs.
Open Innovation
(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?”
Source
Hardware
Open Source Design
Ura
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
Business model
Patreon — $77/mo
Commissions by OTF Usability Lab
6-person team, each passionate about open movements
Open Technology Fund
Usability Lab
https://www.opentech.fund/labs/usability-lab/
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
Focus
Articles
Events
Jobs & Projects
Goals
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
https://opensourcedesign.net/
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
I will:
share my design experiences; both the good and the bad
find opportunities to design in the open
http://opendesign.foundation/
Difficulties of design in Open Source
Community
Opinions
Everyone has an opinion on design
Designers have to fight for their opinions
Solution: set clear goals, discourage “taste talk”
Decision-making
Current decision foundation
Difficulty of implementation
Should be: alignment to goals, impact & effort
“Likes”
Autochecks — automatic decisions for developers
Design is not as quantifiable as code
Decision makers are developers
Usability vs unit tests
Rule-based evaluation
4 more items...
Usability tests require preparation and people
Solution: educate developers, give designers more voice
Feedback
Solutions: bring more designers to open source
Not many people who can provide feedback
Loneliness
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
Mature, independent
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.
Cultural conflict
People believe...
Nature of design
3 more items...
Benefits of open source
3 more items...
OS motivaiton
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
Words
CI/CD
2 more items...
PR
2 more items...
Engineering and design cultures
Collaboration
In design
1 more item...
In software
1 more item...
More design work = more work for devs
Infrastructure
Markdown
Cannot be opened by default on Mac and Windows
Standard for readmes and documentation
GitHub/GitLab
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
Legal
Licenses are confusing, too many of them
Solution: Creative Commons
Design tools
Universities teach “industry standard”
Not very accessible
Solution: Figma
Solution: SVG or other shareable formats
Tools are difficult to use
Git is hard
Language is confusing
Not automatic
Solution: SparkleShare
Assets
No website source code
No easy way to find source files
Documentation
No design contribution docs
Solution: Design contribution page
SVG
SVG can be diffed but it's not widely used in design
Instead proprietary tool formats are used
General
Motivational
Infrastructural
Cultural
Software
Linux
“The Cathedral and the Bazaar”
Cathedral model
WIP is closed
Releases are public
Bazaar model
Code is developed in the view of the public
Open source appropriate technology
Useful tables
“Open culture”
on Wikipedia
“Open Access”
on Wikipedia
Design
Currently — engineering design / design of physical products
Examples
Zoybar: open source 3D printed guitar
Uzebox: open-design video game console
RepRap: general-purpose 3D printer that can print itself
Directions
Advanced projects that are too hard for single company
High-tech local solutions for sustainable development
Developing technologies for common good
https://en.wikipedia.org/wiki/Open-design_movement
Content
Media
(transparent media)
Motivations
Collaboration
More eyes and hands can notice and improve more flaws
Everybody can contribute and improve the work or build upon it
Knowledge sharing
Free access for developing countries
Mass access to knowledge
For companies
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
(recognition, citations)
Challenges for open models
Funding $$$
Current models
Direct
Paywall
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)
Donations
Separate line of non-open material
Selling physical products
“Author-pays-for-publication” model
Advertisements, subscriptions and other regular business models
Indirect (external)
Funds, grants and government support
Individual's savings/passive income/wage
Part of the revenue of a company/corporation
What for?
Paying contributors (non-profit)
Operational costs
Getting profit (company)
Incentivizing contributors
Failed :(
Paying by contribution amount
Failed due to not having the “open-source spirit”.
Current models
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.
Work quality
Quality misconception
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)
Information disclosure
Revealing intellectual property and losing competitive advantage
Potential for revealing information not intended for sharing
Process control
And regulating how contributors affect a project
Complexity of controlling the development/innovation process
Related cultures
Maker Culture
Hacker Culture
DIY Culture
Resources
Tools
Developers + designers
JIRA
Zeplin
Figma Developer Handoff
Webflow
Collaborative
Closed
(only invited people can view and participate)
Avocode
Notion
Coggle
Vectary
InVision
Mural
In-person
Whiteboard
Paper and a pen
Open
(everyone can view & contribute)
Glitch
GitHub/GitLab
CodePen
They are only accessible to developers
Too open
or
closed
Google Docs
Dropbox Paper
You can invite people or open them for everyone to edit
Figma
Non-collaborative
Principle, Flinto, Origami etc.
Sketch
Kaktus (VCS for Sketch)
Adobe PS, AI etc.
Organization, discussion
Slack, Twist, Discord
Zoom, Hangouts
Trello
Forums, Q&A (Stack Exchange)
Learning
Curriculum
Online courses
Going to art school
Reading materials
Thoughts, concepts, essays, etc.
Design lessons (theory)
Case studies
Research papers
Guidelines
Individual
Mentorship
Analyze others' work
Individuals' and agencies' portfolios
Freely shared design assets
Videos
Types
News, tool reviews
Tutorials & how-tos
Tips and tricks
Basics of design (theory)
Business of design
Examples
Charli Marie
TheFutur
Zimri
Femke
Dann Pretty
Things that are currently adding to the transparency in design and related fields
Digital Collaboration
Access
Who
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
To what
Contributing
Contribution flow
Linear
Contributors can edit the master, don't need to create copies
Example: Open for
editing
Figma and Google Docs files
Little to no moderation
Tree
Contributors can duplicate the master and edit their copy
Example: Open for
viewing
Figma and Google Docs files
If necessary, changes can be added to the master manually
Graph-like
Contributors can edit the copy, then add your edits back to master
Example: GitHub repositories (fork –> commit –> pull)
Kinds
Educate
Test
Build upon
Document
Translate
Promote
Design
Meet up
Primary
Direct edit
Comment
Discuss
Suggest
Viewing
Sharing
When
Process stages
Final result only
Real-time
Examples
GitLab repository
Viewing and Sharing
Open to anyone, anonymous
Can be found freely on the web
Contributing
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
When
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
Or invite-only
Open to anyone with the link, anonymous
Contributing
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
When
Real-time, even the cursor movement is visible
Version history is linear
Wikipedia
There are a lot of
ways to get involved
in this project
Phabricator
tool
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.”
Features
Collaboration
Groups
Dashboards
Chat Rooms
Event Calendar
Assets (mocks and designs)
Project Management
Tasks & Bugs
Projects & Tags
(Kanban style boards)
Code
Source browser
Code review
Audit commits
Build status
Example:
Design Research
project
Contains
Boards with tasks, backlog
Goals
Subprojects
Recent activity
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.
Specifically in
Design
Utopian
Sponsoring the creative open source contributions
https://join.utopian.io/
SteemMonsters
https://steemmonsters.com/
A fully open-source game
My Vision
What kind of design?
Physical Product Design
Fashion
Potentially:
Engineering, CAD
Hardware and software
Interior, exterior, landscape, architecture
“Design of business” (branding, identity, marketing, etc.)
Software Product Design
(initially)
Who is involved?
Business
Researchers
Analysts
Strategists
Entrepreneurs
Marketers
Foundation
Developers
Designers
Other creatives?
Identity
Brand
UX
Prototype & Test
Analysts
Researchers
Copywriters
Graphics
Web/Mobile
What is it?
Non-profit?
Set of tools?
Community
Platform?
Movement!
Platform-agnostic
Transparency
Made by Gleb Sabirzyanov