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

Move more directories under pelican/ #56

Closed
1 of 4 tasks
jpmckinney opened this issue Nov 23, 2021 · 1 comment
Closed
1 of 4 tasks

Move more directories under pelican/ #56

jpmckinney opened this issue Nov 23, 2021 · 1 comment
Labels
Milestone

Comments

@jpmckinney
Copy link
Member

jpmckinney commented Nov 23, 2021

  • Move check-related directories to pelican/ (do this last, so it's easier to blame while doing the other Cleanup issues)
    • contracting_process
    • dataset
    • time_variance
  • Rename files as needed for consistency and clarity
    • Checks should retain the same names to avoid rewriting large parts of pelican-frontend, and currently the file paths of check files match their string names.
    • We'll keep "resource_level" and "time_variance", since the SQL tables and phase enum have the same names.
    • We'll keep "contracting_process" as it's the same as the phase enum.
    • That said, we had already renamed the workers (data_item, time_based), since they form the user-facing API. Also, the docs use "compiled release-level" and "time-based" in English. (Noted in docs homepage.)

Should finish #20 first, as I anticipate that testing processor.py, examples.py, report.py, etc. will require some archaeology.

@jpmckinney jpmckinney added this to the Cleanup milestone Jan 17, 2023
@jpmckinney jpmckinney changed the title General project cleanup File and directory naming cleanup Jan 18, 2023
@jpmckinney jpmckinney changed the title File and directory naming cleanup Move more directories under pelican/ Jan 19, 2023
@jpmckinney
Copy link
Member Author

Even now, I occasionally blame code to see if there's a reason for a methodological choice, so I'll leave it as-is.

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

No branches or pull requests

1 participant