Re: [VOTE]

[Dmitry Volodin]

Thanks Jason!

My choice is concept one. This is the best.

--
Best regards,
Dmitry


вт, 23 апр. 2019 г. в 18:15, Jason Brock :

> Hello everyone!
>
> Here is a first round of design concepts to help refresh the look and feel
> of the Apache Camel website. Please let me know if you require a particular
> file format and I will furnish that to the group.
>
> Concept One:
>
> https://design.jboss.org/camel/website/styleguides/images/01-colorpalette.png
> https://design.jboss.org/camel/website/styleguides/images/01-styleguide.png
>
> Concept Two:
>
> https://design.jboss.org/camel/website/styleguides/images/02-colorpalette.png
> https://design.jboss.org/camel/website/styleguides/images/02-styleguide.png
>
> Concept Three:
>
> https://design.jboss.org/camel/website/styleguides/images/03-colorpalette.png
> https://design.jboss.org/camel/website/styleguides/images/03-styleguide.png
>
>
> All the best,
>
> JASON K BROCK
>
> Web UX DESIGNER, MIDDLEWARE ENGINEERING SERVICES
>
> Red Hat - Austin, TX  | jbr...@redhat.com |
> 512-786-8304
>

Re: [VOTE] Release Apache Camel 2.24.0

[Dmitry Volodin]

+1 (binding)

Thanks, Gregor!

--
Best regards,
Dmitry


вт, 7 мая 2019 г. в 10:30, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.24.0, a new minor release
> with 156 improvements and bug fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344459&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1136/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1136/org/apache/camel/apache-camel/2.24.0/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.24.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.24.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

[Dmitry Volodin]

+1 (binding)

Thanks, Gregor!

--
Best regards,
Dmitry Volodin


вс, 7 июл. 2019 г. в 12:17, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0-M4 (Milestone 4), the
> fourth milestone towards a new 3.0.0 major release with another 105
> improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345567&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1143/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1143/org/apache/camel/apache-camel/3.0.0-M4/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-M4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: [HEADS UP] - camel3 - camel-http4 renaming to camel-http

[Dmitry Volodin]

+1

And +1 to good idea from Tadayoshi as we have a set of the versions based
components, like elastcisearch, jetty, quartz, etc.
--
Best regards,
Dmitry Volodin


чт, 25 июл. 2019 г. в 13:24, Tadayoshi Sato :

> +1
>
> Maybe it's also good time to review other components that have similar
> variants.
>
> On Thu, Jul 25, 2019 at 7:09 PM Alex Dettinger 
> wrote:
>
> > +1
> >
> > On Thu, Jul 25, 2019 at 12:02 PM Andrea Cosentino 
> > wrote:
> >
> > > +1
> > >
> > > Il giorno gio 25 lug 2019 alle ore 11:48 Claus Ibsen <
> > > claus.ib...@gmail.com>
> > > ha scritto:
> > >
> > > > Hi
> > > >
> > > > So what has been bothering Camel 2.x users is that when they use http
> > > > they would likely use the camel-http4 component and then they should
> > > > use http4 as the component name. The old camel-http component is
> > > > deprecated as the http client it uses is EOL for many many years.
> > > >
> > > > So with Camel 3 on the way we have deleted the old camel-http
> > > > component and the camel-http4 component now has both http and http4
> as
> > > > component names.
> > > >
> > > > I think we should rename the camel-http4 back to camel-http and then
> > > > favour using http as the component name, and then deprecate http4 (or
> > > > even remove it).
> > > >
> > > > Any thoughts?
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -
> > > > http://davsclaus.com @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
> > >
> >
>

Re: Release Apache Camel K 1.0.0-M1 and Runtime 1.0.0

[Dmitry Volodin]

+1 (binding)

--
Best regards
Dmitry Volodin

пт, 26 июл. 2019 г., 4:11 Nicola Ferraro :

> Hello all:
>
> This is a combined vote to release Apache Camel K 1.0.0-M1 and Apache Camel
> K Runtime 1.0.0.
>
> Apache Camel K Runtime versions follow a different convention (without
> milestones) and won't necessarily match main Camel K versions in the
> future.
>
> Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1145
> Runtime Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-parent-1.0.0
>
> Camel K staging repository:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.0.0-M1/
> Camel K Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/1.0.0-M1
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
> kamel install --operator-image=camelk/camel-k:1.0.0-M1 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1145
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.0.0-M1 and Apache Camel K
> Runtime 1.0.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Nicola Ferraro
>

Re: [DISCUSS] New Camel website, rump up to go live

[Dmitry Volodin]

Thanks, Zoran!

Beautiful site view!!! Good job of all team working on it.

--
Best regards,
Dmitry Volodin


чт, 1 авг. 2019 г. в 12:19, Zoran Regvart :

> Hi Cameleers,
> so it's been a while since we discussed the state of the new website,
> so let me start by enumerating what we have done so far and then what
> I think needs to be done for the website to go live.
>
> So what has been done:
>
> A lot. A lot of folk over almost two years helped with the website
> effort and their help needs to be acknowledged. I'm sorry not to
> mention everyone here as I would certainly forget someone. I do wish
> to thank you all for your contributions.
>
> In points:
>  - content from the Confluence wiki has been (high 90% of it) cleaned
> up and migrated to asciidoc format and is now maintained in the git
> repository
>  - tools that maintain the documentation were developed (updating from
> javadoc, moving/copying documents and maintaining indexes)
>  - initial website design was contributed and polished over time
>  - tools to build and develop the website were implemented and
> integrated with the CI
>  - a lot of small paper-cut issues were resolved
>
> You can find the majority of these issues as subtasks of CAMEL-11492[1].
>
> What I think needs to be done:
>  - gather more feedback on the staging website
> (https://camel.apache.org/staging/)
>  - find/resolve any search engine issues (such as CAMEL-13800[2])
>
> What I think would be good to do:
>  - more search engine optimization (like the microdata effort
> CAMEL-11494[3])
>  - I'd like to polish the documentation a bit CAMEL-13780[3], if it
> turns out not too much work split up the documentation into even
> further modules (CAMEL-13812[4])
>  - add search (CAMEL-11503)
>  - iron out any design/responsive layout issues
>
> I think we can work on the 'needs to be done' bits in the following
> week and rump up the effort to replace the old website with the new
> one currently present only on the staging.
>
> And depending on the feedback, that is if there are no large blocking
> issues found, I think we can go live with the new website somewhere in
> the middle of August.
>
> So, with that I would like to call to action, I'd like to have a list
> of actionable issues we need to resolve for the go live of the new
> website.
>
> If you can take a moment and have a look at the staging site
> (https://camel.apache.org/staging/) and either by replying on the
> thread or by creating a subtask on CAMEL-11492[1] with any issues that
> you think need to be addressed before we go live.
>
> And, if you can contribute to this effort, by modifying the design,
> improving the build tools, correcting the documentation please feel
> free to do so.
>
> zoran
>
> [1] https://issues.apache.org/jira/browse/CAMEL-11492
> [2] https://issues.apache.org/jira/browse/CAMEL-13800
> [3] https://issues.apache.org/jira/browse/CAMEL-11494
> [4] https://issues.apache.org/jira/browse/CAMEL-13780
> [5] https://issues.apache.org/jira/browse/CAMEL-13812
> [6] https://issues.apache.org/jira/browse/CAMEL-11503
>
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel 3.0.0

[Dmitry Volodin]

+1

Thanks, Gregor!
--
Best regards,
Dmitry Volodin


пн, 25 нояб. 2019 г. в 11:45, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0, a new major release with
> 1012 improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1164/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1164/org/apache/camel/apache-camel/3.0.0/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: FOSDEM 2020

[Dmitry Volodin]

Hi Zoran!

Sorry for late replay, I will also to going to the FOSDEM 2020 and will
welcome to help if needed

--
Best regards,
Dmitry


вт, 7 янв. 2020 г. в 15:11, Zoran Regvart :

> Hi Cameleers,
> FOSDEM[1] is a bit under a month from today (1. & 2. February). I
> think it's good to start planning our presence at the "Integration
> Process Community" stand.
>
> I plan on being most of the time at the stand introducing Camel and
> answering questions from passers by. I'll prepare a "What is Camel"
> slideshow that I'll have running from my laptop.
>
> I've asked for some Camel stickers to be present at the ASF stand[2],
> I'm sure we can ask some of those to be shared at the other stand.
> I've asked for some sponsorship from my employer (Red Hat) in terms of
> any additional Camel related swag and a rollup, I'll keep you posted
> on that.
>
> Anyone else wishes to present at the stand, or has any ideas on what
> else can be done?
>
> I know that several committers will be at FOSDEM, us there an interest
> in repeating the BoF from last year?
>
> We can also organize a social event (drinks at one of the pubs) if
> there is interest in that.
>
> Also, I'd like to create a blog post inviting the community, I'll wait
> on that after we hash-out the details (BoF, social event).
>
> zoran
>
> [1] https://fosdem.org/2020/
> [2] https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2020
> --
> Zoran Regvart
>

Re: Add my email to jenkins notification

[Dmitry Volodin]

Hello Omar!

I'm not sure, but looks like Jenkins build job extract e-mail from the
commit message. This means you are not set it there.

--
Best regards,
Dmitry Volodin


вт, 4 февр. 2020 г. в 14:28, Omar Al-Safi :

> Hello Camelers,
>
> Somehow, I am not getting email notification for jenkin build of Camel (
> https://builds.apache.org/job/Camel/). Can someone with admin access check
> my email if it is added to the list of emails for notifications?
>
> Thank you,
> Omar
>

Re: [VOTE] Release Apache Camel and Camel Spring Boot 3.1.0

[Dmitry Volodin]

+1

Thanks, Gregor!

--
Best regards,
Dmitry Volodin


вс, 23 февр. 2020 г. в 18:00, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.1.0 (with Apache Camel Spring
> Boot), a new minor release with 291 improvements and fixes. Please
> note that Spring Boot support (including all starter dependencies) has
> been moved into a separate repository [1]. Therefore, this vote is for
> the two staging repositories listed below.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346526&projectId=12311211
>
> == Apache Camel 3.1.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1176/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1176/org/apache/camel/apache-camel/3.1.0/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.1.0
>
> == Apache Camel Spring Boot 3.1.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1177/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.1.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 3.1.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>
> [1] https://github.com/apache/camel-spring-boot
>

Re: Apache camel application issue

[Dmitry Volodin]

Hi Muthumari!

Sorry, this is development mail list.
Please ask on gitter first. https://gitter.im/apache/apache-camel

--
Best regards,
Dmitry Volodin


ср, 4 мар. 2020 г. в 11:35, Muthu Bharathi :

> Hi,
>
> Thank you for your time for looking at this issue. I’m working in
> application support. Our java application( Apache camel) is communicating
> with mainframe data base. It is looking for the status in one record. If
> the conditions not satisfied in the iseries record. it is not moving to
> next record. It keep processing the same record in the log. What could be
> the issue?
>
> Need your help immediately.
>
> Thank you
> Muthumari
>

Re: Regarding PR#196

[Dmitry Volodin]

Hi, Prerna!

It's a dev mail list.
You can mention personally someone on GitHub with @name.

--
Best regards
Dmitry Volodin

чт, 12 мар. 2020 г., 15:00 prerna singh :

> Hi sir,
> I am eagerly waiting for your feedback on my PR made today!
>
> Thanks
>

Re: [VOTE] Release Apache Camel 3.2.0 with Spring Boot and Karaf Sub-Projects

[Dmitry Volodin]

+1

Thanks, Gregor!

--
Best regards,
Dmitry Volodin


чт, 2 апр. 2020 г. в 12:54, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.2.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 160
> improvements and fixes.
>
> Please note that Karaf support has been moved into a separate repository
> [1].
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346956&projectId=12311211
>
> == Apache Camel 3.2.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1190/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1190/org/apache/camel/apache-camel/3.2.0/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.2.0
>
> == Apache Camel Spring Boot and Karaf 3.2.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1191/
>
> Please note that Camel Spring Boot and Camel Karaf have been deployed
> to the same staging repository. This should not be a problem as we are
> planning to release everything in one flush. Next time we will make
> sure to create separate release repositories.
>
> Tags:
> -
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.2.0
> -
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.2.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>
> [1] https://github.com/apache/camel-karaf
>

Re: [VOTE] Release Apache Camel 3.4.0 with Spring Boot and Karaf Support Projects

[Dmitry Volodin]

+1 (binding)
Thanks, Gregor

--
Best regards
Dmitry Volodin

пн, 15 июн. 2020 г., 10:15 Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.4.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 118
> improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348216&projectId=12311220
>
> == Apache Camel 3.4.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1220/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1220/org/apache/camel/apache-camel/3.4.0/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.0
>
> == Apache Camel Spring Boot 3.4.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1221/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.0
>
> == Apache Camel Karaf 3.4.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1222/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.4.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: Alternatives to gitter

[Dmitry Volodin]

Hi Luca!

+1 for Zulip.
Have experience to use it in Infinispan

--
Best regards,
Dmitry Volodin


чт, 20 авг. 2020 г. в 14:12, Luca Burgazzoli :

> Hello,
>
> Over the past months I've been trying to be more active on gitter on the
> various camel projects and  overall the user experience was quite terrible
> for me (in particular when using the mobile client), as example:
>
> - threads are not shown properly on the iOS client thus messages are
> messing up
> - messages are extremely slow to load and sometime the message you sent
> take quite long to be visible even on your end so you don't actually know
> what it is happening
> - messages keep being marked as unread even if you did read them
> - sometimes you need to close/reopen the thread sidebar to see new messages
> for a given thread
>
> I don't know if it is only me but because of my frustration with the tool
> I'd like to know if anyone is interested in evaluating some alternatives
> (please note that we DON'T necessarily need to switch to something
> different).
>
> I'd personally would like to suggest to try out Zulip (
> https://zulipchat.com/) as it allow us to have an independent
> organization (
> camel.zulipchat.com) and to login with github/gitter/google so you can
> easily join without having to fill gazillion of details but I know it's
> streams and topic way of organizing conversations may not be optimal for
> everyone.
>
> If anyone has suggestions, let discuss here.
>
>
> ---
> Luca Burgazzoli
>

Re: [VOTE] Switch from Gitter to Zulip as official Camel chatroom

[Dmitry Volodin]

+1

--
Best regards
Dmitry Volodin

пн, 31 авг. 2020 г., 09:45 Luca Burgazzoli :

> Hi,
>
> This is a vote to switch the official Camel chatroom from Gitter [1] to
> Zulip [2].
>
> For detail about the reason for the switch and discussion about
> alternatives, please see the related thread on the @dev mailing list [3]. A
> Zulip test instance you can join using GitHub, GitLab, Google or plain mail
> is available [4], feel free to plain with it while the vote is open.
>
> [ ] +1 To switch from Gitter to Zulip
> [ ] -1 To Veto the switch (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thank you for your participation,
> Luca
>
> [1] https://gitter.im
> [2] https://zulipchat.com/
> [3]
> https://mail-archives.apache.org/mod_mbox/camel-dev/202008.mbox/browser
> [4] https://camel-test.zulipchat.com
>
>
> ---
> Luca Burgazzoli
>

Re: [VOTE] Release Apache Camel 3.7.0 with Spring Boot and Karaf Support Projects

[Dmitry Volodin]

+1 (binding)

Thanks, Gregor!

--
Best regards
Dmitry Volodin

вс, 13 дек. 2020 г., 11:15 Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.7.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 185
> improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349250&projectId=12311220
>
> == Apache Camel 3.7.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1263/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1263/org/apache/camel/apache-camel/3.7.0/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.7.0
>
> == Apache Camel Spring Boot 3.7.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1264/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.7.0
>
> == Apache Camel Karaf 3.7.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1265/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.7.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.7.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

join the group

[Dmitry Volodin]

Please add me to the group
--
Best regards,
Dmitry Volodin

Re: The all seeing camel-catalog

[Dmitry Volodin]

Hi Claus!

Please note, that the camel-olingo2 looks like missing in the readme file

Сб, 4 февр. 2017 г. в 11:52, Claus Ibsen :

> Hi
>
> Just wanted to share that we now include every Camel artifact in the
> camel-catalog.
> What was missing was the other/misc components which is now also included.
>
> So the tables you see at is 100% generated from the catalog
> https://github.com/apache/camel/tree/master/components#components
>
> Likewise it keeps the TOC for the (future) website up to date as well et
> all.
>
> The build is also able to detect if we have missing documentation for
> any of these artifacts, and we can therefore better ensure we have
> documentation for all of it. And we can keep that documentation with
> the source code in the artifact.
>
> That documentation is also included in the catalog, which allows
> tooling to access that as well.
>
> The catalog also allows to use runtime providers so you can filter out
> what that given runtime supports. For example the karaf runtime
> provider will only shown/include what you can use on karaf. Ditto for
> spring-boot etc.
>
> And the catalog has a rest api which we could potentially use to build
> an interactive website.
> https://github.com/apache/camel/tree/master/platforms/catalog-rest-app
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
-- 
-- Best regards, Dmitry Volodin

Re: join the group

[Dmitry Volodin]

Thanks Christian,

I'm a little bit confusing with following phrase from contributing document:
...If you want to have a go at fixing an issue you need to be in the list
of camel-developers on the issue tracker. To join the group, please mail
the dev@camel.apache.org mail list with the email address you used to
register with the issue tracker and we'll add you to the group...

--
Best regards,
Dmitry

2017-02-04 15:54 GMT+03:00 Christian Müller :

> Welcome Dmitry,
>
> you can do it by your own:
> http://camel.apache.org/mailing-lists.html
>
> Best,
> Christian
>
>
> On Tue, Jan 31, 2017 at 3:02 PM, Dmitry Volodin  wrote:
>
> > Please add me to the group
> > --
> > Best regards,
> > Dmitry Volodin
> >
>

Re: Camel 2.19 Roadmap

[Dmitry Volodin]

Hi Zoran!

Thanks a lot for your tips.
As two latest gmaven plugin usage was introduced by me in camel-protobuf
and camel-grpc components, I'm able to schedule gmaven -> gmavenplus
transition in future components improvement.

--
Best regards,
Dmitry

2017-04-21 12:20 GMT+03:00 Zoran Regvart :

> Hi Cameleers,
> we are using gmaven plugin in couple of modules, it seems that going
> forward it would be better to switch to gmavenplus plugin, well, at
> least with Java 9 and Jigsaw[1].
>
> I would like to make that switch, do you think this is something worth
> doing, and worth doing in 2.19?
>
> zoran
>
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+
> 9+-+Jigsaw#Java9-Jigsaw-Thirdpartycomponents
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel 2.19.0

[Dmitry Volodin]

Hi Gregor!

Please also add following new components to the wiki page:
camel-olingo4 (https://issues.apache.org/jira/browse/CAMEL-11056)
camel-grpc (https://issues.apache.org/jira/browse/CAMEL-11107)

--
Best regards,
Dmitry

2017-04-25 22:50 GMT+03:00 Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.19.0, a new minor release
> with over 670 new features, improvements and bug fixes.  A summary of
> the changes is available in the Camel wiki:
> https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.19+Release.
>
> Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12337871&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1073/
>
> Tarballs: https://repository.apache.org/content/repositories/
> orgapachecamel-1073/org/apache/camel/apache-camel/2.19.0/
>
> Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> 0898c94e5225532f9cf0665d8349eaba5ec0fe25
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.19.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Due to the many changes introduced with this new release, it would be
> beneficial if we could get as many Camel riders involved in testing
> this release candidate as possible. :)
>
> Thanks,
> Gregor
>

Re: [DISCUSS] - Apache Camel 2.20 release after summer

[Dmitry Volodin]

Hi All,

+1 to Onder suggestion.
JIRA has a large number of issues which are very old, but still actual for
implementation, for example Any23 data format, Apache MetaModel component,
etc. But some unresolved issues are not actual, not needed or already fixed.
Yes, it's a good idea to cleanup Camel JIRA a little bit...

--
Best regards,
Dmitry

2017-07-10 9:38 GMT+03:00 Onder SEZGIN :

> Hi,
>
> +1
>
> And i also suggest cleaning up JIRA a bit on very old issues.
>
> Maybe we can mark them, already implemented, not valid etc.
>
> For feature suggestions based on old versions, we can reevaluate and update
> the feature suggestions and include them partially in each release if we
> can manage to implement a couple of them in each release cycle.
>
>
> On Sat, Jul 8, 2017 at 5:08 PM, Zoran Regvart  wrote:
>
> > Hi Cameleers,
> >
> > +1
> >
> > I'm all for releasing sooner, one blocker that I see with this is that
> > we can't really rely on the CI builds, they often break with out of
> > memory or artifact errors, perhaps we should also take the opportunity
> > to see if not using Jenkins Maven job type (for example Jenkins
> > pipeline) would help that.
> >
> > I also wanted to experiment with hipster build tools (Buck, Blaze,
> > Pants) and see if the build times can be drastically reduced, but
> > there are only so many hours in the day :)
> >
> > zoran
> >
> > On Sat, Jul 8, 2017 at 9:58 AM, Claus Ibsen 
> wrote:
> > > Hi
> > >
> > > I think it can benefit the community if we try to get a 2.20 release
> > > out after the summer break, such as in early/mid September.
> > >
> > > The reason is that this release has some internal optimisations,
> > > reduced object allocations, and faster startup that would benefit
> > > Camel end users. Also end users can plugin the camel-headersmap module
> > > to use a slightly faster map implementation for case-insensitive keys.
> > >
> > > There has also been work on improving the startup/shutdown sequence of
> > > Camel when running in Spring so this happens better.
> > >
> > > On the same page I would also like to see us being able to do a bit
> > > more frequent releases of Camel minor releases (eg 2.19, 2.20, 2.21
> > > etc) than only 2 times per year. If we can get the momentum up to
> > > 2.5-3.5 times per year then that would be better.
> > >
> > > Any thoughts?
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
> >
> >
> > --
> > Zoran Regvart
> >
>

Components list in the Camel Jira

[Dmitry Volodin]

Hi Cameleers!

I've checked that following components are not in the Jira components list
while create/update issue.
What do you think about to add all (or not deprecated) components to list?

camel-asn1
camel-aws-xray
camel-beanstalk
camel-bonita
camel-context (deprecated)
camel-couchbase
camel-digitalocean
camel-drill
camel-eclipse (deprecated)
camel-eventadmin
camel-fastjson
camel-ganglia
camel-google-bigquery
camel-google-calendar
camel-google-mail
camel-grape
camel-groovy-dsl (deprecated)
camel-guava-eventbus
camel-hipchat
camel-ical
camel-javaspace (deprecated)
camel-jetty9
camel-jing
camel-jira
camel-josql (deprecated)
camel-json-validator
camel-ldif
camel-linkedin
camel-lumberjack
camel-lzf
camel-master
camel-mongodb-gridfs
camel-mustache
camel-openshift (deprecated)
camel-paxlogging
camel-pdf
camel-pgevent
camel-protobuf
camel-pubnub
camel-rest-swagger
camel-routebox (deprecated)
camel-ruby (deprecated)
camel-sap-netweaver
camel-sjms2
camel-spark-rest
camel-spring-cloud-netflix
camel-spring-integration
camel-spring-ldap
camel-swagger-java
camel-tagsoup
camel-test-blueprint
camel-test-cdi
amel-test-karaf
camel-testng (deprecated)
camel-test-spring
camel-thrift
camel-tika
camel-twilio
camel-univocity-parsers
camel-urlrewrite (deprecated)
camel-xmlbeans (deprecated)
camel-yammer
camel-yql
camel-zookeeper-master

--
Best regards,
Dmitry Volodin

Access to cwiki.apache.org for edit

[Dmitry Volodin]

Hi Camelers!

My ICLA have been received at Apache and my user name is: dmvolod
Please provide me access to edit Confluence pages.
Thank you.

--
Best regards,
Dmitry Volodin

gRPC and Google Guava version

[Dmitry Volodin]

Hi Camellers!

The new gRPC version (0.12.0) requires strong own Guava version which is
20.0, however we have an import with version 19.0 in Camel parent which
cause transient dependency problem in the custom/sample projects importing
camel-grpc component:

What do you think about potential sulitions:
1. Add documentation note that users must add following line to custom
pom.xml file
${grpc-guava-version} for
overriding default guava version.

2. Update current google-guava-version in parent from 19.0 to 20.0 which
could relate to the potential problems in other components

3. Play with maven enforcer plugin or suggest another solution.

Thanks in advance.

--
Best regards,
Dmitry Volodin

Re: gRPC and Google Guava version

[Dmitry Volodin]

Andrea,

I added this, but spring boot example doesn't work without explicit version
(20.0) defined.

--
Best regards,
Dmitry Volodin

2018-06-18 11:41 GMT+03:00 Andrea Cosentino :

> I would add a specific guava-version property only for gRPC and gRPC Karaf
> feature.
>
> This is what we usually do for Guava stuff.
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Monday, June 18, 2018, 8:55:37 AM GMT+2, Dmitry Volodin <
> dmvo...@gmail.com> wrote:
>
>
>
>
>
> Hi Camellers!
>
> The new gRPC version (0.12.0) requires strong own Guava version which is
> 20.0, however we have an import with version 19.0 in Camel parent which
> cause transient dependency problem in the custom/sample projects importing
> camel-grpc component:
>
> What do you think about potential sulitions:
> 1. Add documentation note that users must add following line to custom
> pom.xml file
> ${grpc-guava-version} for
> overriding default guava version.
>
> 2. Update current google-guava-version in parent from 19.0 to 20.0 which
> could relate to the potential problems in other components
>
> 3. Play with maven enforcer plugin or suggest another solution.
>
> Thanks in advance.
>
> --
> Best regards,
> Dmitry Volodin
>

Re: [VOTE] Release Apache Camel 2.22.0

[Dmitry Volodin]

+1

--
Best regards,
Dmitry Volodin

2018-06-30 8:28 GMT+03:00 Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.0, a new minor release
> with 216 new features, improvements and bug fixes. This release also
> introduces support for Spring Boot 2.0. Please note that Spring Boot
> 1.x is no longer supported with this release. A summary of the changes
> is available in the Camel wiki:
> https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.22.0+Release.
>
> Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12342707&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1107/
>
> Tarballs: https://repository.apache.org/content/repositories/
> orgapachecamel-1107/org/apache/camel/apache-camel/2.22.0/
>
> Tag: https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=
> refs/tags/camel-2.22.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.22.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: [VOTE] Release Apache Camel 2.21.2

[Dmitry Volodin]

+1 (non-binding)

--
Best regards,
Dmitry Volodin

ср, 18 Июл 2018 г., 0:47 Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.2, the second patch
> release for the camel-2.21.x branch.  This release includes 49 fixes
> and improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343107&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1109/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1109/org/apache/camel/apache-camel/2.21.2/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.21.2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Aggregate with forceCompletionOnStop and Streaming consumer

[Dmitry Volodin]

Hi Camellers!

During the work on https://issues.apache.org/jira/browse/CAMEL-12668 issue,
I've detected that if custom aggregation strategy is too slow or has a
large delays (~5-10 secs and can be emulated with Thread.sleep), the
default shutdown life-cycle doesn't wait for the aggregation and shutdown
route early and cause RejectedExecutionException.

I understand that in most cases the aggregation with 5-10 seconds is not
permitted and deferred route shutdown could solve the problems but what do
you think about potential investigation in this issue to detect why
shutdown strategy not waiting for route and consumer?

--
Best regards,
Dmitry Volodin

Re: Unsubscribe me

[Dmitry Volodin]

Marc-André,

To complete the unsubscription process you must reply to a confirmation
email. If you do not receive this confirmation email, please check your
spam filters to see if they are capturing the message. If all else fails,
you can contact the list *administrator at users-ow...@httpd.apache.org
 to get help*.

Did you contact with mail lists admin?
--
Best regards,
Dmitry Volodin


пт, 2 нояб. 2018 г. в 17:12, Marc-André Roussil <
marous...@tec-connectivia.com>:

> I try several times to unsubscribe from your email.
>
> Dont send me back this url
> http://camel.apache.org/mailing-lists.htmlhttp://camel.apache.org/mailing-lists.html
>
> UNSUBSCRIBE ME
>
> Thanks
>
>
>
>

Re: [VOTE] Release Apache Camel 2.23.0

[Dmitry Volodin]

+1 (non-binding)

Thanks, Gregor!

суббота, 24 ноября 2018 г. пользователь Gregor Zurowski написал:

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.23.0, a new minor release for
> the camel-2.23.x branch with 262 improvements and bug fixes. This is
> also the first release to support Spring Boot 2.1.
>
> Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12343345&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1114/
>
> Tarballs: https://repository.apache.org/content/repositories/
> orgapachecamel-1114/org/apache/camel/apache-camel/2.23.0/
>
> Tag: https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=
> refs/tags/camel-2.23.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.23.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>


-- 
--
Best regards,
Dmitry Volodin

Olingo4 serviceUri as query

[Dmitry Volodin]

Hi Paul!

Thanks for pointing.
I will look at this issue more detail and provide feedback or open jira
ticket.

четверг, 13 декабря 2018 г. пользователь phantomjinx написал:

> Hi,
>
> I am wondering if there is a bug in the olingo4 component/endpoint. The
> documentation[1] states that
> the serviceUri can be used as a query hence
>
>   from("olingo4://read/Products?serviceUri=" + serviceUri);
>
> However, adding this to a simple test script[2], this results in an
> exception[3] that the serviceUri
> has not been set. Digging into the code it seems that the
> Olingo4Configuration is applied to the
> endpoint but only has the apiName and methodName set. Consequently, when
> the call
> configuration.getServiceUri() is called, the value is null.
>
> Any help much appreciated.
>
> Paul
>
> [1]
> https://github.com/apache/camel/blob/master/components/camel
> -olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc
> [2] https://gist.github.com/phantomjinx/085df03915c5813a1f04b32e
> 09d00049#file-simpleolingo4test-java
> [3] https://gist.github.com/phantomjinx/085df03915c5813a1f04b32e
> 09d00049#gistcomment-2784671
>
> --
> Paul Richardson
>
>   * “Confronted by the great record of this country, and the tremendous
> promise of its future, all
> they do is croak, ‘socialism.’"
>
> Harry Truman
>
>
>

-- 
--
Best regards,
Dmitry Volodin

Re: [VOTE] Release Apache Camel 2.21.4

[Dmitry Volodin]

+1 (non-binding)
Thanks, Gregor!

--
Best regards,
Dmitry Volodin


пн, 7 янв. 2019 г. в 11:19, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.4, the last planned patch
> release for the camel-2.21.x branch with 24 improvements and bug
> fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344344&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1115/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1115/org/apache/camel/apache-camel/2.21.4/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.21.4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: Release 2.21.5 next moth

[Dmitry Volodin]

Hello, Andrea!

It's sounds very good, I will add missing fix for camel-olingo4
(CAMEL-13012) and the same fixes for camel-olingo2 also.
Thank you.

--
Best regards,
Dmitry Volodin


чт, 10 янв. 2019 г. в 15:29, Andrea Cosentino :

> Hello,
>
> I think we'll have to release a new 2.21.x release with some fix on AWS MQ.
>
> I pushed this stuff this morning.
>
> So maybe it can be worth to have another final release for 2.21
>
> WDYT?
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>

Re: [VOTE] Release Apache Camel 2.23.1

[Dmitry Volodin]

+1 (non-binding)
Thanks, Gregor!
--
Best regards,
Dmitry Volodin


сб, 12 янв. 2019 г. в 22:45, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.23.1, the first patch release
> for the camel-2.23.x branch with 33 improvements and bug fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344567&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1116/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1116/org/apache/camel/apache-camel/2.23.1/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.23.1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.23.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: [VOTE] Release Apache Camel 2.22.3

[Dmitry Volodin]

+1 (binding)
Thanks Gregor!

--
Best regards,
Dmitry Volodin


сб, 19 янв. 2019 г. в 22:22, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.3, a new patch release for
> the camel-2.22.x branch with 44 improvements and bug fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344398&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1117/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1117/org/apache/camel/apache-camel/2.22.3/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.3
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.22.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

ObjectHelper's classes in Camel 3.0.0

[Dmitry Volodin]

Hi Cammelers!

We have two ObjectHelper's classes in camel-core and camel-util.
What do you think reorganize this classes to keep just one ObjectHelper for
Object's utils only in camel-util and split to separate helpers in
camel-util for others operations like Iterators, etc?

--
Best regards,
Dmitry Volodin

Re: ObjectHelper's classes in Camel 3.0.0

[Dmitry Volodin]

Hello Andrea!

Thanks, missed this. It would be nice to create a JIRA issue if Guillaume
did't do this or I did't find correct issue...

--
Best regards,
Dmitry Volodin


вт, 22 янв. 2019 г. в 18:47, Andrea Cosentino :

> Hello Dmitry!
>
> The ObjectHelper class was splitted to isolate the helper methods using
> camel-api: those methods are under support, while the others are under util
> that can't depend on camel-api.
> Guillaume already suggested to rename one of the two classes.
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Tuesday, January 22, 2019, 4:42:26 PM GMT+1, Dmitry Volodin <
> dmvo...@gmail.com> wrote:
>
>
>
>
>
> Hi Cammelers!
>
> We have two ObjectHelper's classes in camel-core and camel-util.
> What do you think reorganize this classes to keep just one ObjectHelper for
> Object's utils only in camel-util and split to separate helpers in
> camel-util for others operations like Iterators, etc?
>
> --
> Best regards,
> Dmitry Volodin
>

Re: Google Summer of Code 2019 is coming

[Dmitry Volodin]

Hello All!

As idea to optimize a spend time, we can communicate with members who wants
to be volunteers review some already open JIRA (for New Feature,
Improvement and Wish type and no related to new Camel 3.0.0 code, mostly
for new components and components improvements) issues and/or probably
Camel K issues marked with help wanted
<https://github.com/apache/camel-k/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22>)
and marked them with GSoK2019 and mentor labels. I can spent some time for
this but it could be better to do this task together online via some
collaboration tools. I can be a first step to define potential task, but I
don't know what we need to do further, as I don't have such experience.

--
Best regards,
Dmitry Volodin


ср, 30 янв. 2019 г. в 09:38, Zoran Regvart :

> Hi Cameleers,
> the deadline for this is tomorrow, does anyone have the ambition/time
> to mentor or at least can we identify some issues that we would like a
> student to work on?
>
> I think it would be a good opportunity to get someone
> contributing/helping/getting started with Camel 3 effort.
>
> zoran
>
> -- Forwarded message -
> From: Ulrich Stärk 
> Date: Tue, Jan 29, 2019 at 1:24 PM
> Subject: Google Summer of Code 2019 is coming
> To:
>
>
> Hello PMCs (incubator Mentors, please forward this email to your podlings),
>
> Google Summer of Code [1] is a program sponsored by Google allowing
> students to spend their summer
> working on open source software. Students will receive stipends for
> developing open source software
> full-time for three months. Projects will provide mentoring and
> project ideas, and in return have
> the chance to get new code developed and - most importantly - to
> identify and bring in new committers.
>
> The ASF will apply as a participating organization meaning individual
> projects don't have to apply separately.
>
> If you want to participate with your project we ask you to do the
> following things by no later than
> 2019-01-31 19:00 UTC (applications from organizations close a week later)
>
> 1. understand what it means to be a mentor [2].
>
> 2. record your project ideas.
>
> Just create issues in JIRA, label them with gsoc2019, and they will
> show up at [3]. Please be as
> specific as possible when describing your idea. Include the
> programming language, the tools and
> skills required, but try not to scare potential students away. They
> are supposed to learn what's
> required before the program starts.
>
> Use labels, e.g. for the programming language (java, c, c++, erlang,
> python, brainfuck, ...) or
> technology area (cloud, xml, web, foo, bar, ...).
>
> Please use the COMDEV JIRA project for recording your ideas if your
> project doesn't use JIRA (e.g.
> httpd, ooo). Contact d...@community.apache.org if you need assistance.
>
> [4] contains some additional information (will be updated for 2019
> shortly).
>
> 3. subscribe to ment...@community.apache.org; restricted to potential
> mentors, meant to be used as a
> private list - general discussions on the public
> d...@community.apache.org list as much as possible
> please). Use a recognized address when subscribing (@apache.org or one
> of your alias addresses on
> record).
>
> Note that the ASF isn't accepted as a participating organization yet,
> nevertheless you *have to*
> start recording your ideas now or we might not get accepted.
>
> Over the years we were able to complete hundreds of projects
> successfully. Some of our prior
> students are active contributors now! Let's make this year a success again!
>
> P.S.: this email is free to be shared publicly if you want to.
>
> [1] https://summerofcode.withgoogle.com/
> [2] http://community.apache.org/guide-to-being-a-mentor.html
> [3] https://s.apache.org/gsoc2019ideas
> [4] http://community.apache.org/gsoc.html
>
>
> --
> Zoran Regvart
>

Re: Google Summer of Code 2019 is coming

[Dmitry Volodin]

Hi Zoran!

I'm reviewing all open New Features and Improvements and will try to choose
something interesting and not so difficult for GSoC.
I will unassign selected if they are assigned to someone, please correct me
if some of community members are working or planning to work on selected
issues.
https://issues.apache.org/jira/browse/CAMEL-10173?jql=project%20%3D%20CAMEL%20AND%20issuetype%20in%20(Improvement%2C%20%22New%20Feature%22%2C%20Wish)%20AND%20status%20%3D%20Open%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC

--
Best regards,
Dmitry Volodin


чт, 31 янв. 2019 г. в 16:20, Zoran Regvart :

> Hi Cameleers,
> just a reminder that we were asked to nominate some issues for GSoC by
> the end of today. So if you can think of an issue in JIRA just add
> `gsoc2019` label to it. I can see that for now only the website issue
> is labeled for GSoC.
>
> zoran
>
> On Wed, Jan 30, 2019 at 2:15 PM Zoran Regvart  wrote:
> >
> > Hi Cameleers,
> > I've labeled CAMEL-11492 for the new Camel website with `gsoc2019` label.
> >
> > Along with Dimitry's suggestion I suggest that we find some issues
> > that also can be a good fit for GSoC and label them as well.
> >
> > Camel-K is something that might be interesting to a student, I'm
> > guessing we all know one or more tasks in the JIRA that can be a good
> > fit.
> >
> > From what I see we can find mentors, Andrea, Önder and Rafal and I can
> > try to find some time to help out with mentorship as well, so we can
> > rotate as co-mentors and share the load.
> >
> > Thank you all for participating :)
> >
> > zoran
> >
> > On Wed, Jan 30, 2019 at 1:09 PM Dmitry Volodin 
> wrote:
> > >
> > > Hello All!
> > >
> > > As idea to optimize a spend time, we can communicate with members who
> wants
> > > to be volunteers review some already open JIRA (for New Feature,
> > > Improvement and Wish type and no related to new Camel 3.0.0 code,
> mostly
> > > for new components and components improvements) issues and/or probably
> > > Camel K issues marked with help wanted
> > > <
> https://github.com/apache/camel-k/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22
> >)
> > > and marked them with GSoK2019 and mentor labels. I can spent some time
> for
> > > this but it could be better to do this task together online via some
> > > collaboration tools. I can be a first step to define potential task,
> but I
> > > don't know what we need to do further, as I don't have such experience.
> > >
> > > --
> > > Best regards,
> > > Dmitry Volodin
> > >
> > >
> > > ср, 30 янв. 2019 г. в 09:38, Zoran Regvart :
> > >
> > > > Hi Cameleers,
> > > > the deadline for this is tomorrow, does anyone have the ambition/time
> > > > to mentor or at least can we identify some issues that we would like
> a
> > > > student to work on?
> > > >
> > > > I think it would be a good opportunity to get someone
> > > > contributing/helping/getting started with Camel 3 effort.
> > > >
> > > > zoran
> > > >
> > > > -- Forwarded message -
> > > > From: Ulrich Stärk 
> > > > Date: Tue, Jan 29, 2019 at 1:24 PM
> > > > Subject: Google Summer of Code 2019 is coming
> > > > To:
> > > >
> > > >
> > > > Hello PMCs (incubator Mentors, please forward this email to your
> podlings),
> > > >
> > > > Google Summer of Code [1] is a program sponsored by Google allowing
> > > > students to spend their summer
> > > > working on open source software. Students will receive stipends for
> > > > developing open source software
> > > > full-time for three months. Projects will provide mentoring and
> > > > project ideas, and in return have
> > > > the chance to get new code developed and - most importantly - to
> > > > identify and bring in new committers.
> > > >
> > > > The ASF will apply as a participating organization meaning individual
> > > > projects don't have to apply separately.
> > > >
> > > > If you want to participate with your project we ask you to do the
> > > > following things by no later than
> > > > 2019-01-31 19:00 UTC (applications from organizations close a week
> later)
> > > >
> > > > 1. understand what it means to be a mentor [2].
> > > >
> > > 

Re: [VOTE] Release Camel 2.21.5

[Dmitry Volodin]

+1 (binding)
Thanks, Gregor!
--
Best regards,
Dmitry Volodin


вс, 3 февр. 2019 г. в 12:49, Gregor Zurowski :

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.5, a new patch release for
> the camel-2.21.x branch with 21 improvements and bug fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344816&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1118/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1118/org/apache/camel/apache-camel/2.21.5/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.21.5
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.5
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: [Camel-K] Moving the runtime in his own repo

[Dmitry Volodin]

+1
it's a very good idea to split different types of the code in separate repos
--
Best regards,
Dmitry Volodin


чт, 21 февр. 2019 г. в 11:32, Andrea Cosentino
:

> Hello all,
>
> We created a new repo https://github.com/apache/camel-k-runtime
>
> The aim of this repo is containing the runtime bits for Camel-k, so we may
> be able to release it as a separated entity and use it in the camel-k
> repository as dependency.
>
> We'll create a submodule in the camel-k repo until we release on central
> the 0.2.1
>
> We'll add a note on the README in camel-k docs.
>
> Any thoughts?
>
> Thanks
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>