Hi François,
Yeah, sorry to hear that. I'm also sorry that I was able to announce
this only days before the conference. Seems that the BoF sessions
can't be added until the week of FOSDEM...
zoran
On Wed, Jan 30, 2019 at 8:05 AM Francois Papon
wrote:
>
> Hi Zoran,
>
> If I wasn't so far, I will
Hi Andrea,
good idea, this has some background in the guide[1]: "ASF Members and
committers can volunteer to mentor or co-mentor proposals."
So perhaps we just need another co-mentor with Andrea.
zoran
[1] http://community.apache.org/guide-to-being-a-mentor.html
On Wed, Jan 30, 2019 at 8:18 AM
Hi,
(I am sorry I have not checked the guide yet while writing these words.)
I am not sure how much time i can spare for it but I would like to
volunteer with Andrea.
Önder
On Wed, Jan 30, 2019 at 1:29 PM Zoran Regvart wrote:
> Hi Andrea,
> good idea, this has some background in the guide[1]:
Hi,
I was once a GSoC student and I've been a GSoC mentor 5+ times. We had
great results with GSoC in OpenMRS (the project I worked on for 8 years and
continue to contribute in my free time). I strongly support signing us up
for GSoC.
I don't have much expertise with Camel code-base yet, but defi
I currently don't have that time during the week. So I'm out of game. I hope
someone would jump in
Inviato da Yahoo Mail su Android
Il mer, 30 gen, 2019 alle 12:46, Rafal Korytkowski
ha scritto: Hi,
I was once a GSoC student and I've been a GSoC mentor 5+ times. We had
great results with
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
Ca
davsclaus opened a new issue #397: Add spring-boot example in the examples
directory
URL: https://github.com/apache/camel-k/issues/397
It would be good if there was a Spring Boot @Application java file which you
can quickly demo via the new spring boot support.
---
davsclaus opened a new issue #398: Kamel CLI - Add command to view which
dependencies the pre-build context has loaded
URL: https://github.com/apache/camel-k/issues/398
So you can see which JARs are (camel components) are already in the
contexts. For example when demoing and then running t
lburgazzoli commented on issue #398: Kamel CLI - Add command to view which
dependencies the pre-build context has loaded
URL: https://github.com/apache/camel-k/issues/398#issuecomment-458938384
maybe something like ‘kubectl describe’
On Wed, 30 Jan 2019 at 08:09, Claus Ibsen wrote:
davsclaus commented on issue #398: Kamel CLI - Add command to view which
dependencies the pre-build context has loaded
URL: https://github.com/apache/camel-k/issues/398#issuecomment-458938887
Yeah a describe command would be good, and it can be used for also running
integrations to get som
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
oscerd merged pull request #396: Fixed array index out of boun that would kill
camel-k operator in case of a malformed --dependency
URL: https://github.com/apache/camel-k/pull/396
This is an automated message from the Apache
astefanutti opened a new pull request #400: Jolokia trait configuration maps
JVM agent options directly
URL: https://github.com/apache/camel-k/pull/400
This is an automated message from the Apache Git Service.
To respond to
astefanutti opened a new pull request #401: Improve error handling while
parsing Prometheus service monitor labels
URL: https://github.com/apache/camel-k/pull/401
This is an automated message from the Apache Git Service.
To
lburgazzoli commented on a change in pull request #401: Improve error handling
while parsing Prometheus service monitor labels
URL: https://github.com/apache/camel-k/pull/401#discussion_r252374130
##
File path: pkg/trait/prometheus.go
##
@@ -139,14 +146,23 @@ func (t *prom
lburgazzoli commented on a change in pull request #400: Jolokia trait
configuration maps JVM agent options directly
URL: https://github.com/apache/camel-k/pull/400#discussion_r252380594
##
File path: pkg/trait/jolokia.go
##
@@ -107,3 +139,64 @@ func (t *jolokiaTrait) Apply
lburgazzoli merged pull request #400: Jolokia trait configuration maps JVM
agent options directly
URL: https://github.com/apache/camel-k/pull/400
This is an automated message from the Apache Git Service.
To respond to the me
Hi Zoran,
Thanks for setting up the BoF. Yeah, I could show few slides and a quick
demo on bean parameter bindings.
However, I need an adapter and I'm not sure I could grab one before
departure.
So, if one could bring an HMDI female <-> VGA male adapter, or HDMI female
<-> Mini Display Port male
Hi Cameleers,
seems that GitHub actions are available on apache organization. Could
be just me but this is really exciting :)
I'm thinking we could use this for the camel-website repository,
perhaps even replacing Jenkins.
For background, there's a whole discussion over at builds@ on not
having a
It's nice to hear that. I'm quite interesting about that :)
Could you share more information about how to set up the action to
publish the website?
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Jan 31, 2019 at 5:32 AM Zoran Regvart wrote:
>
> Hi Cameleers,
> seems that GitHub action
20 matches
Mail list logo
