Add codeowners so PR's are automatically tagged with reviewers

[thomasyu888]

Problem
Code reviewers have to be assigned manually per PR.

Solution
Add codeowners so PR's are automatically tagged with reviewers

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[thomasyu888]

If you could provide this team write access to this repo, that would be fantastic!

OR... if there is a schematic-developer team, lets add ourselves to that

[linglp]

there's no schematic-developer team. I added @Sage-Bionetworks/python-client-developers manually here:

[linglp]

just changed the role to "maintain"

[linglp]

@thomasyu888 ugh I finally understand why the tests are failing! I think it is because you forked the repository. Next time, please feel free to create a branch. If you fork the repository, you will have to add SYNAPSE_ACCESS_TOKEN and SERVICE_ACCOUNT_CREDS environment variables yourself. SYNAPSE_ACCESS_TOKEN is your synapse access token, but SERVICE_ACCOUNT_CREDS is a bit hard to obtain. We used to have a synapse template that let people download the same service account credentials but that approach was not secure and we deprecated that. The new way of getting SERVICE_ACCOUNT_CREDS can be found here: https://scribehow.com/shared/Enable_Google_Drive_and_Google_Sheets_APIs_for_project__yqfcJz_rQVeyTcg0KQCINA
But the easiest way is of course just to create a new branch using our repo.

[thomasyu888]

@thomasyu888 ugh I finally understand why the tests are failing! I think it is because you forked the repository. Next time, please feel free to create a branch. If you fork the repository, you will have to add SYNAPSE_ACCESS_TOKEN and SERVICE_ACCOUNT_CREDS environment variables yourself. SYNAPSE_ACCESS_TOKEN is your synapse access token, but SERVICE_ACCOUNT_CREDS is a bit hard to obtain. We used to have a synapse template that let people download the same service account credentials but that approach was not secure and we deprecated that. The new way of getting SERVICE_ACCOUNT_CREDS can be found here: https://scribehow.com/shared/Enable_Google_Drive_and_Google_Sheets_APIs_for_project__yqfcJz_rQVeyTcg0KQCINA
But the easiest way is of course just to create a new branch using our repo.

Thanks @linglp ! See this: https://sagebionetworks.slack.com/archives/C07HLTBS5D2/p1724456854221899?thread_ts=1724454270.877609&cid=C07HLTBS5D2

[linglp]

LGTM

[thomasyu888]

Closing due to FAIR having their own process for code reviews.