Should br merged on 25.12. 😉

Closes #354
Closes #356

@earl-warren wrote in #36 (comment):

Our new publish process works fine now, it's published a few seconds after the build job.

As codeberg is moving to https://codeberg.org/git-pages/git-pages/ (which is currently proving to be more stable than the current pages server), would it be an idea to have it moved to Codeberg pages? I could even fast track this for the forgejo.org domain as there's a usable git-pages server running on Codeberg's infra.

The sub-key was published and following instructions at https://forgejo.org/download/ shows it is available with the expected expiration date (June 2027).

yes, we need to stop publishing to uberspace as next step

For 2026:

forgejo/docs!1636 will fix that.

Membership

I propose to become part of the releases team.

1. If you agree, please simply add a 👍 to this issue.
2. If you disagree or have concerns, please write them in a comment below and I will do my best to address them.

This membership request follows the Forgejo decision making process (accepted after 2 weeks, unless concerns are raised).

Pledge

I pledge to act in accordance with the code of conduct, and all other rules and processes agreed via the Forgejo decision making process.

If there is an agreement for me to be a member of the team, I will consider renewing my membership a year later.

Background

I'm already in the devops, security and mergers teams and like to be a backup releaser if no other team member is available.

• forgejo/discussions#411 (comment)

Previous membership requests

No response

Thank you.

I created it via inkscape, lets license its as CC BY-SA 4.0

For the record, most of the work done by @viceice is on a Forgejo instance that is not public for security reasons. Issues and pull requests cannot be observed but https://codeberg.org/forgejo/k8s-cluster is a mirror where the infrastructure as code can be audited.

@viceice dedication to Forgejo is formidable and the k8s infrastructure would not exist without his daily work and expertise. It has proved extremely stable and reliable, even when hammered by excessive crawling involving 1,000,000 unique IPs daily: it flinched but did not break. The absence of any serious or endemic issues in Forgejo's infrastructure is easy to forget. But it does not happen magically. It is the outcome of significant efforts, in a large part thanks to @viceice

Membership

I propose to become part of the devops team.

1. If you agree, please simply add a 👍 to this issue.
2. If you disagree or have concerns, please write them in a comment below and I will do my best to address them.

This membership request follows the Forgejo decision making process (accepted after 2 weeks, unless concerns are raised).

Pledge

I pledge to act in accordance with the code of conduct, and all other rules and processes agreed via the Forgejo decision making process.

If there is an agreement for me to be a member of the team, I will consider renewing my membership a year later.

Background

I plan to continue to work on the Forgejo infrastructure. :hug

Previous membership requests

• December 2024: #199

It's not an octicon.

For the matrix room of https://codeberg.org/forgejo-contrib/forgejo-cli/

Lets close this, feel free to re-open if you find the time to pursue this further.

migrated to https://github.com/FortAwesome/Font-Awesome/discussions/20966

Thank you @0ko !

You are doing a great job 💯

@0ko Yes, I would like to resign due to personal time constraints. Thank you :)

@sclu1034 OK, then i'll self-close it for the moment until i complete proper RFC & decision process.