3 ms·
This is cool: good, reasonable methodology (I like the value x risk idea). Two requests: 1) could you easily add the projects to the CSV file (maybe one column
by bajabaq 2y ago
This is cool: good, reasonable methodology (I like the value x risk idea).
Two requests:
1) could you easily add the projects to the CSV file (maybe one column left of the user: "projectA;projectB;...")
2) could you share the code (understanding that it's rough and lots of hand-curation)
I've long given to EFF, FSF, and other projects sporadically, but this method seems excellent and expandable and customizable, maybe something like:
1) identify the packages on your machine (or used by your team)
2) score them
3 donate based on score
- dmacedo 2y agoI believe this is a better approach for scale. Make it a local or company-wide identification of FOSS packages, and a way for those individuals, teams, and businesses to score them by importance or criticality (or needs of the FOSS project if they are aware).
- kvinogradov 2y agoThanks! 1) Yes. My plan is to continue iterating on this approach and publish more data later, including projects and some other inputs (PyPI, etc.) 2) Maybe. I prefer the full transparency and have planned to publish the code too, but some comments suggest that it might not be ideal. Need to think more about this.