https://github.com/blahah/exploring_openness
OpenPlant March 2016
https://github.com/blahah/exploring_openness
Last synced: 4 months ago
JSON representation
OpenPlant March 2016
- Host: GitHub
- URL: https://github.com/blahah/exploring_openness
- Owner: blahah
- Created: 2016-03-02T14:26:20.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-03-02T14:28:38.000Z (over 9 years ago)
- Last Synced: 2024-12-27T19:13:31.667Z (5 months ago)
- Size: 1000 Bytes
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Explorations of openness
## Goals for this exploration
Help us all understand how this group thinks about openness, their motivations and possible pain-points.
Identify where open practices can be most effectively applied in the work this group does.
How can we collectively maximise the open impact of OpenPlant
## Activities
- introductions
- what does openness mean to you?
- what's the point?
- how are we working openly?
- how can we work openly?
- what are the obstacles?
- action plan
## What openness means
- availability and access
- reuse and redistribution
- universal participation
## 'Open' for data and content
“Open data and content can be freely used, modified, and shared by anyone for any purpose”
http://opendefinition.org/
## 'Open' for code
1. Free Redistribution
2. Source Code [must be included]
3. Derived Works [are allowed]
4. Integrity of The Author's Source Code [is preserved only for credit]
5. No Discrimination Against Persons or Groups
6. No Discrimination Against Fields of Endeavor
7. Distribution of License
8. License Must Not Be Specific to a Product
9. License Must Not Restrict Other Software
10. License Must Be Technology-Neutral
https://opensource.org/osd-annotated
## What should it mean for synbio?
## The goal of open is...
- accessibility
- participation
- agility
- momentum
- testing and rapid prototyping
- leverage
http://openmatt.org/2011/04/06/how-to-work-open/
## the goal of open is not...
- getting your work done for you
- public performance
- bike-shedding
## Open vs. Transparent
- transparent
- Public, but not necessarily enabling participation.
- passively transparent
- Not private; decisions aren’t actively hidden, but are difficult to locate. They may not even be documented. This is usually not done intentionally.
- actively transparent
- Everything is written down, is easily searchable and is locatable by interested parties. This requires intentional, sustained effort.
- open
- Public and participatory. This requires structuring efforts so that "outsiders" can meaningfully participate (and become "insiders" as appropriate).
https://wiki.mozilla.org/Working_open
## Trying to have impact without vast amounts of money
- minimum viable bureaucracy (https://air.mozilla.org/minimum-viable-bureaucracy/)
- self-organising communities
- the cathedral and the bazaar
- things that need to be high quality:
- communication
- information accessibility
- trust
- open is the most effective model
## valid obstacles
- it takes more work
- people will criticize my work
- we're not ready
## what gear of open?
- closed
- not yet
- open
- shout it from the rooftops
we all need to decide what mode we're comfortable in now
and what mode we want to be in
## In practise
- publishing open access
- making code open source
- open discussion
- high quality documentation
- bypassing restrictive systems
## More options
- explore specific tools and platforms
- mapping digital practices
- roadmapping