On 3 October 2012 22:26, llowder <llowde...@gmail.com> wrote: > > > On Wednesday, October 3, 2012 4:40:59 AM UTC-5, Mister Guru wrote: >> >> >> On 3 Oct 2012, at 03:35, Ryan Coleman wrote: >> >> > Hello, >> > >> > If you weren't at PuppetConf or didn't catch my talk, here's a quick >> > recap. I'm product owner for the Puppet Forge team which formed in >> > July with 2 awesome engineers and an equally awesome designer. We're a >> > team dedicated to the Forge and while ramping up, we've shipped three >> > small improvements to the Forge that we hope you enjoy. >> >> Good Morning Ryan! Nice to hear news about the puppet forge! Product >> owner huh?? Hey guys, now we know who to bug when it come to the Forge! >> >> > >> > * Two lists were added to the homepage, highlighting recently active >> > modules and contributors >> > * An authors Gravatar is now displayed on each module page. >> > * Today, the Forge will now retrieve information about GitHub issues >> > and pull requests for a module for display on a module page. This has >> > been automatically enabled for any module that lists GitHub as its >> > 'Project Issue Tracker URL'. >> >> I noticed this last night, it was great. I was stuck with a module I >> downloaded - I looked it up on the forge, and I noticed a link to the git >> page - I then realised the problem was ummm..... me, using the module in >> the not right way. Most useful, saved me bashing my keyboard against the >> computer >> >> > The team is just getting started. In the mean-time, we've been making >> > improvements to our back-end services, user-testing new feature ideas >> > and getting ready for the next wave of functionality. Our next >> > features will focus on these two areas. A) Making it easy for you to >> > contribute your module & B) Improve the information you have to make a >> > decision about which module to use. >> > >> > As we develop and test ideas to address these goals, we want your >> feedback! >> > >> >> Ah yes - Point B - How about ranking by downloads? I'm sure you can pull >> the stats from Forge servers. I'm assuming people log into the forge to do >> some background before running public code, for compliance, and in my case >> to suppress paranoia :) >> >> How about making the forge a bit more social - For example how about >> being able to review a module, or write a comment about it on the forge? >> That way, it's a bit easier for the author to get some feedback, and also >> for others to get an idea how 'good' the module is. >> >> That would come in useful when some modules depend on others, if I'm >> trying to install module A, and A insists on B, C, and D - I'd rather read >> up on others, who went live straight away without testing and are >> complaining about their broken systems .... Oh, I mean, I'd like to read >> the reviews from other users praising the awesomeness of the forge. >> >> Imagine that - In 6 months we could have modules writers competing >> against each other - now that would be cool - Author rankings, (obviously >> Puppet Labs Employees and modules excluded!) - and peer competition could >> only lead to better code >> > > +1 on all these ideas, though I don't think that the "number of downloads" > metric is really useful, a high number could just mean that it is easrlier > in the list and still a crappy module.. > > But I do really like the idea of being able have some sort of community > review on the modules, be that comments or even a simple up/down voting > type system. >
Hmm... Thinking about it, the download stats would be misleading - Good point - Voting up and down would be a place to start. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
