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

prune content in /standard subdir #6

Open
naughtont3 opened this issue Jun 11, 2020 · 5 comments
Open

prune content in /standard subdir #6

naughtont3 opened this issue Jun 11, 2020 · 5 comments
Assignees

Comments

@naughtont3
Copy link
Collaborator

We obviously do not want big chunks of this, but not sure if we want any of it in the openpmix repo. Since I forked this from pmix gh-pages, we already have it, but may just want to wholesale remove from this repo.

Decide if part of this content should live in openpmix, or all lives in pmix (standard) site.

Note - Some of the content under that directory includes RFCs, roles and responsibilities, roadmap, etc. So not just standard content AFAIK.

@naughtont3
Copy link
Collaborator Author

PMIx (standard) gh-page

OpenPMIx gh-page (not directly linked from webpages)

It may make sense to have OpenPMIx remove this subdir and just refer to the /pmix-standard, which will show the status of the pmix-standard repo (problem I was fixing that raised this conflict to begin with). ;-)

@naughtont3 naughtont3 self-assigned this Jun 11, 2020
@rhc54
Copy link
Contributor

rhc54 commented Jun 11, 2020

Something we should look at - GitHub automatically redirects from the pmix project to the openpmix project because we simply moved the repos. I suspect this is the root cause of the problem you hit. It might be time to break that redirect?

@naughtont3
Copy link
Collaborator Author

Hmm, maybe. But in the case of that redirect it was from pmix/pmix.github.io to pmix/pmix-standard (both in pmix). Regardless, it may be good to remove that redirect b/c things are relatively well delineated now.

@rhc54
Copy link
Contributor

rhc54 commented Jun 12, 2020

My bad - it redirects at the repo level, so there is no confusion so long as we don't create a pmix repo in the github.com/pmix project. Yeah, we should remove the directory from openpmix and just reference the official standard location.

@rhc54
Copy link
Contributor

rhc54 commented Jun 12, 2020

Anything that isn't part of the standard should be moved somewhere else on the site.

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

2 participants