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.

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

Archiving repositories #477

Open
neoncitylights opened this issue Nov 11, 2017 · 7 comments
Open

Archiving repositories #477

neoncitylights opened this issue Nov 11, 2017 · 7 comments

Comments

@neoncitylights
Copy link
Contributor

Making this ticket after a ping in Brickimedia/splash@ea75cbb (thanks for the ping!)

We'll probably be fine with deleting most of them or all of them. Here are some reasons why:

  • Don't have a purpose anymore (e.g the LocalSettings repo or extensions repo which is just a group of gitmodules)
  • others have been already migrated (e.g Refreshed and ArticleRatings)
  • Migrated and merged into something else (NumberOfComments was merged into Comments, GlobalContribs is in progress of being merged into GlobalContributions, DeepSea was archived after it was merged into the Theme extension, becoming a new available theme)
  • Archived (Snippet was archived in favor of TextExtracts extension), or USERNAME as an example, which didn't work as a PHP implementation.
  • or projects that used to be worked on but aren't worked on anymore (the Answers extension, Custard + Lia + Quartz skins, design-guide)

Pinging for @georgebarnick and @mary-kate for thoughts on this.

@georgebarnick
Copy link
Member

Is there a built-in way to archive a repository through GitHub?

@neoncitylights
Copy link
Contributor Author

Yes. (https://help.github.com/articles/archiving-a-github-repository/ https://help.github.com/articles/archiving-repositories/ etc)

If archiving is preferred to deleting, I'm fine with that too

@georgebarnick
Copy link
Member

I'd rather that just to preserve backlinks and other traces where we might have linked to stuff in the past.

georgebarnick added a commit to Brickimedia/LocalSettings that referenced this issue Nov 15, 2017
georgebarnick added a commit to Brickimedia/extensions that referenced this issue Nov 15, 2017
@georgebarnick
Copy link
Member

Archived LocalSettings and extensions as they're both deprecated repositories. Waiting to hear if anyone else has thoughts on archiving other repositories before proceeding.

georgebarnick added a commit to Brickimedia/splash that referenced this issue Nov 16, 2017
georgebarnick added a commit to Brickimedia/generalscripts that referenced this issue Nov 16, 2017
@neoncitylights
Copy link
Contributor Author

I was thinking of blanking the skin + extension repos so that just in case there's people who are using those, are forced to use whatever we provide as the replacement in the README instead. (e.g Brickimedia/Refreshed should provide a link to wikimedia/mediawiki-skins-Refreshed, Brickimedia/Snippet provides a link to wikimedia/mediawiki-extensions-TextExtracts). Thoughts on that?

@georgebarnick
Copy link
Member

Would it be possible for us to turn Brickimedia/Refreshed into a mirror of wikimedia/mediawiki-skins-Refreshed?

@neoncitylights
Copy link
Contributor Author

After some looking, apparently that's possible (didn't know that till now). Here's the link (which contains 3 different sections): https://help.github.com/articles/duplicating-a-repository/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants