How about requiring plugin authors to post a specially tagged compatibility notice? then a script could gather, sort and display those sections from the authors, and tell the porter which plugin to investigate himself if the author has not made the section.
Niels L On Sun, 2014-12-14 at 16:46 +0100, Sawyer X wrote: > The problem is that it makes us accountable for every plugin, and I > definitely don't want that. > > It's great to see Dancer as an ecosystem but we can't account for all > plugins, their changes, their authors, their design, and their problems. We > would need to keep our documentation up-to-date on all plugins and I'm not > sure that's a good idea. > > I think racke's suggestion of providing a place to list plugin information > (such as "we know these exist" or perhaps "the following are known to work > on the latest version", etc.) but this has been proven difficult to > maintain. Hell, the module we used to check whether plugins started having > problems at some point too. > > While I understand the desire, I'm not sure it's something we can and > should be doing. > (not that I'm saying no, I'm simply raising the problem with it because I > don't know what to do with it yet.) > _______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
