On 27.04.2015, at 10:33, 'Bruno P. Kinoshita' via Jenkins Developers <jenkinsci-dev@googlegroups.com> wrote:
> We could create a default template, with just that Confluence macro that > brings the plug-in details (Jira, GitHub repo, name, maintainer/assigner, > etc). This would just result in plugins instead having dead wiki pages with autogenerated content only. Those would still not tell you anything about what the plugin does and how it works. Something like this shouldn't be necessary. Having and enforcing some clearly documented, minimal standards for plugins for the benefit of users and other devs does not constitute 'barriers to entry' so could easily be done consistent with the project values. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/10EE4F21-7D6C-4973-AD6A-2E7786FF4109%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
