+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://github.com/apache/cordova/discussions/507 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
