I am one of the developers of Copr. I would love to integrate Copr with discussion.f.o. What can I do for it?
I would probably like to have a category named “Copr projects” and have a topic for each project (we have 9k projects) and have it embedded on each copr project page. Is it feasible?
I created the Copr category with a description and gave you moderator rights for Discourse - it would certainly be doable to create a topic for each project. It seems a lot but it’s just 9000 rows in a database so it should be fine.
So I am a bit concerned that it just overload the main index page. Is there a way to have a more balanced view, or just hide copr from that ?
Cause if suddenly, there is 9000 topics, there will likely be lots of discussions. My screen show 12 lines. So if each copr topic receive a message every 2 years (cause 12 * 365 * 2 => 8760 messages, so kinda 9000), the main page would show 12 discussions on copr, and any discussion older than 1 day would be pushed down.
And 1 message every 2 years is not that much traffic per package, and so that’s not exactly great IMHO.
Hello, is it possible for a user to reply directly on a page where discourse is loaded in the embedded mode? We would like this option very much in our Copr projects. See e.g. here: https://copr-fe-dev.cloud.fedoraproject.org/coprs/g/mock/mock/. Needing to jump back and forth to comment wouldn’t be very pleasant experience for our users.
@sanja: thank you for looking at it. This is quite important feature for us. This discussion forum here is a fine thing but we would like our users to stay on Copr site when they encounter some interesting project and they would like to comment.
@msuchy@clime Shall we consider this not working for the COPR purpose then?
Embed Discourse comments on another website via Javascript - admins - Discourse Meta says that “One important thing to note with this setup is that users have to navigate to your forum to post replies . This is intentional, as we feel that the posting interface on a Discourse forum is currently much richer than what we could embed via Javascript.” - that’s a shame but not something we can currently change (not easily or quickly anyway).
On our team meeting, we did not come to 100% conclusion that we want it. So we are going postpone the work on this. @sanja you can revoke my and @frostyx admin rights. We may revisit this later.