Browse Source

update source reference to this specific file

master
Mel Chua 1 year ago
committed by GitHub
parent
commit
cceeae873e
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 9 deletions
  1. +7
    -9
      notes-11-10-2019.md

+ 7
- 9
notes-11-10-2019.md View File

@ -1,5 +1,3 @@
_These are also early stage analysis notes that synthesize across some of the first and second round transcripts, and are being used for third-round interviews._
# Plain text for posting during interviews
## Infrastructure vs non-infrastructure software
@ -52,25 +50,25 @@ JACKIE: As a user of other packages, I never really looked at sustainability bec
## FOSS vs non-FOSS infrastruture
> _Source(s): early analysis notes_
> _Source(s): notes-11-10-2019.md_
>
> 1. Infrastructure is “magical plumbing.” FOSS infrastructure lets you look behind the curtain if you so choose; non-FOSS infrastructure likely does not.
> _Source(s): early analysis notes_
> _Source(s): notes-11-10-2019.md_
>
> 2. Infrastructure requires technical effort for operations (as well as development). FOSS infrastructure may begin as a pet project and then “accidentally” go into production; non-FOSS infrastructure is more likely to be deliberately planned with allocated resources and to have project management much earlier on.
> _Source(s): early analysis notes_
> _Source(s): notes-11-10-2019.md_
>
> 3. Infrastructure requires development capacity (people-time). FOSS infrastructure is likely to have some or all of this development capacity come from self-directed volunteers, but that effort is also more likely to fade out during the “last mile.” Non-FOSS infrastructure is more likely to have its development resources known, managed, and allocated in advance.
> _Source(s): early analysis notes_
> _Source(s): notes-11-10-2019.md_
>
> 4. Infrastructure requires bureaucratic/organizational work. FOSS infrastructure is likely to have this set up late, during the “last mile” or the “sticking point.” Non-FOSS infrastructure is more likely to have this infrastructure (legal, organizational, financial, managerial, marketing, etc.) be set up early.
> _Source(s): early analysis notes_
> _Source(s): notes-11-10-2019.md_
>
> 5. Infrastructure user data and usage patterns are important for determining future resource needs. FOSS infrastructure maintainers are less likely than non-FOSS infrastructure ones to have complete and reliable access to that data because of intentional cultural choices to prioritize user freedom and access over it.
## Aggregated definitions of "well-maintained"
> _Source(s): early analysis notes_
> _Source(s): notes-11-10-2019.md_
>
> 1. There are people there to triage and address issues that come up in a timely manner.
> 1. There are people to make sure a project is keeping up with changes in the ecosystem (ex: maintaining compatibility when dependencies are updated, etc.)
@ -83,7 +81,7 @@ JACKIE: As a user of other packages, I never really looked at sustainability bec
## Aggregated definitions of "sustainability"
> _Source(s): early analysis notes_
> _Source(s): notes-11-10-2019.md_
>
> 1. There are resources (donated services or money to pay directly) for ongoing operating costs, including computing resources, people for operations, people for development, and people for “management.”
> 1. Will the resources needed for the project continue to be provided in the future?

Loading…
Cancel
Save