mirror of
https://github.com/go-gitea/gitea.git
synced 2026-03-09 12:46:42 -05:00
NLnet grant application for federation (deadline October 1st, 2021) #7756
Closed
opened 2025-11-02 07:35:35 -06:00 by GiteaMirror
·
15 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#7756
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @techknowlogick on GitHub (Aug 26, 2021).
Bonjour,
During the videoconference concluding the generic grant application, it was decided that @zeripath and @techknowlogick will apply to the NLnet Next Generation Search and Discovery call for proposal for a total amount of 50K€. Should the proposal be accepted the work could begin around January 1st, 2022.
This issue will contain the draft of the proposal, its final version and all communications with NLnet (only redacted for privacy) for the sake of transparency.
The action items are distributed as follows:
The proposal will be submitted by @zeripath as the primary contact.
Cheers
Posted on behalf of @dachary, source
NLnet.md
@pilou- commented on GitHub (Sep 6, 2021):
Posted on behalf of Loic.
Bonjour,
This week-end NLnet sent the following message, which motivated me to draft the workplan sooner rather than later:
Here is a tentative workplan for a total budget of 50,000€ with an hourly rate of £40 / 45€ / 70$ Canadian with 7 hours per day i.e. 315€ per day that is approximately 160 days of work or 8 month (20 work days per month). @zeripath @techknowlogick this is merely a guide to get you started: since you're going to be the one doing the work it must ultimately be something you feel you can easily accomplish in the timeframe. And the hourly rate must also be adjusted to match your needs. A few notes:
What do you think?
plan.md (6.0 KB)
@pilou- commented on GitHub (Sep 15, 2021):
Posted on behalf of Loic.
@techknowlogick @zeripath a gentle reminder: you have pending action items :-) The deadline is in 15 days and it would be wise to finish it as soon as possible to avoid any last minute troubles.
It should not take more than one hour of your time.
@pilou- commented on GitHub (Sep 16, 2021):
Posted on behalf of Loic
I have good news :slight_smile: It turns out the workplan is not binding. What it means is that this workplan is just an indication that there exists a workplan already, instead of not. Assuming the proposal is accepted, the actual workplan as well as the cost of each subtask will be negotiated roughly one month after the acceptance. It makes sense: plans and personal situations can change between the date of the submission and the date when the work begins, three months later.
Bottom line, @zeripath has no work item left 🎉 And there is just one item left for @techknowlogick : filling your bio & motivation in the grant application.
@pilou- commented on GitHub (Sep 17, 2021):
Posted on behalf of Loic
@techknowlogick I copy/pasted the bio you sent via email. The application is complete 🎉 Since you agreed with @zeripath on having the same daily rate, I assumed you would be comfortable with an hourly rate of 60€ and wrote down a daily rate of 480€ per day in the proposal. Feel free to change that if this is not correct.
I wrote a letter of recommendation that essentially says I support this grant application because it will be an important step forward to make fedeproxy redundant (being redundant is the ultimate goal of fedeproxy, the measure of success).
2021-10-gitea-nlnet-loic-dachary-recommendation.txt (1.5 KB)
Unless you have an objection, I will submit the proposal at https://nlnet.nl/thema/NGIZeroDiscovery.html on your behalf September 27th, 2021, together with the letters of recommendation. Since @zeripath is the primary contact, he will receive the confirmation and from that point on it will be in your hands, I will no longer be involved.
2021-10-gitea-nlnet-application.txt (8.5 KB)
2021-10-gitea-nlnet-workplan.txt (6.0 KB)
@rektide commented on GitHub (Sep 27, 2021):
This is a core capability that will let developers find new ways to work together & to share work. It's also a core step to making the act of coding more visible, & more tangible. I could not be more excited for this work. Good luck on this grant application.
@pilou- commented on GitHub (Sep 27, 2021):
Posted on behalf of Loic.
There was no objection, I'll post the proposal today at NLnet; NGI Zero Discovery on behalf of @zeripath. I made minor wording changes, the final version is attached below for archive.
2021-10-gitea-nlnet-application.txt|attachment (8.5 KB)
2021-10-gitea-nlnet-workplan.txt|attachment (6.0 KB)
2021-10-gitea-nlnet-loic-dachary-recommendation.txt|attachment (1.5 KB)
From that point on I will not be involved anymore. I'm very happy about the work that was done. Even if this grant application is denied, there is excellent material to answer future calls and I'm convinced funding will be granted eventually. It was made in a 100% transparent way, which is very rare and valuable to the Free Software community. I already stated that it was a precondition for my participation and I'd like to express my gratitude for everyone involved: it is an unusual requirement and it went very smoothly.
@zeripath commented on GitHub (Sep 27, 2021):
Thank you Loïc for all of your work on this!
@ShadowJonathan commented on GitHub (Dec 15, 2021):
I heard from someone that this development, even though the grant wasn't given, is still being continued, where can i find information on that?
@melvincarvalho commented on GitHub (Dec 21, 2021):
I think this would be relatively easy to get going
Have a JSON(-LD) blob in your gitea profile page, embedded in a <SCRIPT> tag
This blob contains your profile information, your nick (
@user@gitea.example), and, importantly a nested link to your SSH keys. An important design consideration in the JSON blob is to allow different objects e.g. (#me- Person,#key- public key,""- document meta data)Start to allow federated features such as single-sign-on, pull requests, where your ssh key can be used to verify your federated identity
After this proof of concept is working, expand out the federation features
I'll add that since yesterday, you can now sign commits with your SSH key, that's already a big step forward, and this style can be expanded to create global social coding
@aschrijver commented on GitHub (Dec 21, 2021):
Cross-ref to prior ActivityPub design discussion: https://github.com/go-gitea/gitea/issues/14186
@melvincarvalho commented on GitHub (Dec 21, 2021):
@aschrijver thank you for the pointer!
Let me add this tag for those discovering this thread:
https://github.com/go-gitea/gitea/labels/theme%2Ffederation
From my experience, doing the profile pages well gives the best pay-off, in terms of federation. That's because it acts as a means of orchestration for everything else. They are also really hard to future-proof, so the first version of the design is likely to stick around for a long time. The simple step of adding your public key to your profile is a major improvement (or standarizing on the
.keyspattern which can be tagged on to the username). Will continue design discussion in the relevant threads@madnificent commented on GitHub (Dec 22, 2021):
Thank you for the work on this! Is this the issue we should track for development on this, or is there another tracking issue we should follow?
@techknowlogick commented on GitHub (Jan 6, 2022):
Apologies for keeping mum on this, however we can now say we have been accepted into NLnet. https://nlnet.nl/project/Gitea/
@melvincarvalho commented on GitHub (Jan 6, 2022):
Congrats!
I can commit to running a testing server. I will try and help overall too with milestones, design and code. I have a use case in mind which is to do with signing git commits.
@aschrijver commented on GitHub (Jan 7, 2022):
FYI There's great interest. The announcement is also discussed on Hacker News