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

Zenodo versus Github versus Ecosystem #33

Open
AndreaMargit opened this issue Sep 30, 2022 · 3 comments
Open

Zenodo versus Github versus Ecosystem #33

AndreaMargit opened this issue Sep 30, 2022 · 3 comments
Assignees

Comments

@AndreaMargit
Copy link
Member

We have really embraced the Zenodo-Github link, and a lot of resources are now floating in Zenodo - of Polifonia members - some of those Zenodo contributions are part of the Polifonia community - other live their own Zenodo live. It would be great to have an overview, and actually all should show up - nicely annotated - in the Ecosystem, searchable via the website. To give an example: the Polifonia Corpus (see first hits here https://zenodo.org/communities/polifonia/search?page=1&size=20&q=data), where is this under the Ecosystem. People, I'm lost ;-) Open for proposals

@raphaelfournier
Copy link
Member

Currently, adding components to the Ecosystem website is manual. The Polifonia Corpus has not yet been added (I don't know why, perhaps Enrico knows).

The Polifonia Corpus repository seems correctly annotated and would be well searchable. However, I am not sure about what you mean by "an overview", besides what we currenly have (ie, the Ecosystem website, the Portal, and Zenodo): what kind of different "view" would you like to see?

@AndreaMargit
Copy link
Member Author

Could we see what is in the GitHub, and what of those GitHub repositories are annotated as Ecosystem components? Does this question makes sense to you?

@raphaelfournier
Copy link
Member

Hmm, not exactly sure. I understand that you would like to have, on the Ecosystem website, "what is in the Github". That's exactly the purpose of the Ecosystem website, but it's not automatic. "Why?", you may ask. One answer is: to allow some flexibility in the Polifonia community, to allow developers to create "dumb/WIP" repositories, without seeing them in the Ecosystem (which would become a "polluted website").
But, otherwise, we aim at having "properly annotated/validated" repos show up on the ecosystem website, to offer "an overview of what is on Github".

That being said, there may be some "views" (ie, some ways to present information) that could be useful for the Ecosystem website. Currently, we promote the "sidebar" navigation, with WP/Pilot classification, it may be improved, if you have suggestions.

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

3 participants