Proposal: Public community-driven roadmap for the Jenkins project

[Oleg Nenashev]

Dear Jenkins contributors,

On Jan 31 we had a Jenkins contributor summit in Brussels. At this unconference we discussed a number of ongoing projects and key initiatives which could help us to evolve the project (meeting notes). One of the proposals there was to create a public community-driven roadmap for the project. There was a strong consensus about doing so, so I went ahead and created a Public Jenkins Roadmap process proposal draft which is based on the discussion results. I plan to submit it as a formal Jenkins Enhancement Proposal later after getting initial feedback from contributors who were not in Brussels. Any feedback will be appreciated!   

Motivation: Jenkins is a community-driven project. Changes there happen only in those areas where we have contributors. So changes in the project may sometimes appear chaotic to an external observer. At the same time, now we have a lot of entities like special interest groups, sub-projects and teams. These entities drive key initiatives in the community, and largely use their own channels for that. One has to find these channels to follow a project. A Jenkins user or an outside contributor might have difficulties understanding what is going on and how to contribute.

This proposal documents a new roadmap process which would make planned changes more explicit and which would highlight the potential projects to Jenkins contributors and users. It will help Jenkins users and vendors to properly plan their work and to contribute to the projects they are interested in.

Links:

• JEP draft in Google Doc
• Prototype implementation for jenkins.io 
• Roadmap JSON from the PoC (feel free to contribute!) 

Note that my proposal does not define the roadmap items on its own, it only defines the process and the implementation for it. Not all proposals from the contributor summit have been added to the draft, but I plan to follow-up on that during the proposal review. In the coming weeks I am planning to reach out to Special Interest Groups, teams and sub-projects so that they could contribute their roadmap items for key initiatives. Maintainers of Jenkins plugins are also welcome to make suggestions.

Thanks for your time and feedback,

Oleg Nenashev

[Oleg Nenashev]

Just a sample screenshot for those who are interested to see how it may look like.

This is a mock data and a PoC layout, so please do not consider it as a final version.

[Matt Sicker]

That looks really cool!

On Thu, Mar 12, 2020 at 11:45 AM Oleg Nenashev <o.v.ne...@gmail.com> wrote:
>
> Just a sample screenshot for those who are interested to see how it may look like.
> This is a mock data and a PoC layout, so please do not consider it as a final version.
>
>
>

> --
> 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-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/220e2089-26d1-48ff-bde1-0c8ca862cb98%40googlegroups.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

[Rick]

This is very cool.

--
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-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBdF_KoHzLnBDqP8cj9o6D_arGY79C9jyTvQoaphzoJrg%40mail.gmail.com.

[Marky Jackson]

Oleg,

This is really great! I think this is a really good thing for the community.

On Mar 12, 2020, at 9:09 AM, Oleg Nenashev <o.v.ne...@gmail.com> wrote:



[Daniel Beck]

Really cool, thanks for driving this!

[Oleg Nenashev]

Thanks all for the feedback and for the comments in the Google Doc!

I will go ahead tomorrow and suggest a formal JEP.

All Jenkins contributors are welcome to suggest their roadmap items!

On Sunday, March 15, 2020 at 11:50:24 PM UTC+1, Daniel Beck wrote:

[Oleg Nenashev]

I will submit a JEP today. Once it is in place, I would also like to go ahead with the suggested rollout plan and to deploy a WIP version of the Roadmap page on the website. All disclaimers will be applied there.

Added the approval request to the next governance meeting agenda: https://jenkins.io/project/governance-meeting/

Best regards,

Oleg

[Oleg Nenashev]

Quick updates: https://jenkins.io/project/roadmap/ is live!

• Roadmap JEP has been published as a draft: JEP-14
• Initial pull request was merged as it was agreed at the governance meeting last week. It is considered as a work-in-progress draft, so the data does not represent the final roadmap. Blue Ocean's Javascript magic was replaced by old faithful HAML, so we do not 
• Data is now stored in the YAML format: /content/_data/roadmap/roadmap.yml

 Any feedback will be appreciated, especially Jenkins Roadmap item proposals.Please feel free to just submit pull requests!

Best regards,

Oleg

[Matt Sicker]

Looks great! Thanks for the hard work everyone!

> --
> 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-de...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0d57f091-0ea9-441c-92a9-71cce6f59c99%40googlegroups.com.

[Jon Brohauge]

Totally love the roadmap. Sincerely missed in most software.

Rgds
Jon

[Oleg Nenashev]

Hi all,

Just to provide some updates, we have had a few roadmap reviews at the Jenkins Governance meetings, and we have also collected roadmap feedback from all special interest groups and sub-projects. We have been less successful with plugin maintainer communications, but I hope to address it in the coming week by hosting an online meetup and, maybe, reaching out to maintainers through the Jenkins contributor newsletter which I would like to establish.Current roadmap can be found here: https://www.jenkins.io/project/roadmap/

I would like to suggest a few changes there based on the experience:

1. Introduce a new "Preview" status. We have any initiatives which are stuck in Current but which are available to users for preview, e.g. WebSockets support (JEP-223), new Windows Installer, and so on. Moving it to a new category would allow to highlight the preview status and, hopefully, to facilitate feedback
• I created https://github.com/jenkins-infra/jenkins.io/pull/3444 for review
2. Introduce labels of initiatives (e.g. "feature", "documentation", "service", "outreach-program", etc.)
• Each initiative will be able to have multiple categories. There will be a JavaScript-powered filter which will allow filtering categories
• "Documentation" and "Outreach Programs" sections would be largely merged into user-focused categories on the roadmap.
• For example, Jenkins UI/UX Hackfest would be in the "User Experience" group while having an "outreach-program" label

Would appreciate your feedback about these proposals.

Thanks in advance,

Oleg

[Slide]

I think this sounds great, thanks for all of your efforts in this area!

--

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-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.

--

Website: http://earl-of-code.com

[Marky Jackson]

This is great! Thank you for all that you do.

--
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-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.

[Oleg Nenashev]

I have updated https://github.com/jenkins-infra/jenkins.io/pull/3444. Now it includes initiative labels and filtering support (pardon my JavaScript).

Among major changes, Documentation, Infrastructure and Advocacy/Outreach categories have been largely merged into other groups.

Any feedback will be appreciated!

Filtering example:

On Wednesday, June 10, 2020 at 9:41:08 PM UTC+2, Marky Jackson wrote:

This is great! Thank you for all that you do.

On Jun 10, 2020, at 12:15 PM, Oleg Nenashev <o.v.n...@gmail.com> wrote:

Hi all,

Just to provide some updates, we have had a few roadmap reviews at the Jenkins Governance meetings, and we have also collected roadmap feedback from all special interest groups and sub-projects. We have been less successful with plugin maintainer communications, but I hope to address it in the coming week by hosting an online meetup and, maybe, reaching out to maintainers through the Jenkins contributor newsletter which I would like to establish.Current roadmap can be found here: https://www.jenkins.io/project/roadmap/

I would like to suggest a few changes there based on the experience:

1. Introduce a new "Preview" status. We have any initiatives which are stuck in Current but which are available to users for preview, e.g. WebSockets support (JEP-223), new Windows Installer, and so on. Moving it to a new category would allow to highlight the preview status and, hopefully, to facilitate feedback
• I created https://github.com/jenkins-infra/jenkins.io/pull/3444 for review
2. Introduce labels of initiatives (e.g. "feature", "documentation", "service", "outreach-program", etc.)
• Each initiative will be able to have multiple categories. There will be a JavaScript-powered filter which will allow filtering categories
• "Documentation" and "Outreach Programs" sections would be largely merged into user-focused categories on the roadmap.
• For example, Jenkins UI/UX Hackfest would be in the "User Experience" group while having an "outreach-program" label

Would appreciate your feedback about these proposals.

Thanks in advance,

Oleg

On Monday, April 6, 2020 at 8:10:34 PM UTC+2, Jon Brohauge wrote:

Totally love the roadmap. Sincerely missed in most software.

Rgds
Jon

--
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 jenkin...@googlegroups.com.

[Oleg Nenashev]

Hi all,

Thanks to everyone who contributed their roadmap items or provided feedback over the past months.

Some summary of the next steps:

• On Jul 10 we will be organizing a developer meetup about the Roadmap and the Roadmap process: https://www.meetup.com/Jenkins-online-meetup/events/271768902/ . Everybody is welcome to join!
• On Jul 15 I propose to publicly vote on releasing the roadmap and marking JEP-14 as active. After that I suggest to switch to the formal roadmap addition process proposed in the JEP

Any additional feedback will be appreciated! I am ready to incorporate content and roadmap changes to make the roadmap better and more usable by users and contributors.

Thanks for your time,

Oleg Nenashev

[Oleg Nenashev]

Hi all,

Materials from the today's online meetup:

• Video recording: https://www.youtube.com/watch?v=ldWBY5BdQ5I
• Slides: https://bit.ly/jenkins-meetup-roadmap

Next week I will address the feedback we received during and after the meetup so that it is fully ready for the publishing discussion by the Governance meeting on July 15th.. Any additional comments will be appreciated!

Best regards,

Oleg Nenashev

[Oleg Nenashev]

Hi all,

I am happy to announce that the Jenkins Roadmap is now officially public. It is a major achievement for the project. Thanks to everyone who contributed to this project over the last 6 months!

Updates from the yesterday's Governance meeting (notes, video):

• We have reviewed the status of JEP-14. All feedback was addressed, and there was no remaining feedback to be addressed 
• Alex Earl has approved JEP-14 as a BDFL Delegate, and it was transferred to the "Active" state
• We have reviewed the roadmap page, and we agreed that it is ready for publishing once the staged pull requests are integrated. The recent feedback from users was addressed: lack of clear way to archive roadmap items, missing descriptions in a few stories, etc.
• We plan to have the next roadmap meeting in late August or September once the vacation period is over. Before that, everyone is welcome to submit roadmap updates like JEP-14 describes, they do not have to wait for a roadmap meeting to be integrated if there is a consensus.

I have integrated jenkins.io/pull/3527 which removes the work-in-progress disclaimers. Once the change is propagated, the roadmap will be fully official. Thanks again to everyone, and let's make sure that the roadmap initiatives happen and provide a lot of value to the Jenkins users and the community!

Best regards,

Oleg Nenashev