forgejo/discussions
49
43

Forgejo monthly reports #9

Closed
opened 2023年03月03日 10:52:21 +01:00 by Ghost · 6 comments

When Forgejo was created, it was promised that reports would be published on a regular basis so that Codeberg can get a high level view of what is happening and decide during the general assembly if it is going in a direction that is compatible with Codeberg's mission.

The first two reports were published:

The February report is yet to be written and noone stepped up yet. How should the Forgejo community go about this?

When Forgejo was created, it was promised that reports would be published on a regular basis so that Codeberg can get a high level view of what is happening and decide during the general assembly if it is going in a direction that is compatible with Codeberg's mission. The first two reports were published: * February 2023 https://blog.dachary.org/2023/03/06/my-forgejo-monthly-update-february-2023/ * January 2023 https://forgejo.org/2023-01-31-monthly-update/ * December 2022 https://forgejo.org/2022-12-26-monthly-update/ The February report is yet to be written and noone stepped up yet. How should the Forgejo community go about this?

I was planning on writing the February report but it turns out to be too much work for me right now.

I was planning on [writing the February report](https://codeberg.org/forgejo/website/issues/86) but it turns out to be too much work for me right now.

I will write a February report on my blog instead, in the same style. It can then be used either as a first person substitute to the monthly report. Or copy/pasted to create a report that meets the agreement of the Forgejo community.

I will write a February report on my blog instead, in the same style. It can then be used either as a first person substitute to the monthly report. Or copy/pasted to create a report that meets the agreement of the Forgejo community.

https://blog.dachary.org/2023/03/06/my-forgejo-monthly-update-february-2023/ published and ready for copy/pasting if someone is willing to do what it takes to turn it into a blog post suitable for publication at https://forgejo.org

The corresponding markdown content is stored for convenience in a PR forgejo/website#150

https://blog.dachary.org/2023/03/06/my-forgejo-monthly-update-february-2023/ published and ready for copy/pasting if someone is willing to do what it takes to turn it into a blog post suitable for publication at https://forgejo.org The corresponding markdown content is stored for convenience in a PR https://codeberg.org/forgejo/website/pulls/150

The March 2023 report was published today https://forgejo.org/2023-03-monthly-update/

It started from what I intended to publish on my blog and was finalized about a week later. I decided not to publish on my blog as it would be redundant. I'll try something similar next month, i.e. propose a base content and inviting people to reuse the material.

The March 2023 report was published today https://forgejo.org/2023-03-monthly-update/ It started from what I intended to publish on my blog and was finalized about a week later. I decided not to publish on my blog as it would be redundant. I'll try something similar next month, i.e. propose a base content and inviting people to reuse the material.

The April 2023 report was published https://forgejo.org/2023-04-monthly-update/

There does not seem to be value in repeating this here is there?

The April 2023 report was published https://forgejo.org/2023-04-monthly-update/ There does not seem to be value in repeating this here is there?

Closing this as I assume the discussion is completed and a new discussion will be open if something new comes up. Feel free to re-open if you want this to continue.

Closing this as I assume the discussion is completed and a new discussion will be open if something new comes up. Feel free to re-open if you want this to continue.
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
2 participants
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#9
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?