Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Retention standards #34

Open
ben-sagar opened this issue Jan 17, 2020 · 1 comment
Open

Retention standards #34

ben-sagar opened this issue Jan 17, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@ben-sagar
Copy link
Contributor

We should articulate our approach to data retention, in particular how it relates to open code.
@ben-sagar ben-sagar added the enhancement New feature or request label Jan 17, 2020
@Cruikshanks
Copy link
Member

I think if we focus on 'code' as data, then this would be useful.

How long we should keep projects around, what the process is for code that is no longer used, does this /should this process differ for published code vs private code etc.

GitHub has the ability to Archive projects. GitLab does to (though my experience is it hides them so well you might as well have deleted the project!) Before any of this was available I created and have used the archive group. Be nice to pin this down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Cruikshanks @ben-sagar