forgejo/forgejo
forgejo/forgejo
67
1.8k
Fork 280
Code Issues 773 Pull requests 40 Releases 60 Packages 1 Activity Actions 4

[FEAT] implement federation #59

New issue
Closed
opened 2022-11-27 22:36:38 +00:00 by xy · 27 comments
xy commented 2022-11-27 22:36:38 +00:00
Copy link

Update June 2024: this issue is no longer updated. Progress on federation can be followed from:

This issue tracks the progress of implementing federation in Forgejo.

Ongoing tasks (updated monthly)

Tasks backlog

Discovery

This is done.

Actors

This is almost done.

  • Create public/private keypair go-gitea@github.com/gitea#17071
  • HTTP signature middleware go-gitea@github.com/gitea#19133
  • Mapping Gitea's concepts ("People", "Teams") into AP "Actor" concepts
  • Mapping Gitea's actor concepts into the ontology
  • Assign Actor IRIs go-gitea@github.com/gitea#19133
  • Manage inbox and outbox
  • Send out activities to followers
  • Render followed user updates in your user feed
  • Periodically fetch and update cached remote users' data
  • Clean out avatar cache

ForgeFed

go-ap

Adding ForgeFed types to go-ap Mastodon discussion, mailing list discussion

  • Implement Commit type
  • Implement Repository type
  • Implement Branch type
  • Implement Push type
  • Implement Ticket type
  • Tests
  • Export more JSON functions from go-ap/activitypub (solved by using a fork https://gitea.com/Ta180m/activitypub)

Serving ActivityStreams

  • Addressing
  • Transport (HTTPS with HTTP signatures) go-gitea@github.com/gitea#19133
  • Retry sending activities to servers that are down or have an outgoing activity queue
  • Serve AS representation of users
  • Use F3 to serve AS representation of repos and repo contents
  • Serve AS representation of organizations

Processing ActivityStreams

  • Verify that actor or attributedTo matches HTTP signature
  • sharedInbox? (not necessary)
  • C2S ActivityPub? (not necessary)
  • Process Follow and Undo Follow activities
  • Process Like and Undo Like activities
  • Use F3 to process repo-related activities
  • Process organization-related activities
  • Cross-instance Git push
  • Mirroring using HTTP signature authentication
  • Federated private repos (use HTTP signatures for auth)
  • Federated discussions? (like GitHub discussions?)

Database representation of remote data

  • Remote federated users
  • Remote organizations
  • Remote repositories
  • Database field for storing IRIs
  • External issues (and reference in comments)
  • External PRs (and reference in comments)
  • External projects (and reference in comments)

User eXperience and User Interface

See https://gitea.com/xy/gitea/issues/8 for discussions

Migrations

See https://gitea.com/xy/gitea/issues/9

  • Username or repo renames (See https://github.com/go-gitea/gitea/pull/19133#discussion_r1050648579)
  • Moving a user or repo to a different instance
  • Official way to migrate entire GitHub account to a Gitea instance
  • Official way to migrate entire GitHub organization to a Gitea instance
  • Configurable cooldown period in which usernames cannot be claimed
  • Import repo from F3

Interoperability

  • Federated following with Mastodon, Pleroma, etc
  • Federated commenting on issues from Mastodon, etc mastodon@github.com/mastodon#18806
  • Handle Mastodon delegation
  • Federation with GitHub by redirecting github.com resources to a different domain that generates AS representations of GitHub data and can proxy issues and PRs via a bot account on GitHub, something like Forgeflux or Forgefriends?

Moderation

See https://gitea.com/xy/gitea/issues/10

  • Disable all federation features by default
  • Blocking a user
  • Blocking a server
  • Moderation UI
  • Limited federation mode where your instance only federates with whitelisted instances
  • Rate limit federation requests
  • Rate limit user signups
  • Rate limit issue creation/commenting in UI

Contributing

If you'd like to help out with forge federation but don't know where to start, the links below might be helpful.

General

Some high-level links for learning about forge federation and the bigger picture

ActivityPub

Resources for learning ActivityPub (AP)

ForgeFed/F3

Forge federation protocol based on AP

Go-Ap

A lightweight AP library in Go that Gitea is using for implementing federation

Running federated Forgejo

You can also help federation development by running federated Forgejo and reporting bugs and regressions.

  • Make backups: This code will make possibly unexpected changes to your database.
  • Compile: Clone this repo and checkout the forgejo-federation branch. If you would like to build a Docker image, there is a Dockerfile in this repo. If you would like to build a binary, install Go and Node.js and then run TAGS="bindata" make.
  • Configuration: Set ENABLED=true in the [federation] section of your config file.
Update June 2024: this issue is no longer updated. Progress on federation can be followed from: * The [monthly reports](https://forgejo.org/tag/report/) * [Issues](https://codeberg.org/forgejo/forgejo/issues?labels=79349) and [pull requests](https://codeberg.org/forgejo/forgejo/pulls?labels=79349) tagged with `forgejo/federation` --- This issue tracks the progress of implementing [federation](https://nlnet.nl/project/Forgejo/) in Forgejo. # Ongoing tasks (updated monthly) * Federated stars draft [implementation in progress](https://codeberg.org/forgejo/forgejo/pulls/1680), see the [March 2024 report](https://domaindrivenarchitecture.org/posts/2024-03-27-state-of-federation/) * F3 published a User Research report. Read more in the [March 2024](https://forum.forgefriends.org/t/f3-monthly-update-march-2024/1022) report. # Tasks backlog ## Discovery This is done. - [x] Nodeinfo endpoint [go-gitea@github.com/gitea#16758](https://github.com/go-gitea/gitea/issues/16758) [#19561](https://github.com/go-gitea/gitea/pull/19561) - [x] WebFinger [go-gitea@github.com/gitea#19462](https://github.com/go-gitea/gitea/pull/19462) [go-gitea@github.com/gitea#19133](https://github.com/go-gitea/gitea/pull/19133) - [ ] Delegation? (WebFinger responses to a different domain, like what Mastodon does with its `WEB_DOMAIN` variable. This enables federation for instances using a subdirectory) ## Actors This is almost done. - [x] Create public/private keypair [go-gitea@github.com/gitea#17071](https://github.com/go-gitea/gitea/pull/17071) - [x] HTTP signature middleware [go-gitea@github.com/gitea#19133](https://github.com/go-gitea/gitea/pull/19133) - [x] Mapping Gitea's concepts ("People", "Teams") into AP "Actor" concepts - [x] Mapping Gitea's actor concepts into the ontology - [x] Assign Actor IRIs [go-gitea@github.com/gitea#19133](https://github.com/go-gitea/gitea/pull/19133) - [x] Manage inbox and outbox - [ ] Send out activities to followers - [ ] Render followed user updates in your user feed - [ ] Periodically fetch and update cached remote users' data - [ ] Clean out avatar cache ## ForgeFed - [x] Adapt Commit forgefed vocabulary for the needs of Gitea - [x] Adapt Repository forgefed vocabulary for the needs of Gitea - [x] Figure out the best way to represent pull requests in ForgeFed [ForgeFed@codeberg.org/ForgeFed#88](https://codeberg.org/ForgeFed/ForgeFed/issues/88) - [ ] Merge [F3](https://forum.forgefriends.org/t/about-the-friendly-forge-format-f3/681) and ForgeFed - [ ] Issue state changes [ForgeFed@codeberg.org/ForgeFed#98](https://codeberg.org/ForgeFed/ForgeFed/issues/98) - [ ] Add milestones to ForgeFed - [ ] Add project board federation to ForgeFed - [ ] Add migrations to ForgeFed spec [ForgeFed@codeberg.org/ForgeFed#149](https://codeberg.org/ForgeFed/ForgeFed/issues/149) ## go-ap Adding ForgeFed types to go-ap [Mastodon discussion](https://social.exozy.me/@ta180m/108466642486831048), [mailing list discussion](https://lists.sr.ht/~mariusor/activitypub-go/%3C6aivY9YmilsvQ6CauRoaXbvXX2bdZEXOEv-xnaTD0JLvodqKPZ2FMdQHmXYKmEOdzrPZU9Ipro5sOynfe-hJbi5f31MiqOV8EI4rDOw88wg%3D%40proton.me%3E) - [x] Implement Commit type - [x] Implement Repository type - [x] Implement Branch type - [x] Implement Push type - [x] Implement Ticket type - [ ] Tests - [x] Export more JSON functions from go-ap/activitypub (solved by using a fork https://gitea.com/Ta180m/activitypub) ## Serving ActivityStreams - [x] Addressing - [x] Transport (HTTPS with HTTP signatures) [go-gitea@github.com/gitea#19133](https://github.com/go-gitea/gitea/pull/19133) - [ ] Retry sending activities to servers that are down or have an outgoing activity queue - [x] Serve AS representation of users - [ ] Use F3 to serve AS representation of repos and repo contents - [ ] Serve AS representation of organizations ## Processing ActivityStreams - [x] Verify that actor or `attributedTo` matches HTTP signature - [ ] sharedInbox? (not necessary) - [ ] C2S ActivityPub? (not necessary) - [x] Process Follow and Undo Follow activities - [x] Process Like and Undo Like activities - [ ] Use F3 to process repo-related activities - [ ] Process organization-related activities - [ ] Cross-instance Git push - [ ] Mirroring using HTTP signature authentication - [ ] Federated private repos (use HTTP signatures for auth) - [ ] Federated discussions? (like GitHub discussions?) ## Database representation of remote data - [x] Remote federated users - [ ] Remote organizations - [x] Remote repositories - [ ] Database field for storing IRIs - [ ] External issues (and reference in comments) - [ ] External PRs (and reference in comments) - [ ] External projects (and reference in comments) ## User eXperience and User Interface See https://gitea.com/xy/gitea/issues/8 for discussions - [ ] Use cases ([federated issues](https://forum.forgefriends.org/t/forgefriends-full-description/13#presentation-1) etc.) - [ ] Drafting UX in PenPot - [ ] Remote interactions pop-up UI (like Mastodon) - [x] `authorize_interaction?uri=` page (like Mastodon) - [x] Federation handling for Gitea internal functions for creating issues, starring repos, etc - [ ] Global search bar - [ ] Discoverability (See https://sepiasearch.org/, https://github.com/forgeflux-org/northstar) ## Migrations See https://gitea.com/xy/gitea/issues/9 - [ ] Username or repo renames (See https://github.com/go-gitea/gitea/pull/19133#discussion_r1050648579) - [ ] Moving a user or repo to a different instance - [ ] Official way to migrate entire GitHub account to a Gitea instance - [ ] Official way to migrate entire GitHub organization to a Gitea instance - [ ] Configurable cooldown period in which usernames cannot be claimed - [ ] Import repo from F3 ## Interoperability - [x] Federated following with Mastodon, Pleroma, etc - [ ] Federated commenting on issues from Mastodon, etc [mastodon@github.com/mastodon#18806](https://github.com/mastodon/mastodon/issues/18806) - [ ] Handle Mastodon delegation - [ ] Federation with GitHub by redirecting github.com resources to a different domain that generates AS representations of GitHub data and can proxy issues and PRs via a bot account on GitHub, something like Forgeflux or Forgefriends? ## Moderation See https://gitea.com/xy/gitea/issues/10 - [x] Disable all federation features by default - [ ] Blocking a user - [ ] Blocking a server - [ ] Moderation UI - [ ] Limited federation mode where your instance only federates with whitelisted instances - [ ] Rate limit federation requests - [ ] Rate limit user signups - [ ] Rate limit issue creation/commenting in UI # Contributing If you'd like to help out with forge federation but don't know where to start, the links below might be helpful. ## General Some high-level links for learning about forge federation and the bigger picture - https://matrix.to/#/#general-forgefed:matrix.batsense.net General forge federation chatroom - https://matrix.to/#/#forgefederation:matrix.batsense.net Forge federation Matrix space - https://forum.forgefriends.org/ ForgeFriends forum - https://forgeflux.org/ Forge federation using forge APIs - https://coding.social/ Social Coding movement - https://forgefriends.org/blog/2022/06/30/2022-06-state-forge-federation/ The state of forge federation, 2021-2023 - https://a.exozy.me/posts/forge-federation-myths/ - https://a.exozy.me/posts/forge-federation-design-discussion/ - https://framatube.org/w/giYiJxH3bH2BekhJzk4x2C LibrePlanet 2023 talk - https://git.exozy.me/a/gitea Old 2022 ForgeFed implementation in Gitea (not based on F3) - https://gitea.com/xy/gitea/issues Forge federation design discussions ## ActivityPub Resources for learning ActivityPub (AP) - https://activitypub.rocks/ Official ActivityPub website - https://www.w3.org/TR/activitypub/ ActivityPub specification - https://a.exozy.me/posts/activitypub-eats-your-brain/ An opinionated ActivityPub guide - https://socialhub.activitypub.rocks/pub/guide-for-new-activitypub-implementers Guide for AP implementers - https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/ Tutorial for implementing a very basic AP server - https://blog.joinmastodon.org/2018/07/how-to-make-friends-and-verify-requests/ Tutorial for federated following - https://docs.joinmastodon.org/spec/activitypub/ Mastodon's AP subset - https://tinysubversions.com/notes/reading-activitypub/ How to read the AP spec - https://flak.tedunangst.com/post/ActivityPub-as-it-has-been-understood Lots of AP resources - https://delightful.club/delightful-activitypub-development/ AP developer resources ## ForgeFed/F3 Forge federation protocol based on AP - https://forgefed.org/ ForgeFed website - https://codeberg.org/ForgeFed/ForgeFed ForgeFed repo - https://matrix.to/#/#forgefed:libera.chat ForgeFed chatroom - https://vervis.peers.community/browse Reference ForgeFed implementation - https://f3.forgefriends.org/ F3 documentation ## Go-Ap A lightweight AP library in Go that Gitea is using for implementing federation - https://github.com/go-ap/activitypub Lightweight Go implementation of AP - https://github.com/go-ap/fedbox Reference implementation of a AP server using go-ap - https://man.sr.ht/~mariusor/go-activitypub/go-ap/index.md go-ap docs - https://lists.sr.ht/~mariusor/go-activitypub-discuss go-ap mailing list # Running federated Forgejo You can also help federation development by running federated Forgejo and reporting bugs and regressions. - Make backups: This code will make possibly unexpected changes to your database. - Compile: Clone this repo and checkout the `forgejo-federation` branch. If you would like to build a Docker image, there is a `Dockerfile` in this repo. If you would like to build a binary, install Go and Node.js and then run `TAGS="bindata" make`. - Configuration: Set `ENABLED=true` in the `[federation]` section of your config file.
👍 55 👀 19 ❤️ 44 🎉 2 🚀 4
xy added the
enhancement/feature
 label 2022-11-27 22:36:38 +00:00
Ghost added the
forgejo/federation
 label 2022-11-27 23:36:14 +00:00
Ghost commented 2022-11-27 23:38:28 +00:00
Copy link

I'm in favor of creating a forgejo-federation feature branch. AFAICT forge federation is a goal shared by all people involved in Forgejo.

I'm in favor of creating a **forgejo-federation** feature branch. AFAICT forge federation is a goal shared by all people involved in Forgejo.
👍 12
xy was assigned by Ghost 2022-11-28 07:38:33 +00:00
Ghost commented 2023-06-10 07:50:24 +00:00
Copy link

@xy are there are changes in the forgejo-federation branch that should be merged in v1.20?

@xy are there are changes in the `forgejo-federation` branch that should be merged in v1.20?
ADRN0 commented 2023-06-10 11:09:47 +00:00
Copy link

Just to add to the mill: be aware that the French CHATONS collective is very eager to see this feature implemented. Indeed, some of us know each other, and we personnally maintain quite the database of login/passwords to contribute to our comrades forges and repositories. Be it documentation, infrastructural code, or even free projects forks and patches. Many of us used to run Gitea, and e.g. Deuxfleurs (the chaton I participate in) notably moved to Forgejo already.

See this forum post (in French): https://forum.chatons.org/t/federation-de-forges/1869

So I'm not the only one to believe that enabling federation between Forgejo instances would be beneficial to free software at large. It would tighten our infrastructural bounds, improve our capacity to contribute, and allow us to produce more generalistic software more easily.

Very glad to see you have a NLNet partnership towards this end!

Just to add to the mill: be aware that the French [CHATONS](https://chatons.org) collective is very eager to see this feature implemented. Indeed, some of us know each other, and we personnally maintain quite the database of login/passwords to contribute to our comrades forges and repositories. Be it documentation, infrastructural code, or even free projects forks and patches. Many of us used to run Gitea, and e.g. [Deuxfleurs](https://deuxfleurs.fr) (the chaton I participate in) notably moved to [Forgejo](https://git.deuxfleurs.fr) already. See this forum post (in French): https://forum.chatons.org/t/federation-de-forges/1869 So I'm not the only one to believe that enabling federation between Forgejo instances would be beneficial to free software at large. It would tighten our infrastructural bounds, improve our capacity to contribute, and allow us to produce more generalistic software more easily. Very glad to see you have a NLNet partnership towards this end!
👍 4 ❤️ 3
xy commented 2023-06-10 14:25:35 +00:00
Author
Copy link

@xy are there are changes in the forgejo-federation branch that should be merged in v1.20?

Unfortunately no, since I am once again busy with something else at the moment, but hopefully I'll finally be able to resume work on it later this month.

> @xy are there are changes in the `forgejo-federation` branch that should be merged in v1.20? Unfortunately no, since I am once again busy with something else at the moment, but hopefully I'll finally be able to resume work on it later this month.
👍 1
caesar pinned this 2023-08-15 22:56:37 +00:00
caesar unpinned this 2023-08-15 22:56:59 +00:00
ip commented 2023-09-03 21:11:46 +00:00
Copy link

With GitLab implementing federation, it would be great to see Forgejo do the same

With GitLab implementing federation, it would be great to see Forgejo do the same
earl-warren commented 2023-09-04 06:30:55 +00:00
Owner
Copy link

@ip GitLab does not implement federation and never will, because it would hurt their business model. GitLab restricts the direction in which you can mirror git repositories, this is where they stand. If you want git mirroring in both directions you are required to acquire a proprietary license. That's telling you how far away they are from even the idea of federated forges 😄

That being said, I'm working on implementing federation in Forgejo and there is a lot to do. Would you like to help? There is no need to have particular skills. Just time.

@ip GitLab does not implement federation and never will, because it would hurt their business model. GitLab **restricts** the direction in which you can mirror git repositories, this is where they stand. If you want git mirroring in both directions you are required to acquire a proprietary license. That's telling you how far away they are from even the idea of federated forges 😄 That being said, I'm working on implementing federation in Forgejo and there is a lot to do. Would you like to help? There is no need to have particular skills. Just time.
😆 3
marie commented 2023-09-04 09:21:24 +00:00
Copy link

GitLab is working on implementing federation between GitLab instances1.
Only for merge requests for now iirc, but one of the people implementing it, said they will consider ForgeFed when also implementing support for other stuff2.

But yes, they will probably limit some stuff like they do with mirrors, because of them being a for-profit company.

GitLab is working on implementing federation between GitLab instances[^1]. Only for merge requests for now iirc, but one of the people implementing it, said they will consider ForgeFed when also implementing support for other stuff[^2]. But yes, they will probably limit some stuff like they do with mirrors, because of them being a for-profit company. [^1]: https://gitlab.com/groups/gitlab-org/-/epics/11247 [^2]: https://gitlab.com/gitlab-org/gitlab/-/issues/21582
earl-warren commented 2023-09-04 11:26:01 +00:00
Owner
Copy link

That's a lot of activity and I missed it completely, thanks for the pointers. Are there merge requests to implement that already? When you write "GitLab is working" do you mean that all these epics / issues originate from GitLab employees in their official capacity? Or is it more of an initiative from people in the GitLab community but not necessarily endorsed by GitLab? It would actually be better news if it was the later.

That's a **lot** of activity and I missed it completely, thanks for the pointers. Are there merge requests to implement that already? When you write "GitLab is working" do you mean that all these epics / issues originate from GitLab employees in their official capacity? Or is it more of an initiative from people in the GitLab community but not necessarily endorsed by GitLab? It would actually be better news if it was the later.
marie commented 2023-09-04 12:32:15 +00:00
Copy link

I'm not really sure how far it's done, I'm not active in the GitLab community, I just heard about it from a friend.
I'm also not sure how much GitLab as a company is involved here, If I remember correctly, the federation stuff is primarily implemented by a community member and not by GitLab itself, but don't call me on that, I lost track on all of these issues/epics/merge requests.

I'm not really sure how far it's done, I'm not active in the GitLab community, I just heard about it from a friend. I'm also not sure how much GitLab as a company is involved here, If I remember correctly, the federation stuff is primarily implemented by a community member and not by GitLab itself, but don't call me on that, I lost track on all of these issues/epics/merge requests.
👍 1
earl-warren commented 2023-09-04 14:01:33 +00:00
Owner
Copy link

@marie it's a lot, some going back five years. But it's good to have that revived. I wish there would be merge requests but I can't seem to find any just yet. If you ever see one and you remember this conversation when it happens, I would love to know.

@marie it's a lot, some going back five years. But it's good to have that revived. I wish there would be merge requests but I can't seem to find any just yet. If you ever see one and you remember this conversation when it happens, I would love to know.
👍 1
Anafabula commented 2023-09-04 14:20:54 +00:00
Copy link

@earl-warren There is one, but I know neither Gitlab nor ActivityPub.

@earl-warren There is [one](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127023), but I know neither Gitlab nor ActivityPub.
caesar commented 2023-09-04 14:41:21 +00:00
Member
Copy link

I think GitLab's activity is a bit off topic for this issue, but here's my understanding:

  • The feature requests have been open for years with no traction until last month (approx).
  • One external volunteer developer is working on it. He has some level of blessing from GitLab but they're not working on it themselves and obviously they will have to approve anything that gets merged.
  • At present the developer is working on implementing support for following an issue from Mastodon via ActivityPub – approximately equivalent to what has already been implemented for Forgejo.
  • Actual federation is something he plans to work on in future and he is aware of ForgeFed.

I don't want to diminish the work being done for GitLab at all. I think it's great to see movement there, and so long as it's done in a thoughtful and interoperable way (and every sign so far indicates that that's the intention), it will be good for the entire ecosystem including Forgejo. It's very exciting to see we're not the only ones working on it.
But it's important to be aware of the limits of what's being done at present - on both sides - and not be drawn in by hyperbole.

I think GitLab's activity is a bit off topic for this issue, but here's my understanding: - The feature requests have been open for years with no traction until last month (approx). - One external volunteer developer is working on it. He has some level of blessing from GitLab but they're not working on it themselves and obviously they will have to approve anything that gets merged. - At present the developer is working on implementing support for following an issue from Mastodon via ActivityPub – approximately equivalent to what has already been implemented for Forgejo. - Actual federation is something he plans to work on in future and he is aware of ForgeFed. I don't want to diminish the work being done for GitLab at all. I think it's great to see movement there, and so long as it's done in a thoughtful and interoperable way (and every sign so far indicates that that's the intention), it will be good for the entire ecosystem including Forgejo. It's very exciting to see we're not the only ones working on it. But it's important to be aware of the limits of what's being done at present - on both sides - and not be drawn in by hyperbole.
👍 3
earl-warren commented 2023-09-04 15:05:03 +00:00
Owner
Copy link

Sorry for contributing to derail this topic. I created a new topic in the forgefriends forum where other GitLab related efforts were tracked in the past.

Sorry for contributing to derail this topic. I created a new topic in the [forgefriends forum](https://forum.forgefriends.org/t/add-activitypub-releases-profile-and-outbox/996) where other GitLab related efforts were tracked in the past.
👍 1
earl-warren added the
User Research - federation
 label 2023-10-25 12:10:10 +00:00
farooqkz commented 2023-10-25 16:15:34 +00:00
Copy link

Keep it up! May the Source be with you! Is there a group for testing calls for the federation thing?

Keep it up! May the Source be with you! Is there a group for testing calls for the federation thing?
❤️ 5
earl-warren commented 2023-10-26 12:57:54 +00:00
Owner
Copy link

No group yet.

No group yet.
mokazemi commented 2024-01-08 15:57:48 +00:00
Copy link

Any news on this awesome project? 😃

Any news on this awesome project? 😃
earl-warren commented 2024-01-08 16:19:23 +00:00
Owner
Copy link

It is great that you find it awesome. As you will see in following the links at the top of the issue, there is daily progress. Nothing usable just yet though. if you know of someone (all kinds of skills are needed) willing to help, please ask them! There is much to do.

It is great that you find it awesome. As you will see in following the links at the top of the issue, there is daily progress. Nothing usable just yet though. if you know of someone (all kinds of skills are needed) willing to help, please ask them! There is much to do.
👍 7 ❤️ 4 🚀 6
hexaheximal commented 2024-02-25 19:54:45 +00:00
Copy link

This is a great idea. Can't wait to see forgejo instances federate seamlessly some day :)

This is a great idea. Can't wait to see forgejo instances federate seamlessly some day :)
❤️ 9 🚀 4
Haui commented 2024-02-28 10:41:49 +00:00
Copy link

It is great that you find it awesome. As you will see in following the links at the top of the issue, there is daily progress. Nothing usable just yet though. if you know of someone (all kinds of skills are needed) willing to help, please ask them! There is much to do.

I'd like to help but I'm not a professional coder. I'll try and run a docker container of the project and start reporting bugs. I do the same for Mastodon, Lemmy and Matrix. My limited Python and C# knowledge doesnt seem to be of much help atm. Feel free to lmk if I can do anything else. (I made an account just to voice my support in this. Git+Federation is going to change everything imo.)

P.S.: I think there should be much more updates to the state of federation in git forges (if that is the correct term even) because a lot of us fedi folk are looking forward to it but its hard to find which project is ahead and when we can start testing, etc. Obviously, the fediverse would be great for such updates. I would help with that too if needed.

> It is great that you find it awesome. As you will see in following the links at the top of the issue, there is daily progress. Nothing usable just yet though. if you know of someone (all kinds of skills are needed) willing to help, please ask them! There is much to do. I'd like to help but I'm not a professional coder. I'll try and run a docker container of the project and start reporting bugs. I do the same for Mastodon, Lemmy and Matrix. My limited Python and C# knowledge doesnt seem to be of much help atm. Feel free to lmk if I can do anything else. (I made an account just to voice my support in this. Git+Federation is going to change everything imo.) P.S.: I think there should be much more updates to the state of federation in git forges (if that is the correct term even) because a lot of us fedi folk are looking forward to it but its hard to find which project is ahead and when we can start testing, etc. Obviously, the fediverse would be great for such updates. I would help with that too if needed.
❤️ 3
n0toose commented 2024-03-08 16:34:33 +00:00
Member
Copy link

It has come to my attention that there are onlookers that regularly check this this thread because they are curious about the status of federation in Forgejo. For this reason (hello strangers 👋), it might be worth mentioning here that this issue is not a declarative source and that Forgejo's monthly updates are worth checking out.

As of March 8, 2024, some of the PRs that may be worth taking a look at can be found here:

This list is not exhaustive and will get outdated fast (and I'm also not a reliable source because I don't actively work on those features :D). The pull requests marked using the labels forgejo/moderation and forgejo/federation may be worth checking out, as well as f3.forgefriends.org and forgefriends.org.

Forgejo's Issues and Pull Requests are a place of work and there is a dedicated repository for discussions (both of these places are subjected to Forgejo's Code of Conduct).

It has come to my attention that there are onlookers that regularly check this this thread because they are curious about the status of federation in Forgejo. For this reason (hello strangers 👋), it might be worth mentioning here that this issue is not a declarative source and that [Forgejo's monthly updates](https://forgejo.org/news/) are worth checking out. As of March 8, 2024, some of the PRs that may be worth taking a look at can be found here: - https://codeberg.org/forgejo/forgejo/pulls/1680 - https://codeberg.org/forgejo/forgejo/pulls/2465 - https://codeberg.org/forgejo/forgejo/pulls/2388 This list is not exhaustive and will get outdated fast (and I'm also not a reliable source because I don't actively work on those features :D). The pull requests marked using the labels [forgejo/moderation](https://codeberg.org/forgejo/forgejo/pulls?q=moderation&type=all&labels=120787) and [forgejo/federation](https://codeberg.org/forgejo/forgejo/pulls?q=federation&type=all&labels=79349) may be worth checking out, as well as [f3.forgefriends.org](https://f3.forgefriends.org/) and [forgefriends.org](https://forgefriends.org/). Forgejo's Issues and Pull Requests are a place of work and there is a [dedicated repository for discussions](https://codeberg.org/forgejo/discussions/issues) (both of these places are subjected to Forgejo's [Code of Conduct](https://codeberg.org/forgejo/code-of-conduct/)).
👍 16 ❤️ 4 😆 2
fnetX removed the
User Research - federation
 label 2024-04-09 16:50:16 +00:00
nercon commented 2024-04-23 13:52:01 +00:00
Copy link

'we will contribute the federation code upstream to Gitea.' https://forgejo.org/2023-01-10-answering-forgejo-federation-questions/#will-gitea-also-gain-federation

Is that still the plan after the hard fork?

'we will contribute the federation code upstream to Gitea.' https://forgejo.org/2023-01-10-answering-forgejo-federation-questions/#will-gitea-also-gain-federation Is that still the plan after the hard fork?
👍 3
earl-warren commented 2024-04-23 14:02:04 +00:00
Owner
Copy link

Well, yes. And Gitness and Gogs really. Whoever needs it. Will it be easy? Not really. But what would be the point of federation of some forges are left behind?

Well, yes. And Gitness and Gogs really. Whoever needs it. Will it be easy? Not really. But what would be the point of federation of some forges are left behind?
👍 8 ❤️ 11
earl-warren commented 2024-06-16 18:35:24 +00:00
Owner
Copy link

This issue is no longer updated. Progress on federation can be followed from:

Although it still lacks a user friends UI, the first federated feature was merged recently (federated stars). Things are moving forward.

This issue is no longer updated. Progress on federation can be followed from: * The [monthly reports](https://forgejo.org/tag/report/) * [Issues](https://codeberg.org/forgejo/forgejo/issues?labels=79349) and [pull requests](https://codeberg.org/forgejo/forgejo/pulls?labels=79349) tagged with `forgejo/federation` Although it still lacks a user friends UI, the first federated feature was merged recently (federated stars). Things are moving forward.
👍 7 🎉 1
silverpill commented 2024-06-23 23:58:48 +00:00
Copy link

@earl-warren I can't find an issue about opening issues from other Fediverse platforms (e.g. Mastodon). Is it planned?

That would be a great addition, because registration wall is a big problem for small self-hosted forges.

@earl-warren I can't find an issue about opening issues from other Fediverse platforms (e.g. Mastodon). Is it planned? That would be a great addition, because registration wall is a big problem for small self-hosted forges.
👍 4
Haui commented 2024-06-24 05:36:44 +00:00
Copy link

From the reports I'm not positive I know when and how to use federation. I dont see any Q&A entries either that touch the topic. My version (7.0.4) does also not show any federation entries. Can someone point me to the correct info?

From the reports I'm not positive I know when and how to use federation. I dont see any Q&A entries either that touch the topic. My version (7.0.4) does also not show any federation entries. Can someone point me to the correct info?
👍 1
earl-warren commented 2024-06-24 06:06:24 +00:00
Owner
Copy link

From the reports I'm not positive I know when and how to use federation.

Nobody knows. It will be ready when it is ready. There is much to do and it is progressing but help is much needed. Would you like to give a hand? Or know someone who would?

> From the reports I'm not positive I know when and how to use federation. Nobody knows. It will be ready when it is ready. There is much to do and it is progressing but help is much needed. Would you like to give a hand? Or know someone who would?
earl-warren commented 2024-06-24 06:12:40 +00:00
Owner
Copy link

@silverpill there is no such issue but this is something I'd like to use as well. Last week my contribution to the effort was helping setup the test environment to launch a GitLab instance so it can be connected via ActivityPub to a Forgejo instance. https://code.forgejo.org/forgejo/end-to-end/pulls/207

I recommend you follow the reports, that's currently the best way to keep up to date. And if you ever know someone willing to participate in the implementation, they would be very welcome. There is a need for a lot more workforce.

@silverpill there is no such issue but this is something I'd like to use as well. Last week my contribution to the effort was helping setup the test environment to launch a GitLab instance so it can be connected via ActivityPub to a Forgejo instance. https://code.forgejo.org/forgejo/end-to-end/pulls/207 I recommend you follow the reports, that's currently the best way to keep up to date. And if you ever know someone willing to participate in the implementation, they would be very welcome. There is a need for a lot more workforce.
❤️ 1
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
forgejo
renovate/forgejo-sortablejs-1.x
renovate/forgejo-mermaid-11.x
v9.0/forgejo
bp-v9.0/forgejo-7aeb1ba
v7.0/forgejo
renovate/forgejo-typescript-5.x
bp-v9.0/forgejo-45fa9e5
v8.0/forgejo
bp-v9.0/forgejo-86bac2c
bp-v9.0/forgejo-dcc4423
bp-v8.0/forgejo-e9e3b8c
v1.21/forgejo
v1.20/forgejo
v1.19/forgejo
v1.18/forgejo
v1.17/forgejo
v9.0.2
v7.0.11
v9.0.1
v7.0.10
v9.0.0
v10.0.0-dev
v8.0.3
v7.0.9
v8.0.2
v7.0.8
v8.0.1
v7.0.7
v8.0.0
v7.0.6
v7.0.5
v9.0.0-dev
v7.0.4
v1.21.11-2
v7.0.3
v7.0.2
v7.0.1
v7.0.0
v1.21.11-1
v1.21.11-0
v1.21.10-0
v8.0.0-dev
v1.21.8-0
v1.21.7-0
v1.21.6-0
v1.21.5-0
v1.21.4-0
v1.21.3-0
v1.20.6-1
v1.21.2-1
v1.21.2-0
v1.20.6-0
v1.21.1-0
v1.20.5-1
v1.21.0-rc2
v1.21.0-rc1
v1.20.5-0
v7.0.0-dev
v1.21.0-rc0
v1.20.4-1
v1.20.4-0
v1.20.3-0
v1.20.2-0
v1.20.1-0
v1.20.0
v1.19.4-0
v1.21.0-dev
v1.20.0-rc2
v1.19.3-0
v1.19.2-0
v1.19.1-0
v1.19.0-3
v1.19.0-2
v1.18.5-0
v1.20.0-dev
v1.19.0-rc0
v1.18.3-2
v1.18.3-1
v1.18.3-0
v1.18.2-1
v1.18.2-0
v1.18.1-0
v1.18.0-1
v1.18.0-0
v1.18.0-rc1-2
v1.18.0-rc1-1
v1.18.0-rc1
v1.18.0-rc0
v1.19.0-dev
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   
arch
amd64

Archived

  
arch
arm6

Archived

  
arch
arm64

Archived

  
arch
arm7

Archived

  
arch
riscv64

Archived

  
backport/v1.19

Scheduled for backport to Forgejo v1.19

Archived

  
backport/v1.20

Scheduled for backport to Forgejo v1.20

Archived

  
backport/v1.21/forgejo

Scheduled for backport to Forgejo v1.21

Archived

  
backport/v7.0/forgejo

Scheduled for backport to Forgejo v7.0

  
backport/v8.0/forgejo

Scheduled for backport to Forgejo v8.0

Archived

  
backport/v9.0/forgejo

Scheduled for backport to Forgejo v9.0

  
breaking

The release containing this change is not backward compatible

  
bug

Something is not working

Archived

  
bug
confirmed
it can be reproduced

  
bug
duplicate
bug has already been reported in the Forgejo tracker

  
bug
needs-more-info
the information provided does not contain enough details

  
bug
new-report
bug has just been reported and need triage (default label on issue creation)

  
bug
reported-upstream
bug cannot be fixed within Forgejo easily, it has been reported upstream

  
codeberg

related to Codeberg but not generic enough to apply to Forgejo

  
database
CockroachDB
https://github.com/cockroachdb/cockroach & https://codeberg.org/forgejo/discussions/issues/174

Archived

  
database
MySQL
https://www.mysql.com/

  
database
PostgreSQL
https://www.postgresql.org/

  
database
SQLite
https://sqlite.org/

  
dependency-upgrade

https://codeberg.org/forgejo/forgejo/issues/2779

  
dependency
ACT
https://code.forgejo.org/forgejo/act

Archived

  
dependency
alpine
https://alpinelinux.org/

Archived

  
dependency
asciinema-player
https://github.com/asciinema/asciinema-player

Archived

  
dependency
bleve
github.com/blevesearch/bleve

Archived

  
dependency
cache
https://codeberg.org/redict or https://redis.io/ or https://github.com/microsoft/garnet/

Archived

  
dependency
certmagic
github.com/caddyserver/certmagic

Archived

  
dependency
chart.js
https://github.com/chartjs/Chart.js

Archived

  
dependency
Chi
https://github.com/go-chi/chi/

Archived

  
dependency
Chroma
https://github.com/alecthomas/chroma/

Archived

  
dependency
citation.js
https://github.com/larsgw/citation.js/

Archived

  
dependency
codespell
https://github.com/codespell-project/codespell

Archived

  
dependency
css-loader
https://github.com/webpack-contrib/css-loader

Archived

  
dependency
devcontainers
https://github.com/devcontainers/cli

Archived

  
dependency
dropzone
https://github.com/dropzone/dropzone

Archived

  
dependency
editorconfig-checker
https://github.com/editorconfig-checker/editorconfig-checker

Archived

  
dependency
elasticsearch
https://www.elastic.co/elasticsearch

Archived

  
dependency
enmime
https://github.com/jhillyerd/enmime

Archived

  
dependency
F3
https://f3.forgefriends.org/

  
dependency
ForgeFed
https://forgefed.org

  
dependency
garage
https://git.deuxfleurs.fr/Deuxfleurs/garage

  
dependency
Git
https://git-scm.com/

Archived

  
dependency
git-backporting
https://github.com/kiegroup/git-backporting

Archived

  
dependency
Gitea
https://github.com/go-gitea/gitea

  
dependency
gitignore
https://github.com/github/gitignore

Archived

  
dependency
go-ap
https://github.com/go-ap/activitypub

Archived

  
dependency
go-enry
https://github.com/go-enry/go-enry

Archived

  
dependency
go-gitlab
https://github.com/xanzy/go-gitlab

Archived

  
dependency
Go-org
https://github.com/niklasfasching/go-org

Archived

  
dependency
go-rpmutils
https://github.com/sassoftware/go-rpmutils

Archived

  
dependency
go-sql-driver mysql
https://github.com/go-sql-driver/mysql/

Archived

  
dependency
go-swagger
github.com/go-swagger/go-swagger

Archived

  
dependency
go-version
https://github.com/hashicorp/go-version

Archived

  
dependency
go-webauthn
https://github.com/go-webauthn/webauthn

Archived

  
dependency
gocron
https://github.com/go-co-op/gocron

Archived

  
dependency
Golang
https://go.dev/

  
dependency
goldmark
https://github.com/yuin/goldmark

Archived

  
dependency
goquery
github.com/PuerkitoBio/goquery

Archived

  
dependency
Goth
https://github.com/markbates/goth/

Archived

  
dependency
grpc-go
https://github.com/grpc/grpc-go

Archived

  
dependency
happy-dom
https://github.com/capricorn86/happy-dom

Archived

  
dependency
Helm
https://helm.sh/

Archived

  
dependency
image-spec
https://github.com/opencontainers/image-spec

Archived

  
dependency
jsonschema
https://github.com/santhosh-tekuri/jsonschema

Archived

  
dependency
KaTeX
https://github.com/KaTeX/KaTeX

Archived

  
dependency
lint
All linting tools and libraries

Archived

  
dependency
MariaDB
https://mariadb.com/

Archived

  
dependency
Mermaid
https://github.com/mermaid-js/mermaid/

Archived

  
dependency
minio-go
https://github.com/minio/minio-go/

Archived

  
dependency
misspell
github.com/golangci/misspell/cmd/misspell

Archived

  
dependency
Monaco
https://github.com/microsoft/monaco-editor

Archived

  
dependency
PDFobject
https://pdfobject.com/

Archived

  
dependency
playwright
https://playwright.dev/

Archived

  
dependency
postcss
https://github.com/postcss/postcss

Archived

  
dependency
postcss-plugins
https://github.com/csstools/postcss-plugins

Archived

  
dependency
pprof
https://github.com/google/pprof

Archived

  
dependency
prometheus client_golang
https://github.com/prometheus/client_golang

Archived

  
dependency
protobuf
https://google.golang.org/protobuf

Archived

  
dependency
relative-time-element
https://github.com/github/relative-time-element

Archived

  
dependency
renovate
https://github.com/renovatebot/renovate

Archived

  
dependency
reply
https://code.forgejo.org/forgejo/reply

Archived

  
dependency
ssh
https://github.com/gliderlabs/ssh

Archived

  
dependency
swagger-ui
https://github.com/swagger-api/swagger-ui

Archived

  
dependency
tailwind
https://tailwindcss.com/

Archived

  
dependency
temporal-polyfill
https://github.com/fullcalendar/temporal-polyfill

Archived

  
dependency
terminal-to-html
github.com/buildkite/terminal-to-html

Archived

  
dependency
tests-only
Undifferentiated dependencies used for testing only

Archived

  
dependency
text-expander-element
https://github.com/github/text-expander-element

Archived

  
dependency
urfave
https://github.com/urfave/cli

Archived

  
dependency
vfsgen
https://github.com/lunny/vfsgen

Archived

  
dependency
vite
https://vitejs.dev/

Archived

  
dependency
Woodpecker CI
https://woodpecker-ci.org/

Archived

  
dependency
x tools
https://golang.org/x/tools

Archived

  
dependency
XORM
https://gitea.com/xorm/xorm

Archived

  
Discussion

   
duplicate

This issue or pull request already exists

  
enhancement/feature

New feature

  
forgejo/accessibility

Accessibility (a11y)

  
forgejo/actions

Actions

  
forgejo/api

API

  
forgejo/branding

Branding (logo, name, tagline etc.)

  
forgejo/ci

Forgejo Actions CI configuration

  
forgejo/documentation

   
forgejo/email

Everything related to email in Forgejo

  
forgejo/federation

Federation

  
forgejo/furnace cleanup

Keeping Forgejo in sync with its dependencies and contributing back to them

Archived

  
forgejo/i18n

t9n/translation, l10n/localization, and i18n/internationalization of Forgejo

  
forgejo/moderation

Moderation

  
forgejo/privacy

Privacy first

  
forgejo/release

Release management

  
forgejo/scaling

Performance and scaling

  
forgejo/security

Security (please disclose responsibly)

  
forgejo/time-tracker

Time tracking feature for issues and the JS stopwatch. Not actively maintained by Forgejo.

  
forgejo/ui

User interface

  
forgejo/wiki
  
Gain
High
User research provides indicators that this would be good to have, interested contributors are encouraged to pick this.

  
Gain
Nice to have
This is likely worth having, but the assumption is not backed by user research data (it might benefit a small amount of users only.) Unlikely to receive much attention, but feel free to pick.

  
Gain
Undefined
There is not enough information to justify the effort for this request, and the issue might get closed to stay focused. You can help with user research to collect information supporting this request.

  
Gain
Very High
User research confirms this is an important improvement for our users. Contributions very welcome!

  
good first issue

Start your contribution here! Optionally see who added the label, ask for help and watch out for further explanations.

  
Incompatible license

This pull request contains changes that are not (yet) compatible with the current Forgejo license

  
issue
closed
The issue was resolved in the repository of the dependency

  
issue
do-not-exist-yet
An issue should be created in the respository of the dependency

  
issue
open
An open issue exists in the upstream repository of the dependency

  
manual test

Pull requests that have been merged with a manual test

Archived

  
Manually tested during feature freeze

The manual test instructions were followed

  
OS
FreeBSD
Specific to the FreeBSD Operating System

  
OS
Linux
Specific to (GNU/)Linux Operating Systems

  
OS
MacOS
Specific to the MacOS Operating System

  
OS
Windows
Specific to the Windows Operating System

  
QA

   
regression

found in the version of the milestone and not before

  
release blocker

Issues that must be fixed before the release can be published

  
Release Cycle
Feature Freeze
Only bug fixes with automated tests (except for CSS/JavaScript)

  
release-blocker
v7.0
Issues that must be fixed before Forgejo v7.0 can be released 17 April 2024

Archived

  
release-blocker
v7.0.1
Issues that must be fixed before Forgejo v7.0.1 can be released

Archived

  
release-blocker
v7.0.2
Issues that must be fixed before Forgejo v7.0.2 can be released

Archived

  
release-blocker
v7.0.3
Issues that must be fixed before Forgejo v7.0.3 can be released

Archived

  
release-blocker
v7.0.4
Issues that must be fixed before Forgejo v7.0.4 can be released

Archived

  
release-blocker
v8.0.0
Issues that must be fixed before Forgejo v8.0.0 can be released

Archived

  
release-blocker/v9.0.0

Issues that must be fixed before Forgejo v9.0.0 can be released

  
run-end-to-end-tests

Trigger additional tests on the PR when it is ready to be merged

  
test
manual
manual testing has been documented

  
test
needed
test should be added

  
test
needs-help
help needed to add a test

  
test
not-needed
no additional test is needed

  
test
present
test has been added

  
untested

Pull requests that have been merged with no test and submitted as is to the dependency where they belong

Archived

  
valuable code

This PR was closed because the implementation is incomplete

  
worth a release-note

Add this PR to the release notes

  
User Research - Accessibility

Requires input about accessibility features, likely involves user testing.

  
User Research - bug

Archived

  
User Research - Config (instance)

Problems and ideas on how to improve the instance-wide configuration.

  
User Research - Dashboard

Everything that could potentially fit a redesigned dashboard, including issue / PR / todo displays.

  
User Research - documentation

Archived

  
User Research - Errors

How to deal with errors in the application and write helpful error messages.

  
User Research - feature

Archived

  
User Research - federation

Archived

  
User Research - Filters

How filter and search is being worked with.

  
User Research - In the Future

The issue might be inspiring for future design work.

  
User Research - Labels

Active research about Labels

  
User Research - Moderation

Moderation Featuers for Admins are undergoing active User Research

  
User Research - Needs Input

Use this label to let the User Research team know their input is requested.

  
User Research - Notifications

Research on how to improve the notification views is currently active.

  
User Research - release

Archived

  
User Research - Repo creation

Active research about the New Repo dialog.

  
User Research - Repo Units

The repo sections, disabling them and the "Add more" button.

  
User Research - security

   
User Research - Settings (in-app)

How to structure in-app settings in the future?

  
User Research - testing

Archived

  
User Research - UI

Archived

  
User Research - UX

Archived

No labels
arch
amd64
arch
arm6
arch
arm64
arch
arm7
arch
riscv64
backport/v1.19
backport/v1.20
backport/v1.21/forgejo
backport/v7.0/forgejo
backport/v8.0/forgejo
backport/v9.0/forgejo
breaking
bug
bug
confirmed
bug
duplicate
bug
needs-more-info
bug
new-report
bug
reported-upstream
codeberg
database
CockroachDB
database
MySQL
database
PostgreSQL
database
SQLite
dependency-upgrade
dependency
ACT
dependency
alpine
dependency
asciinema-player
dependency
bleve
dependency
cache
dependency
certmagic
dependency
chart.js
dependency
Chi
dependency
Chroma
dependency
citation.js
dependency
codespell
dependency
css-loader
dependency
devcontainers
dependency
dropzone
dependency
editorconfig-checker
dependency
elasticsearch
dependency
enmime
dependency
F3
dependency
ForgeFed
dependency
garage
dependency
Git
dependency
git-backporting
dependency
Gitea
dependency
gitignore
dependency
go-ap
dependency
go-enry
dependency
go-gitlab
dependency
Go-org
dependency
go-rpmutils
dependency
go-sql-driver mysql
dependency
go-swagger
dependency
go-version
dependency
go-webauthn
dependency
gocron
dependency
Golang
dependency
goldmark
dependency
goquery
dependency
Goth
dependency
grpc-go
dependency
happy-dom
dependency
Helm
dependency
image-spec
dependency
jsonschema
dependency
KaTeX
dependency
lint
dependency
MariaDB
dependency
Mermaid
dependency
minio-go
dependency
misspell
dependency
Monaco
dependency
PDFobject
dependency
playwright
dependency
postcss
dependency
postcss-plugins
dependency
pprof
dependency
prometheus client_golang
dependency
protobuf
dependency
relative-time-element
dependency
renovate
dependency
reply
dependency
ssh
dependency
swagger-ui
dependency
tailwind
dependency
temporal-polyfill
dependency
terminal-to-html
dependency
tests-only
dependency
text-expander-element
dependency
urfave
dependency
vfsgen
dependency
vite
dependency
Woodpecker CI
dependency
x tools
dependency
XORM
Discussion
duplicate
enhancement/feature
forgejo/accessibility
forgejo/actions
forgejo/api
forgejo/branding
forgejo/ci
forgejo/documentation
forgejo/email
forgejo/federation
forgejo/furnace cleanup
forgejo/i18n
forgejo/moderation
forgejo/privacy
forgejo/release
forgejo/scaling
forgejo/security
forgejo/time-tracker
forgejo/ui
forgejo/wiki
Gain
High
Gain
Nice to have
Gain
Undefined
Gain
Very High
good first issue
Incompatible license
issue
closed
issue
do-not-exist-yet
issue
open
manual test
Manually tested during feature freeze
OS
FreeBSD
OS
Linux
OS
MacOS
OS
Windows
QA
regression
release blocker
Release Cycle
Feature Freeze
release-blocker
v7.0
release-blocker
v7.0.1
release-blocker
v7.0.2
release-blocker
v7.0.3
release-blocker
v7.0.4
release-blocker
v8.0.0
release-blocker/v9.0.0
run-end-to-end-tests
test
manual
test
needed
test
needs-help
test
not-needed
test
present
untested
valuable code
worth a release-note
User Research - Accessibility
User Research - bug
User Research - Config (instance)
User Research - Dashboard
User Research - documentation
User Research - Errors
User Research - feature
User Research - federation
User Research - Filters
User Research - In the Future
User Research - Labels
User Research - Moderation
User Research - Needs Input
User Research - Notifications
User Research - release
User Research - Repo creation
User Research - Repo Units
User Research - security
User Research - Settings (in-app)
User Research - testing
User Research - UI
User Research - UX
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
15 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: forgejo/forgejo#59
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?