-
-
Notifications
You must be signed in to change notification settings - Fork 600
Create funding.json for https://floss.fund/blog/announcing-floss-fund/ #2567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for having a stab at this. Here is what I finished with last time I had a go: https://github.com/graphile/graphile.github.io/blob/develop/static/funding.json We ran into problems with it being validated, although one of the tools suggested it was correct I kept running into problems actually submitting it. We have But if I have a fundamental misunderstanding somewhere, please do let me know. |
Okay I will check it and let you know.
I will try to contact some enginner at zerodha and see if he can help with
the submission.
*Best Regards,*
Abhishek Lomesh
*Frontend Developer - Technology Team**, EZ*
*Mob./ WhatsApp : +91 **9910416282*
…On Wed, 11 Jun 2025, 18:50 Jem, ***@***.***> wrote:
*jemgillam* left a comment (graphile/crystal#2567)
<#2567 (comment)>
Thank you for having a stab at this.
Here is what I finished with last time I had a go:
https://github.com/graphile/graphile.github.io/blob/develop/static/funding.json
We ran into problems with it being validated, although one of the tools
suggested it was correct I kept running into problems actually submitting
it. We have .well-known links already set up from this repo pointing to
the one hosted on graphile.org, I think this might be better being a PR
against there: https://github.com/graphile/graphile.github.io/
But if I have a fundamental misunderstanding somewhere, please do let me
know.
—
Reply to this email directly, view it on GitHub
<#2567 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAQFWY6FWRQ5URO3STXYCI33DAUIRAVCNFSM6AAAAAB7BSNHY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNRSGY4DMMJZGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
<https://www.ez.works/> <https://www.facebook.com/EZWorksGlobal/>
<https://www.linkedin.com/company/ez-works/>
<https://www.instagram.com/ez_works_/> --DISCLAIMER: The information
transmitted by this email is intended only for the person or entity to
which it is addressed. This email may contain proprietary,
business-confidential and/or privileged material. If you are not the
intended recipient of this message, be aware that any use, review,
retransmission, distribution, reproduction or any action taken in reliance
upon this message is strictly prohibited. If you received this in error,
please contact the sender and delete the material from all devices.
|
I've had some time to look at this again, we are getting a "too many lines" error, as outlined in this issue on the foos fund repo: floss-fund/portal#24 I had assumed our funding file was too long, but the open issue says:
|
Hi @Abhishekezworks we've now successfully had the Our problems were a combination of the issue I linked above, and the system not recognising what to do with a monorepo. Thank you for prompting us to look at this again with fresh eyes. We will be taking a look at your funding plan suggestions and incorporating them as appropriate over the coming month or so. |
For interest, here are the commits where we fixed the issue |
Description
Performance impact
Security impact
Checklist
yarn lint:fix
passes.yarn test
passes.RELEASE_NOTES.md
file (if one exists).