Yes, +1 for removal. Disqus is obsolete now. Let's get rid of it. I think just adding a link, even without the name of the blog post as title will suffice. With the name is also good off course.
Kind regards. Pieter Van Poyer software architect (A) DI/DA Haven van Antwerpen-Brugge/Port of Antwerp-Bruges Zaha Hadidplein 1, 2030 Antwerpen, België T +32 3 229 76 85 pieter.vanpo...@portofantwerpbruges.com http://www.portofantwerpbruges.com/ -----Oorspronkelijk bericht----- Van: Niklas Merz <niklasm...@apache.org> Verzonden: maandag 4 november 2024 8:17 Aan: dev@cordova.apache.org Onderwerp: Re: [DISCUSS] Keep or Remove Disqus from Blog If we don't want to change the workflow too much for now we could add a generated link to the bottom of every blog post something like this: "Questions or comments about this release? Please go to GitHub discussion" and then generate a link for a new discussion with the name of the blog post as the title. I just tried out that a link like this: <https://github.com/apache/cordova/discussions/new?category=general&title=test&body=Hello> pre-fills the fields on GitHub. Creating a discussion with the same markdown and linking to it would be an extra step of work. Or we can automate it somehow. But I wouldn't get rid of the blog with the full release information on the website. The blog is probably the go-to place for every ordinary users and is pretty accessible and nice to scroll through. On November 2, 2024, Norman Breau <nor...@breautek.com> wrote: > +1 for removal > > I think Disque is kind of out-dated, so I don't see much point in > putting in the effort of maintaining it, especially if it's broken. > We've started using Cordova Discussions for > > support, no reason why we can't also use it for announcements as well. > > Is there any particular apache policy that states that we must post a > blog on the website? I believe at minimum we need to post to the > mailing list, and everything else is extra. > > Currently our flow is write the blog markdown for the website, and > then post to the mailing list with the link to the blog. Perhaps we > should start writing markdown for github discussions instead, and have > a mailing list/blog post link to the github discussions. Or maybe the > same markdown can be used for both discussion post and the blog. Not > sure how much of this could be automated what the exact flow would > look like but just kinda throwing out some ideas for later. > > For the camera release I just made a discussions thread: > <https://git/ > hub.com%2Fapache%2Fcordova%2Fdiscussions%2F507&data=05%7C02%7CPieter.V > anPoyer%40portofantwerpbruges.com%7C33669caccf054c61a9bf08dcfca09ec9%7 > C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C638663014006501155%7CUnkno > wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=WyvvniomRdhGRTfotQeKMkN5qwGhfGp1OA8hzu2lvxU%3D&reserved=0> > but feels weird to post a link to the actual content, and if they want to > comment they'll need to come back to the GH page. > > On 2024-11-02 10:43 a.m., ke...@steerment.com wrote: > > Hey Team! > > > > If you did want to fix it, I'd be happy to monitor it (providing I > get notifications) and then prompt people to redirect bug reports to > GitHub. > > > > It'll show other devs thinking of using Cordova that the project is > still actively monitored and developed. > > > > Let me know! > > On 2 Nov 2024 at 09:37 +0000, Niklas Merz <niklasm...@apache.org>, > wrote: > >> I'm also in favor of removing Disqus because of the monitoring > issue. We > >> just cant keep track of those comments. > >> > >> Redirecting the users to Github discussion sounds like the best > >> approach. > >> > >> On November 2, 2024, Erisu <er...@apache.org> wrote: > >>> Our website used to display a Disqus commenting section at the > bottom > >>> of > >>> each blog post, allowing readers to leave comments. > >>> > >>> It appears that this feature stopped working about nine months ago > >>> (based on the date of the last comment). > >>> > >>> While inspecting the developer tools as the website loaded, I > noticed > >>> that > >>> two resource files were failing to load because they are missing > from > >>> the > >>> `frame-src` directive in the Content Security Policy. > >>> > >>> I wanted to raise the following questions: > >>> > >>> - Do we want to fix and continue supporting Disqus on our blog > posts? > >>> - Do we want to discontinue support and remove Disqus? > >>> - Has anyone actively monitored or reviewed the comments posted on > >>> Disqus while it was still functioning on the site? > >>> > >>> Personally, I am in favor of removing Disqus from the website. I > >>> haven't actively monitored blog comments to see what was being > >>> discussed. > Some > >>> users were raising issues and making requests in the comments, but > I > >>> believe these should be posted on our GitHub repositories. General > >>> discussions could also be moved to the Discussions tab of our > Cordova > >>> repo. > >>> > >>> There may be solutions for integrating GitHub Discussions into the > >>> blog posts as an alternative to Disqus, though this would require > >>> additional investigation. > >>> > >>> If we decide to keep Disqus, I'll update the Content Security > Policy > >>> to > >>> include the two missing resource files and proceed from there. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org ________________________________ Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van Haven van Antwerpen-Brugge NV van publiek recht en kunnen vertrouwelijke of persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te verspreiden of te ontsluiten naar derden. Haven van Antwerpen-Brugge NV van publiek recht is op geen enkele manier verantwoordelijk voor fouten of onnauwkeurigheden in de inhoud van deze e-mail. Haven van Antwerpen-Brugge NV van publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of fout in deze e-mail. English Translation: This e-mail and all attached files are official documents of Antwerp-Bruges Port Authority and may contain confidential or personal information. If you have received this e-mail in error, you are asked to inform the sender by e-mail or telephone immediately, and to remove it from your system without reading or reproducing it or passing it on to other parties. Antwerp-Bruges Port Authority is in no way responsible for any errors or inaccuracies in the contents of this e-mail, nor can it be held liable for any direct or indirect loss, damage or inconvenience arising from any such errors or inaccuracies. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
