[Project]: Seismic Shifts Data Set [was Exodus]

[geekygirldawn]

Project Name (1 - 3 words)

Seismic Shifts

Description

Note: most of this description is out of date - see comments below

This project will take a Biweekly approach to gathering information to move along toward the goal of even defining what "exodus" is, the behaviors we see around it, and where we want to go with this research.

TASK FOR 06/05-06/13: Fill out examples of instances of people leaving a project, or events where you think people left projects in this form:

https://docs.google.com/spreadsheets/d/1KntxoZWfUxkfp1XHlDRuoWOZnpC0Y6SF3OCFJxbMihU/edit?usp=sharing

Please put anything that comes to mind, we will clean up all the examples later on!

Additional food for thought / conversation topic from the April 10, 2024 CHAOSS Data Science WG meeting:

• Takeoff, but should we also consider exodus as the other side.
• Plan to form a research group to look at signals before / after a mass exodus (like Redis) - what do people find using different tools. Research paper or blog might be a good outcome. This is something @cdolfi & @GaryPWhite have been talking about.
• Sophia's MSR paper might also be relevant for this topic: Estimating Usage Of Open Source Projects

From Cali on Slack: A discussion in the Augur-8Knot meeting (@Gary White) came up to look at specific metrics around the xz vulnerability (repo is locked in https://github.com/tukaani-project/xz). I wanted to open it up to a broader research idea I had. Originally mine was around codebase signals before a mass exodus of a project. It would be great to organize with whoever is interested to:

• Choose whether we wanted to look at the topic project exodus or malicious code vulnerability
• pick a few projects that had the cited event happen
• each person look at the tools/metrics they regularly use to see if there are any trends leading up to this event
• See if there are any relevant conclusions from this experiment and create a blog post or otherwise with our findings

Related Links

(https://docs.google.com/spreadsheets/d/1KntxoZWfUxkfp1XHlDRuoWOZnpC0Y6SF3OCFJxbMihU/edit?usp=sharing)

How would you like to be involved in this project?

@cdolfi will take the the lead on this one!

Additional Notes.

I wanted to capture this along with the rest of the projects, but no pressure at all to work on this now. I know that Cali is on vacation / really busy at work, so this is here for whenever people are ready to tackle it.

[cdolfi]

Sheet to fill out, more context to come https://docs.google.com/spreadsheets/d/1KntxoZWfUxkfp1XHlDRuoWOZnpC0Y6SF3OCFJxbMihU/edit?usp=sharing

[geekygirldawn]

The idea behind this project is to build a dataset of Seismic Shifts - big things that happen to projects that are likely to cause disruptions (e.g., license changes, forks, move to foundation, acquisition, community unrest). The spreadsheet above has a start at building this dataset, which could be used by other projects to look at what happens before / after certain types of big events.