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

Refactoring PAML naming to LabOP #162

Closed
photocyte opened this issue Sep 30, 2022 · 5 comments
Closed

Refactoring PAML naming to LabOP #162

photocyte opened this issue Sep 30, 2022 · 5 comments

Comments

@photocyte
Copy link
Member

photocyte commented Sep 30, 2022

Per #107 & Dan's recent email to the mailing list (https://groups.google.com/g/bioprotocols/c/ijV7jHK5t2w) PAML is being renamed to LabOP.

Clearly there are a lot of places to make this replacement rename, and it might take awhile to be fully accomplished. Here is a short list that can start taking a crack at...

(1) This repo name itself & included documentation pamled
(2) The Github landing page (https://github.com/Bioprotocols) (excluding the logo as of 2022-10-18)
(3) The Bioprotocols.org landing page (https://bioprotocols.github.io/paml/ <- note paml in URL)
(4) Places in code in various repos... "labop" repo
(5) Documentation on Open Collective (https://opencollective.com/bioprotocols)

@rpgoldman
Copy link
Collaborator

Suggest we unpack these into individual issues. The rationale is that if we bundle multiple to-do items into one issue, then it is very hard for us to tell if/when they are done and what remains to do.

Need to carefully maintain all the old pointers, as well.

Not sure what to do with the OWL stuff -- we're all just at the mercy of what the various tools can do with redirection/sameAs.

@danbryce
Copy link
Collaborator

I pushed e807e5f, which renames PAML to LabOP. This take of 1 and 4 (for this repo).

@photocyte
Copy link
Member Author

photocyte commented Oct 18, 2022

Hi @rpgoldman , I'm totally in support of separate issues - I'm personally planning on sticking to renaming in the documentation & letting others rename in code so I don't break things. But, if making separate issues, might be nice to have them make a bidirectional link to this issue just so they're easy to find.

Regarding (2), I've updated the text documentation, but I don't know how to change the overall logo at the top left of the page. Maybe @danbryce has that authorization?

I'll edit & strike out the finished items on my first post in this issue.

@danbryce
Copy link
Collaborator

danbryce commented Oct 19, 2022 via email

@photocyte
Copy link
Member Author

I believe this is probably completed? Closing if so. Can reopen if not.

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

3 participants