On Tue, 28 Apr 2015 09:30:35 +0200 Miroslav Suchy msuchy@redhat.com wrote:

On 04/28/2015 01:38 AM, Martin Cigorraga wrote:

...

1. Copr needs a place where users and packager(s) can discuss stuff

about the packages and repositories, that could be achieved by simply letting logged people to comment on each Copr repo page;

Hmm this can be easily done by embedded disqus.com. Ideally users will manage their own discussion. So we should as for 'disqus_shortname' variable and if provided then we can embedded the disqus JS snippet.

I'm not sure I like the idea of us depending on/suggesting/using a non free service like that. ;(

Perhaps we could do something later this year with hyperkitty and a copr-discuss list?

kevin

Dne 29.4.2015 v 06:14 Martin Cigorraga napsal(a):

Hello Miroslav, Kevin,

What type of free licences are we looking for, GPL? Affero GPL? MIT? BSD? Apache? Any F/LOSS-compatible licence? I've found three alternatives for you to examine: Isso, hosted on https://github.com/posativ/isso with a last commit about four months ago, markets itself as a free-as-in-freedom Disqus alternative. Isso is licensed under MIT Licence. HashOver: http://tildehash.com/. As Isso its author markets it as a Disqus replacement as well with this strong but meaningful words: "Say goodbye to Disqusting third-party...". HashOver is licensed under GNU Affero GPL Licence. Last but no least we have Vanilla: http://vanillaforums.org/ This is without doubt the most mature product of the list albeit it might be a little overkill for what we are looking for; also it's worth noting this software was first conceived as a forum engine more than a 'social' comment system so most of its super powers are aimed to that end. They offer both a cloud-hosted setup as well a ready-to-download self-hosted version. While they claim this is OSS I couldn't find anywhere under what licence it is granted for use.

I revisited this topic and tried all referenced webs (thanks for that).

Most of them are either provided as code you can install and *maintain* yourself. This is something I would like to avoid. Or it is paid (Discourse). Are we willing to pay for such service?

Ask and Mailman3 does not fit our needs IMO. I do not want (and I suppose others as well) discussion about Copr projects in general (those who want that are already on this mailing list). I want discussion platform for every single project on Copr. And creating mailing list for every projects is probably over-kill.

So unless someone is volunteering to maintain Isso or Hashover instance, I see only viable option either paid plan of Discourse or free (as a beer) but not free (as libre) Disqus. Or nothing.

Dne 16.6.2015 v 14:12 Kevin Fenzi napsal(a):

IMHO, a way to just mail the owner(s) of a copr would be enough. If there needs to be a discussion between the owners and interested folks, they can always take that discussion to whatever medium they like.

I could not expose <fas>@fedorapeople.org as this alias exist only if you are at least one group. Which does not need to be true for all Copr users. I can get user regular email from FAS [citation needed], but I'm not sure if users would be happy if I just quote their email on public page. It may lead to increase of SPAM in their inbox.

Copr is a bit of a odd case as it's in our Cloud and not Fedora Infrastructure proper, but our policy at: https://fedoraproject.org/wiki/Infrastructure_Licensing Notes that all our software is Free Software, so I really think using a non free service isn't an option here.

This apply to code we wrote or which we are hosting. However what I would like to use is Software as a Service (SaaS). Neither hosting nor coding on our side. Just to put few lines of HTML there referencing some 3rd party JS and that's all. I would hesitate to do that for mission critical data, but the discussion is completely unimportant. If it disappear one day and we will not have the data, nothing really happen. This is reason why I'm still thinking about Disqus, which fit our needs best.

Mirek

On 04/28/2015 09:30 AM, Miroslav Suchy wrote:

On 04/28/2015 01:38 AM, Martin Cigorraga wrote:

...

1. Copr needs a place where users and packager(s) can discuss stuff

about the packages and repositories, that could be achieved by simply letting logged people to comment on each Copr repo page;

Hmm this can be easily done by embedded disqus.com. Ideally users will manage their own discussion. So we should as for 'disqus_shortname' variable and if provided then we can embedded the disqus JS snippet.

Mirek _______________________________________________ copr-devel mailing list copr-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/copr-devel

It's yet another service .. how about using a Copr tag on https://ask.fedoraproject.org ?

R

On Wed, 29 Apr 2015 12:28:08 -0300 Martin Cigorraga martincigorraga@gmail.com wrote:

On Wed, Apr 29, 2015 at 5:03 AM, Radek Vokál rvokal@redhat.com wrote:

...

It's yet another service .. how about using a Copr tag on https://ask.fedoraproject.org ?

R

+1

Hello Radek, guys,

I can see your point trying to stay away as much as possible from bloatedness and keeping the code as minimal and maintainable as it could be, a Golden goal, if you wish.

While it is true that a comment section built-in in Copr would feel more 'natural', it is no less true that a properly tagged question on Ask Fedora already solves the burden of implementing a new solution.

My question is: how feasible could it be to add a function to Copr that automatically reads each repository information (may be on page load) and automatically generates a link that points to an Ask Fedora question already tagged with the name of the repo and the maintainer? That way it would be like hitting the jackpot:

1. We can use a very useful solution that's already up, working and

proven; 2. Discussions and development would be automatically accessible for everyone using Ask Fedora; 3. All the information would be kept in a central hub instead being scattered through different places.

Well, I am not sure ask is a good fit here (at least that way).

ask is setup for questions and answers, not general discussion. I suppose with a tag per coper we could group the questions, but I am afraid they might be too scattered and non question like. ;(

Theres not really a way to make a tag without making a question for it, and adding questions that aren't questions like "Copr XYZ" won't really be good.

I wonder if it might be better to do two things:

1. Add a 'mail people who have acls to this copr' button. This would allow people to send feedback like 'please update' or 'this is great thanks' to the people responsible.

2. Point people to a 'copr-discuss' list. (which hopefully we could make with hyperkitty). This could be used for any higher level discussions about things.

kevin