Looks great! Thanks for the hard work everyone! On Wed, Apr 1, 2020 at 3:44 PM Oleg Nenashev <[email protected]> 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 <[email protected]> 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/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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox99iUa6-NMxWnU9VUWBkz1CqFj82cY6ey5uZx4cv%2Br5Q%40mail.gmail.com.
