phuse-org / E2E-OS-Guidance

Collaboration area for PHUSE End-to-End Open-Source Guidance
https://phuse-org.github.io/E2E-OS-Guidance/
MIT License
7 stars 3 forks source link

Additional feedback from Pfizer #20

Closed nandriychuk closed 1 year ago

nandriychuk commented 1 year ago

A project could also have no activity as it has been abondened after or before it reached"v1.0.

A summary and recommendation of licence types, with particular focus on permissive vs copyleft licences and the ramifications on code built on top of your project Relevance of licences present in dependencies, direct vs transitive dependencies, and the issues around compiling with dependencies that could occur in something like a public shiny app

In /using.html#what-is-the-open-source-health-of-the-package:

There are no universal magic metrics to summarise whether an OS project is ‘healthy’; for example if a project has had no activity for 12 months, is that because the product has been abandoned/superseded, or could it be it had a small well-defined scope and is now stable and feature complete?

In /using.html#how-active-are-the-community-behind-a-project:

By looking through the issues, subjective impressions on community health can be made, for instance whether it’s a few people giving feedback and one person developing, does it have stale issues no-one replies to, or does it have a lively community engaged in discussion and coordination.

AEBilgrau commented 1 year ago

First two bullets are fixed in PR #18 and PR #21.