32
41
Fork
You've already forked website
52

Iterate on draft blog post (monthly update feb 2023) #175

Closed
Ryuno-Ki wants to merge 9 commits from Ryuno-Ki/forgejo-website:wip-2023-02-blog-take-2 into main
pull from: Ryuno-Ki/forgejo-website:wip-2023-02-blog-take-2
merge into: forgejo:main
forgejo:main
forgejo:monthly-2026-05
forgejo:mahlzahn-eslint-js
forgejo:preview-link-status
forgejo:nightfire
forgejo:2022年12月14日-main
Contributor
Copy link

Subsedes #150

Relates to #86

Subsedes https://codeberg.org/forgejo/website/pulls/150 Relates to https://codeberg.org/forgejo/website/issues/86
monthly update february 2023
All checks were successful
forgejo-ci/pr/woodpecker Pipeline was successful
d136e1bffd
Ryuno-Ki force-pushed wip-2023-02-blog-take-2 from 67d8a4244e
Some checks failed
forgejo-ci/pr/woodpecker Pipeline failed
to d131155c0a
All checks were successful
forgejo-ci/pr/woodpecker Pipeline was successful
2023年03月09日 18:37:18 +01:00
Compare
Collaborator
Copy link
Preview ready: https://forgejo.codeberg.page/@pull_175/
Author
Contributor
Copy link
See https://forgejo.codeberg.page/@pull_175/2023-03-09-monthly-update/
Ghost requested changes 2023年03月09日 19:18:09 +01:00
Dismissed
Ghost left a comment
Copy link

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.

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.
Author
Contributor
Copy link

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.

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.
First-time contributor
Copy link

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.

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.
Ryuno-Ki marked this conversation as resolved
@ -0,0 +208,4 @@
internationalization or maintainability in general, we will welcome you with
open arms.
### Privacy headers
Author
Contributor
Copy link

Done.

Done.
Ryuno-Ki marked this conversation as resolved
@ -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.
Author
Contributor
Copy link

I was referring to forgejo/meta#159

I was referring to https://codeberg.org/forgejo/meta/pulls/159
Author
Contributor
Copy link

So . we need an issue for that to legitimise it?
I'm still not up-to-date with our processes :(

So . we need an issue for that to legitimise it? I'm still not up-to-date with our processes :(
Ryuno-Ki marked this conversation as resolved
@ -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.
Author
Contributor
Copy link

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.

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.
Author
Contributor
Copy link

Rephrased.

Rephrased.
Author
Contributor
Copy link

I'd like to have another pair on eyes on this.
No offense, but I feel like you are to emotionally involved in this.

I'd like to have another pair on eyes on this. No offense, but I feel like you are to emotionally involved in this.
Author
Contributor
Copy link

(redacted)

(redacted)
Author
Contributor
Copy link

this message was redacted by the moderation team, if you would like to know more please write to moderation@forgejo.org

this message was redacted by the moderation team, if you would like to know more please write to moderation@forgejo.org
Author
Contributor
Copy link

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.

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
Author
Contributor
Copy link

Right. The update happened on March 1st.
Off-by-one.

https://github.com/awesome-selfhosted/awesome-selfhosted/pull/3467

Right. The update happened on March 1st. Off-by-one. https://github.com/awesome-selfhosted/awesome-selfhosted/pull/3467
Author
Contributor
Copy link

Removed.

Removed.
Ryuno-Ki marked this conversation as resolved
@ -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?
Author
Contributor
Copy link

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.

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.
Author
Contributor
Copy link

@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!

@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!
Author
Contributor
Copy link

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.

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.
Ryuno-Ki marked this conversation as resolved
Ghost requested changes 2023年03月10日 12:10:38 +01:00
Dismissed
Ghost left a comment
Copy link

Two more details and it is good to go.

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.

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.
Author
Contributor
Copy link

Pfft, details 😹

Fixed.

Pfft, details 😹 Fixed.
Ryuno-Ki marked this conversation as resolved
earl-warren requested changes 2023年03月10日 14:55:39 +01:00
Dismissed
earl-warren left a comment
Copy link

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 💙

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 💙
Author
Contributor
Copy link

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.

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.
Ryuno-Ki force-pushed wip-2023-02-blog-take-2 from 97c359769e
All checks were successful
forgejo-ci/pr/woodpecker Pipeline was successful
to a8eb15e0ce
All checks were successful
forgejo-ci/pr/woodpecker Pipeline was successful
2023年03月10日 20:16:29 +01:00
Compare
Ghost requested changes 2023年03月10日 23:57:36 +01:00
Dismissed
Ghost left a comment
Copy link

I approve the content. It needs to be agreed upon by more people before it is published.

I approve the content. It needs to be agreed upon by more people before it is published.
Author
Contributor
Copy link
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
earl-warren dismissed earl-warren's review 2023年03月12日 11:34:19 +01:00
Author
Contributor
Copy link

What's needed to move this PR forward?

What's needed to move this PR forward?
Author
Contributor
Copy link

March has passed. I don't see a point in keeping this PR open any longer.

March has passed. I don't see a point in keeping this PR open any longer.
Ryuno-Ki closed this pull request 2023年04月03日 12:55:49 +02:00
Some checks are pending
forgejo-ci/pr/woodpecker Pipeline was successful
pr / preview (pull_request)
Required

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No reviewers
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
5 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!175
Reference in a new issue
forgejo/website
No description provided.
Delete branch "Ryuno-Ki/forgejo-website:wip-2023-02-blog-take-2"

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?