Re: New website design: help needed
"Yury V. Zaytsev via mc-devel" <mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org> Wed, 12 Mar 2025 08:49:48 +0100
| Newsgroups | gmane.comp.gnome.apps.mc.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============6069904729420708003== Content-Type: multipart/alternative; boundary="Apple-Mail=_1AD74246-DB6E-4EA0-B535-171B243FC53B" --Apple-Mail=_1AD74246-DB6E-4EA0-B535-171B243FC53B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Sergey, Thanks for the feedback! We haven't decided yet how to collect NEWS entries for the next release. = My suggestion right now is to use GitHub's wiki, and specifically the = page you found. I've tried using a draft release for this, but it's just too painful and = dangerous. In my opinion, the default button should be "save", and it = shouldn't be possible to accidentally click "publish" without any = confirmation. During my experiments, I ended up accidentally "releasing" = mc-4.8.34 and creating a tag by simply hitting Enter on the tag field. = Using the wiki seems no different than our current process, so this = appears to be acceptable. I'm also not sure if we will be using releases in the future. We already = have a NEWS file in the repository that is updated with every release. = If I have to create the GitHub releases in addition to updating the NEWS = file, that's extra manual work for me every release (for seemingly = little benefit). In addition, releases have several other problems: * Drafts are private, so you can't see work in progress https://github.com/orgs/community/discussions/4192 * The links to git export archives without build systems cannot be = suppressed https://github.com/orgs/community/discussions/6003 * I have created a new discussion for the =E2=80=9Cdanger=E2=80=9D = aspect of it: https://github.com/orgs/community/discussions/153766 I don't think any of these will be addressed anytime soon. Right now I have a badge for the latest tag, and the good thing is that = the tag name is automatically detected, so I don't have to update the = website all the time. What more exactly do you want? A link to the NEWS entry for the = currently released version? A link to the NEWS entry for the development = version? Or both? Do you have a specific suggestion to solve your = problem? All the best, Yury > On 11. Mar 2025, at 16:17, Sergey Naumov <[email protected]> wrote: >=20 > Hello, Yury. >=20 > My favorite page on the current website is "What's new". >=20 > I can't find the corresponding page, item or link in the proposed = variant. >=20 > I started to search, tried to find releases on GitHub, but there are = only tags, and only then I found news on GitHub wiki, and there is page = only for upcoming release. >=20 > These "What's new" summaries were very convenient, and it would be = good to make them easily accessible in the new version of the site. >=20 > Thanks, > Sergey. >=20 --Apple-Mail=_1AD74246-DB6E-4EA0-B535-171B243FC53B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"content-type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Hi = Sergey,</div><div><br></div><div>Thanks for the = feedback!</div><div><br></div><div>We haven't decided yet how to collect = NEWS entries for the next release. My suggestion right now is to use = GitHub's wiki, and specifically the page you = found.</div><div><br></div><div>I've tried using a draft release for = this, but it's just too painful and dangerous. In my opinion, the = default button should be "save", and it shouldn't be possible to = accidentally click "publish" without any confirmation. During my = experiments, I ended up accidentally "releasing" mc-4.8.34 and creating = a tag by simply hitting Enter on the tag field. Using the wiki seems no = different than our current process, so this appears to be = acceptable.</div><div><br></div><div>I'm also not sure if we will be = using releases in the future. We already have a NEWS file in the = repository that is updated with every release. If I have to create the = GitHub releases in addition to updating the NEWS file, that's extra = manual work for me every release (for seemingly little benefit). In = addition, releases have several other = problems:</div><div><br></div><div>* Drafts are private, so you can't = see work in progress</div><div><br></div><div><a = href=3D"https://github.com/orgs/community/discussions/4192">https://github= .com/orgs/community/discussions/4192</a></div><div><br></div><div>* The = links to git export archives without build systems cannot be = suppressed</div><div><br></div><div><a = href=3D"https://github.com/orgs/community/discussions/6003">https://github= .com/orgs/community/discussions/6003</a></div><div><br></div><div>* I = have created a new discussion for the =E2=80=9Cdanger=E2=80=9D aspect of = it:</div><div><br></div><div><a = href=3D"https://github.com/orgs/community/discussions/153766">https://gith= ub.com/orgs/community/discussions/153766</a></div><div><br></div><div><div= >I don't think any of these will be addressed anytime = soon.</div><div><br></div><div>Right now I have a badge for the latest = tag, and the good thing is that the tag name is automatically detected, = so I don't have to update the website all the = time.</div><div><br></div><div>What more exactly do you want? A link to = the NEWS entry for the currently released version? A link to the NEWS = entry for the development version? Or both? Do you have a specific = suggestion to solve your problem?</div></div><div><br></div><div><font = color=3D"#000000"><span style=3D"caret-color: rgb(0, 0, 0);">All the = best,</span></font></div><div><font color=3D"#000000"><span = style=3D"caret-color: rgb(0, 0, 0);">Yury<br = id=3D"lineBreakAtBeginningOfMessage"></span></font><div><br><blockquote = type=3D"cite"><div>On 11. Mar 2025, at 16:17, Sergey Naumov = <[email protected]> wrote:</div><br = class=3D"Apple-interchange-newline"><div><p dir=3D"ltr">Hello, Yury. = </p><p dir=3D"ltr">My favorite page on the current website is "What's = new".</p><p dir=3D"ltr">I can't find the corresponding page, item or = link in the proposed variant.</p><p dir=3D"ltr">I started to search, = tried to find releases on GitHub, but there are only tags, and only then = I found news on GitHub wiki, and there is page only for upcoming = release. </p><p dir=3D"ltr">These "What's new" summaries were very = convenient, and it would be good to make them easily accessible in the = new version of the site.</p><p dir=3D"ltr">Thanks,<br> Sergey.</p> </div></blockquote></div><br></div></body></html>= --Apple-Mail=_1AD74246-DB6E-4EA0-B535-171B243FC53B-- --===============6069904729420708003== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- mc-devel mailing list mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org https://lists.midnight-commander.org/mailman/listinfo/mc-devel --===============6069904729420708003==--