November 17th update #97

Merged
Ghost merged 1 commit from :main into main 2022-11-18 00:33:20 +01:00
No description provided.
Signed-off-by: Loïc Dachary <loic@dachary.org>
@ -11,1 +11,4 @@
### November 17th
Preparations are made to publish Forgejo 1.18.0-rc1 as soon as Gitea 1.18.0-rc1 is released. A security team is discussed to cover both Forgejo and Codeberg. The Forgejo domain name (forgejo.org) is in the name of Codeberg e.V. at the registrar. A grant application is drafted to support Forgejo.

s/is in/is registered in/

`s/is in/is registered in/`
Collaborator

A security team is discussed to cover both Forgejo and Codeberg.

We're considering to build up a security team for both, Forgejo and Codeberg.

?

> A security team is discussed to cover both Forgejo and Codeberg. We're considering to build up a security team for both, Forgejo and Codeberg. ?

It was registered in the name of oliverpool but is now in the name of Codeberg, reason why I chose to write "is in" because it was, afterwards, moved to an account in the name of Codeberg in the OVH registrar. Maybe there is a better choice of words that reflect the reality, is simple enough and does not raise an eyebrow. 🤔

It was registered in the name of oliverpool but is now in the name of Codeberg, reason why I chose to write "is in" because it was, afterwards, moved to an account in the name of Codeberg in the OVH registrar. Maybe there is a better choice of words that reflect the reality, is simple enough and does not raise an eyebrow. 🤔
@Ryuno-Ki see https://codeberg.org/forgejo/meta/issues/37
First-time contributor

@dachary: I read the comment by @Ryuno-Ki as to @Ryuno-Ki proposed a different wording for the sentence. Maybe @Ryuno-Ki can clarify whether this was actually a question or a rephrase-proposal.

@dachary: I read the comment by @Ryuno-Ki as to @Ryuno-Ki proposed a different wording for the sentence. Maybe @Ryuno-Ki can clarify whether this was actually a question or a rephrase-proposal.
Collaborator

The upper line was the current version, the line below my proposal, yes.

The upper line was the current version, the line below my proposal, yes.

Thanks for the clarification, I thought it was a question! Sorry for the misunderstanding.

Thanks for the clarification, I thought it was a question! Sorry for the misunderstanding.

@Ryuno-Ki the updates are in the third person and never using "we" or "our" etc. My English is not excellent and I would appreciate if you could reword "We're considering to build up a security team for both, Forgejo and Codeberg." accordingly. I must confess that I find it difficult 😅

@Ryuno-Ki the updates are in the third person and never using "we" or "our" etc. My English is not excellent and I would appreciate if you could reword "We're considering to build up a security team for both, Forgejo and Codeberg." accordingly. I must confess that I find it difficult 😅

For the sake of keeping the updates up to date I'm going to merge this. I'll update if needed.

For the sake of keeping the updates up to date I'm going to merge this. I'll update if needed.
Ghost merged commit 1eafa3512d into main 2022-11-18 00:33:20 +01:00
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
4 participants
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/gitea-open-letter!97
No description provided.