https://issues.apache.org/jira/browse/CAMEL-20880

Created this.
--Andrea Cosentino ----------------------------------Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

    On Monday, June 17, 2024 at 06:38:25 AM GMT+2, Claus Ibsen 
<claus.ib...@gmail.com> wrote:  
 
 On Mon, Jun 17, 2024 at 6:11 AM Tadayoshi Sato <sato.tadayo...@gmail.com>
wrote:

> Hi team,
>
> On a broader note: I wonder if we should start having middle folders to
> > help categorize other components as well. For example, having categories
> > for:
>
> - databases
> > - http
> > - messaging
> > - big-data (?)
> > - iot
> > - spring
>
>
> I like this idea. There are already a bit too many components right under
> the components folder, and it's becoming a bit hard to navigate to the
> components I'm interested in.
> If we go the path, maybe we could start from something obvious like: ai,
> databases, http, messaging, and leave the others as-is.
>
> I'd like to just double check that in this proposed idea we don't divide
> them based on the basic taxonomy: components, data formats, languages, and
> eips, right?
>
>
No I actually dont think that is a good idea, you have components that fit
multiple categories
and then where should it be.

The AI is special as its a lot of experiments and need special attention.

We already have labels on components that are associated and you can see in
camel-catalog, or via jbang.

camel catalog --filter=database

What we could do is to see if we can make the Camel website show these
labels in the component overview.
https://camel.apache.org/components/4.4.x/




> Thank you,
>
> On Sun, Jun 16, 2024 at 3:12 PM Otavio Rodolfo Piske <angusyo...@gmail.com
> >
> wrote:
>
> > A bit late on the reply but ... +1 from me Claus
> >
> > On a broader note: I wonder if we should start having middle folders to
> > help categorize other components as well. For example, having categories
> > for:
> >
> > - databases
> > - http
> > - messaging
> > - big-data (?)
> > - iot
> > - spring
> >
> > This can be a slippery slope: some components may fit more than one
> > category, it may require more changes to the plugins and the effort is
> not
> > negligible. However, it could also help us look for ways to share more
> code
> > between similarly related components, thus reducing duplication and the
> > amount of code we have to maintain.
> >
> > Kind regards
> >
> > On Mon, Jun 3, 2024 at 9:30 AM Claus Ibsen <claus.ib...@gmail.com>
> wrote:
> >
> > > Hi
> > >
> > > I wonder if we should consider moving those vector database components
> > into
> > > camel-ai, as they are used for AI stuff.
> > >
> > > Just mind that when moving into "middle" folders, then you need to
> > adjust a
> > > bit of code in the camel-package-maven-plugin.
> > >
> > > Just do a git grep for one of the existing components and see (git
> > > grep camel-djl)
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
> >
> > --
> > Otavio R. Piske
> > http://orpiske.net
> >
>
>
> --
> Tadayoshi Sato
>


-- 
Claus Ibsen
-----------------
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
  

Reply via email to