You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some very modular projects are managed in an entire namespace created just for that project. It might be helpful to allow the listing of whole namespaces. Unfortunately, this might break many of the conventions we have so far.
How do we deal with projects in a namespace that are not open source?
Some projects in a namespace might just be bad.
Some project might be very old.
So far we have tried to add the core repository, but in many cases this does not work when projects are very modular. Here is a well known example: https://github.com/IPCC-WG1
I do not know of a solution for this yet.
The text was updated successfully, but these errors were encountered:
Maybe we can treat all the repos in a namespace as a single repository, counting commits, issues, contributors etc across all of them into a single entity?
We could try, but how much complexity would it add to ecosystem.ms? Is it worth it? It might also skew the statistics. We would need to change the Contribution Guide to only allow such entries when it is clear that a project/application is being developed across a whole namespace, and that the individual parts cannot be reused in isolation.
Some very modular projects are managed in an entire namespace created just for that project. It might be helpful to allow the listing of whole namespaces. Unfortunately, this might break many of the conventions we have so far.
So far we have tried to add the core repository, but in many cases this does not work when projects are very modular. Here is a well known example: https://github.com/IPCC-WG1
I do not know of a solution for this yet.
The text was updated successfully, but these errors were encountered: