or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
Digital Infrastructure Research Program Collaborative Notes
Funded Project Presentations
University of Washington (Kaylea Champion, Benjamin Mako Hill, Aaron Shaw, Morten Warncke-Wang) — Underproduction
Anushah Hossain — Supporting international OS communities
Frank Timmes et al. ASU, UC Santa Barbara, U Wisconsin-Madison
Erin Ytsma and Jana Gallus (Carnegie Mellon and UCLA) — Studies into motivation with non-monetary incentives
NYU (Thomas Streinz presenting — Critical Digital Infrastructure: Legal Technologies and Institutional Design
University of Canberra (Mathieu O’Neil et al. including with zack@debian) — Organizational hybridity
CMU (Laura Dabbish, Jim Herbsleb plus others not here) — Divisity and inclusion in digital infrastructure projects
Berkeley, San Diego, etc (Stu Geiger w/ Dorothy Howard presenting) —The Visible and Invisible Work of Maintaining Open Source Infrastructure
Stanford from Digital Civil Society Lab (Lucy Bernholz and ???) —
Martin Michlmayr — FOSS Foundations
RIT (Mel Chua + Stephen Jacobs) — How do people define sustainable?
Implicit Development Environments based in Berlin
Subject Matter Experts
Matt Germonprez (University of Nebraska, Omaha)
Nadia Eghbal (Independent Researcher at Protocol Labs)
Ben Nickolls (octobox)
Anna Filippova (GitHub)
Benjamin Mako Hill (University of Washington)
Common Questions that seem to apply to many projects:
Resources / Links
Polis poll report
Reading list
Organized by category
Open source basics
Economics
Legal
Licenses
Scholars
Case Studies
Governance
Culture
Hacking
Labor
Security (personal/institutional/national)
Infrastructure
Note: This is a quite random selection of "infrastructure" literature curated by NYU's IILJ project on "infrastructures as regulation" (InfraReg): www.iilj.org/infrareg
Ethnographies
Published literature reviews
Peer Production https://mako.cc/academic/benkler_shaw_hill-peer_production_ci.pdf
Data about OSS
Open data / access to data
Case Studies on specific domains/Genre
Tools for managing OSS communities: https://todogroup.org/guides/management-tools/
Cohort Recommendations
Maintainer Survey conversation notes
Technical Debt
Internal collaboration practices
Intentionality behind the role of a maintainer
Governance structure
Why software is not being maintained? Another way to think about it: competencies
Time use for maintainers
Economics of engagement
Ideas for how to spend money
Onboarding
How maintainers think about success
(open ended) What are you most concerned about / what keeps you up at night? (Already in a survey)
Repeat survey on a regular basis? Track over time
Demographics: type of project, respondent demographics
Tool ecosystem
Maintainer's self perceived role
How close are you to burnout?
Does your work feel rewarding?
What are outcome measures: satisfaction with process, satisfaction with outcomes?
Culture component: values like meritocracy
Can we reuse job satisfaction work and measures?
If we interview: