Nobody WANTS to submit code without documentation, but when adding to the docs takes as much work as writing the code, it's inevitable that the docs will go wanting. On the other side of the coin, the docs team wants to provide great documentation, but without being able to read the developer's mind, it's not always easy (or even possible). This session will look at some ways we can make it easier for developers to contribute code, and perhaps more important, what it will take to motivate them to do it.
We hope to come away with at least the seed of a process that we can put into place during the Juno cycle so that developers are motivated and able to provide at least the seeds of documentation that the docs team can then work into the actual manuals.
