Short and medium term objectives

This page can get stale quickly, so please check the last edit date to assess whether or not it's worth your time.

Transitioning in new maintainers, here are the steps we need:

• Each person will need contributor access level
• All should have logins for artifactory and the Jenkins wiki
• One or more folks will need access for releasing new versions
• Perhaps we can delineate responsibilities between maintainers (software, docs, release, etc). For example, each area could have a go-to person, but other maintainers should be able to help across other areas. This might help spread the workload and help us be more responsive to the community. ** Plus 1 on figuring out a proper way to divide labor, whether it's by feature, area of the codebase, function, whatever (from Ben). You guys can also think about using the board feature from GitHub if that helps organize.

Unordered list of areas to improve.

• Documentation (e.g., a page on "Common questions or issues") -- that is good practice but can also make it easier to quickly respond issues logged by users
• Jenkinsfile improvements
• The plugin itself is built on older Cloudbees infrastructure. To upgrade it, we'd need to create a Jenkinsfile for the repo itself, and log in a ticket with the Cloudbees infrastructure team to switch to the new, faster infrastructure.
• Adding tests to the job DSL (recent upgrades for Jenkins 2 compatibility mean we can adopt the test patterns laid out on the jenkins-job-dsl plugin)
• ... pls add your ideas here