The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #3696

High Level Feature #15401: Ratings, Download counts, watching and other features for determining module popularity.

Site should allow logged-in users to comment on a module

Added by Igal Koshevoy almost 4 years ago. Updated 4 months ago.

Status:AcceptedStart date:04/28/2010
Priority:NormalDue date:
Assignee:Ryan Coleman% Done:

0%

Category:webSpent time:-
Target version:-
Keywords: Affected URL:
Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket is now tracked at: https://tickets.puppetlabs.com/browse/FORGE-4


Description

We want users to be able to leave comments on individual modules, such as “this module eats babies, don’t use it” or “to do this on solaris, set the foosball to 12 and move the lever”.

The site should display these comment on the module page.

When leaving a comment, the user should be able to optionally indicate what release of the module they’re referring to using a drop-down selector of releases.

A site admin or the person that posted a comment should be able to delete the comment.

The module owner should have some way to see these comments, either as a feed or via emails.


Related issues

Related to Puppet Forge - Feature #3697: Site users should be able to subscribe to comments Needs Decision 04/28/2010

History

#1 Updated by Igal Koshevoy almost 4 years ago

  • Status changed from Unreviewed to Accepted

#2 Updated by Igal Koshevoy almost 4 years ago

  • Target version set to 54

#3 Updated by Igal Koshevoy over 3 years ago

  • Assignee deleted (Igal Koshevoy)

#4 Updated by Anonymous over 3 years ago

  • Target version changed from 54 to 79

#5 Updated by Daniel Pittman about 2 years ago

  • Target version deleted (79)

#6 Updated by Ryan Coleman almost 2 years ago

  • Status changed from Accepted to Needs Decision
  • Assignee set to Ryan Coleman
  • Priority changed from High to Low
  • Parent task set to #15401

#7 Updated by Lee Lowder over 1 year ago

As someone who has, until recently, given up on the forge completely, I really, really want to see this sort of functionality. It’d be a huge help and IMO, would make the forge a lot more usable and admin-friendly.

#8 Updated by Ryan Coleman over 1 year ago

  • Status changed from Needs Decision to Accepted
  • Priority changed from Low to Normal

Lee Lowder wrote:

As someone who has, until recently, given up on the forge completely, I really, really want to see this sort of functionality. It’d be a huge help and IMO, would make the forge a lot more usable and admin-friendly.

Don’t give up Lee! Give us a couple of months. :–)

Thanks for your feedback — we’ll be sure to get something going on this.

#9 Updated by Lee Lowder about 1 year ago

As I had said – I had given up, until you and your team came along and started giving me a reason not to.

Given the sheer number of modules on the forge – up to 850+ from the last tweet I remember seeing, the need for this sort of community feedback is just going to grow.

For some projects – apache, nagios/icinga, postgres, there are dozens of modules to chose from, and they range in age and and code quality. It’s quite time consuming to have to go into each, read through the code to see if their are tests, what other modules this may depend on, if those will step on modules already in use, if it has been updated recently etc etc.

I’ve seen some that look promising, but had some deps I thought where a little questionable, and have tried to find users in IRC or on the mailing list to try to get some feedback on, and have been unsuccessful thus far.

If you look at https://ask.puppetlabs.com/question/7/which-forge-modules-should-i-choose/ The accepted answer has 10 votes ( which I think is one of if not the highest voted question on the site) an even that process is for selecting a module is pretty involved and time consuming and subject to trial and error. Being able to draw on the time others have spent evaluating (comments would need to be timestamped, so we can see if perhaps the issues in them have been addressed) would be very win.

#10 Updated by Anonymous 4 months ago

Redmine Issue #3696 has been migrated to JIRA:

https://tickets.puppetlabs.com/browse/FORGE-4

Also available in: Atom PDF