Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
First up, you need to use more than just the master branch, which is appears is what you're doing. Developers use repositories in different ways (unfortunately) and this makes it hard to benchmark. You said there was 0% retention of developers and no activity, and as an example of how that number is inaccurate I'd point you to heifner's profile on github. You can see within the last few days he's both created code, issues, and been managing pull requests. Scroll back to 2019 and you'll find him contributing to the core codebase. If you continue to look through the top contributors on the eosio/eos repo you'll continue to find more of the top developers are actually active and developing on the project.
Secondly, for a project you need to also include more than a single github fork. I know you said you focused on block production - but that doesn't tell the whole story. Many projects are split up into multiple forks even for just "block production". Again using EOSIO as an example, I'd point you to the mandel release, which you can see is actively being updated and has a release candidate in the last week. If you reference the core developers of the EOSIO/EOS repository against this new repository, you'll find developers who have been working on the same project for years just operating in a different repository. Notably you'll find tbfleming and swatanabe. The retention rate of these developers has been constant and the knowledge they have after years of working on the project is still within the ecosystem and contributing.
I used https://streamlit.io/. Glad you enjoyed it!