Author:
Hash:
Timestamp:
+43 -0 +/-1 browse
Kevin Schoon [me@kevinschoon.com]
3b032d24bc61dd0f54d6729d32fb9acb33ba0b91
Tue, 21 Jul 2026 12:28:28 +0000 (2 weeks ago)
| 1 | diff --git a/funding/nlnet-commons-1.md b/funding/nlnet-commons-1.md |
| 2 | new file mode 100644 |
| 3 | index 0000000..959ebba |
| 4 | --- /dev/null |
| 5 | +++ b/funding/nlnet-commons-1.md |
| 6 | @@ -0,0 +1,43 @@ |
| 7 | + # NLNet Commons Fund Application |
| 8 | + |
| 9 | + We applied for an NLNet Commons Fund grant on Jan 30 2026 which was accepted |
| 10 | + to the second round on May 7 and finally rejected on July 13. |
| 11 | + |
| 12 | + ```text |
| 13 | + Code : 2026-02-511 |
| 14 | + Requestor : REDACTED |
| 15 | + Email : REDACTED |
| 16 | + Phone : REDACTED |
| 17 | + Organization: Independent Software Developer |
| 18 | + Country : Italy |
| 19 | + Consent : You may keep my data on record |
| 20 | + Call : Commons_Fund |
| 21 | + Project : ForgeFeed Specification |
| 22 | + Website : https://forge-feed.org |
| 23 | + Abstract : ForgeFeed is a collection of specifications and recommendations which when implemented can enhance interoperability and content discovery of different code forges across the internet. The goal of ForgeFeed is to define a simple lightweight and standardized way to query structured information about a codebase over HTTP in a way that is agnostic to the hosting code forge. The specification is currently hosted at https://forge-feed.org. |
| 24 | + Experience : Yes. I have been working on a code forge called Ayllu over the last few years off and on. See https://ayllu-forge.org. I'm the principal author of that project and am the sole author of the Forge Feed specification as it exists today. See https://forge-feed.org. |
| 25 | + Amount : € 15000 |
| 26 | + Use : The grant money would be used to sustain the development of the following: |
| 27 | + |
| 28 | + * A formal RFC style specification of ForgeFeed and an IETF submission. |
| 29 | + Including: |
| 30 | + * WebFinger Project Identification - Identify Software Projects via WebFinger |
| 31 | + * WebFinger Repository Identification - Identify VCS Repository Content via WebFinger |
| 32 | + * Atom Feed Project Discovery - Subscribe to a forge over Atom |
| 33 | + * ForgeFeed Site Identifier - HTML Meta Tag Indicating ForgeFeed Capabilities |
| 34 | + |
| 35 | + * A Go based reference implementation of the ForgeFeed specification. |
| 36 | + * A Rust based reference implementation of the ForgeFeed specification. |
| 37 | + * Continued development of forge-feed.org and it's Javascript based validation tool. |
| 38 | + * Continued engagement and advocacy of the specification across code forges. |
| 39 | + Comparison : The main project to compare the ForgeFeed specification with is the NG0 grant recipient ForgeFed. I've copied an excerpt of a PR I have open to integrate ForgeFeed into Forgejo: https://codeberg.org/forgejo/forgejo/issues/10150 comparing the two protocols: |
| 40 | + |
| 41 | + The ForgeFed federation protocol which is actively being implemented for Forgejo (AIU) is an exciting prospect which will bring Mastodon style federation to Forgejo instances. Once implemented you will be able to discover content, make PRs, comments, etc all from the Forgejo (or other participating forge) instance of your choosing. This prospect is super exciting but requires a high bar in terms of the effort required to participate in an activity pub based network and excludes those who don't want to accrue the operational (or maybe psychological?) burden of running and participating such a network. The ForgeFeed specifications don't detract in anyway from the ForgeFed protocol but just add another mechanism by which forges can participate and even continues to use the common protocol of WebFinger. |
| 42 | + Challenges : The specification is relatively simple and the reference implementations will be straight forward to write however the main challenge will be designing a protocol that is flexible enough to support existing forges and seeking it's adoption. |
| 43 | + Ecosystem : The ecosystems relevant to the project are basically any software communities who host their own code and want it to be accessible in an agnostic way. |
| 44 | + |
| 45 | + I have started discussions with the two largest Europe based alternative code forges today and have received some positive feedback. **Please note that no entity or individual has explicitly endorsed this specification yet, it is solely my own work at this point in time.** |
| 46 | + |
| 47 | + https://codeberg.org/forgejo/forgejo/issues/10150 |
| 48 | + https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3Ct7p45vn5tt5xm6wde3mwqe5jbannx3bn7retg7mfj4wts7fovy@p4aktei645uf%3E |
| 49 | + ``` |