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
Our repository contains a deprecated folder for storing code that members want to keep around, but is no longer used. Rather than storing this code inside a deprecated folder, we should move this code into our documentation site, for several reasons:
Confusion amongst new members ("Why is there a deprecated folder?")
Needing to exclude search results from deprecated when attempting to find resources using tools like fd or grep
Moving the code into documentation can make it easier to find for new members and those not on a computer
This task requires going through the code listed in deprecated and moving the code into our documentation. This will require sifting through the code, determining what is important, and then putting that into a cute format for our documentation! :)
How would this task be tested?
This task is simply code cleanup and documentation, so there shouldn't need to be any tests. Just ensure that nothing is broken by moving around different files and pieces of files!
Contacts
We need help from the mechanical team.
We need help from the electrical team.
We need help from Dr. Schwartz or other faculty.
We need help from a company or an organization.
We need help from another UF staff member or organization (ex, facilities).
The text was updated successfully, but these errors were encountered:
Assignee
No response
Deadline
No response
What needs to change?
Our repository contains a
deprecated
folder for storing code that members want to keep around, but is no longer used. Rather than storing this code inside adeprecated
folder, we should move this code into our documentation site, for several reasons:deprecated
when attempting to find resources using tools likefd
orgrep
This task requires going through the code listed in
deprecated
and moving the code into our documentation. This will require sifting through the code, determining what is important, and then putting that into a cute format for our documentation! :)How would this task be tested?
Contacts
The text was updated successfully, but these errors were encountered: