If we all agree about having discussions in Apache Camel repository, I'll ask to INFRA.
Il giorno gio 27 lug 2023 alle ore 10:35 Otavio Rodolfo Piske < angusyo...@gmail.com> ha scritto: > Hi Claus, > > Thanks for the discussion and sharing your thoughts and concerns about this > feature with me! > > On my side there also was a big miscommunication: I should have done a > better job engaging the community on the discussions about CAMEL-18957, and > what would be the short, medium and long term plans for it. > > After we get Camel 4 GA released, I'll share an updated plan with more > details and also engage the community so that we can iteratively and > jointly design and implement this feature. > > As for GitHub discussions: +1 for that idea. I think it can be a good venue > for discussions. > > Kind regards > > On Thu, Jul 27, 2023 at 10:23 AM Nicolas Filotto <nfilo...@talend.com> > wrote: > > > +1 to use GitHub Discussion too > > ________________________________ > > From: Andrea Cosentino <ancosen1...@yahoo.com.INVALID> > > Sent: Thursday, July 27, 2023 10:13 > > To: dev <dev@camel.apache.org> > > Subject: Re: Using camel-test-infra-core vs regular testing > > > > I'm +1 to use discussions and I think we could to enable it to INFRA. > > > > -- > > Andrea Cosentino > > ---------------------------------- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > > > > > > > > > > > On Thursday, July 27, 2023 at 10:11:01 AM GMT+2, Claus Ibsen < > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > Hi > > > > I had a talk with Otabio about this subject. > > > > There has been some misunderstanding and miscommunication on my part, and > > this mail thread may also have a few related subjects conflated. > > > > In the short term we should focus on bringing Camel 4.0 to GA. > > After this release then I think there is time where we can focus on > > discussing this again, but from a fresh start. > > Otavio said he will at that given time put together some details and > share > > it with the community. > > > > > > > > On another note we also wonder if we could try GitHub Discussion for > this. > > As mailing lists are a bit out-of-date, and > > maybe GH discussions is a better place for a wider audience to see and > > bring feedback. > > > > The Camel Karavan project has GH discussions > > > > > https://urldefense.com/v3/__https://github.com/apache/camel-karavan/discussions__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBs5X8Cmo$ > > > > > > > > > > On Thu, Jul 20, 2023 at 7:24 AM Claus Ibsen <claus.ib...@gmail.com> > wrote: > > > > > Hi > > > > > > I noticed that we are migrating some components to use camel-test-infra > > > for unit testing. > > > And I think it makes sense when you have > > > > > > - need to use docker / test-containers > > > - or to setup some internal embedded system that usually would require > a > > > base class with some code to do that. > > > > > > However for basic components that are not in need for that then we > should > > > not use camel-test-infra but just regular camel-test, just as camel end > > > users will do that. > > > > > > For example this PR > > > > > > https://urldefense.com/v3/__https://github.com/apache/camel/pull/10739__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBs_qR8OQ$ > > > > > > I fail to see the need for test-infra-core for camel-asn1. This is > just a > > > message transformation (dataformat) library that works purely > in-memory. > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > @davsclaus > > > Camel in Action 2: > > > https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBwcuHNv8$ > > > > > > > > > > > -- > > Claus Ibsen > > ----------------- > > @davsclaus > > Camel in Action 2: > > > https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBwcuHNv8$ > > > > As a recipient of an email from the Talend Group, your personal data will > > be processed by our systems. Please see our Privacy Notice < > > https://www.talend.com/privacy-policy/> for more information about our > > collection and use of your personal information, our security practices, > > and your data protection rights, including any rights you may have to > > object to automated-decision making or profiling we use to analyze > support > > or marketing related communications. To manage or discontinue promotional > > communications, use the communication preferences portal< > > https://info.talend.com/emailpreferencesen.html>. To exercise your data > > protection rights, use the privacy request form< > > > https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl > >. > > Contact us here <https://www.talend.com/contact/> or by mail to either > of > > our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, > San > > Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 > Suresnes, > > France > > > > > -- > Otavio R. Piske > http://orpiske.net >
