Iterate on draft blog post (monthly update feb 2023) #175
Ryuno-Ki/forgejo-website:wip-2023-02-blog-take-2 into main
67d8a4244e
d131155c0a
Preview ready: https://forgejo.codeberg.page/@pull_175/
A few minor changes, otherwise looks good. It is great that you're willing to work on that.
The most difficult part is ahead: getting an agreement so it can be published. It is very different from publishing a technical documentation because it is written in the name of the entire Forgejo community. And as such must be agreed upon. I don't think there is a need to go through the decision making process. But there definitely is a need to make sure the majority of Forgejo contributors who participated in February had a chance to review and express their concerns.
@ -0,0 +176,4 @@
Each headline now shows a `#` that you can use to link deep into your favourite
part of our website. We took special care to mark up these links to be friendly
to our pals that use assistive technology. They belong into tech as well.
Hm, I change it to „ally" now. That term is used in the inclusive community (CC @fsologureng). Usually for people with privileges that side with minority groups.
I'm open for suggestions.
I would use: We have taken special care to make these links accessible".
I am not comfortable using "ally" because it is not what I would expect from all readers of this website. The readership is usually larger than those involved in the development or use of the software.
@ -0,0 +208,4 @@
internationalization or maintainability in general, we will welcome you with
open arms.
### Privacy headers
Done.
@ -0,0 +253,4 @@
process and communicating properly when a problem happens is what
Forgejo users expect and deserve.
A new FreeBSD team was established and our social account team extended.
I was referring to forgejo/meta#159
So . we need an issue for that to legitimise it?
I'm still not up-to-date with our processes :(
@ -0,0 +278,4 @@
aggressive comments disrupting communications and creating tensions. It
went on during weeks and the interim moderation team was not prepared
to handle the challenge. In fact, at this point the moderation team is
effectively disbanded. We hope to reestablish it as soon as possible.
I see what you mean. My idea was that a disbanded moderation team could be interpreted at no moderation happening at all. And that the Forgejo community would be fine with it. That's not what should come across.
Rephrased.
I'd like to have another pair on eyes on this.
No offense, but I feel like you are to emotionally involved in this.
(redacted)
this message was redacted by the moderation team, if you would like to know more please write to moderation@forgejo.org
I thought long and hard about what to do here.
As you can guess, there were additional comments in between. The respective authors have chosen to delete them. I will respect their decision.
That being said, I value the conversation here as a public record. Therefore I am not going to update mine. I also encourage you to look at the commits to understand how the section in question developed over time.
@ -0,0 +294,4 @@
safe space and organize moderation to efficiently and quickly put an
end to the most toxic behaviors.
### Awesome Selfhosted candidate
Right. The update happened on March 1st.
Off-by-one.
https://github.com/awesome-selfhosted/awesome-selfhosted/pull/3467
Removed.
@ -0,0 +304,4 @@
This way, even more people can learn about what we are building here together.
Thank you for that! Keep it going.
## What's next?
I see what you mean.
My intention to have some kind of „conclusion" as I am used to it in a blog post format.
As such I was hoping to not end on a bad note.
Then the grants are not finalised (except yours for F3 MoU in March). So it has a future aspect to it.
@crystal and @earl-warren I pushed an update here on this section.
Would like to get your opinion on whether I got the details right.
Remember that I want to refer to the state of February.
Thanks in advance!
I did not mention it (since it didn't show up in our funding/sustainability repo).
But that's the first accepted grant of this year that I'm aware of.
Two more details and it is good to go.
@ -0,0 +297,4 @@
## On grant applications
Our applications on NLnet grants to fund the work on Forgejo are progressing.
s/Our/The/
"Our grant" mean that, in the future, the Forgejo community will be held accountable for how the grant was executed. But the beneficiaries of each grant application are specific groups of individuals / organizations. Forgejo, as a community (us, our) is not a beneficiary of these grants, has no control over them or their implementation.
There is one grant application for which you are the beneficiary and you alone decide what it is and how it relates to Forgejo. There is another grant application for which beneficiaries are yet to be determined, probably @crystal and @earl-warren. I wrote it, sent the application and passed the first hurdle, but I'm not a beneficiary.
Pfft, details 😹
Fixed.
LGTM without the addition of "In fact, at this point the moderation team is
effectively disbanded. We hope to reestablish it as soon as possible.". It will make it easier
to get approval from the wider Forgejo community.
Thanks for taking the time to work on this: very useful, very time consuming 💙
Picked up the feedback from @earl-warren and @fsologureng. Thanks!
If this PR passes the review I kindly ask someone else to hit the merge button.
There are personal events I need to attend to and I will only get back earliest Tuesday next week.
97c359769e
a8eb15e0ce
I approve the content. It needs to be agreed upon by more people before it is published.
I asked all of them in the Development channel: https://matrix.to/#/!zpNKWqkiEOyljSMQDK:matrix.org/$crIGAcTjru0mo5Y02s13L1wwo6-eo60NFSc9mHnvRA8?via=matrix.org&via=aria-net.org&via=kle.li
What's needed to move this PR forward?
March has passed. I don't see a point in keeping this PR open any longer.
Pull request closed
No due date set.
No dependencies set.
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?