quantified.uncertainty/metaforecast
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

tweak: Point to conventional commits

Browse Source
This commit is contained in:
NunoSempere 2022-03-15 15:47:00 -04:00
parent 1cba1ec35a
commit b8e6435fee
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -65,5 +65,6 @@ With regards the quality, I am most uncertain about Smarkets, Hypermind, Ladbrok
## Various notes
- Commits follow [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#summary)
- Right now, I'm fetching only a couple of common properties, such as the title, url, platform, whether a question is binary (yes/no), its percentage, and the number of forecasts.
- For elicit and metaculus, this library currently filters questions with <10 predictions.

2
roadmap.md
View File

@ -37,7 +37,7 @@ If I was doing this on my own, I would deploy 1. into a Njal.la server using Alp
- A Digital Ocean droplet using Ubuntu/Debian
- A Heroku instance.
The biggest difference between Digital Ocean and Heroku is that I'm using [pm2](https://pm2.keymetrics.io/) on Digital Ocean, whereas Heroku has its own load balancer, logs, etc.
The biggest difference between Digital Ocean and Heroku is that I'm using [pm2](https://pm2.keymetrics.io/) on Digital Ocean, whereas Heroku has its own load balancer, logs, etc.
## General code review
Importance: 3/5, but good first issue. Would also allow you to incorporate