Marat,

I created the repository for moving the project:
https://github.com/apache/camel-karavan

Il giorno mer 29 set 2021 alle ore 06:53 JB Onofré <j...@nanthrax.net> ha
scritto:

> No objection from my side. The only thing we are to be careful is during
> code donation: IP/cla, license, header, etc.
> I can help on these checks/verify.
>
> Regards
> JB
>
> > Le 29 sept. 2021 à 06:47, Andrea Cosentino <anco...@gmail.com> a écrit :
> >
> > Do we all agree on creating the repository under Apache Camel and start
> the
> > migration of the project?
> >
> > Thanks.
> >
> >> Il giorno mer 29 set 2021 alle ore 03:27 Marat Gubaidullin <
> >> marat.gubaidul...@gmail.com> ha scritto:
> >>
> >> Hello Luca,
> >>
> >> Thank you for your feedback.
> >>
> >> 1. Theoretically it is possible to create a Karavan editor as an
> extension
> >> for VS Code.
> >> It is a React app and all logic is on the front-end sidd. However this
> is
> >> my first project with Typescript and React,
> >> so to convert it into vscode extension might take some time and require
> >> some help from an expert.
> >>
> >> 2. Why was Karavan designed as a webapp and not a vscode extension in
> the
> >> first place?
> >> As a Java developer I prefer to use Camel-Quarkus for integrations. It
> is
> >> faster, testable and I could use the full power of Camel.
> >> However some Integrations are simple, not mission critical and could be
> >> created by citizen developers or non-java engineers without Camel
> >> expertise.
> >> The idea of Karavan is to help them create integrations intuitively
> without
> >> learning Camel DSL syntax and any developer tools (ex vscode).
> >> If you see any other use cases for Karavan, could you please share?
> >>
> >> Marat
> >>
> >> On Tue., Sep. 28, 2021, 11:55 Luca Burgazzoli <lburgazz...@gmail.com>
> >> wrote:
> >>
> >>> Hi Marat,
> >>>
> >>> I do agree with Andrea and Claus: it is an awesome project and it would
> >> be
> >>> very nice addition to the camel ecosystem.
> >>> The only thing that would make it even more awesome (not sure if
> >> technical
> >>> possible) would be having a support for VS Code and http://github.dev.
> >>>
> >>> ---
> >>> Luca Burgazzoli
> >>>
> >>>
> >>> On Fri, Sep 24, 2021 at 9:50 AM Claus Ibsen <claus.ib...@gmail.com>
> >> wrote:
> >>>
> >>>> Hi Marat
> >>>>
> >>>> Yay this looks great. I like that the editor is dis-connected from
> >>>> Camel, where you can either save the generated file to disk,
> >>>> or push to a git repository.
> >>>>
> >>>> It also seems you use the EIP json files from the catalog to list the
> >>> EIPs.
> >>>> I noticed we didn't have them labelled too nicely so I will polish
> >>>> this in the camel-core.
> >>>>
> >>>>
> >>>> On Thu, Sep 23, 2021 at 1:55 AM Marat Gubaidullin
> >>>> <marat.gubaidul...@gmail.com> wrote:
> >>>>>
> >>>>> Hello Camel Developers,
> >>>>>
> >>>>> For the last few months I've been working on the Karavan project:
> >>>>> Integration Designer for Camel/Camel-K.
> >>>>> https://github.com/mgubaidullin/karavan
> >>>>>
> >>>>> Karavan is still in the preliminary/experimental stage, however it is
> >>>>> possible to "draw" an integration. It already supports Kamelets and a
> >>> lot
> >>>>> of EIP. It works in local mode to store YAMLs on a local machine. In
> >>>> cloud
> >>>>> mode <
> >>>> https://github.com/mgubaidullin/karavan/blob/main/openshift/README.md
> >
> >>>>> Karavan stores YAMLs into a git repository for deployment using
> >> GitOps
> >>>>> techniques.
> >>>>>
> >>>>> Karavan demos:
> >>>>> 1. Basic integration design: https://youtu.be/a2xPcSE4TxA
> >>>>> 2. Cloud mode demo: https://youtu.be/CUCpw1UFLCc
> >>>>>
> >>>>> I would like to donate the Karavan project to ASF to run it as a
> >> Camel
> >>>> sub
> >>>>> project and continue to work on it together with the Camel Community.
> >>>>>
> >>>>> What do you think?
> >>>>>
> >>>>> Thanks
> >>>>> Marat Gubaidullin
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Claus Ibsen
> >>>> -----------------
> >>>> http://davsclaus.com @davsclaus
> >>>> Camel in Action 2: https://www.manning.com/ibsen2
> >>>>
> >>>
> >>
>
>

Reply via email to