Double-check and modify references to parser and core

[Mec-iS]

Now that the parser and core have been moved to their own repository, documentation has to point to the new repos:

• https://github.com/HTTP-APIs/hydra-openapi-parser/issues
• https://github.com/HTTP-APIs/hydra-python-core/issues

@Mec-iS hello! are you referring to this link as the documentation? If not, please point me to the correct documentation and I'll do the needful changes.

[de-sh]

@Mec-iS hello! are you referring to this link as the documentation? If not, please point me to the correct documentation and I'll do the needful changes.

Hey @sukhdeepg we use hydraecosystem.org, for documenting our implementation of the Hydra draft to which your link points to.

@de-sh Thanks for the feedback. My only confusion is to on which page should I put these links. The place where I though it should go was this:

I couldn't find a valid place on hydraecosystem.org, as I was not able to find any previous github repos linked on this page as I checked the page source. Help will be really appreciated.

[de-sh]

@sukhdeepg we don't intend to modify the Hydra-CG docs. Here @Mec-iS is pointing towards making changes in this repo, we used to have these two modules within hydrus that were moved out into their own repos recently. We want to mirror this fact in our docs by changing reference to the old modules showing clearly that they are in their own repos now.

@de-sh thanks for the prompt response. Now as considering the hydraecosystem.org as your doc. I went and searched the doc and found these:


I wasn't able to find any mention of hydra-python-core. If I'm still missing something, please do correct me. Thanks for the patience.

[de-sh]

It's not only about linking to the correct repo. We intend to write better documentation for the project. Currently the documents here concern mostly the previous iteration of hydrus, we have changed a lot since then. Writing documentation in order to reflect those very changes is high priority. If you can help, do try rewriting some of the pages after understanding the codebase or the applications of the project.

As you mention, the parser page is a good option to start with, we need to make sure different components of the suite are not documented, at all. We need better, more well rounded explanations of the same.

@de-sh understood. Thanks. I'll start with that then.

[gustavodemorais]

The references were checked and the existing ones modified in #52 and #53.

What we might need is actually an own page for python core, will open an issue for this.