WIP: Create 'forgejo-should-adopt-semver' article #52
KaKi87/forgejo-website:semver into main
@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 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.
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?
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).
A blog post is published to draw attention to why and how SemVer should be adopted by Forgejo
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?
Maybe not, indeed. Shall I close this ?
I think yes. And it can be re-opened later if needed.
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?