Clone / copy repo to https://github.com/spacetelescope/poppy

[mperrin]

• Copy the code
• Copy the open issues and PRs
• Update URL links in docs, etc.
• Update URL links in PyPI and Conda when doing next release
• inform team members to update their remotes.

[pllim]

Is this done? I just realized I am in this version of GitHub repo and it is not a fork of the spacetelescope one. I am confused. Which one is the canon repo?

[mperrin]

The spacetelescope one is the canonical one. This is not a fork since it's older than the spacetelescope one by many years. Would have needed a time machine to fork it!

I left this one in place to avoid breaking existing links and forks, but all development is on the spacetelescope repo now. Which is why this issue never got closed; we instead closed the copy at spacetelescope/poppy#260

Yes this is somewhat confusing.... but webbpsf and poppy are relatively old in Python package terms. Older than astropy, even.

[pllim]

Is it possible to at least archive this one?

[joseph-long]

Please do not revive three year old issues just for fun, as it triggers emails to all the collaborators. As Marshall said, this repository is pointed to by forks and it's not worth breaking those links. You can find recent development at https://github.com/spacetelescope/poppy

[pllim]

It is not very fun for me either. I got here because one of your colleagues pointed me to a file in this repo.

[douglase]

It is possible to request github re-route the fork: https://support.github.com/contact?tags=rr-forks