{"data":{"proposalCid":"QmQuwRPAVnp6xC5ZffaA5cHqNGhUHdAHaMHzjjG4qLbsoq","content":"Hey [@W1ZSPR3](1ZSPR3zNg5Po3obkhXTPR95DepNBzBZ3CyomHXGHK9Uvx6w-polkadot), thanks for following up on this.\n\n> Thanks - can you explain why the technical fellowship wouldn't fund this from their treasury? I may have missed it but in the link you posted, it just states that you thought it would be a fit for the technical fellowship treasury to fund it and they declined, but I didn't see any reason or link to a discussion of why.\n\nFrom the FAQ post:\n> [We did reach out to the Fellowship](https://collectives.subsquare.io/posts/12) for funding almost a year ago (prior to the original referendum), but were informed that our work's nature was out of scope for funding by Fellowship. And to our knowledge, the Fellowship has not funded any research papers to date.\n\nTo add detail to this: We were in email contact with technical fellowship's secretariate, and they informed us that the technical fellowship deemed our proposal out of scope for funding by them, since the scope for technical projects would be limited to what the fellowship collective needs *internally*. An example of tooling that helps fellowship's day-to-day needs is https://collectives.subsquare.io/posts/18, i.e. the work of Bryan Chen (fellowship member) on ecosystem test environments.\n\nFor external confirmation of this, you can check out the related discussion on [AAG #193](https://youtu.be/o3C2nxIZM0A?t=4644), and the clarification of the technical fellowship on the scope of their treasury on [OpenDev call July 2024](https://www.youtube.com/watch?v=oWppBMrgU7M&t=1055s) (both links directly to related sections of the calls).\n","contentType":"markdown","commenterNetwork":"polkadot","version":"2","timestamp":1754295415},"address":"15tQ5joTz2nywZ4UgPYWDMN522s91W7yTmhvV1rp4hpVhZT3","signature":"0xd866d52cf1a065c6483340aee820d2a81892399d0fb35832507720774f583702b1627cdfa74e31c9f493dbf80203223235d023da3c6b5680e6862c1c493ac682","version":"2"}