To apply to the fund, the `funding.json` has to be publicly available in GitHub source code or on a project website. At the same time, the file should contain such information as email and account details. IMHO, it's not a good idea to make it publicly available at least before approval.
the submission user flow needs a lot of rethinking. it should be super easy for OSS projects - as simple as connecting your github account and choosing the repo you wish to submit.
FLOSS/fund has released a database of projects that have applied. This makes it possible to analyze what has happened since the fund launched 36 odd days ago.
The CSV file has 80 rows - covering 130 projects, 2.4 M$ in funding requested. That number actually comes down to 1.8-1.9 million, once I weed out some outliers.
TLDR is: After an initial burst at launch, new projects applying to the fund has become a trickle - very few submissions in the past 12 days. This is puzzling and hard to explain. I am hoping that people in the community can help find projects and more importantly - get them to apply.
I'm also wondering how much of "friction" the funding.json itself creates ? I'd love to hear from anyone who has actually submitted a funding.json file to floss.fund !
reply