On Thursday, July 16, 2015 at 3:31:58 PM UTC+3, Daniel Beck wrote: > > 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 > > 1) As person that has INFRA access: *update confluence.* This is the blocker for me for any docs activities. 2) Review/re-organise/clean-up current docs (they are duplicated in many places because people can't find right page and creating new). 3) Stop living in workflow only world https://github.com/jenkinsci/workflow-plugin/commit/b127fd48c37ed034d5d04d62d10d3de8136e04f3#commitcomment-11916805
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3705ab10-5790-4dc2-9fff-7bdb1f5c735c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
