Thank you.

As per Zulip: "let's see how it goes with Apps repository, so we can
better evaluate the impact on the console images. Actually not only
consoles.. all apps related images".

Hopefully we'll have more info soon-ish as I already see that Tibor
managed to get Runtimes done.

On Tue, Feb 6, 2024 at 3:51 PM ricardo zanini fernandes
<ricardozan...@gmail.com> wrote:
>
> Yes, I'll preserve the console images. But see my messages in the
> reproducible builds at #kogito-dev.
>
> Thank you, I'll go on and archive the operator.
>
> On Tue, Feb 6, 2024 at 11:08 AM Enrique Gonzalez Martinez <
> egonza...@apache.org> wrote:
>
> > +1
> >
> > El mar, 6 feb 2024, 15:02, Pere Fernandez <pere.fernan...@gmail.com>
> > escribió:
> >
> > > +1
> > >
> > > On Tue, 6 Feb 2024 at 14:56, Yeser Amer <ya...@apache.org> wrote:
> > >
> > > > +1
> > > >
> > > > On 2024/02/06 13:53:02 Alex Porcelli wrote:
> > > > > Thank you Ricardo for the assessment! The only thing that I'd change
> > > > > is to preserve the console images for now.
> > > > >
> > > > > +1 for the proposal with the adjustments to preserve the console
> > images
> > > > >
> > > > > On Mon, Feb 5, 2024 at 1:59 PM ricardo zanini fernandes
> > > > > <ricardozan...@gmail.com> wrote:
> > > > > >
> > > > > > Folks, here is the assessment:
> > > > > >
> > > > > >
> > https://github.com/apache/incubator-kie-kogito-operator/issues/1537
> > > > > >
> > > > > > Let me know what you think, once I get +1 from you, I'll move
> > forward
> > > > and
> > > > > > clean up everything. It would be nice to have some help under the
> > > docs
> > > > > > section while I'll work through the code.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > On Tue, Jan 30, 2024 at 3:43 AM Pere Fernandez (apache) <
> > > > pefer...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > El dl., 29 de gen. 2024, 17:03, Alex Porcelli <a...@porcelli.me>
> > > va
> > > > > > > escriure:
> > > > > > >
> > > > > > > > Thank you, Ricardo. Looking forward to your assessment.
> > > > > > > >
> > > > > > > > On Mon, Jan 29, 2024 at 10:56 AM Enrique Gonzalez Martinez
> > > > > > > > <egonza...@apache.org> wrote:
> > > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > El lun, 29 ene 2024, 16:55, ricardo zanini fernandes <
> > > > > > > > > ricardozan...@gmail.com> escribió:
> > > > > > > > >
> > > > > > > > > > Alex,
> > > > > > > > > >
> > > > > > > > > > Not only the images we should remove/deprecate as we did
> > with
> > > > Mongo
> > > > > > > > etc. We
> > > > > > > > > > also need to review the examples, docs, and so on.
> > Including
> > > > this:
> > > > > > > > > > https://github.com/knative-extensions/eventing-kogito
> > > > > > > > > >
> > > > > > > > > > I'll do a doc for this assessment later this week and share
> > > it
> > > > with
> > > > > > > the
> > > > > > > > > > community.
> > > > > > > > > >
> > > > > > > > > > A part from that, can I have more +1? :)
> > > > > > > > > >
> > > > > > > > > > Cheers!
> > > > > > > > > >
> > > > > > > > > > On Sun, Jan 28, 2024 at 10:53 AM Alex Porcelli <
> > > > a...@porcelli.me>
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Was thinking about this proposal and the potential
> > > additional
> > > > > > > impact.
> > > > > > > > > > >
> > > > > > > > > > > if we don’t ship operator, we may not need provide out of
> > > > the box
> > > > > > > the
> > > > > > > > > > > images, so less code and security surface to cover (ie.
> > > > CVEs).
> > > > > > > > > > >
> > > > > > > > > > > I understand we’ll continue with the serverless workflow
> > > > operator,
> > > > > > > > so my
> > > > > > > > > > > suggestion is reduce the images by the only ones used by
> > > > serverless
> > > > > > > > > > > workflow operator.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Jan 26, 2024 at 2:08 PM Jason Porter <
> > > > > > > > lightguar...@apache.org>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Do we have the minutes at least for this weekly meeting
> > > we
> > > > can
> > > > > > > > post on
> > > > > > > > > > > the
> > > > > > > > > > > > mailing list, or an accessible link at least?
> > > > > > > > > > > >
> > > > > > > > > > > > On 2024/01/26 15:05:26 ricardo zanini fernandes wrote:
> > > > > > > > > > > > > Friends,
> > > > > > > > > > > > >
> > > > > > > > > > > > > As discussed in the weekly meeting, I'm proposing to
> > > > archive
> > > > > > > the
> > > > > > > > > > legacy
> > > > > > > > > > > > > Kogito Operator repository and not make it part of
> > the
> > > > next
> > > > > > > > release.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Reasons are:
> > > > > > > > > > > > >
> > > > > > > > > > > > > 1. It uses a very old concept of deploying
> > applications
> > > > that
> > > > > > > > today
> > > > > > > > > > can
> > > > > > > > > > > be
> > > > > > > > > > > > > achieved via Quarkus Addons and SpringBoot tools.
> > > > > > > > > > > > > 2. One can also use Helm Charts and pipelines tooling
> > > to
> > > > do the
> > > > > > > > same
> > > > > > > > > > > > > 3. It has the old `kogito cli` that lost traction.
> > One
> > > > can use
> > > > > > > > > > kubectl
> > > > > > > > > > > or
> > > > > > > > > > > > > quarkus cli to achieve the same
> > > > > > > > > > > > > 4. It deploys explainability, trusty, infinispan, and
> > > > other
> > > > > > > > services
> > > > > > > > > > > that
> > > > > > > > > > > > > we are not supporting anymore.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I'll archive the repository and I can write a blog
> > post
> > > > about
> > > > > > > > this
> > > > > > > > > > > > decision
> > > > > > > > > > > > > once we have a release.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I'll update the pipelines to not run it anymore too.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I need your +1 to move ahead.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Cheers!
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Ricardo Zanini Fernandes
> > > > > > > > > > > > > Vida longa e próspera.
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > >
> > > > ---------------------------------------------------------------------
> > > > > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > > > > > > > > > > For additional commands, e-mail:
> > dev-h...@kie.apache.org
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > > > > > > For additional commands, e-mail: dev-h...@kie.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > > > For additional commands, e-mail: dev-h...@kie.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > > For additional commands, e-mail: dev-h...@kie.apache.org
> > > >
> > > >
> > >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
For additional commands, e-mail: dev-h...@kie.apache.org

Reply via email to