Adopt a standard layout for the repository that includes standard CI and api best practices

[matentzn]

https://github.com/tiangolo/full-stack-fastapi-postgresql

[matentzn]

Adopt the project layout from pheval:

https://github.com/monarch-initiative/pheval

Sooner rather than layer, in particular, adopt these files:

• Standard workflows: https://github.com/monarch-initiative/pheval/tree/main/.github/workflows
• And

[anitacaron]

Is the proposed layout related to the cookie cutter? Can you change the title, please?

[matentzn]

They are related - I changed the title; the point is to make a sane, standard repo structure with sane code style checking and integration testing, and a reasonably standard modular structure according to fastapi best practice

[anitacaron]

I was thinking of creating a cookie cutter for reuse, but that is different.

[matentzn]

You can, if you like! But this is less of a priority here then adding standardising this specific repo. My suggestion would be to first create a perfect layout here, and then, once we are happy with all of its aspects, transform it into a cookie cutter for monarch fastapi development?

[anitacaron]

Yes, entirely not the scope of this issue now and not previously.

[anitacaron]

Looking into the LICENSE in the pheval repo, it's missing to replace this part:

Copyright [yyyy] [name of copyright owner]

What does it need to be in the SSSOM API repo?

[matentzn]

Can you ask this question in the #codestyle channel in monarch org on slack?