forgejo/docs
32
45
Fork
You've already forked docs
204

[v14.0] docs(federation): add strongly worded warning #1674

Merged
Beowulf merged 1 commit from bp-v14.0-0e9dc1e into v14.0 2026年01月10日 17:16:57 +01:00
Collaborator
Copy link

Backport: #1643

With some usable federation features now merged, I think it might be worth to add a warning for people who want to inevitably try it out. Maybe a point on federation in the FAQ could also be useful.

This should be backported to the v14 docs as well.

**Backport:** https://codeberg.org/forgejo/docs/pulls/1643 With some usable federation features now merged, I think it might be worth to add a warning for people who want to inevitably try it out. Maybe a point on federation in the FAQ could also be useful. This should be backported to the v14 docs as well.
docs(federation): add strongly worded warning ( #1643 )
All checks were successful
pr / preview (pull_request_target) Successful in 2m19s
backport / backporting (pull_request_target) Has been skipped
ec4fb621b0
With some usable federation features now merged, I think it might be worth to add a warning for people who want to inevitably try it out. Maybe a point on federation in the FAQ could also be useful.
This should be backported to the v14 docs as well.
Reviewed-on: #1643
Reviewed-by: Lucas <sclu1034@noreply.codeberg.org>
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
Reviewed-by: Beowulf <beowulf@beocode.eu>
Co-authored-by: famfo <famfo@famfo.xyz>
Co-committed-by: famfo <famfo@famfo.xyz>
(cherry picked from commit 0e9dc1ead7)
Author
Collaborator
Copy link
Preview ready: https://forgejo.codeberg.page/@docs_pull_1674/
Member
Copy link

I wrote this initially, feels weird to approve the backport myself ^^'

I wrote this initially, feels weird to approve the backport myself ^^'

@famfo wrote in #1674 (comment):

I wrote this initially, feels weird to approve the backport myself ^^'

That's OK. You'd approve that the backport was successful and didn't mess up anything. So, no need to hesitate to approve.

@famfo wrote in https://codeberg.org/forgejo/docs/pulls/1674#issuecomment-9711170: > I wrote this initially, feels weird to approve the backport myself ^^' That's OK. You'd approve that the backport was successful and didn't mess up anything. So, no need to hesitate to approve.
Beowulf deleted branch bp-v14.0-0e9dc1e 2026年01月10日 17:16:58 +01:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
404

Broken links or missing content
backport/v1.19

Changes which should be backported to the v1.19 docs

Archived

backport/v1.20

Changes which should be backported to the v1.20 docs

Archived

backport/v1.21

Changes which should be backported to the v1.21 docs

Archived

backport/v10.0

Automated backport to v10.0

Archived

backport/v11.0

Automated backport to v11.0
backport/v12.0

Automated backport to v12.0

Archived

backport/v13.0

Automated backport to v13.0
backport/v14.0

Automated backport to v14.0
backport/v7.0

Automated backport to the v7.0 docs

Archived

backport/v8.0

Automated backport to the v8.0 docs

Archived

backport/v9.0

Automated backport to the v9.0 docs

Archived

good first issue

This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta

Tooling and processes for maintaining the docs
new docs

Content to be added to the documentation

Archived

User research - Accessibility

Requires input about accessibility features, likely involves user testing.
User research - Blocked

Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community

Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)

Instance-wide configuration, authentication and other admin-only needs.
User research - Errors

How to deal with errors in the application and write helpful error messages.
User research - Filters

How filter and search is being worked with.
User research - Future backlog

The issue might be inspiring for future design work.
User research - Git workflow

AGit, fork-based and new Git workflow, PR creation etc
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/Dashboard

Research on how users should know what to do next.
User research - Rendering

Text rendering, markup languages etc
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?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 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/docs!1674
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "bp-v14.0-0e9dc1e"

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?