forgejo/discussions
50
43

Domain name organizational structure #1

Open
opened 2023年03月02日 10:11:57 +01:00 by Ghost · 0 comments

Followup of forgejo/meta#41


Followup of the domain name registration.

This could be documented in https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING.md which is, for now, the source of truth, in the same way it is for Gitea.

  • The co195585-ovh account is in the name of Codeberg e.V. which ultimately controls the doains in case of a dispute
  • The secret keepers (for lack of a better name) have access to the OVH registrar account co195585-ovh where all domains are grouped
  • The renewal of domains is the responsibility of the "secret keepers".
  • The email of co195585-ovh forwards to the "secret keepers" and at least one Codeberg e.V. representative
Followup of https://codeberg.org/forgejo/meta/issues/41 --- Followup of the [domain name registration](https://codeberg.org/forgejo/meta/issues/35#issuecomment-691380). This could be documented in https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING.md which is, for now, the source of truth, in the same way it is for Gitea. * The co195585-ovh account is in the name of Codeberg e.V. which ultimately controls the doains in case of a dispute * The [secret keepers](https://codeberg.org/org/Forgejo/teams/owners) (for lack of a better name) have access to the OVH registrar account co195585-ovh where all domains are grouped * The renewal of domains is the responsibility of the "secret keepers". * The email of co195585-ovh forwards to the "secret keepers" and at least one Codeberg e.V. representative
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
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
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/discussions#1
Reference in a new issue
forgejo/discussions
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?