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