Proposal: Public community-driven roadmap for the Jenkins project

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

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!   

MotivationJenkins 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.

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBdF_KoHzLnBDqP8cj9o6D_arGY79C9jyTvQoaphzoJrg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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.

roadmap_draft.PNG



On Thursday, March 12, 2020 at 5:09:27 PM UTC+1, Oleg Nenashev wrote:
Dear Jenkins contributors,

On Jan 31 we had a <a href="https://www.meetup.com/jenkinsmeetup/events/267684785/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.meetup.com%2Fjenkinsmeetup%2Fevents%2F267684785%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGV71ptFFiF0GahGhrmV5gBVOgcVQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.meetup.com%2Fjenkinsmeetup%2Fevents%2F267684785%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGV71ptFFiF0GahGhrmV5gBVOgcVQ&#39;;return true;">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 (<a href="https://docs.google.com/document/d/1-OGpDPWkOdKw-e8C0v9hUGgQshCLmToodo0biwlejdk/edit?usp=sharing" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://docs.google.com/document/d/1-OGpDPWkOdKw-e8C0v9hUGgQshCLmToodo0biwlejdk/edit?usp\x3dsharing&#39;;return true;" onclick="this.href=&#39;https://docs.google.com/document/d/1-OGpDPWkOdKw-e8C0v9hUGgQshCLmToodo0biwlejdk/edit?usp\x3dsharing&#39;;return true;">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 <a href="https://docs.google.com/document/d/1-pM-G41VUJiuE21VDCwy1Fg3Q-tRL29b2oHy282zFec/edit?usp=sharing" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://docs.google.com/document/d/1-pM-G41VUJiuE21VDCwy1Fg3Q-tRL29b2oHy282zFec/edit?usp\x3dsharing&#39;;return true;" onclick="this.href=&#39;https://docs.google.com/document/d/1-pM-G41VUJiuE21VDCwy1Fg3Q-tRL29b2oHy282zFec/edit?usp\x3dsharing&#39;;return true;">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!   

MotivationJenkins 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:
  • <a href="https://docs.google.com/document/d/1-pM-G41VUJiuE21VDCwy1Fg3Q-tRL29b2oHy282zFec/edit?usp=sharing" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://docs.google.com/document/d/1-pM-G41VUJiuE21VDCwy1Fg3Q-tRL29b2oHy282zFec/edit?usp\x3dsharing&#39;;return true;" onclick="this.href=&#39;https://docs.google.com/document/d/1-pM-G41VUJiuE21VDCwy1Fg3Q-tRL29b2oHy282zFec/edit?usp\x3dsharing&#39;;return true;">JEP draft in Google Doc
  • <a href="https://github.com/jenkins-infra/jenkins.io/pull/2957" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2957\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFJgmo-7e9nfVNp3Gnpt6sn-_gIWw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2957\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFJgmo-7e9nfVNp3Gnpt6sn-_gIWw&#39;;return true;">Prototype implementation for jenkins.io 
  • <a href="https://github.com/oleg-nenashev/jenkins.io/blob/jenkins-roadmap-2020/content/project/roadmap/data.json" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2Fjenkins.io%2Fblob%2Fjenkins-roadmap-2020%2Fcontent%2Fproject%2Froadmap%2Fdata.json\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFpdMuxmFBS82efBChrX6OE1cZFkw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2Fjenkins.io%2Fblob%2Fjenkins-roadmap-2020%2Fcontent%2Fproject%2Froadmap%2Fdata.json\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFpdMuxmFBS82efBChrX6OE1cZFkw&#39;;return true;">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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/220e2089-26d1-48ff-bde1-0c8ca862cb98%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

Matt Sicker
That looks really cool!

On Thu, Mar 12, 2020 at 11:45 AM Oleg Nenashev <[hidden email]> 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.
>
>
>
> On Thursday, March 12, 2020 at 5:09:27 PM UTC+1, Oleg Nenashev wrote:
>>
>> 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
>>
> --
> 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 [hidden email].
> 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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oytQrwS8NPdvfZT4n2u%2Bv_cwtfVhTRafPQTzV0twvXzTg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re:Proposal: Public community-driven roadmap for the Jenkins project

Rick-2
In reply to this post by Oleg Nenashev

This is very cool.
On 03/13/2020 00:09[hidden email] wrote:
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!   

MotivationJenkins 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.

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBdF_KoHzLnBDqP8cj9o6D_arGY79C9jyTvQoaphzoJrg%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/21fcd5c6.1a5.170d11ac0e2.Coremail.zxjlwt%40126.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

Marky Jackson
In reply to this post by Oleg Nenashev
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 <[hidden email]> wrote:


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!   

MotivationJenkins 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.

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBdF_KoHzLnBDqP8cj9o6D_arGY79C9jyTvQoaphzoJrg%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C3676F9F-7DD6-41B3-A442-9A79A3F8A039%40gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

Daniel Beck
In reply to this post by Oleg Nenashev


> On 12. Mar 2020, at 17:09, Oleg Nenashev <[hidden email]> wrote:
>
> 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.
>


Really cool, thanks for driving this!


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/348C09B2-16E9-4C79-B00C-0043500B6B9C%40beckweb.net.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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:


> On 12. Mar 2020, at 17:09, Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="LB37UiaBAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> wrote:
>
> 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 <a href="http://jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">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.
>


Really cool, thanks for driving this!


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6ccf8a50-7e1b-40fd-9118-dfdc1aedec3f%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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


On Monday, March 16, 2020 at 10:28:07 AM UTC+1, Oleg Nenashev wrote:
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:


> On 12. Mar 2020, at 17:09, Oleg Nenashev <[hidden email]> wrote:
>
> 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 <a href="http://jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">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.
>


Really cool, thanks for driving this!


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c40cbe1b-4c2a-414d-bb1b-ae0ff801e032%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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


On Monday, March 23, 2020 at 11:21:45 AM UTC+1, Oleg Nenashev wrote:
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: <a href="https://jenkins.io/project/governance-meeting/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fproject%2Fgovernance-meeting%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF9wlJMZIK4bs_uwQ65zqCPvaonzg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fproject%2Fgovernance-meeting%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF9wlJMZIK4bs_uwQ65zqCPvaonzg&#39;;return true;">https://jenkins.io/project/governance-meeting/

Best regards,
Oleg


On Monday, March 16, 2020 at 10:28:07 AM UTC+1, Oleg Nenashev wrote:
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:


> On 12. Mar 2020, at 17:09, Oleg Nenashev <[hidden email]> wrote:
>
> 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 <a href="http://jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">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.
>


Really cool, thanks for driving this!


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0d57f091-0ea9-441c-92a9-71cce6f59c99%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

Matt Sicker
Looks great! Thanks for the hard work everyone!

On Wed, Apr 1, 2020 at 3:44 PM Oleg Nenashev <[hidden email]> wrote:

>
> 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
>
>
> On Monday, March 23, 2020 at 11:21:45 AM UTC+1, Oleg Nenashev wrote:
>>
>> 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
>>
>>
>> On Monday, March 16, 2020 at 10:28:07 AM UTC+1, Oleg Nenashev wrote:
>>>
>>> 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:
>>>>
>>>>
>>>>
>>>> > On 12. Mar 2020, at 17:09, Oleg Nenashev <[hidden email]> wrote:
>>>> >
>>>> > 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.
>>>> >
>>>>
>>>>
>>>> Really cool, thanks for driving this!
>>>>
>>>>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0d57f091-0ea9-441c-92a9-71cce6f59c99%40googlegroups.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox99iUa6-NMxWnU9VUWBkz1CqFj82cY6ey5uZx4cv%2Br5Q%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

Jon Brohauge
In reply to this post by Marky Jackson
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/13333237-1cd8-480c-8115-c9188fd8ab18%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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
  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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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

On Wed, Jun 10, 2020 at 12:15 PM Oleg Nenashev <[hidden email]> 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
  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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.


--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVeiqG4d4JX4Zb0_UKBGsDogrxheY6Yr6P8CF%2BO4%2BqAmMQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

Marky Jackson
In reply to this post by Oleg Nenashev
This is great! Thank you for all that you do.

On Jun 10, 2020, at 12:15 PM, Oleg Nenashev <[hidden email]> 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
  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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/80C37C2D-DE49-4F38-AE55-B3027791FFC0%40gmail.com.

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="f44XJulhAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> 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: <a href="https://www.jenkins.io/project/roadmap/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;">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 <a href="https://github.com/jenkins-infra/jenkins.io/pull/3444" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="f44XJulhAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3590f9c6-be5d-4197-8587-02e1bd805e0eo%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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

On Friday, June 12, 2020 at 2:16:14 PM UTC+2, Oleg Nenashev wrote:
I have updated <a href="https://github.com/jenkins-infra/jenkins.io/pull/3444" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;">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 <[hidden email]> 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: <a href="https://www.jenkins.io/project/roadmap/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;">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 <a href="https://github.com/jenkins-infra/jenkins.io/pull/3444" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;">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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/70c4ed88-2ba5-4159-b510-cede6947814fo%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

Oleg Nenashev
Hi all,

Materials from the today's online meetup:
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

On Tuesday, July 7, 2020 at 11:57:40 AM UTC+2, Oleg Nenashev wrote:
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: <a href="https://www.meetup.com/Jenkins-online-meetup/events/271768902/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.meetup.com%2FJenkins-online-meetup%2Fevents%2F271768902%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHuGlXkp_royiT8qeP7p-Sjimf8DQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.meetup.com%2FJenkins-online-meetup%2Fevents%2F271768902%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHuGlXkp_royiT8qeP7p-Sjimf8DQ&#39;;return true;">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

On Friday, June 12, 2020 at 2:16:14 PM UTC+2, Oleg Nenashev wrote:
I have updated <a href="https://github.com/jenkins-infra/jenkins.io/pull/3444" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;">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 <[hidden email]> 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: <a href="https://www.jenkins.io/project/roadmap/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;">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 <a href="https://github.com/jenkins-infra/jenkins.io/pull/3444" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;">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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c188b655-442a-4b26-ab8b-c45d555002c6o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Public community-driven roadmap for the Jenkins project

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

On Friday, July 10, 2020 at 11:49:15 PM UTC+2, Oleg Nenashev wrote:
Hi all,

Materials from the today's online meetup:
  • Video recording: <a href="https://www.youtube.com/watch?v=ldWBY5BdQ5I" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.youtube.com/watch?v\x3dldWBY5BdQ5I&#39;;return true;" onclick="this.href=&#39;https://www.youtube.com/watch?v\x3dldWBY5BdQ5I&#39;;return true;">https://www.youtube.com/watch?v=ldWBY5BdQ5I
  • Slides: <a href="https://bit.ly/jenkins-meetup-roadmap" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fbit.ly%2Fjenkins-meetup-roadmap\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGxpDVXuoMTzP7KNlDOTQ0ZUavRnA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fbit.ly%2Fjenkins-meetup-roadmap\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGxpDVXuoMTzP7KNlDOTQ0ZUavRnA&#39;;return true;">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

On Tuesday, July 7, 2020 at 11:57:40 AM UTC+2, Oleg Nenashev wrote:
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: <a href="https://www.meetup.com/Jenkins-online-meetup/events/271768902/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.meetup.com%2FJenkins-online-meetup%2Fevents%2F271768902%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHuGlXkp_royiT8qeP7p-Sjimf8DQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.meetup.com%2FJenkins-online-meetup%2Fevents%2F271768902%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHuGlXkp_royiT8qeP7p-Sjimf8DQ&#39;;return true;">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

On Friday, June 12, 2020 at 2:16:14 PM UTC+2, Oleg Nenashev wrote:
I have updated <a href="https://github.com/jenkins-infra/jenkins.io/pull/3444" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;">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 <[hidden email]> 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: <a href="https://www.jenkins.io/project/roadmap/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Froadmap%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6elTpWlzD5bqDip30c26DxXPhQA&#39;;return true;">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 <a href="https://github.com/jenkins-infra/jenkins.io/pull/3444" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F3444\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG5-DJ8wWBwFBpNo-5jAAMqrnzvig&#39;;return true;">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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/46eca5da-9ef2-454e-a83c-198234f20603o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/97968895-da93-4a86-92c8-0071997139afo%40googlegroups.com.