snowdrift/tasks
12
1

ForgeFed Integration and funding features #970

Open
opened 2025年06月03日 11:55:30 +02:00 by fr33domlover · 1 comment

Hi team :) I'm still working on ForgeFed, these days mostly working on the specification itself, leaving the coding to the Forgejo Federation team. I'd really like to support project funding via the federated network (going to look into floss.fund, liberapay, github sponsors etc. and figure out the data model). Hoping to add this to the specification within my current NLnet grant (which ends in October). Obviously it has extra complications compared to a centralized forge (asking for funding on a fake copy of some popular project... small instances being unable to handle credit card stuff... etc. etc.)

Maybe this is also an opportunity to somehow integrate Snowdrift / crowdmatching into the mix?

If that sounds interesting, let's talk :)

https://linksta.cc/@pere has my email and matrix links

Hi team :) I'm still working on ForgeFed, these days mostly working on the specification itself, leaving the coding to the Forgejo Federation team. I'd really like to support project funding via the federated network (going to look into floss.fund, liberapay, github sponsors etc. and figure out the data model). Hoping to add this to the specification within my current NLnet grant (which ends in October). Obviously it has extra complications compared to a centralized forge (asking for funding on a fake copy of some popular project... small instances being unable to handle credit card stuff... etc. etc.) Maybe this is also an opportunity to somehow integrate Snowdrift / crowdmatching into the mix? If that sounds interesting, let's talk :) https://linksta.cc/@pere has my email and matrix links

My main initial thought is that we have accepted that our goal at this point is to get an adequate proof-of-real-world-potential for crowdmatching to the degree that others accept the premise and do any mix of collaborating with us to accelerate our work directly or building the idea into more tools and places. The vision is of a world where coordinated power of regular citizens via crowdmatching and similar brings back balance to our world so distorted by concentrated wealth. And in that sense, it seems others need to see crowdmatching in action beyond a conceptual model in order to embrace it.

So, my sense is that the federated approach is something people will help realize after seeing a centralized proof of viability.

What do you think?

We're still on Matrix of course, and happy to chat there, though we could adapt this issue into a visioning of what it would take to make sure that ForgeFed specification has what it needs so that crowdmatching is feasible within the spec...

My main initial thought is that we have accepted that our goal at this point is to get an adequate proof-of-real-world-potential for crowdmatching to the degree that others accept the premise and do any mix of collaborating with us to accelerate our work directly or building the idea into more tools and places. The vision is of a world where coordinated power of regular citizens via crowdmatching and similar brings back balance to our world so distorted by concentrated wealth. And in that sense, it seems others need to see crowdmatching in action beyond a conceptual model in order to embrace it. So, my sense is that the federated approach is something people will help realize after seeing a centralized proof of viability. What do you think? We're still on Matrix of course, and happy to chat there, though we could adapt this issue into a visioning of what it would take to make sure that ForgeFed specification has what it needs so that crowdmatching is feasible within the spec...
Sign in to join this conversation.
No Branch/Tag specified
master
master-pre-reset
v0.1.4
v0.1.3
v0.1.2
v0.1.1
release-0.1.0.1
Labels
Clear labels
Blocked
Confidential
We track some issues in a private repo, typically when they contain personal information. In the interest of transparency (and ease of tracking for us), we also keep a stub here in the public issues.
design
Visual design and assets
dev
dev/frontend

Archived

docs
Documentation
finances
Management of financial accounts; Grants and other funding sources
good first issue
Issues that do not require in-depth understanding of background or code
governance
Organisational structure and bylaws
legal
Legal terms, policies and documents
needs-info

Archived

ops
Operations
outreach
Community messaging and recruitment
product/blog
For the blog / Ghost
product/crm
For the CRM / CiviCRM
product/elm-site
Relates to https://codeberg.org/snowdrift/elm-website
product/forum
For the forum / Discourse
product/wiki
product/yesod-site
Relates to https://codeberg.org/snowdrift/snowdrift
research
Research, reference materials and studies
security
Issues about authorisation and authentication
type
bug
Broken feature or regression
type
chore
Housekeeping
type
feature
New feature or functionality
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
snowdrift/tasks#970
Reference in a new issue
snowdrift/tasks
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?