You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we predict the likelihood of sudden archiving of project otherwise successful in the sense of being used by others with active development?
Projects that are suddenly and unexpectedly archived can create significant issues for the people / organizations who rely on those projects.
Data concerns:
Can a large dataset of examples be generated? (probably need hundreds or thousands of examples)
Can metadata metrics be found that seem to correlate with repositories where this occurs?
How predictive are those metadata metrics in the sense of when they appear in a repository (looking back in time)?
What metrics can we use to distinguish between projects that are archived suddenly and unexpectedly vs. those that are archived when they've reached the natural end of life?
This is often related to Elephant Factor, which refers to too much control by a single company. These negative events in a project’s life that are strongly associated with too much single company control, meaning they are different than what occurs in a project with a diverse community of contributors and maintainers.
Related Links
No response
Note that we also have a Project Scope Template doc that you can use to think about the project details if you find it useful (not required).
How would you like to be involved in this project?
I am interested in this project, but do not plan to work on it myself
Additional Notes.
No response
The text was updated successfully, but these errors were encountered:
Project Name (1 - 3 words)
Sudden Archival
Description
Can we predict the likelihood of sudden archiving of project otherwise successful in the sense of being used by others with active development?
Projects that are suddenly and unexpectedly archived can create significant issues for the people / organizations who rely on those projects.
Data concerns:
This is often related to Elephant Factor, which refers to too much control by a single company. These negative events in a project’s life that are strongly associated with too much single company control, meaning they are different than what occurs in a project with a diverse community of contributors and maintainers.
Related Links
No response
Note that we also have a Project Scope Template doc that you can use to think about the project details if you find it useful (not required).
How would you like to be involved in this project?
I am interested in this project, but do not plan to work on it myself
Additional Notes.
No response
The text was updated successfully, but these errors were encountered: