It seems like I had trouble finding good information about entry points. It also did not seem like there were any references to the javadoc from the wiki(I always found what I needed using google).
Also, it seems like there are some significant sources of information about plugins and such that are not really mentioned. For example, back in October you commented on https://github.com/jenkinsci/ssh-plugin/pull/9#issuecomment-121570158 with several significant insights about how the plugin was being used and how changes under consideration would impact the user base. Where did that information come from? Another example would be https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Report+Card, which I do not recall ever seeing any mention of until somebody mentioned it on the mail list. Those are just two examples, but I would say anything that can help developers understand how plugins(and core) are used and what the potential impact of changes would be is going to be incredibly helpful. John Tatum john.ta...@live.com http://scientifichooliganism.net Although this e-mail and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and/or upon which it is opened, it is the responsibility of the recipient(s) to ensure that it is virus and/or defect free and John Tatum bears no responsibility for any loss and/or damage arising in any way from its use. > From: m...@beckweb.net > Subject: Improvements to the developer docs > Date: Thu, 16 Jul 2015 14:31:48 +0200 > To: jenkinsci-dev@googlegroups.com > > Hi everyone, > > I'm looking into improving the developer documentation for Jenkins. I'm not > going to be able to do an entire rewrite of the docs, but if you have > specific issues with the docs you think should be improved, please let me > know. What parts do you think are documented insufficiently? > > This should preferably be issues with getting the 'big picture', > interaction/relation of different parts, discovering available APIs, etc. -- > things not as easily done in Javadoc, but if you see major problems with > these, add them to the list. > > I'm also specifically inviting less experienced core/plugin developers to > provide suggestions. What are/were you struggling with the most? What > documentation would you have liked to find but couldn't? > > Daniel > > -- > 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/52690EB6-1E39-4248-A46A-2124822FD162%40beckweb.net. > For more options, visit https://groups.google.com/d/optout. -- 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/BLU179-W89562A502016E131C834B7F7990%40phx.gbl. For more options, visit https://groups.google.com/d/optout.
