-
Notifications
You must be signed in to change notification settings - Fork 2
Mothball
Matthew Gentzkow edited this page Sep 12, 2020
·
1 revision
A mothballed repository refers to a repository where no further active work is expected but the repository is kept in a condition such that work can readily begin again. To mothball a repository, confirm all of the following requirements have been satisfied. During this process, you are welcome to reach out to previous comment makers if you need their input to satisfy the mothballing requirements.
- All current issues have been closed with clear deliverables (if the issue was complete) or clear summaries of what was done / not done (if the issue was incomplete).
- All branches have been merged to master if they contain completed work that we would like to keep. Once relevant branches have been merged to master, all branches should be deleted.
- Complete copies of all relevant data (both raw and cleaned) have been documented and stored somewhere safe and easily accessible.
- A "Mothball" page has been added to the repository wiki with a summary of what we did in the project, why we decided to pause work, and the state we are leaving the project in.
- Practice Task
- Autofilling Values
- Overleaf Workflow
- IT Support
- Research Clusters
- Legacy Tools
- Style Guides
- Mothballing Projects
- Recruiting on Social Media
- PhD Applications
- Gentzkow-Shapiro Lab Notes
- Allcott-Gentzkow Lab Notes