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
FOSS and its projects are a core part of an open development ecosystem, whether for profit or not for profit. This especially true for decetralization and web3, as many of the projects we know and love would be impossible otherwise. This idea/project attempts to make asessment and discoverability of healthy projects mucht easier and quicker, enabling developers, companies and users to quickly assess whether it makes sense to use or contribute to a software (or whether it is not sustainable/not healthy/dying)
Talk a little about yourself:
I've been on and off again at ethberlin and involved with various projects here and there, in the early days I helped with organizing eth meetups. Currently I work mostly on legal tech, foss policy, data privacy and it security. Furthermore I do research that uses computational methods/data science or AI of various kinds. The vision of ethberlin especially spoke to me about building for sustainablity, of which project health is a very important part.
Idea description
Due to my work on foss policy and data privacy, and when surveying the whole FOSS and web3/decentralized ecosystem, I cam to realize that the health of a FOSS project is incredibly important for the success of a project, and thereby the ideas and technosocial systems associated with it. There are various ideas of metrics of how to measure foss project health and quality, but so far, as far as I know, these are not widely deployed or accessible. Examples for existing metrics are CHAOSS and https://github.com/dbsystel/oss-red-flag-checker
The idea is to define a subset of these metrics, ideally one that can be automated, and the build an MVP that shows a sort of "leaderboard" of projects, allows for filtering/weighting of metrics and takes in new data with a scraper or other data input method automatically. This ideally should benefit FOSS overall and especially also the web3 community, for whom foss and source access in various forms is important. Thus it should help to select a good project to use if its health metrics and red flags can be queried and assessed quickly.
step21
changed the title
[NEW]: FOSSRank - Measuring FOSS health and making it easily accessible
[NEW]: FOSSHealth - Measuring FOSS health, and making it easily accessible for sustainable and stable ecosystems
May 2, 2024
Introduction
FOSS and its projects are a core part of an open development ecosystem, whether for profit or not for profit. This especially true for decetralization and web3, as many of the projects we know and love would be impossible otherwise. This idea/project attempts to make asessment and discoverability of healthy projects mucht easier and quicker, enabling developers, companies and users to quickly assess whether it makes sense to use or contribute to a software (or whether it is not sustainable/not healthy/dying)
Talk a little about yourself:
I've been on and off again at ethberlin and involved with various projects here and there, in the early days I helped with organizing eth meetups. Currently I work mostly on legal tech, foss policy, data privacy and it security. Furthermore I do research that uses computational methods/data science or AI of various kinds. The vision of ethberlin especially spoke to me about building for sustainablity, of which project health is a very important part.
Idea description
Due to my work on foss policy and data privacy, and when surveying the whole FOSS and web3/decentralized ecosystem, I cam to realize that the health of a FOSS project is incredibly important for the success of a project, and thereby the ideas and technosocial systems associated with it. There are various ideas of metrics of how to measure foss project health and quality, but so far, as far as I know, these are not widely deployed or accessible. Examples for existing metrics are CHAOSS and https://github.com/dbsystel/oss-red-flag-checker
The idea is to define a subset of these metrics, ideally one that can be automated, and the build an MVP that shows a sort of "leaderboard" of projects, allows for filtering/weighting of metrics and takes in new data with a scraper or other data input method automatically. This ideally should benefit FOSS overall and especially also the web3 community, for whom foss and source access in various forms is important. Thus it should help to select a good project to use if its health metrics and red flags can be queried and assessed quickly.
http://oss-watch.ac.uk/resources/ssmm
CHAOSS
https://github.com/dbsystel/oss-red-flag-checker
Skillset
What skills do you need, or think you might need to implement the idea?
Communication
Consider leaving your personal Matrix address so that the team can contact you off GitHub.
Note that this is only a template, feel free to talk about anything you want teams to know!
The text was updated successfully, but these errors were encountered: