[FOLIO-1710] Document method for archiving repositories as deprecated Created: 16/Jan/19  Updated: 28/Feb/22  Resolved: 28/Feb/22

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: David Crossley Assignee: David Crossley
Resolution: Done Votes: 0
Labels: devdoc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1838 Follow the documented procedure to fu... Open
Relates
relates to FOLIO-618 clean-up folio organization Open
Sprint: CP: ready for planning, DevOps Sprint 134
Development Team: FOLIO DevOps

 Description   

Document the method for archiving repositories as deprecated.

There are various repositories that are no longer in use. Some have already been partially marked, in different ways, as being deprecated. Some have been "archived" as read-only at GitHub, but no statement in the README or "About" text. Some have been renamed, but not archived.

Follow https://dev.folio.org/faqs/how-to-archive-repository/
(Note that if really must be renamed, then that is very different and has many ramifications.)

This enables people to know at a glance, and enables any maintenance scripts that process all repositories to avoid these.

Please add Comments at FOLIO-1838 Open for other repositories that we know should be archived. Please close any of its open pull-requests. Note that archiving does still enable the repository to be re-enabled later if needed.



 Comments   
Comment by David Crossley [ 16/Jan/19 ]

There are some notes in FOLIO-1678 Closed .

Comment by Jakub Skoczen [ 28/Feb/19 ]

David Crossley can you provide some context here? Would this information be published on dev.folio.org?

Comment by David Crossley [ 01/Mar/19 ]

Yes i reckon at dev.folio.org

I am away now for the week-end. Will add more context next week. Will also add separate ticket for applying the procedure to the current set of partially deprecated repositories.

Comment by Peter Murray [ 30/Dec/20 ]

David Crossley: I'm wondering if my actions caused you to look at this. As a part of FOLIO-2900 Closed , I had to change the way I find eligible GitHub repos for translations. Previously I could rely on Lokalise to give me a list; now I need to pull a list of all stripes- and ui- from GitHub and check to see if there are translations on Lokalise. The lokalise-to-github script ignores repositories that have been marked as "archived", so there is now an interest in making sure deprecated repos are marked as archived. (Each call to Lokalise to get translations takes 20-25 seconds, so if I can avoid repos where we know there will be no translations the program will run faster.)

I marked one or two GitHub repos that I knew weren't being used, but I didn't follow a particular method to make sure everything that needed to be done was done.

Comment by David Crossley [ 30/Dec/20 ]

No Peter, it was because i am preparing for FOLIO-2926 In Code Review which inspects many older backend modules which still use the deprecated jenkins-slave-all Java 8 CI build image. I am finding that many of these have not yet upgraded to Java 11. For some of them i am suggesting that they consider being "Archived".

So i am encouraging them to finalise any open pull-requests, then list them at FOLIO-1838 Open , and i will follow to do the archiving steps.

Would you please also mention at FOLIO-1838 Open the ones that you have recently archived. I will investigate whether they need anything more done. That is where i am listing any that i have archived.

Comment by David Crossley [ 28/Feb/22 ]

The procedure is now documented: https://dev.folio.org/faqs/how-to-archive-repository/

Generated at Thu Feb 08 23:15:19 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.