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

Links on the public mps site at ravenbrook.com are unclear or not up to date #200

Open
thejayps opened this issue Mar 14, 2023 · 1 comment
Assignees
Labels
essential Will cause failure to meet customer requirements. Assign resources. git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo

Comments

@thejayps
Copy link
Contributor

"Read the Documentation" does not point to the current documentation hosted at readthedocs
"Fork it on Github" presupposes that a visitor intends to fork the MPS. They might want to just look at the project.

@rptb1 rptb1 added the git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo label Mar 14, 2023
@rptb1 rptb1 added this to the Perforce Divorce milestone Mar 14, 2023
@rptb1 rptb1 self-assigned this Mar 14, 2023
@rptb1 rptb1 removed this from the Perforce Divorce milestone Mar 15, 2023
@thejayps thejayps added the essential Will cause failure to meet customer requirements. Assign resources. label Mar 27, 2023
@rptb1
Copy link
Member

rptb1 commented Oct 20, 2023

Partially resolved by Perforce changelist 199686 (see #166 (comment) ).

We could introduce further rewrite rules to resolve this further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
essential Will cause failure to meet customer requirements. Assign resources. git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo
Projects
Development

No branches or pull requests

2 participants