32
41
Fork
You've already forked website
52

WIP: Create 'forgejo-should-adopt-semver' article #52

Closed
KaKi87 wants to merge 4 commits from KaKi87/forgejo-website:semver into main
pull from: KaKi87/forgejo-website:semver
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
Member
Copy link
No description provided.
KaKi87 changed title from (削除) WIP: semver (削除ここまで) to WIP: Create 'forgejo-should-adopt-semver' article 2023年01月09日 17:16:08 +01:00
Author
Member
Copy link

@dachary

Maybe with a paragraph of introduction as a reminder of what semver is and why it matters?

Doesn't line 10 adress this ?

As a Go developer I would be motivated to take action if it points to a detailed action plan that I can work on immediately, without worrying too much about the context. Linking to forgejo/forgejo#212 would maybe do that.

Done !

@dachary > Maybe with a paragraph of introduction as a reminder of what semver is and why it matters? Doesn't line 10 adress this ? > As a Go developer I would be motivated to take action if it points to a detailed action plan that I can work on immediately, without worrying too much about the context. Linking to https://codeberg.org/forgejo/forgejo/issues/212 would maybe do that. Done !

@dachary

Maybe with a paragraph of introduction as a reminder of what semver is and why it matters?

Doesn't line 10 address this ?

Disclaimer: I'm first and foremost a developer and my advice when it comes to writing content are to be taken with a grain of salt.

That being said 😇 ... I'm under the impression that the first paragraph is the most important because that's essentially the only thing most people who are intrigued by the title will read. Hence my suggestion.

> @dachary > > > Maybe with a paragraph of introduction as a reminder of what semver is and why it matters? > > Doesn't line 10 address this ? Disclaimer: I'm first and foremost a developer and my advice when it comes to writing content are to be taken with a grain of salt. That being said 😇 ... I'm under the impression that the first paragraph is the most important because that's essentially the only thing most people who are intrigued by the title will read. Hence my suggestion.
Author
Member
Copy link

I'm first and foremost a developer and my advice when it comes to writing content are to be taken with a grain of salt

Well, same for me. 😅

the first paragraph is the most important because that's essentially the only thing most people who are intrigued by the title will read

I just swapped the first paragraphs, what do you think ?

> I'm first and foremost a developer and my advice when it comes to writing content are to be taken with a grain of salt Well, same for me. 😅 > the first paragraph is the most important because that's essentially the only thing most people who are intrigued by the title will read I just swapped the first paragraphs, what do you think ?

Do you think it will appeal to the reader? You had me convinced in the chat, there are maybe elements to get from that discussion and into the blog post?

Do you think it will appeal to the reader? You had me convinced in the chat, there are maybe elements to get from that discussion and into the blog post?
Member
Copy link

I think this needs some kind of an introduction explaining what it's all about and making it clear why it's on the blog (eg is public opinion being solicited? Or is this useful /actionable information for users?), as at present tbh it reads more like an issue from the issue tracker. A simple introduction before launching into the technical details would help a lot I think (if this does belong on the blog).

I think this needs some kind of an introduction explaining what it's all about and making it clear why it's on the blog (eg is public opinion being solicited? Or is this useful /actionable information for users?), as at present tbh it reads more like an issue from the issue tracker. A simple introduction before launching into the technical details would help a lot I think (if this does belong on the blog).
Author
Member
Copy link

A blog post is published to draw attention to why and how SemVer should be adopted by Forgejo

Source

> A blog post is published to draw attention to why and how SemVer should be adopted by Forgejo [Source](https://codeberg.org/forgejo/forgejo/issues/207#issuecomment-759958)
Author
Member
Copy link

You had me convinced in the chat

Here's pretty much all I said about it.


> You had me convinced in the chat Here's pretty much all I said about it. ![](https://codeberg.org/attachments/5cd4003d-8fbb-4013-8b83-c5ef61359fe5) ![](https://codeberg.org/attachments/0d6767ba-4d3a-4a87-8301-eaa857a84031)

This article is difficult to write for both you and me. Since there now is active development going on towards SemVer, do you feel it is still necessary to make it happen?

This article is difficult to write for both you and me. Since there now is active development going on towards SemVer, do you feel it is still necessary to make it happen?
Author
Member
Copy link

Maybe not, indeed. Shall I close this ?

Maybe not, indeed. Shall I close this ?

I think yes. And it can be re-opened later if needed.

I think yes. And it can be re-opened later if needed.
KaKi87 closed this pull request 2023年01月21日 22:09:01 +01:00

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
3 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!52
Reference in a new issue
forgejo/website
No description provided.
Delete branch "KaKi87/forgejo-website:semver"

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?