31 lines
1.2 KiB
Plaintext
31 lines
1.2 KiB
Plaintext
change characteristics
|
|
- interaction/union of technical and procedural change
|
|
- NEED: is there any eval of whether change worked or not
|
|
- NEED: introduction of new thing or update to existing thing
|
|
|
|
actors
|
|
- NEED: to what extent are the actors abstracted away from, their actions evaluated on their own merits
|
|
- NEED: seniority; what's the direction of the change in lay terms, bottom-up or top-down; also, is the change agent within the project or the ecosystem
|
|
- NEED a little bit more color regarding the operationalized definition of contirbutor or maintainer
|
|
|
|
methods:
|
|
- NEED small-n case studies or broad data set
|
|
|
|
environment
|
|
- NEED the extent to which the project was aligned with the environment beforehand
|
|
- NEED: is the gap directly articulate by the environment? or more competitive/TFG
|
|
- same as identifying antecedents or constant differnec
|
|
- e.g. compiance or popularity
|
|
misc
|
|
- NEED framing the change as good?
|
|
- scope of the change vs. taken for granted
|
|
- relevant intrinsic motivations? productivity for productivity's sake?
|
|
- NEED is the work descriptive or evaluative
|
|
|
|
additional categories:
|
|
- scope/relevance of the change
|
|
- how do the researchers focus on/identify intention?
|
|
- NEED practitioner recommendations/broader impacts
|
|
|
|
|