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

POC Rename ef-open (Do not merge :-)) #229

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Conversation

markeaton123
Copy link

Ticket

PTP-1955

Details

This PR is a working POC illustrating the feasibility of using standard shell tools with little developer intelligence to effect the removal of ellation and most abbreviations thereof from the repo
Include any relevant details like:

install.log
unittests.log
sample_execution_expected_failure.log

Copy link

@othiym23 othiym23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • The sed patterns used for this ended up creating a bunch of typos (I flagged the ones I spotted but I'm not confident I caught them all). If we were to do this for real, it would probably need to be done in a text editor that supports multi-file search and replace.
  • On its own this is not ready to merge even to this repo, because of the dependencies on other repos and the dependencies that other parts of our delivery and infrastructure management tools have back into the repo. I think it probably needs to be broken up into several PRs to split up the renaming of the tools (which other repos depend on) from reconfiguring to different S3 bucket and host names.
  • We need to either remove or update the copyright messages in the individual files. This is a matter for Legal to provide guidance on, but my preference would be to remove the copyright statements if at all feasible, potentially replacing them with a LICENSE for the repo as a whole.

README.md Outdated
@@ -74,5 +74,5 @@ The Jenkins CI pipeline will then recognize the new tag, build it, and publish i
_DO NOT_ delete a tag and retag the same tag on a different commit. This will not result in a replacement in PyPI, it will just make you sad.

# License
Copyright 2016-2017 Ellation, Inc.
Copyright 2016-2017 Crunchyroll, Inc.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably either update the dates to include 2016-2022, or do something like

Copyright 2016-2021 Ellation, Inc.
Copyright 2021-2022 Crunchyroll, Inc.

@@ -1,5 +1,5 @@
"""
Copyright 2016-2017 Ellation, Inc.
Copyright 2016-2017 Crunchyroll, Inc.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above re: copyright dates.

@@ -1,5 +1,5 @@
"""
Copyright 2016-2017 Ellation, Inc.
Copyright 2016-2017 Crunchyroll, Inc.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above re: copyright dates.

@@ -1,5 +1,5 @@
"""
Copyright 2016-2018 Ellation, Inc.
Copyright 2016-2018 Crunchyroll, Inc.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above re: copyright dates.

@@ -9,7 +9,7 @@
3 if some other error occurred


Copyright 2016-2017 Ellation, Inc.
Copyright 2016-2017 Crunchyroll, Inc.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above re: copyright dates.

versioneer.py Outdated
"TAG_PREFIX": cfg.tag_prefix,
"PARENTDIR_PREFIX": cfg.parentdir_prefix,
"TAG_PRCRFIX": cfg.tag_prefix,
"PARENTDIR_PRCRFIX": cfg.parentdir_prefix,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Search & replace fail.

versioneer.py Outdated
@@ -1613,8 +1613,8 @@ def run(self):
f.write(LONG %
{"DOLLAR": "$",
"STYLE": cfg.style,
"TAG_PREFIX": cfg.tag_prefix,
"PARENTDIR_PREFIX": cfg.parentdir_prefix,
"TAG_PRCRFIX": cfg.tag_prefix,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Search & replace fail.

versioneer.py Outdated
"TAG_PREFIX": cfg.tag_prefix,
"PARENTDIR_PREFIX": cfg.parentdir_prefix,
"TAG_PRCRFIX": cfg.tag_prefix,
"PARENTDIR_PRCRFIX": cfg.parentdir_prefix,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Search & replace fail.

versioneer.py Outdated
@@ -1714,8 +1714,8 @@ def do_setup():
LONG = LONG_VERSION_PY[cfg.VCS]
f.write(LONG % {"DOLLAR": "$",
"STYLE": cfg.style,
"TAG_PREFIX": cfg.tag_prefix,
"PARENTDIR_PREFIX": cfg.parentdir_prefix,
"TAG_PRCRFIX": cfg.tag_prefix,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Search & replace fail.

versioneer.py Outdated
"TAG_PREFIX": cfg.tag_prefix,
"PARENTDIR_PREFIX": cfg.parentdir_prefix,
"TAG_PRCRFIX": cfg.tag_prefix,
"PARENTDIR_PRCRFIX": cfg.parentdir_prefix,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Search & replace fail.

@markeaton123
Copy link
Author

  • For sure, my use of sed was heavy-handed. OTOH, I was just as heavy handed in aggressively correcting the changes. FWIW, all of the typos were non-functional in nature, but annoying to be sure. It's actually really hard to make sure you're not overzealous in doing global replaces even with an editor that does support multi-file access, but I get your point. And, yes, I do know how to use PyCharm to do this :-)
  • The repo dependency is unfortunate. Devops will need to provide a rubric for the sequencing and that's beyond what I wanted to comment.
  • I've updated all of the copyrights. This is a larger issue than just the rename activity, I must say.

Anyway, there's lots of outdated conversations now - we can leave them as is or revisit this at another time.

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

Successfully merging this pull request may close these issues.

None yet

2 participants