32
41
Fork
You've already forked website
52

Updating Gitea-derived documentation #141

Closed
opened 2023年03月03日 21:59:16 +01:00 by Ryuno-Ki · 4 comments
Contributor
Copy link

Our documentation as it currently stands is based on Codeberg (CC BY-SA) and Gitea (Apache).

Especially for Gitea we would like to sync updates downstream if an update is released.

I have some parts where I see room for improvement but am not sure what the best way forward is.
Shall I try to get my changes merged into Gitea docs?
Open a PR against Forgejo's website?

Do we have to take something special into account regarding the Apache license picked by Gitea for their docs?

Our documentation as it currently stands is based on Codeberg (CC BY-SA) and Gitea (Apache). Especially for Gitea we would like to sync updates downstream if an update is released. I have some parts where I see room for improvement but am not sure what the best way forward is. Shall I try to get my changes merged into Gitea docs? Open a PR against Forgejo's website? Do we have to take something special into account regarding the Apache license picked by Gitea for their docs?

Do we have to take something special into account regarding the Apache license picked by Gitea for their docs?

I don't think so.

> Do we have to take something special into account regarding the Apache license picked by Gitea for their docs? I don't think so.

Shall I try to get my changes merged into Gitea docs?
Open a PR against Forgejo's website?

Since I do not have a GitHub account, I will keep opening PRs against Forgejo's website.

> Shall I try to get my changes merged into Gitea docs? > Open a PR against Forgejo's website? Since I do not have a GitHub account, I will keep opening PRs against Forgejo's website.
Author
Contributor
Copy link

Thanks.
That's already helpful.

I suggest then that we get back to this issue once the v1.19 release is out of the door. I assume that our changes should have stabilised by then and we can look into whether Gitea is interested in accepting changes we made.

Thanks. That's already helpful. I suggest then that we get back to this issue once the v1.19 release is out of the door. I assume that our changes should have stabilised by then and we can look into whether Gitea is interested in accepting changes we made.

I think that this issue got "solved" by the time passing.

I think that this issue got "solved" by the time passing.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/lock-file-maintenance
renovate/linters
renovate/hast-3.x
monthly-2026-05
mahlzahn-eslint-js
preview-link-status
nightfire
2022年12月14日-main
No results found.
Labels
Clear labels
404
Broken links or missing content
Accessibility
Accessibility
Blog post
Documentation
Forgejo Documentation
Internationalisation
i18n and l10n
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
3 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/website#141
Reference in a new issue
forgejo/website
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?