May I suggest you also post to SocialHub to keep the AP community informed?
@pilou would you be so kind as to post this reply?
@techknowlogick thanks for your reply and guidance It’s good to know the timing is right and I’m hopeful someone will be interested.
you were to use these funds I would recommend giving them directly to the developer working on this PR, and the maintainers reviewing it, rather than to the project itself
I’ll follow your advice. Since fedeproxy is horizontal (no organization) the funds originate from individuals (Pierre-Louis and myself, 50% each) and it will be possible to pay the person(s) doing the work directly.
as this is likely a large PR…
Maybe it can be broken down in smaller tasks / PRs? It would be easier to review and implement. And it will also be easier to prioritize which task should be worked on first and which ones can fit is the modest budget there is.
@aschrijver that was my intention, as soon as cj and zeripath comment or a week pass, which ever comes first. I take this opportunity to ask your advice on how to word the toot / message to announce it. You have a talent to make it so people pay attention
People on Lemmy ask where they can donate. I think I will provide 3 places: FedeProxy, Gitea and GoFed.
- FedeProxy ??? can people donate?
- Gitea OpenCollective - does not go directly to this initiative
- GoFed ActivityPub Labs OpenCollective - does not go directly to this initiative
The ForgeFed website is still down, for over a week now, so I just posted to Feneas about it. Maybe they want to step in too with this new development going on.
Update: Instead I pointed here.
FedeProxy is a horizontal community of individuals, therefore not incorporated: it is not possible to donate to the organization because it does not exist. As a consequence each member of the community is responsible for raising their own money and for receiving funds that they pledge to dedicate to the advancement of the fedeproxy project.
As you can see in the liberapay page, the funds currently go directly to individuals (Pierre-Louis and myself). The income and expsense spreadsheet will show, weekly, if the money that we received via liberapay is actually accounted for. That’s the quantitative benefit of full transparency. The more difficult question is to evaluate if the way we spent the money makes sense at all. A good example is the current discussion on what to do with the diversity grant.
Regarding the Gitea federation features here is how it will go:
- Someone adds to the https://liberapay.com/fedeproxy/ account and earmarks it for the implementation of federation in Gitea
- I will add this to the income part of spreadsheet
- When someone claims credit for getting a pull request merged in Gitea that helps with federation, a new topic will be opened on the forum for the community to come to a consensus (because that’s how the decision process starts).
- When the decision is final Pierre-Louis or myself will send them the required amount
- I will add that to the expense part of the spreadsheet
- Someone can verify in the spreadsheet later on, with a URL to the decision to release the funds, that their donation was used as intended.
Weave the threads, Luke! That thread you mentioned on the Gitea forum also really needs a real update, knitting all of the ongoing conversations together.
I just added a comment to the Gitea GH issue with all the places there’s talk about funding mentioned in it.
PS. Your other posts on Gitea forum are still flagged. I’d DM an admin of the forum.
Posted by southerntofu following our exchanges on libera#peers:
While working on the grant application today, I ran into a question that is worth posting on the issue. Would you be so kind as to copy/paste it on my behalf?
While working on the grant application today, I ran into a question that is probably worth discussing before moving forward. Go-fed is AGPLv3+, and Gitea is MIT. Adding Go-fed as a dependency of Gitea means that Gitea, as a whole (meaning Gitea+Go-fed+other dependencies), can only be released under the AGPLv3+. Or not released at all.
To be more precise, here is the minimal set of actions required to distribute a gitea executable that contains Go-fed:
- The https://github.com/go-gitea/gitea repository needs no change
- A license notice stating the executable is under the AGPLv3+ license must be prominently added to the user interface (e.g. added at the beginning of js/licenses.txt)
This is not the only possible course of action, only the simplest.
What do people think about this?
2 posts were split to a new topic: Grant application for federation in Gitea
This is no problem. Only
apcore is AGPL, but this project is an opinionated server framework, meant to make life easier in implementing a full-blown server. The go-fed libraries are - probably very deliberately not under AGPL, but BSD-3 license. Gitea would not need
apcore and already has a bunch of server aspects implemented their own way. They’d need to reimplement some things again, but not involving too much work (e.g. webfinger).
@pilou would you be so kind as to post the following on my behalf?
Oh… my bad, thanks for the clarification!
Since it seems likely that nobody will be interested in the 5K€ grant, it would be a good thing to set an expiration date. Would November 1st 2021 be sensible?
@zeripath in the 1.16 plan you write “(It’s worth noting that although this may appear orthogonal to things like federation - this is key to making federation possible.)”. You mentioned this a few times and I concur: authentication / authorization is a building block of federated activities. Maybe I’m stating the obvious but here it is: if issues were created around that topic that clearly articulate how they are relevant to federation, it would be possible to fund their implementation with the money earmarked for federation. My 2cts
3 posts were merged into an existing topic: Grant application for federation in Gitea