Re: can't remove or update a custom plugin

[Serge Huber]

I realize I forgot to answer your last question. The failure in your bundle
show not happen. I suggest you check the Karaf logs (in data/log/karaf.log
or by using the ld shell command) to see what the error was on deployment.

Regards,
  Serge

On Thu, Jan 31, 2019 at 10:14 PM Thaisa Mirely 
wrote:

> Hi everyone,
> I found a critical problem during some manual tests.
>
> The first problem is when I remove a custom plugin, it is impossible to
> remove the rules associated with Karaf / Unomi.
>
> The second scenario is, when I add a new version of the plugin, my changes
> are not applied. For example, if I make a  change in the rule condition
> that existed in the first version of the removed plugin, the changes will
> not be available in the Unomi service.
>
> *:: Steps to reproduce ::*
>
>
>- *Unomi version:* build generated from this commit
>
> https://github.com/apache/incubator-unomi/commit/26ce3c1746632ff2180f490e1f2b32b0e588af94
>- *running an instance of Unomi / ES locally*
>- inside the plugin we are using a rule with the profile merge action
>(attached in the email)
>
>
> Plugin version with the rule example_version01
>
> 0) create a sample plugin using the rule_version01 and generate a jar
>
> 1) install the plugin version copying the jar to
> unomi-1.4.0-incubating-SNAPSHOT/deploy folder
>
> 2) start Karaf/Unomi and make 2 request (payload in the file
> request_version01). It is possible to see that a single profile was
> generated.
>
> 3) remove the plugin from the
> unomi-1.4.0-incubating-SNAPSHOT/deploy folder
>
> 4) restart the cluster (system:shutdown -r)
>
> When we make a request to check the rules (http://localhost:8181/cxs/rules),
> it is possible to see that the rules of the plugin that was removed are
> still available.
>
> 5) the step 2 must be repeated
> and the behavior is the same from when the plugin was present.
>
>
> Plugin version with the rule example_version02
>
> 0) generate a new plugin by updating the rule with the file rule_version02
>
> 1) install the plugin version copying the jar to
> unomi-1.4.0-incubating-SNAPSHOT/deploy folder
>
> 2) start Karaf/Unomi and make 2 requests (payload in the file
> request_version02)
>
> The behavior is not what was expected. In this case, the merge was made
> using the name_a property instead of name_b (changes made in the new
> version of the plugin with rule_version02)
>
> Making 2 requests using request_version01, you can see the profile being
> updated as if the first version of the plugin was installed.
>
>
> Note:
> When I make a *bundle:list*, my plugin (unomi-segmenter.jar) shows a
> Failure status.
> Could someone tell me if this status is expected?
>
> [image: Screen Shot 2019-01-31 at 14.41.53.png]
>
> *OSGI lifecycle reference:*
> https://eclipsesource.com/blogs/2013/01/23/how-to-track-lifecycle-changes-of-osgi-bundles/
>
> have a nice day
>
>

Re: can't remove or update a custom plugin

[Serge Huber]

Hello Thaisa,

Thank you for your detailed post and all the data you provided.

The version number that you use in your Maven project is important here,
please see:
http://unomi.apache.org/manual/1_3_x/index.html#_deployment_and_custom_definition

Also, there are shell commands that might also help you can find them here:
http://unomi.apache.org/manual/1_3_x/index.html#_runtime_commands

As for removing rules when undeploying a plugin, this is by design for the
moment, as you might be replacing it or just deactivating it temporarily.
But maybe it could be improved to remove them in certain conditions.

You can, however, use the REST API to remove rules if you need to.

Regards,
  Serge.


On Thu, Jan 31, 2019 at 10:14 PM Thaisa Mirely 
wrote:

> Hi everyone,
> I found a critical problem during some manual tests.
>
> The first problem is when I remove a custom plugin, it is impossible to
> remove the rules associated with Karaf / Unomi.
>
> The second scenario is, when I add a new version of the plugin, my changes
> are not applied. For example, if I make a  change in the rule condition
> that existed in the first version of the removed plugin, the changes will
> not be available in the Unomi service.
>
> *:: Steps to reproduce ::*
>
>
>- *Unomi version:* build generated from this commit
>
> https://github.com/apache/incubator-unomi/commit/26ce3c1746632ff2180f490e1f2b32b0e588af94
>- *running an instance of Unomi / ES locally*
>- inside the plugin we are using a rule with the profile merge action
>(attached in the email)
>
>
> Plugin version with the rule example_version01
>
> 0) create a sample plugin using the rule_version01 and generate a jar
>
> 1) install the plugin version copying the jar to
> unomi-1.4.0-incubating-SNAPSHOT/deploy folder
>
> 2) start Karaf/Unomi and make 2 request (payload in the file
> request_version01). It is possible to see that a single profile was
> generated.
>
> 3) remove the plugin from the
> unomi-1.4.0-incubating-SNAPSHOT/deploy folder
>
> 4) restart the cluster (system:shutdown -r)
>
> When we make a request to check the rules (http://localhost:8181/cxs/rules),
> it is possible to see that the rules of the plugin that was removed are
> still available.
>
> 5) the step 2 must be repeated
> and the behavior is the same from when the plugin was present.
>
>
> Plugin version with the rule example_version02
>
> 0) generate a new plugin by updating the rule with the file rule_version02
>
> 1) install the plugin version copying the jar to
> unomi-1.4.0-incubating-SNAPSHOT/deploy folder
>
> 2) start Karaf/Unomi and make 2 requests (payload in the file
> request_version02)
>
> The behavior is not what was expected. In this case, the merge was made
> using the name_a property instead of name_b (changes made in the new
> version of the plugin with rule_version02)
>
> Making 2 requests using request_version01, you can see the profile being
> updated as if the first version of the plugin was installed.
>
>
> Note:
> When I make a *bundle:list*, my plugin (unomi-segmenter.jar) shows a
> Failure status.
> Could someone tell me if this status is expected?
>
> [image: Screen Shot 2019-01-31 at 14.41.53.png]
>
> *OSGI lifecycle reference:*
> https://eclipsesource.com/blogs/2013/01/23/how-to-track-lifecycle-changes-of-osgi-bundles/
>
> have a nice day
>
>

Re: Error requests taking long time

[Serge Huber]

Hello Diogo,

Sorry, I didn't get back to you sooner I wanted to test it locally
first and was very busy with the graduation.

If you have some step to reproduce this on a vanilla Unomi
installation sure you may create the ticket.

What I would suggest is that you also include some thread dumps while
the system is "waiting", that might be helpful to understand why that
wait is happening.

Regards,
  Serge Huber.

On Fri, Jan 25, 2019 at 11:30 AM Diogo Munaro Vieira
 wrote:
>
> Hi Serge, may I open an issue with it? The real problem here is a
> connection waiting long time with an error instead of respond fast and take
> other requests
>
> Em ter, 22 de jan de 2019 10:21, Thaisa Mirely  escreveu:
>
> > * 1) you need to run Unomi / ES locally with just one instance for each (we
> > are running in a Docker container)
> >
> >
> > *até,*
> > *energias boas para você. *
> >
> > Thaisa Mirely
> > *Thought*Works - Recife, Brazil
> >
> >
> > On Tue, Jan 22, 2019 at 9:19 AM Thaisa Mirely 
> > wrote:
> >
> > > a brief context about this problem is that it occurred when we tried to
> > > simulate a nullPointerException (we'll report it as soon as we can
> > > reproduce again)
> > >
> > > To reproduce the error that Munaro sent,
> > > 1) you need to run Unomi / ES locally using only one instance for each
> > (we
> > > are running in a docking window)
> > > 2) we removed some body properties from the request to create a profile
> > > via the API.
> > >
> > >
> > > have a nice day
> > >
> > > *Thought*Works - Recife, Brazil
> > >
> > >
> > > On Tue, Jan 22, 2019 at 5:28 AM Serge Huber  wrote:
> > >
> > >> Hello Diogo,
> > >>
> > >> From the exception, it seems more like there is a timeout while
> > >> waiting for the body of the request. Are you sure the client is
> > >> properly committing the request ? What kind of client are you using ?
> > >>
> > >> Regards,
> > >>   Serge...
> > >>
> > >>
> > >>
> > >> On Mon, Jan 21, 2019 at 10:15 PM Diogo Munaro Vieira
> > >>  wrote:
> > >> >
> > >> > Hi friends!
> > >> >
> > >> > When we send an event with wrong body it takes about 2 seconds to
> > >> respond
> > >> > timeout as error instead of right error message. Do you know about it?
> > >> >
> > >> >
> > >> > HTTP ERROR 500
> > >> > > Problem accessing /context.json. Reason:
> > >> > > Server ErrorCaused
> > >> > > by:java.io.IOException:
> > >> java.util.concurrent.TimeoutException:
> > >> > > Idle timeout expired: 30005/3 ms
> > >> > > at
> > >> > >
> > >>
> > org.eclipse.jetty.server.HttpInput$ErrorState.noContent(HttpInput.java:852)
> > >> > > at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:191)
> > >> > > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> > >> > > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> > >> > > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> > >> > > at java.io.InputStreamReader.read(InputStreamReader.java:184)
> > >> > > at java.io.BufferedReader.fill(BufferedReader.java:161)
> > >> > > at java.io.BufferedReader.readLine(BufferedReader.java:324)
> > >> > > at java.io.BufferedReader.readLine(BufferedReader.java:389)
> > >> > > at org.apache.unomi.web.HttpUtils.getPayload(HttpUtils.java:154)
> > >> > > at
> > >> org.apache.unomi.web.ContextServlet.service(ContextServlet.java:112)
> > >> > > at
> > >> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
> > >> > > at
> > >> > >
> > >>
> > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584)
> > >> > > at
> > >> > >
> > >>
> > org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)
> > >> > > at
> > >> > >
> > >>
> > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> > >> > > at
> > >> > >
> > >>
> > org.eclipse.jetty.security.Se

Re: Unomi incubator report february 2019

[Serge Huber]

Cool, can you put it up on the Wiki and sign-off JB please ? I don't
have the kharma anyway :)

cheers,
   Serge...

On Fri, Jan 25, 2019 at 7:38 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> it looks good to me, thanks.
>
> Regards
> JB
>
> On 24/01/2019 20:49, Serge Huber wrote:
> > Hello,
> >
> > As it seems with the Podling Name search process the graduation is
> > taking a little longer than expected I have prepared a report for
> > February 2019. I'm sure it's not perfect so please don't hesitate to
> > comment.
> >
> > Thanks & Regards,
> >   Serge...
> >
> > Apache Unomi February 2019 Report
> >
> > Unomi
> >
> > Unomi is a reference implementation of the OASIS Context Server 
> > specification
> > currently being worked on by the OASIS Context Server Technical Committee. 
> > It
> > provides a high-performance user profile and event tracking server.
> >
> > Unomi has been incubating since 2015-10-05.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Conclude IPMC graduation vote
> >   2. Complete Podling Name Search
> >   3. Submit graduation to Apache Board once the IPMC vote and PNS are 
> > completed.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > No
> >
> > How has the community developed since the last report?
> >
> > We are seeing more activity on the relatively new user mailing list
> > and continuing to support existing community members finalize some
> > large projects.
> >
> > How has the project developed since the last report?
> >
> > We have now started the graduation process and hope to complete it in
> > the next month.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [X ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2018-09-10
> >
> > When were the last committers or PPMC members elected?
> >
> > 2018-09-19
> >
> > Have your mentors been helpful and responsive or are things falling
> > through the cracks? In the latter case, please list any open issues
> > that need to be addressed.
> >
> > Our mentor is very helpful and responsive and is doing his best to
> > assist the project when asked. He is alone but the project has now
> > matured and is less dependent on mentors as it is in the graduation
> > process.
> >
> > Signed-off-by:
> >
> >   [ ](unomi) Jean-Baptiste Onofre
> >  Comments:
> >
> > IPMC/Shepherd notes:
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Unomi incubator report february 2019

[Serge Huber]

Hello,

As it seems with the Podling Name search process the graduation is
taking a little longer than expected I have prepared a report for
February 2019. I'm sure it's not perfect so please don't hesitate to
comment.

Thanks & Regards,
  Serge...

Apache Unomi February 2019 Report

Unomi

Unomi is a reference implementation of the OASIS Context Server specification
currently being worked on by the OASIS Context Server Technical Committee. It
provides a high-performance user profile and event tracking server.

Unomi has been incubating since 2015-10-05.

Three most important issues to address in the move towards graduation:

  1. Conclude IPMC graduation vote
  2. Complete Podling Name Search
  3. Submit graduation to Apache Board once the IPMC vote and PNS are completed.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No

How has the community developed since the last report?

We are seeing more activity on the relatively new user mailing list
and continuing to support existing community members finalize some
large projects.

How has the project developed since the last report?

We have now started the graduation process and hope to complete it in
the next month.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-09-10

When were the last committers or PPMC members elected?

2018-09-19

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Our mentor is very helpful and responsive and is doing his best to
assist the project when asked. He is alone but the project has now
matured and is less dependent on mentors as it is in the graduation
process.

Signed-off-by:

  [ ](unomi) Jean-Baptiste Onofre
 Comments:

IPMC/Shepherd notes:

Re: Error requests taking long time

[Serge Huber]

Hello Diogo,

>From the exception, it seems more like there is a timeout while
waiting for the body of the request. Are you sure the client is
properly committing the request ? What kind of client are you using ?

Regards,
  Serge...



On Mon, Jan 21, 2019 at 10:15 PM Diogo Munaro Vieira
 wrote:
>
> Hi friends!
>
> When we send an event with wrong body it takes about 2 seconds to respond
> timeout as error instead of right error message. Do you know about it?
>
>
> HTTP ERROR 500
> > Problem accessing /context.json. Reason:
> > Server ErrorCaused
> > by:java.io.IOException: java.util.concurrent.TimeoutException:
> > Idle timeout expired: 30005/3 ms
> > at
> > org.eclipse.jetty.server.HttpInput$ErrorState.noContent(HttpInput.java:852)
> > at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:191)
> > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> > at java.io.InputStreamReader.read(InputStreamReader.java:184)
> > at java.io.BufferedReader.fill(BufferedReader.java:161)
> > at java.io.BufferedReader.readLine(BufferedReader.java:324)
> > at java.io.BufferedReader.readLine(BufferedReader.java:389)
> > at org.apache.unomi.web.HttpUtils.getPayload(HttpUtils.java:154)
> > at org.apache.unomi.web.ContextServlet.service(ContextServlet.java:112)
> > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
> > at
> > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584)
> > at
> > org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)
> > at
> > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> > at
> > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> > at
> > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> > at
> > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> > at
> > org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:296)
> > at
> > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
> > at
> > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> > at
> > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> > at
> > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> > at
> > org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)
> > at
> > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> > at org.eclipse.jetty.server.Server.handle(Server.java:539)
> > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)
> > at
> > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
> > at
> > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
> > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
> > at
> > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> > at
> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> > at
> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
> > at
> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
> > at
> > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
> > at
> > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
> > at java.lang.Thread.run(Thread.java:748)
> > Caused by: java.util.concurrent.TimeoutException: Idle timeout expired:
> > 30005/3 ms
> > at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:166)
> > at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
> > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > at
> > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> > at
> > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> > at
> > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> > ... 1 more
> > Suppressed: java.lang.Throwable: HttpInput failure
> > at org.eclipse.jetty.server.HttpInput.failed(HttpInput.java:648)
> > at
> > org.eclipse.jetty.server.HttpConnection$BlockingReadCallback.failed(HttpConnection.java:606)
> > at org.eclipse.jetty.io.FillInterest.onFail(FillInterest.java:138)
> > at
> > org.eclipse.jetty.io.AbstractEndPoint.onI

Re: [ANNOUNCE] Apache Roadshow Chicago, Call for Presentations

[Serge Huber]

Hello Michael,

Yes that would be fantastic. For the moment I have no plans for those
dates but you never know.

Anyway please don't hesitate to ask for anything, let's help you make
Unomi shine!

Regards,
  Serge...


Serge Huber
CTO & Co-Founder

T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
jahia.com
SKYPE | LINKEDIN | TWITTER | VCARD


> JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia is a 
> leading User Experience Platform (UXP) for Digital Transformation.


On Sun, Jan 20, 2019 at 5:28 PM Francois Papon
 wrote:
>
> Thanks Michael for talking about Unomi!
>
> Don't hesitate to tell us if you need help to prepare your demo ;)
>
> Regards,
>
> François Papon
> fpa...@apache.org
>
> Le 20/01/2019 à 20:07, Michael Ghen a écrit :
> > Cool, thanks for the heads up! I had the opportunity to attend that session.
> >
> > Looks like CFP is open until the 15th of February so I will write up an
> > abstract and share it here.
> >
> > On Sun, Jan 20, 2019 at 1:50 AM Jean-Baptiste Onofré 
> > wrote:
> >
> >> Hi Michael,
> >>
> >> FYI, Serge and I did a demo at last ApacheCon. If you need some
> >> material, please let us know.
> >>
> >> Unfortunately, I won't be in the US in May.
> >>
> >> Regards
> >> JB
> >>
> >> On 20/01/2019 07:38, Michael Ghen wrote:
> >>> Thanks for sharing Trevor! I used to live in Chicago, May is a great time
> >>> of year to be there.
> >>>
> >>> I was considering submitting something about getting started with Unomi,
> >>> has anyone else looked at this? Is this something I could do?
> >>>
> >>> I could give a demo running Unomi locally and show how to use the
> >>> endpoints. I noticed that at my company we already put most of the
> >> customer
> >>> profile data into ES and we make just a small tweak to that to get Unomi
> >>> running. The rules feature is really liked at my company. I could
> >> probably
> >>> share about that too. I'm not sure I got the whole plugin thing figured
> >> out
> >>> yet but I might by May.
> >>>
> >>> On Tue, Jan 15, 2019 at 9:44 AM Trevor Grant 
> >> wrote:
> >>>> Hello Devs!
> >>>>
> >>>>
> >>>> You're receiving this email because you are subscribed to one or more
> >>>> Apache developer email lists.
> >>>>
> >>>> I’m writing to let you know about an exciting event coming to the
> >> Chicago
> >>>> area: The Apache Roadshow Chicago.  It will be held May 13th and 14th at
> >>>> three bars in the Logan Square neighborhood (Revolution Brewing, The
> >>>> Native, and the Radler).
> >>>>
> >>>> There will be six tracks:
> >>>>
> >>>>-
> >>>>
> >>>>Apache in Adtech:  Tell us how Apache works in your advertising stack
> >>>>-
> >>>>
> >>>>Apache in Fintech: Tell us how Apache works in your finance/insurance
> >>>>business
> >>>>-
> >>>>
> >>>>Apache in Startups: Tell us how you’re using Apache in your startup
> >>>>-
> >>>>
> >>>>Diversity in Apache: How do we increase and encourage diversity in
> >>>>Apache and tech fields overall?
> >>>>-
> >>>>
> >>>>Made in Chicago: Apache related things made by people in Chicago that
> >>>>don’t fall into other buckets
> >>>>-
> >>>>
> >>>>Project Shark Tank: Do you want more developers or users for your
> >> Apache
> >>>>project? Come here and pitch it!
> >>>>
> >>>>
> >>>> This is an exciting chance to learn about how Apache Projects are in
> >> use in
> >>>> production around Chicago, how business users make the decision to use
> >>>> Apache projects, to learn about exciting new projects that want help
> >> from
> >>>> developers like you, and how/why to increase diversity in tech and IT.
> >>>>
> >>>> If you have any use cases of Apache products in Adtech, Fintech, or
> >>>> Startups; if you represent a minority working in tech and have
> >> perspectives
> >>>> to share, if you live in the Chicagoland area and want to highlight some
> >>>> work you’ve done on an Apache project, or if you want to get other
> >> people
> >>>> excited to come work on your project, then please submit a CFP before
> >> the
> >>>> deadline on February 15th!
> >>>>
> >>>> Tickets to the Apache Roadshow Chicago are $100; speakers will get a
> >>>> complimentary ticket.
> >>>>
> >>>> We’re looking forward to reading your submissions and seeing you there
> >> on
> >>>> May 13-14!
> >>>>
> >>>> Sincerely,
> >>>>
> >>>> Trevor Grant
> >>>>
> >>>> https://www.apachecon.com/chiroadshow19/cfp.html
> >>>>
> >>>> https://www.apachecon.com/chiroadshow19/register.html
> >>>>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>

Re: [NOTICE] Mandatory migration of git repos to gitbox.apache.org - three weeks left!

[Serge Huber]

Thanks you so much JB & François for taking care of this !

Regards,
  Serge...

On Thu, Jan 17, 2019 at 6:51 AM Francois Papon
 wrote:
>
> Hi,
>
> I updated the Jenkins job to Gitbox and add build badges on the README.md.
>
> Regards,
>
> François Papon
> fpa...@apache.org
>
> Le 16/01/2019 à 23:35, Francois Papon a écrit :
> > Thanks JB!
> >
> > Regards,
> >
> > François Papon
> > fpa...@apache.org
> >
> > Le 16/01/2019 à 23:28, Jean-Baptiste Onofré a écrit :
> >> Hi guys,
> >>
> >> I did the move to gitbox:
> >>
> >> https://gitbox.apache.org/repos/asf?p=incubator-unomi.git
> >>
> >> You just have to update your remote and you are ready to go.
> >>
> >> FYI, thanks to gitbox, we now have github integration (with merge button
> >> support).
> >>
> >> Regards
> >> JB
> >>
> >> On 15/01/2019 09:20, Jean-Baptiste Onofré wrote:
> >>> Hi guys,
> >>>
> >>> I'm volunteer to deal with gitbox migration. It's straight forward and
> >>> pretty fast.
> >>>
> >>> No objection ?
> >>>
> >>> Regards
> >>> JB
> >>>
> >>> On 15/01/2019 08:50, Apache Infrastructure Team wrote:
>  Hello, unomi folks.
>  As stated earlier in 2018, and reiterated two weeks ago, all git
>  repositories must be migrated from the git-wip-us.apache.org URL to
>  gitbox.apache.org, as the old service is being decommissioned. Your
>  project is receiving this email because you still have repositories on
>  git-wip-us that needs to be migrated.
> 
>  The following repositories on git-wip-us belong to your project:
>   - incubator-unomi.git
> 
> 
>  We are now entering the remaining three weeks of the mandated
>  (coordinated) move stage of the roadmap, and you are asked to please
>  coordinate migration with the Apache Infrastructure Team before February
>  7th. All repositories not migrated on February 7th will be mass migrated
>  without warning, and we'd appreciate it if we could work together to
>  avoid a big mess that day :-).
> 
>  As stated earlier, moving to gitbox means you will get full write access
>  on GitHub as well, and be able to close/merge pull requests and much
>  more. The move is mandatory for all Apache projects using git.
> 
>  To have your repositories moved, please follow these steps:
> 
>  - Ensure consensus on the move (a link to a lists.apache.org thread will
>    suffice for us as evidence).
>  - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> 
>  Your migration should only take a few minutes. If you wish to migrate
>  at a specific time of day or date, please do let us know in the ticket,
>  otherwise we will migrate at the earliest convenient time.
> 
>  There will be redirects in place from git-wip to gitbox, so requests
>  using the old remote origins should still work (however we encourage
>  people to update their remotes once migration has completed).
> 
>  As always, we appreciate your understanding and patience as we move
>  things around and work to provide better services and features for
>  the Apache Family.
> 
>  Should you wish to contact us with feedback or questions, please do so
>  at: us...@infra.apache.org.
> 
> 
>  With regards,
>  Apache Infrastructure
> 

Re: generate Unomi 1.4.0-SNAPSHOT

[Serge Huber]

Hello Thaisa,

Could you describe the issues you were facing when building the
SNAPSHOT ? The most common one is tests that don't work properly but
you could also prevent them from running as these failures are not
systematic (it's a timing issue that still needs to be correct) but
doesn't affect in any mean the quality of the release.

Regards,
  Serge...


On Thu, Jan 17, 2019 at 7:48 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> SNAPSHOT tag doesn't make sense: it's also the latest revision of a
> branch (master most of the time).
>
> You can find SNAPSHOT build on repository.apache.org (snapshot repo) or
> you can ever build unomi yourself (from master) to have your own SNAPSHOT.
>
> Regards
> JB
>
> On 17/01/2019 03:45, Thaisa Mirely wrote:
> > Hello everyone,
> > I am now working on verifying Unomi performance for integration with my
> > project data ecosystem.
> > We recently saw an important bug fix related to the merge properties in the
> > profiles.
> > We tried to use the master version to generate an internal version of Unomi
> > for use in performance testing, but generating that version was a bit
> > difficult and we had some problems.
> > So, my question is whether it would be possible to generate a SNAPSHOT
> > version of the API, with the merge fix, being made available in the maven
> > repository?
> > Also, having a SNAPSHOT tag in github would be a good approach =]
> >
> > thanks,
> > have a nice day.
> >
> > *Thought*Works - Recife, Brazil
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: [NOTICE] Mandatory migration of git repos to gitbox.apache.org - three weeks left!

[Serge Huber]

Big +1,

Thanks JB for doing this because I don't have the kharma (yet) to do it !

Regards,
  Serge...

On Tue, Jan 15, 2019 at 10:24 AM Francois Papon
 wrote:
>
> +1
>
> Thanks JB!
>
> Regards,
>
> François Papon
> fpa...@apache.org
>
> Le 15/01/2019 à 12:20, Jean-Baptiste Onofré a écrit :
> > Hi guys,
> >
> > I'm volunteer to deal with gitbox migration. It's straight forward and
> > pretty fast.
> >
> > No objection ?
> >
> > Regards
> > JB
> >
> > On 15/01/2019 08:50, Apache Infrastructure Team wrote:
> >> Hello, unomi folks.
> >> As stated earlier in 2018, and reiterated two weeks ago, all git
> >> repositories must be migrated from the git-wip-us.apache.org URL to
> >> gitbox.apache.org, as the old service is being decommissioned. Your
> >> project is receiving this email because you still have repositories on
> >> git-wip-us that needs to be migrated.
> >>
> >> The following repositories on git-wip-us belong to your project:
> >>  - incubator-unomi.git
> >>
> >>
> >> We are now entering the remaining three weeks of the mandated
> >> (coordinated) move stage of the roadmap, and you are asked to please
> >> coordinate migration with the Apache Infrastructure Team before February
> >> 7th. All repositories not migrated on February 7th will be mass migrated
> >> without warning, and we'd appreciate it if we could work together to
> >> avoid a big mess that day :-).
> >>
> >> As stated earlier, moving to gitbox means you will get full write access
> >> on GitHub as well, and be able to close/merge pull requests and much
> >> more. The move is mandatory for all Apache projects using git.
> >>
> >> To have your repositories moved, please follow these steps:
> >>
> >> - Ensure consensus on the move (a link to a lists.apache.org thread will
> >>   suffice for us as evidence).
> >> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> >>
> >> Your migration should only take a few minutes. If you wish to migrate
> >> at a specific time of day or date, please do let us know in the ticket,
> >> otherwise we will migrate at the earliest convenient time.
> >>
> >> There will be redirects in place from git-wip to gitbox, so requests
> >> using the old remote origins should still work (however we encourage
> >> people to update their remotes once migration has completed).
> >>
> >> As always, we appreciate your understanding and patience as we move
> >> things around and work to provide better services and features for
> >> the Apache Family.
> >>
> >> Should you wish to contact us with feedback or questions, please do so
> >> at: us...@infra.apache.org.
> >>
> >>
> >> With regards,
> >> Apache Infrastructure
> >>

[RESULT][VOTE] [TAKE2] Apache Unomi Top Level Graduation

[Serge Huber]

Hello,

The voting is now closed.

Here are the results for the vote to graduate Apache Unomi to a
top-level project:

7 binding votes +1:

- Thomas Draier
- Serge Huber
- Jean-Baptiste Onofré
- François Papon
- Kevan Jahanshahi
- David Griffon
- Bertrand Delacretaz

1 non-binding vote +1:
- Damien Gaillard

No 0 or -1.

The proposal to graduate Apache Unomi to a top-level project has been
approved by the team.
The next step is to start a vote in the IPMC.

You can find the vote thread here [1].

Regards,
  Serge...

[1] 
https://lists.apache.org/thread.html/095d94557746fdd1b8d33f87feab939c70abbf22fd732980a2e7c59e@%3Cdev.unomi.apache.org%3E

Re: [VOTE] [TAKE2] Apache Unomi Top Level Graduation

[Serge Huber]

Here's my

+1 (binding)

Regards,
  Serge...

On Tue, Jan 8, 2019 at 3:47 PM Serge Huber  wrote:
>
> Hi everyone,
>
> Please vote on the draft resolution proposed by the Apache Unomi PPMC
> below, which establishes Apache Unomi as a new top-level project at
> the Apache Software Foundation, as follows:
>
> [ ] +1, Graduate Apache Unomi from the Incubator.
> [ ] +0, Don't care.
> [ ] -1, Don't graduate Apache Unomi from the Incubator because...
>
> Before voting, please see the full text of the draft resolution below,
> and vote only after you feel ready to do so. You can also find the
> maturity model assessment here [2]. The vote will be open for at least
> 72 hours. This is a procedural vote [2]; it is adopted by a simple
> majority of qualified votes (with no minimum).
>
> If approved by the Apache Unomi PPMC, the proposed resolution will be
> submitted to the Apache Incubator PMC for their consideration.
>
> Thank you!
> Serge
>
> [1] http://apache.org/foundation/voting.html
> [2] https://unomi.incubator.apache.org/community-maturity-model-report.html
>
> The full-text of the draft resolution proposed by the Apache Unomi PPMC:
>
> Establish the Apache Unomi Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to providing a reference implementation of the OASIS Customer
> Data Platform specification currently being worked on by the OASIS
> Context Server Technical Committee. It provides a high-performance user
> profile and event tracking server.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Unomi Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Unomi Project be and hereby is responsible for
> the creation and maintenance of software related to providing a
> reference implementation of the OASIS Customer Data Platform
> specification currently being worked on by the OASIS Context Server
> Technical Committee. It provides a high-performance user profile and
> event tracking server; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Unomi" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Unomi
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Unomi Project;
> and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Unomi Project:
>
>  * David Griffon
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Kevan Jahanshahi 
>  * Serge Huber  
>  * Thomas Draier
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber be appointed to
> the office of Vice President, Apache Unomi, to serve in accordance with
> and subject to the direction of the Board of Directors and the Bylaws of
> the Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Unomi PMC be and hereby is tasked with
> the creation of a set of bylaws intended to encourage open development
> and increased participation in the Apache Unomi Project; and be it
> further
>
> RESOLVED, that the Apache Unomi Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Unomi podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Unomi podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

[VOTE] [TAKE2] Apache Unomi Top Level Graduation

[Serge Huber]

Hi everyone,

Please vote on the draft resolution proposed by the Apache Unomi PPMC
below, which establishes Apache Unomi as a new top-level project at
the Apache Software Foundation, as follows:

[ ] +1, Graduate Apache Unomi from the Incubator.
[ ] +0, Don't care.
[ ] -1, Don't graduate Apache Unomi from the Incubator because...

Before voting, please see the full text of the draft resolution below,
and vote only after you feel ready to do so. You can also find the
maturity model assessment here [2]. The vote will be open for at least
72 hours. This is a procedural vote [2]; it is adopted by a simple
majority of qualified votes (with no minimum).

If approved by the Apache Unomi PPMC, the proposed resolution will be
submitted to the Apache Incubator PMC for their consideration.

Thank you!
Serge

[1] http://apache.org/foundation/voting.html
[2] https://unomi.incubator.apache.org/community-maturity-model-report.html

The full-text of the draft resolution proposed by the Apache Unomi PPMC:

Establish the Apache Unomi Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to providing a reference implementation of the OASIS Customer
Data Platform specification currently being worked on by the OASIS
Context Server Technical Committee. It provides a high-performance user
profile and event tracking server.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Unomi Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache Unomi Project be and hereby is responsible for
the creation and maintenance of software related to providing a
reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server
Technical Committee. It provides a high-performance user profile and
event tracking server; and be it further

RESOLVED, that the office of "Vice President, Apache Unomi" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Unomi
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Unomi Project;
and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Unomi Project:

 * David Griffon
 * Francois Papon   
 * Jean-Baptiste Onofré 
 * Kevan Jahanshahi 
 * Serge Huber  
 * Thomas Draier

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber be appointed to
the office of Vice President, Apache Unomi, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws of
the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be it further

RESOLVED, that the initial Apache Unomi PMC be and hereby is tasked with
the creation of a set of bylaws intended to encourage open development
and increased participation in the Apache Unomi Project; and be it
further

RESOLVED, that the Apache Unomi Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator Unomi podling; and
be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Unomi podling encumbered upon the Apache Incubator PMC are hereafter
discharged.

Re: Happy new year

[Serge Huber]

Yes there is a user list, should have maybe announced it in the dev
list, forgot to do that :)

Regards,
  Serge...

On Wed, Jan 2, 2019 at 1:32 PM Diogo Munaro Vieira
 wrote:
>
> Wow, there is an user list! Happy New year!!
>
> Em qua, 2 de jan de 2019 01:47, Francois Papon  escreveu:
>
> > Happy new year to all the Apache Unomi users!
> >
> > Let's start this new year with the top level graduation :)
> >
> > Regards,
> >
> > --
> > François Papon
> > fpa...@apache.org
> >
> >

Re: EventCollector doesn't create profiles

[Serge Huber]

Hello Diogo,

You are right the EventCollector servlet doesn't create the profile,
only the ContextServlet does. But you can send events to the
ContextServlet too so in theory you could do it all with a single
request.

Actually I'm wondering if the EventCollectorServlet is actually still useful ?

As to the updated result, the value corresponds to the following constants:

/**
 * No change occurred following an event being handled.
 */
int NO_CHANGE = 0;
/**
 * The associated session was updated following an event being handled.
 */
int SESSION_UPDATED = 1;
/**
 * The associated profile was updated following an event being handled.
 */
int PROFILE_UPDATED = 2;

Regards,
  Serge...

On Fri, Dec 28, 2018 at 3:15 PM Diogo Munaro Vieira
 wrote:
>
> Hi friends, I'm using event collector as documentation example
> :
>
> curl -H "Content-Type: application/json" -X POST -d
> '{"events":[{"eventType":"view","scope":
> "example","source":{"itemType": "site","scope":"example","itemId":
> "mysite"},"target":{"itemType":"page","scope":"example","itemId":"homepage","properties":{"pageInfo":{"referringURL":""]}'
> http://localhost:8181/eventcollector?sessionId=1234
>
> But when I access https://localhost:9443/cxs/profiles/count then no profile
> was created.
>
> I'm using Unomi 1.3.0
>
> Another question about EventCollector: What's the difference between
> response with "updated: 0" or "updated: 1"?
>
> Thank you guys!
>
> --
> Diogo Munaro Vieira
>
> ---
> Big Data
> Ramal: 6866
>
> http://diogomunaro.com
> (21) 98656-0745

[jira] [Commented] (UNOMI-216) Configure Unomi by editing one configuration file & read env variables for Docker compatibility

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726846#comment-16726846
 ] 

Serge Huber commented on UNOMI-216:
---

Added a link to the Apache Karaf issue that could help simplify this greatly 
using system properties to override configadmin properties.

> Configure Unomi by editing one configuration file & read env variables for 
> Docker compatibility
> ---
>
> Key: UNOMI-216
> URL: https://issues.apache.org/jira/browse/UNOMI-216
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.0.0-incubating, 1.1.0-incubating, 1.2.0-incubating, 
> 1.3.0-incubating, 1.4.0-incubating
>Reporter: Serge Huber
>Assignee: Serge Huber
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The idea here is to make it easy to "override" common configuration 
> properties in Apache Unomi by modifying a single configuration file. Of 
> course this type of deployment is focused on "static" deployments, not 
> deployment where the configuration admin is used to dynamically update 
> configuration. Also this will address the need of Docker containers that pass 
> configuration through environment variables.
> As a consequence, default Unomi properties should be "placeholdered", with 
> default values
> Here is the section in the Karaf documentation about configuration, including 
> environment variables references : 
> [http://karaf.apache.org/manual/latest/#_configuration_3]
> "Properties can be referenced inside configuration files using the syntax 
> {{$\{}}}. Default and alternate values can be specified using 
> {{$\{:-}}} and {{$\{:+}}} 
> syntaxes respectively."
> "Environment variables can be referenced inside configuration files using the 
> syntax {{$\{env:}}} (e.g.{{property=$\{env:FOO}}} will set "property" 
> to the value of the enviroment variable "FOO"). Default and alternate values 
> can be defined for them as well using the same syntax as above." 
> Some difficulty might come from configuration files such as the Hazelcast XML 
> configuration file that can only reference system properties, so we might 
> have to setup the placeholders in the custom.system.properties file.
> This story includes modifications to the documentation to use this 
> centralized file, both on the Unomi website.
> Migration will be handle through documentation as well, indicating where the 
> properties must be moved.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (UNOMI-66) Integrate Apache Kafka

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726061#comment-16726061
 ] 

Serge Huber commented on UNOMI-66:
--

Can't wait JB :) 

> Integrate Apache Kafka
> --
>
> Key: UNOMI-66
> URL: https://issues.apache.org/jira/browse/UNOMI-66
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Reporter: Serge Huber
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> It would be really great to integrate Apache Kafka into Apache Unomi so that 
> we can push event data and other "heavy" operations into its messaging 
> systems and therefore make it easier to decouple some large scale operations 
> that might require a lot of processing power such as large segment updates, 
> etc...
> An interesting idea would be to put Kafka in "front" of Unomi to absorb the 
> traffic and then clients could use something like the [Kafka REST Proxy 
> |https://docs.confluent.io/1.0/kafka-rest/docs/intro.html] to insert events 
> into Unomi.
> This would also make it a lot easier to integrate with BigData systems such 
> as Apache Spark, Hadoop or others.
> We might want at the same time to see if we can define a mechanism to get the 
> status of long-running operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (UNOMI-66) Integrate Apache Kafka

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724399#comment-16724399
 ] 

Serge Huber commented on UNOMI-66:
--

Parts of it were done, the profile import/export supports Kafka.

On the "front-end" part I think JB has a prototype but it hasn't been 
committed. 

At least there is nothing committed yet on the front-end part, so if you have a 
contribution you would like to share I could look at it and let you know 
because it is definitely something that is interesting to a lot of people.

Regards,
  Serge... 

> Integrate Apache Kafka
> --
>
> Key: UNOMI-66
> URL: https://issues.apache.org/jira/browse/UNOMI-66
> Project: Apache Unomi
>  Issue Type: Improvement
>      Components: core
>Reporter: Serge Huber
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> It would be really great to integrate Apache Kafka into Apache Unomi so that 
> we can push event data and other "heavy" operations into its messaging 
> systems and therefore make it easier to decouple some large scale operations 
> that might require a lot of processing power such as large segment updates, 
> etc...
> An interesting idea would be to put Kafka in "front" of Unomi to absorb the 
> traffic and then clients could use something like the [Kafka REST Proxy 
> |https://docs.confluent.io/1.0/kafka-rest/docs/intro.html] to insert events 
> into Unomi.
> This would also make it a lot easier to integrate with BigData systems such 
> as Apache Spark, Hadoop or others.
> We might want at the same time to see if we can define a mechanism to get the 
> status of long-running operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [CANCEL] Re: [VOTE] Apache Unomi Top Level Project Graduation

[Serge Huber]

You can find his answer here [1].

Depending on how you interpret it it means that either the Whimsy
roster was not up to date or that there are PPMC members but he did
say some things that added to the confusion I think.

Looking back and including the discussion in the incubator general
list, I think we should simply add to the PPMC (and PMC) some of the
initial committers that are still (potentially) active on the project,
these are :

Thomas Draier, tdra...@apache.org,
Kevan Jahanshahi, jke...@apache.org,
David Griffon, dgrif...@apache.org,

That should bring the PMC to a better roster, and they are all initial
committers on the Apache Unomi incubation proposal [2]. Other initial
committers are less active and some don't have an Apache ID properly
registered (for various reasons) so for simplicity reasons I filtered
the list, but we could also go with all the ones that have a valid ID
at this point. I'll leave that to you guys the mentors to let me know
what is better :)

Thanks for you help,
Regards,
  Serge...

[1] 
https://lists.apache.org/thread.html/f683800e06b1ecbd2fcf54f0ec556b164b28480e4e4b630724367b0d@%3Cdev.unomi.apache.org%3E
[2] http://incubator.apache.org/projects/unomi.html

On Mon, Dec 17, 2018 at 3:23 PM Bertrand Delacretaz
 wrote:
>
> On Mon, Dec 17, 2018 at 3:14 PM Jean-Baptiste Onofré  
> wrote:
> > ...Justin said we should have a NOTICE
> > even for the initial committers
>
> Ouch. If you have a link to that statement I'm happy to fight it where
> it happened ;-)
>
> -Bertrand

[CANCEL] Re: [VOTE] Apache Unomi Top Level Project Graduation

[Serge Huber]

Hello,

I am officially canceling the vote to be able to start the process of
adding more PPMC members through a round of votes for people that
should have already been official PPMC members but as the NOTICEs were
never sent we will use the official process of voting them in.

It would be nice if the mentors could identify asap any other
outstanding issues that could prevent graduation as I might have
missed something?

Regards,
  Serge...

On Sat, Dec 15, 2018 at 3:24 PM Serge Huber  wrote:
>
> Ok, what I propose is that we cancel the graduation vote and that we
> start votes to "officially add" more PPMC members (that are depending
> on the point of view already PPMC members but let's make it more
> official) right away. It should be acceptable to do these in parallel
> I hope Bertrand ?
>
> If not we can also do them sequentially but that will take a lot more
> time to get ready for graduation.
>
> Thanks for the feedback and the help, hopefully, we'll get there soon :)
>
> cheers,
>   Serge...
> On Sat, Dec 15, 2018 at 11:34 AM Jean-Baptiste Onofré  
> wrote:
> >
> > Hi Bertrand,
> >
> > Since the beginning, Unomi has committer == PPMC. So, up to last week,
> > we had ~ 10 PPMC.
> >
> > However, even if committer == PPMC since the beginning of the Unomi
> > incubation, we forgot to send the NOTICE.
> > Justin was very strict about that, and so, we updated the PPMC with
> > mentor and the one for whom we sent a NOTICE.
> >
> > It's really a pity, and I would kindly ask to re-add all committer as
> > PPMC as we had in the past.
> >
> > Thoughts ?
> >
> > Regards
> > JB
> >
> > On 15/12/2018 10:27, Bertrand Delacretaz wrote:
> > > Hi,
> > >
> > > On Fri, Dec 14, 2018 at 5:58 PM Serge Huber  wrote:
> > >> RESOLVED, that the persons listed immediately below be and hereby are
> > >> appointed to serve as the initial members of the Apache Unomi Project...
> > >
> > > I don't think 3 PMC members is enough. That's the bare minimum for a
> > > viable project, so if one of them becomes unavailable you're stuck.
> > >
> > > I think we've been graduating projects with 5 PMC members in the past,
> > > IMO that would be a minimum.
> > >
> > > -Bertrand
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com

Re: [VOTE] Apache Unomi Top Level Project Graduation

[Serge Huber]

Ok, what I propose is that we cancel the graduation vote and that we
start votes to "officially add" more PPMC members (that are depending
on the point of view already PPMC members but let's make it more
official) right away. It should be acceptable to do these in parallel
I hope Bertrand ?

If not we can also do them sequentially but that will take a lot more
time to get ready for graduation.

Thanks for the feedback and the help, hopefully, we'll get there soon :)

cheers,
  Serge...
On Sat, Dec 15, 2018 at 11:34 AM Jean-Baptiste Onofré  wrote:
>
> Hi Bertrand,
>
> Since the beginning, Unomi has committer == PPMC. So, up to last week,
> we had ~ 10 PPMC.
>
> However, even if committer == PPMC since the beginning of the Unomi
> incubation, we forgot to send the NOTICE.
> Justin was very strict about that, and so, we updated the PPMC with
> mentor and the one for whom we sent a NOTICE.
>
> It's really a pity, and I would kindly ask to re-add all committer as
> PPMC as we had in the past.
>
> Thoughts ?
>
> Regards
> JB
>
> On 15/12/2018 10:27, Bertrand Delacretaz wrote:
> > Hi,
> >
> > On Fri, Dec 14, 2018 at 5:58 PM Serge Huber  wrote:
> >> RESOLVED, that the persons listed immediately below be and hereby are
> >> appointed to serve as the initial members of the Apache Unomi Project...
> >
> > I don't think 3 PMC members is enough. That's the bare minimum for a
> > viable project, so if one of them becomes unavailable you're stuck.
> >
> > I think we've been graduating projects with 5 PMC members in the past,
> > IMO that would be a minimum.
> >
> > -Bertrand
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: [VOTE] Apache Unomi Top Level Project Graduation

[Serge Huber]

And here's my +1 (binding)

Regards,
  Serge...
On Fri, Dec 14, 2018 at 5:57 PM Serge Huber  wrote:
>
> Hi everyone,
>
> Please vote on the draft resolution proposed by the Apache Unomi PPMC
> below, which establishes Apache Unomi as a new top-level project at
> the Apache Software Foundation, as follows:
>
> [ ] +1, Graduate Apache Unomi from the Incubator.
> [ ] +0, Don't care.
> [ ] -1, Don't graduate Apache Unomi from the Incubator because...
>
> Before voting, please see the full text of the draft resolution below,
> and vote only after you feel ready to do so. You can also find the
> maturity model assessment here [2]. The vote will be open for at least
> 72 hours. This is a procedural vote [2]; it is adopted by a simple
> majority of qualified votes (with no minimum).
>
> If approved by the Apache Unomi PPMC, the proposed resolution will be
> submitted to the Apache Incubator PMC for their consideration.
>
> Thank you!
> Serge
>
> [1] http://apache.org/foundation/voting.html
> [2] https://unomi.incubator.apache.org/community-maturity-model-report.html
>
> The full-text of the draft resolution proposed by the Apache Unomi PPMC:
>
> Establish the Apache Unomi Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a reference implementation of the OASIS Customer Data
> Platform specification currently being worked on by the OASIS Context
> Server Technical Committee. It provides a high-performance user profile
> and event tracking server.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Unomi Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Unomi Project be and hereby is responsible for
> the creation and maintenance of software related to a reference
> implementation of the OASIS Customer Data Platform specification
> currently being worked on by the OASIS Context Server Technical
> Committee. It provides a high-performance user profile and event
> tracking server; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Unomi" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Unomi
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Unomi Project;
> and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Unomi Project:
>
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Serge Huber  
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber be appointed to
> the office of Vice President, Apache Unomi, to serve in accordance with
> and subject to the direction of the Board of Directors and the Bylaws of
> the Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Unomi PMC be and hereby is tasked with
> the creation of a set of bylaws intended to encourage open development
> and increased participation in the Apache Unomi Project; and be it
> further
>
> RESOLVED, that the Apache Unomi Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Unomi podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Unomi podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

[VOTE] Apache Unomi Top Level Project Graduation

[Serge Huber]

Hi everyone,

Please vote on the draft resolution proposed by the Apache Unomi PPMC
below, which establishes Apache Unomi as a new top-level project at
the Apache Software Foundation, as follows:

[ ] +1, Graduate Apache Unomi from the Incubator.
[ ] +0, Don't care.
[ ] -1, Don't graduate Apache Unomi from the Incubator because...

Before voting, please see the full text of the draft resolution below,
and vote only after you feel ready to do so. You can also find the
maturity model assessment here [2]. The vote will be open for at least
72 hours. This is a procedural vote [2]; it is adopted by a simple
majority of qualified votes (with no minimum).

If approved by the Apache Unomi PPMC, the proposed resolution will be
submitted to the Apache Incubator PMC for their consideration.

Thank you!
Serge

[1] http://apache.org/foundation/voting.html
[2] https://unomi.incubator.apache.org/community-maturity-model-report.html

The full-text of the draft resolution proposed by the Apache Unomi PPMC:

Establish the Apache Unomi Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a reference implementation of the OASIS Customer Data
Platform specification currently being worked on by the OASIS Context
Server Technical Committee. It provides a high-performance user profile
and event tracking server.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Unomi Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache Unomi Project be and hereby is responsible for
the creation and maintenance of software related to a reference
implementation of the OASIS Customer Data Platform specification
currently being worked on by the OASIS Context Server Technical
Committee. It provides a high-performance user profile and event
tracking server; and be it further

RESOLVED, that the office of "Vice President, Apache Unomi" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Unomi
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Unomi Project;
and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Unomi Project:

 * Francois Papon   
 * Jean-Baptiste Onofré 
 * Serge Huber  

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber be appointed to
the office of Vice President, Apache Unomi, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws of
the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be it further

RESOLVED, that the initial Apache Unomi PMC be and hereby is tasked with
the creation of a set of bylaws intended to encourage open development
and increased participation in the Apache Unomi Project; and be it
further

RESOLVED, that the Apache Unomi Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator Unomi podling; and
be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Unomi podling encumbered upon the Apache Incubator PMC are hereafter
discharged.

Re: Help with my first plugin

[Serge Huber]

Hello Michael,

Nice to see how things have progressed!

I did a quick review of your code, and here are my notes:
1. Overall nice work! You say you have little experience with Java but
overall I think you did a good job.
2. I noticed there are several empty files (they just have a license
header), what is the purpose of this? Did you plan to add more
configuration at a later time?
3. I would remove the plugin from the KAR packaging, as it is not
started automatically. I think that we could add documentation to
deploy it as we did for the Salesforces and MailChimp connectors here:
http://unomi.apache.org/manual/latest/index.html#_connectors
4. Also, would you mind moving the project to extensions? Most of the
new extensions are there. The plugins directory might be removed at
some point.
5. I saw the change in the ProfileService, seems interesting but I
wonder if we don't need a more global solution for all the exceptions
in the REST services? What do you think?
6. For the tests that you have commented out, maybe we could reduce
the thread count to 2000? Would that work better for you?

Thanks for all the work! I hope my notes are constructive enough I
want to encourage you to continue not the opposite :)

Regards,
  Serge
On Mon, Dec 10, 2018 at 9:14 PM Michael Ghen  wrote:
>
> Ok, makes sense.
>
> Would anyone mind reviewing my webhook action? I haven't written too much
> Java code so I'd appreciate any feedback.
>
> https://github.com/apache/incubator-unomi/compare/master...mikeghen:feature/webhook-action?expand=1
>
> I create this rule like so with Python and I run a server on localhost that
> prints out the POST data, seems to work OK:
>
> import requests
>
> r = requests.post('http://localhost:8181/cxs/rules/',
> auth=('karaf','karaf'),
> json ={
>   "metadata": {
> "id": "webhookExample",
> "name": "WebhookExample",
> "description": "Webhook Example"
>   },
>   "condition": {
> ...
>   },
>   "actions": [
> {
>   "parameterValues": {
> "webHookUrl": "http://localhost:5000/test";,
> "webHookMethod": "POST",
> "webHookData": "{\"var1\":\"xyz\",\"var2\":\"xyz\"}",
> "webHookHeaders": "Content-Type:application/json"
>   },
>   "type": "webHookAction"
> }
>   ]
> })
> print("Rule Response Code:", r)
> print("Rule Response Content:", r.content)
>
> When I added the POST functionality, I may have broken the GET
> functionality. I'm not sure the best way to set up a test for this action,
> any recommendations?
>
> On Mon, Dec 10, 2018 at 4:14 AM Serge Huber  wrote:
>
> > Hello Michael,
> >
> > I didn't envision a mapping type but I think it could be an
> > interesting one to consider. I'd need to give it some thought though
> > because I'm not sure if ElasticSearch can work with that in the
> > queries.
> >
> > Regards,
> >   Serge...
> > On Mon, Dec 10, 2018 at 4:59 AM Michael Ghen  wrote:
> > >
> > > The suggestion for a token in the string and parsing it will work, was
> > > thinking the same thing. Do you envision adding a mapping type to
> > > parameters? I was kind of looking into where that would be implemented
> > but
> > > it seems non-trivial. For now, I'll roll with a token approach for
> > headers.
> > >
> > > On Tue, Dec 4, 2018 at 11:04 AM Serge Huber  wrote:
> > >
> > > > On Tue, Dec 4, 2018 at 3:01 PM Michael Ghen  wrote:
> > > > > BTW, the new unomi: commands are very helpful in 1.4
> > > >
> > > > I'm glad you like them, I have developed most of them out of need,
> > > > especially to diagnose some problems for example in definition
> > > > registration, rule execution or simply event format checks.
> > > >
> > > > My favorites are :
> > > > event-tail
> > > > event-view
> > > > rule-tail
> > > > rule-view
> > > > rule-watch
> > > >
> > > > what are yours ? :)
> > > >
> > > > cheers,
> > > >   Serge...
> > > >
> >

Re: Help with my first plugin

[Serge Huber]

Hello Michael,

I didn't envision a mapping type but I think it could be an
interesting one to consider. I'd need to give it some thought though
because I'm not sure if ElasticSearch can work with that in the
queries.

Regards,
  Serge...
On Mon, Dec 10, 2018 at 4:59 AM Michael Ghen  wrote:
>
> The suggestion for a token in the string and parsing it will work, was
> thinking the same thing. Do you envision adding a mapping type to
> parameters? I was kind of looking into where that would be implemented but
> it seems non-trivial. For now, I'll roll with a token approach for headers.
>
> On Tue, Dec 4, 2018 at 11:04 AM Serge Huber  wrote:
>
> > On Tue, Dec 4, 2018 at 3:01 PM Michael Ghen  wrote:
> > > BTW, the new unomi: commands are very helpful in 1.4
> >
> > I'm glad you like them, I have developed most of them out of need,
> > especially to diagnose some problems for example in definition
> > registration, rule execution or simply event format checks.
> >
> > My favorites are :
> > event-tail
> > event-view
> > rule-tail
> > rule-view
> > rule-watch
> >
> > what are yours ? :)
> >
> > cheers,
> >   Serge...
> >

[jira] [Commented] (UNOMI-216) Configure Unomi by editing one configuration file & read env variables for Docker compatibility

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713228#comment-16713228
 ] 

Serge Huber commented on UNOMI-216:
---

Thanks Michael for the suggestion but the question is how to link the 
properties in the centralized configuration file to the config admin or XML 
files. 

For the moment this is what I'm trying to do:

In a config admin file I put stuff like this : 
{code:java}
encryption.enabled = ${org.apache.unomi.security.encryption.enabled:-false}
{code}
then in the unomi.properties file I put something like this : 
{code:java}
org.apache.unomi.security.encryption.enabled=${env:UNOMI_ENCRYPTION_ENABLED:-false}
{code}
Which means that you can then set the UNOMI_ENCRYPTION_ENABLED environment to 
enable/disable the encryption. It also has default values everywhere in case 
the values is not set.

For hazelcast.xml I changed it like this :
{code:java}

${org.apache.unomi.hazelcast.tcp-ip.members}
${org.apache.unomi.hazelcast.tcp-ip.interface}
{code}
And then in the custom.system.properties I setup the values like this : 
{code:java}
org.apache.unomi.hazelcast.tcp-ip.members=${env:UNOMI_HAZELCAST_TCPIP_MEMBERS:-127.0.0.1}
org.apache.unomi.hazelcast.tcp-ip.interface=${env:UNOMI_HAZELCAST_TCPIP_INTERFACE:-127.0.0.1}{code}

The biggest issue with this type of solution is that it requires to put the 
placeholders in a lot of properties just in case someone needs to override them 
using environment variables. 

What would be fantastic would be some kind of universal override that could 
work in any configuration files. Right now Docker recommends to do that with 
"sed" commands but something more specific to Java properties file (maybe a 
bootstrap mechanism for Karaf ?) would be fantastic.

What do you think ?

> Configure Unomi by editing one configuration file & read env variables for 
> Docker compatibility
> ---
>
> Key: UNOMI-216
> URL: https://issues.apache.org/jira/browse/UNOMI-216
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.0.0-incubating, 1.1.0-incubating, 1.2.0-incubating, 
> 1.3.0-incubating, 1.4.0-incubating
>        Reporter: Serge Huber
>Assignee: Serge Huber
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The idea here is to make it easy to "override" common configuration 
> properties in Apache Unomi by modifying a single configuration file. Of 
> course this type of deployment is focused on "static" deployments, not 
> deployment where the configuration admin is used to dynamically update 
> configuration. Also this will address the need of Docker containers that pass 
> configuration through environment variables.
> As a consequence, default Unomi properties should be "placeholdered", with 
> default values
> Here is the section in the Karaf documentation about configuration, including 
> environment variables references : 
> [http://karaf.apache.org/manual/latest/#_configuration_3]
> "Properties can be referenced inside configuration files using the syntax 
> {{$\{}}}. Default and alternate values can be specified using 
> {{$\{:-}}} and {{$\{:+}}} 
> syntaxes respectively."
> "Environment variables can be referenced inside configuration files using the 
> syntax {{$\{env:}}} (e.g.{{property=$\{env:FOO}}} will set "property" 
> to the value of the enviroment variable "FOO"). Default and alternate values 
> can be defined for them as well using the same syntax as above." 
> Some difficulty might come from configuration files such as the Hazelcast XML 
> configuration file that can only reference system properties, so we might 
> have to setup the placeholders in the custom.system.properties file.
> This story includes modifications to the documentation to use this 
> centralized file, both on the Unomi website.
> Migration will be handle through documentation as well, indicating where the 
> properties must be moved.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [PROPOSAL] Move to gitbox.apache.org

[Serge Huber]

I think it's a good idea and it would be coherent with our site
repository that's already on gitbox.

cheers,
  Serge...
On Fri, Dec 7, 2018 at 6:28 PM Francois Papon
 wrote:
>
> Hi JB,
>
> Thanks for the proposal, I agree to move forward on it!
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 07/12/2018 à 21:10, Jean-Baptiste Onofré a écrit :
> > Hi guys,
> >
> > our repository is currently located on git-wip-us.apache.org.
> >
> > In preparation for the graduation and as this service will be
> > decommissioned in the coming months, I propose to move our repository to
> > gitbox.apache.org.
> >
> > I'm volunteer to start a formal vote, and if pass, to deal with infra.
> >
> > Thoughts ?
> >
> > Regards
> > JB
>

[jira] [Created] (UNOMI-216) Configure Unomi by editing one configuration file & read env variables for Docker compatibility

[Serge Huber (JIRA)]

Serge Huber created UNOMI-216:
-

 Summary: Configure Unomi by editing one configuration file & read 
env variables for Docker compatibility
 Key: UNOMI-216
 URL: https://issues.apache.org/jira/browse/UNOMI-216
 Project: Apache Unomi
  Issue Type: Improvement
  Components: core
Affects Versions: 1.3.0-incubating, 1.2.0-incubating, 1.1.0-incubating, 
1.0.0-incubating, 1.4.0-incubating
Reporter: Serge Huber
Assignee: Serge Huber
 Fix For: 1.4.0-incubating


The idea here is to make it easy to "override" common configuration properties 
in Apache Unomi by modifying a single configuration file. Of course this type 
of deployment is focused on "static" deployments, not deployment where the 
configuration admin is used to dynamically update configuration. Also this will 
address the need of Docker containers that pass configuration through 
environment variables.

As a consequence, default Unomi properties should be "placeholdered", with 
default values

Here is the section in the Karaf documentation about configuration, including 
environment variables references : 
[http://karaf.apache.org/manual/latest/#_configuration_3]

"Properties can be referenced inside configuration files using the syntax 
{{$\{}}}. Default and alternate values can be specified using 
{{$\{:-}}} and {{$\{:+}}} syntaxes 
respectively."

"Environment variables can be referenced inside configuration files using the 
syntax {{$\{env:}}} (e.g.{{property=$\{env:FOO}}} will set "property" to 
the value of the enviroment variable "FOO"). Default and alternate values can 
be defined for them as well using the same syntax as above." 

Some difficulty might come from configuration files such as the Hazelcast XML 
configuration file that can only reference system properties, so we might have 
to setup the placeholders in the custom.system.properties file.

This story includes modifications to the documentation to use this centralized 
file, both on the Unomi website.

Migration will be handle through documentation as well, indicating where the 
properties must be moved.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Help with my first plugin

[Serge Huber]

On Tue, Dec 4, 2018 at 3:01 PM Michael Ghen  wrote:
> BTW, the new unomi: commands are very helpful in 1.4

I'm glad you like them, I have developed most of them out of need,
especially to diagnose some problems for example in definition
registration, rule execution or simply event format checks.

My favorites are :
event-tail
event-view
rule-tail
rule-view
rule-watch

what are yours ? :)

cheers,
  Serge...

Re: Help with my first plugin

[Serge Huber]

Hello Michael,

The reason your bundle is not started with the "core" bundle is
because it is not registered in the list here (reserved for core
Apache Unomi bundles) :
https://github.com/apache/incubator-unomi/blob/master/tools/shell-commands/src/main/resources/OSGI-INF/blueprint/blueprint.xml
This configuration is the list of bundles that the unomi:start command
will actually start.

By default all the bundles in Unomi are stopped to allow for the
migration tasks to happen (if needed).

Once you install and start your bundle it will remain started even if
you restart Karaf. Btw one VERY useful command to know, especially as
you have already learned how to install from your local Maven
repository is the bundle:watch command. Once you call that with your
bundle id it will watch your local repository (the location from which
you have installed) and refresh the bundle if it changes. That way you
can simply do : mvn clean install on your bundle and it will
automatically refresh in Karaf without needed to restart anything.

For the key pair it is not possible to do that with parameters, but I
would suggest the following: simply "encode" the pairs in a string
property, something like :

   {
  "id": "headers",
  "type": "string",
  "multivalued": false
}

and then put in headers something easy to parse like :

Content-Type:application/json###Basic: asdf978adsf###

or you could serialize some JSON in there and parse it out. That would
also make the payload easy to store.

Regards,
  Serge...
On Tue, Dec 4, 2018 at 3:42 PM Michael Ghen  wrote:
>
> One more thing about this plugin, seems like the HTTP GET request worked OK
> so I'm interested in adding headers (for basic HTTP auth) and setting up
> POST.
>
> Is there a way to accept key, value pairs in the parameters?
>
> I have this as parameters in my JSON now:
>
> "parameters": [
> {
>   "id": "webHookUrl",
>   "type": "string",
>   "multivalued": false
> },
> {
>   "id": "webHookMethod",
>   "type": "string",
>   "multivalued": false
> }
>   ]
>
> Would like to add "headers" and "payload" both as key-value pairs, I don't
> see a type = mapping anywhere and I'm not sure what "multivalued" is, maybe
> that could help?
>
>
> On Tue, Dec 4, 2018 at 9:01 AM Michael Ghen  wrote:
>
> > OK, I got this sorted out. Ended up running:
> >
> > karaf@root()> bundle:install
> > mvn:org.apache.unomi/unomi-plugins-webhook/1.4.0-incubating-SNAPSHOT
> > Bundle ID: 179
> > karaf@root()> bundle:start 179
> >
> > Then my webhook action shows in unomi:action-list. Thanks Damien and Serge.
> >
> > I'm not sure why it is that the action I added is not immediately
> > available like the other actions but this at least lets me give my webhook
> > a try.
> >
> > BTW, the new unomi: commands are very helpful in 1.4
> >
> > On Mon, Dec 3, 2018 at 11:47 AM Michael Ghen  wrote:
> >
> >> Serge, I was mostly just copying exactly what was there so I just did
> >> everything that existed for the mail action. I will try this bunble:start
> >> thing and see what happens. I'll see if I can get it working with headers
> >> and post body and maybe I can contribute it back.
> >>
> >> On Mon, Dec 3, 2018 at 6:03 AM Serge Huber  wrote:
> >>
> >>> Hello Michael,
> >>>
> >>> I tried your code and everything is there, the only thing is that your
> >>> bundle is not started. You have added it as part of the main Karaf
> >>> Feature of Unomi (was this intentional ? Are you intending to
> >>> contribute this as part as the core of Unomi ?)
> >>>
> >>> Anyway I just did a bundle:start on the bundle ID and your action was
> >>> up and running (it's listed in the action-list command).
> >>>
> >>> If you're just looking to build an optional extension I would
> >>> recommend building a seperate feature (or just a bundle) as Damien
> >>> suggested.
> >>>
> >>> But it's true that a webhook plugin is a really good idea !
> >>>
> >>> Regards,
> >>>   Serge...
> >>>
> >>>
> >>>
> >>> On Mon, Dec 3, 2018 at 10:55 AM Damien GAILLARD 
> >>> wrote:
> >>> >
> >>> > Hi Michael,
> >>> >
> >>> > I haven't look at your entire code yet but 

Re: Help with my first plugin

[Serge Huber]

Hello Michael,

I tried your code and everything is there, the only thing is that your
bundle is not started. You have added it as part of the main Karaf
Feature of Unomi (was this intentional ? Are you intending to
contribute this as part as the core of Unomi ?)

Anyway I just did a bundle:start on the bundle ID and your action was
up and running (it's listed in the action-list command).

If you're just looking to build an optional extension I would
recommend building a seperate feature (or just a bundle) as Damien
suggested.

But it's true that a webhook plugin is a really good idea !

Regards,
  Serge...



On Mon, Dec 3, 2018 at 10:55 AM Damien GAILLARD  wrote:
>
> Hi Michael,
>
> I haven't look at your entire code yet but did you check if your bundle is
> activated by using the command bundle:list | grep unomi it should show up
> in the list.
> If the bundle is here it's a good start and if it's in resolved you might
> just need to start it, with something like that:
>
> bundle:install 
> mvn:org.apache.unomi/login-integration-samples/${project.version}
>
> or like that:
>
> feature:repo-add
> mvn:org.apache.unomi/unomi-salesforce-connectors-karaf-kar/${project.version}/xml/features
> feature:install unomi-salesforce-connectors-karaf-kar
>
> I'm pretty sure we have some documentation somewhere but I could not find
> it, and the closest video that show how to deploy a plugin might be this
> one but the quality is not really good:
> https://www.youtube.com/watch?v=IvP_iIlw2vQ&t=1389s
> and this is the repo that was used for the demo so you can easily use it as
> an example
> https://github.com/Jahia/unomi-twilio
>
> Cheers
>
> On Sun, Dec 2, 2018 at 6:11 PM Michael Ghen  wrote:
>
> > PS: The message I get in the logs is:
> >
> > 2018-12-01T22:23:13,867 | WARN  | pool-44-thread-1 | ParserHelper
> >| 185 - org.apache.unomi.services - 1.4.0.incubating-SNAPSHOT |
> > Couldn't resolve action types : webHookAction
> >
> > On Sun, Dec 2, 2018 at 12:06 PM Michael Ghen  wrote:
> >
> > > Hi,
> > >
> > > I'm working on my first plugin. I'm trying to add a general webhook
> > action
> > > to send requests to another service when a condition is met in a rule. I
> > > looked at the docs about Plugins and looked a little at OSGI. I took the
> > > approach of trying to start with a copy of another action and refactor
> > it.
> > >
> > > The plugin I made seems to build OK and shows up in the build.
> > > Unfortunately, when I use unomi:action-list, the action doesn't show up
> > > there and when I add a rule using the action, I just get an error that
> > > unomi can't find my action.
> > >
> > > Would anyone be able to review my plugin and help me trace down what I
> > > missed?
> > >
> > >
> > >
> > https://github.com/apache/incubator-unomi/compare/master...mikeghen:feature/webhook-action?expand=1
> > >
> > > I've been going file by file through my action and comparing it to the
> > > mail action I copied and refactored but can't seem to see what the
> > problem
> > > is. Any suggestions? I tried walking back through the action-list code to
> > > see if that gave me some clues but it did not.
> > >
> > >
> > >
> >
>
>
> --
> Damien GAILLARD
> Software Developer
> 
> 
> 8 rue du sentier | 75002 | France
> 
> 
> jahia.com 
> SKYPE | TWITTER  | VCARD
> 
>
> > JAHIA  empowers organizations to create
> sophisticated websites that drive their business growth

[jira] [Created] (UNOMI-215) Improve tooling for analyzing rule executions

[Serge Huber (JIRA)]

Serge Huber created UNOMI-215:
-

 Summary: Improve tooling for analyzing rule executions
 Key: UNOMI-215
 URL: https://issues.apache.org/jira/browse/UNOMI-215
 Project: Apache Unomi
  Issue Type: Bug
  Components: core
Affects Versions: 1.4.0-incubating
Reporter: Serge Huber
Assignee: Serge Huber
 Fix For: 1.4.0-incubating


The idea is to add SSH shell commands that make it possible to : 
 * watch execution of rules
 * analyze specific rules evaluation and execution



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (UNOMI-214) Fix integration tests

[Serge Huber (JIRA)]

Serge Huber created UNOMI-214:
-

 Summary: Fix integration tests
 Key: UNOMI-214
 URL: https://issues.apache.org/jira/browse/UNOMI-214
 Project: Apache Unomi
  Issue Type: Bug
Reporter: Serge Huber


After a rule was deployed the integration tests started failing because of a 
bug in the JSON deserializing code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Unable to Build, java.lang.OutOfMemoryError

[Serge Huber]

Did you try rebooting ? Running out of native threads seems like an OS limit.

Btw my value is here :
sysctl kern.num_threads
kern.num_threads: 40960

Regards,
  Serge...

On Mon, Nov 26, 2018 at 8:34 PM Michael Ghen  wrote:
>
> I'm going to download the latest from the link in the BUILDING document
> maybe that'll fix this
>
> On Mon, Nov 26, 2018 at 2:32 PM Michael Ghen  wrote:
>
> > Java version 1.8.0_191
> >
> > On Mon, Nov 26, 2018 at 2:22 PM Serge Huber  wrote:
> >
> >> Which JDK version are you using ?
> >>
> >> Regards,
> >>   Serge...
> >>
> >>
> >>
> >> On Mon, Nov 26, 2018 at 7:51 PM Michael Ghen  wrote:
> >> >
> >> > Hello,
> >> >
> >> > I am trying to run "mvn clean install" to build Unomi from source but I
> >> > keep running into this error. I've also tried "mvn -P
> >> > \!integration-tests,\!performance-tests clean install" but get this same
> >> > error.
> >> >
> >> > Is this something with my operating system? I'm running Mac OSx. I'm not
> >> > finding much online about this.
> >> >
> >> > Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.452
> >> sec
> >> > <<< FAILURE! - in
> >> >
> >> org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest
> >> >
> >> testCompareOGNLvsHardcodedPerformance(org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest)
> >> >  Time elapsed: 2.156 sec  <<< ERROR!
> >> > java.lang.OutOfMemoryError: unable to create new native thread
> >> > at java.lang.Thread.start0(Native Method)
> >> > at java.lang.Thread.start(Thread.java:717)
> >> > at
> >> >
> >> java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)
> >> > at
> >> >
> >> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357)
> >> > at
> >> >
> >> java.util.concurrent.AbstractExecutorService.invokeAll(AbstractExecutorService.java:238)
> >> > at
> >> >
> >> org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest.runHardcodedTest(PropertyConditionEvaluatorTest.java:114)
> >> > at
> >> >
> >> org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest.testCompareOGNLvsHardcodedPerformance(PropertyConditionEvaluatorTest.java:83)
> >> >
> >> > java.lang.OutOfMemoryError: unable to create new native thread
> >> > at java.lang.Thread.start0(Native Method)
> >> > at java.lang.Thread.start(Thread.java:717)
> >> > at
> >> >
> >> org.apache.maven.surefire.booter.ForkedBooter.launchLastDitchDaemonShutdownThread(ForkedBooter.java:184)
> >> > at
> >> org.apache.maven.surefire.booter.ForkedBooter.exit(ForkedBooter.java:143)
> >> > at
> >> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:127)
> >> > Exception in thread "main" java.lang.OutOfMemoryError: unable to create
> >> new
> >> > native thread
> >> > at java.lang.Thread.start0(Native Method)
> >> > at java.lang.Thread.start(Thread.java:717)
> >> > at
> >> >
> >> org.apache.maven.surefire.booter.ForkedBooter.launchLastDitchDaemonShutdownThread(ForkedBooter.java:184)
> >> > at
> >> org.apache.maven.surefire.booter.ForkedBooter.exit(ForkedBooter.java:143)
> >> > at
> >> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:135)
> >>
> >

Re: Unable to Build, java.lang.OutOfMemoryError

[Serge Huber]

Which JDK version are you using ?

Regards,
  Serge...



On Mon, Nov 26, 2018 at 7:51 PM Michael Ghen  wrote:
>
> Hello,
>
> I am trying to run "mvn clean install" to build Unomi from source but I
> keep running into this error. I've also tried "mvn -P
> \!integration-tests,\!performance-tests clean install" but get this same
> error.
>
> Is this something with my operating system? I'm running Mac OSx. I'm not
> finding much online about this.
>
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.452 sec
> <<< FAILURE! - in
> org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest
> testCompareOGNLvsHardcodedPerformance(org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest)
>  Time elapsed: 2.156 sec  <<< ERROR!
> java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:717)
> at
> java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357)
> at
> java.util.concurrent.AbstractExecutorService.invokeAll(AbstractExecutorService.java:238)
> at
> org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest.runHardcodedTest(PropertyConditionEvaluatorTest.java:114)
> at
> org.apache.unomi.plugins.baseplugin.conditions.PropertyConditionEvaluatorTest.testCompareOGNLvsHardcodedPerformance(PropertyConditionEvaluatorTest.java:83)
>
> java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:717)
> at
> org.apache.maven.surefire.booter.ForkedBooter.launchLastDitchDaemonShutdownThread(ForkedBooter.java:184)
> at org.apache.maven.surefire.booter.ForkedBooter.exit(ForkedBooter.java:143)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:127)
> Exception in thread "main" java.lang.OutOfMemoryError: unable to create new
> native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:717)
> at
> org.apache.maven.surefire.booter.ForkedBooter.launchLastDitchDaemonShutdownThread(ForkedBooter.java:184)
> at org.apache.maven.surefire.booter.ForkedBooter.exit(ForkedBooter.java:143)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:135)

[jira] [Created] (UNOMI-213) Move twitter sample HTML out of root context and build a proper HTML welcome page in the root context

[Serge Huber (JIRA)]

Serge Huber created UNOMI-213:
-

 Summary: Move twitter sample HTML out of root context and build a 
proper HTML welcome page in the root context
 Key: UNOMI-213
 URL: https://issues.apache.org/jira/browse/UNOMI-213
 Project: Apache Unomi
  Issue Type: Improvement
  Components: core, web
Affects Versions: 1.3.0-incubating, 1.4.0-incubating
Reporter: Serge Huber
Assignee: Serge Huber
 Fix For: 1.4.0-incubating


Right now when we access the root context at 
[http://localhost:8181|http://localhost:8181/] we get an HTML page that is in 
fact the test case for the Twitter sample. This is confusing and not the right 
place for this HTML to be. 

Instead it should be moved in the sample's code itself, and in place I propose 
we build a proper welcome page that would contain something like this : 
h1. Welcome to Apache Unomi

Congratulations, you have successfully installed Apache Unomi !
h2. Where to go from here
 * Checkout some cool [videos & 
tutorials|http://unomi.apache.org/resources.html]
 * Read [Apache Unomi's manual|http://unomi.apache.org/manual/latest/index.html]
 * Try out some 
[samples|http://unomi.apache.org/manual/latest/index.html#_integration_samples]
 * Join [Apache Unomi's mailing lists|http://unomi.apache.org/community.html]
 * Star the project on Github
 * Fork the [code|https://github.com/apache/incubator-unomi] and submit pull 
requests (github repository)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (UNOMI-211) Logging for "Failed to Parse" ElasticSearch errors

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698915#comment-16698915
 ] 

Serge Huber commented on UNOMI-211:
---

Hello Michael,

If you're talking about the CXS endpoint, that is managed by Apache CXF and you 
would have to figure out how to manage errors properly for that. I'm not a big 
expert at CXF myself :) 

One thing that's important, Apache Unomi should not return information that 
might compromise security, so it should NOT return stack traces or even any 
version information in HTTP error results. I prefer that it says something like 
: Server error, please check the logs for more details. This way attackers 
cannot "learn" about the internals and attempt to mess with the system. 

Regards,

  Serge... 

> Logging for "Failed to Parse" ElasticSearch errors
> --
>
> Key: UNOMI-211
> URL: https://issues.apache.org/jira/browse/UNOMI-211
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.3.0-incubating
>Reporter: Michael Ghen
>Priority: Major
>
> I have been noticing a lot of 204 errors which tend to mean something failed. 
> This is one of those issues and I think many people might stumble onto this 
> and get confused. 
> The problem happens when some invalid JSON is created that Elasticsearch does 
> not like. In this case, I have a key value pair in the properties of a 
> profile that looks like:
> {code:java}
> {
> "itemId": "f283309c-9bdc-11e8-9127-0a58ac100323",
> "itemType": "profile",
> "properties": {
>   "firstName": "Mike",
>   "lastName": "Ghen",
>   "": ""  # Something invalid that a programming language may form
> },
> "systemProperties": {},
> "segments": [],
> "scores": {},
> "consents": {}
> }{code}
> When posted to update a profile with the `"": ""` key value, you'll get a 204 
> error. 
> While this might be a silly ES error, I would expect Unomi to return such in 
> the reponse. The 204 response code is not documented. 
> The expected result should be a 415 error code and even better if the error 
> came back in the reponse. When I looked into the Unomi logs I found this 
> error:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: object field starting or 
> ending with a [.] makes object resolution ambiguous: []
> {code}
> Which helped me trace the error down in my profile (which has 200 key value 
> pairs).
> It would be ideal if Unomi could return this "Caused by" error message and a 
> 415 for situations like this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Unomi Docker

[Serge Huber]

Very nice work Michael, should we add this link to the Unomi website ?
Do you want to do a PR to put it in the resources section ?

cheers,
  Serge...
On Fri, Nov 23, 2018 at 8:50 PM Michael Ghen  wrote:
>
> That seemed to do the trick. Thanks, Serge!
>
> Here's the repo in case anyone else is looking to run Unomi on Docker:
> https://github.com/mikeghen/unomi-docker
>
> On Fri, Nov 23, 2018 at 2:30 PM Michael Ghen  wrote:
>
> > Excellent, this looks like what I was trying to find!
> >
> > I'm not sure about the KARAF_HOME message either, I think it's because I
> > set KARAF_HOME in the docker file.
> >
> > On Fri, Nov 23, 2018 at 2:28 PM Serge Huber  wrote:
> >
> >> Hello Michael,
> >>
> >> It seems there is an issue with the KARAF_HOME variable, not sure what
> >> is going on there.
> >>
> >> For Unomi however, it is possible to have it autoStart by using the
> >> following setting in the setenv script :
> >>
> >> export KARAF_OPTS="-Dunomi.autoStart=true"
> >>
> >> This will trigger a start of Unomi as soon as Karaf has finished
> >> initializing.
> >>
> >> Regards,
> >>   Serge...
> >> On Fri, Nov 23, 2018 at 8:08 PM Michael Ghen  wrote:
> >> >
> >> > Hi,
> >> >
> >> > I put together this repo with my docker configuration and a docker
> >> compose
> >> > example.
> >> >
> >> > I'm having an issue now trying to get this running on Kubernetes and was
> >> > hoping someone can help me. I put this "sleep 60" command in the entry
> >> > point script for my docker file between when I start Karaf and when I
> >> issue
> >> > the "unomi:start" command. In Kubernetes, it seems like this doesn't
> >> work
> >> > so I'm trying to find a why to wait for Karaf to finish start up before
> >> > starting unomi.
> >> >
> >> > My entry point script looks like:
> >> >
> >> > #!/bin/sh
> >> > sed -i
> >> "s/elasticSearchAddresses=localhost:9300/elasticSearchAddresses=${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}/g"
> >> > /opt/apache-unomi/etc/org.apache.unomi.persistence.elasticsearch.cfg
> >> > $KARAF_HOME/bin/start
> >> > sleep 60
> >> > $KARAF_HOME/bin/client "unomi:start"
> >> > echo "Started Unomi"
> >> > tail -f $KARAF_HOME/data/log/karaf.log
> >> >
> >> > And in the logs I get this:
> >> >
> >> > start: Ignoring predefined value for KARAF_HOME
> >> > client: Ignoring predefined value for KARAF_HOME
> >> > *Failed to get the session.*
> >> > Started Unomi
> >> >
> >> > The "Failed to get the session." seems to be the client failing to
> >> connect
> >> > to Karaf before it's ready? Is there a better way to start Unomi on
> >> > container startup? I'm new to Karaf and spent the last week pouring over
> >> > the docs looking for something to help with this. I tried to do an if
> >> > statment with bin/status but that wasn't working out.
> >>
> >

Re: Unomi Docker

[Serge Huber]

Hello Michael,

It seems there is an issue with the KARAF_HOME variable, not sure what
is going on there.

For Unomi however, it is possible to have it autoStart by using the
following setting in the setenv script :

export KARAF_OPTS="-Dunomi.autoStart=true"

This will trigger a start of Unomi as soon as Karaf has finished initializing.

Regards,
  Serge...
On Fri, Nov 23, 2018 at 8:08 PM Michael Ghen  wrote:
>
> Hi,
>
> I put together this repo with my docker configuration and a docker compose
> example.
>
> I'm having an issue now trying to get this running on Kubernetes and was
> hoping someone can help me. I put this "sleep 60" command in the entry
> point script for my docker file between when I start Karaf and when I issue
> the "unomi:start" command. In Kubernetes, it seems like this doesn't work
> so I'm trying to find a why to wait for Karaf to finish start up before
> starting unomi.
>
> My entry point script looks like:
>
> #!/bin/sh
> sed -i 
> "s/elasticSearchAddresses=localhost:9300/elasticSearchAddresses=${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}/g"
> /opt/apache-unomi/etc/org.apache.unomi.persistence.elasticsearch.cfg
> $KARAF_HOME/bin/start
> sleep 60
> $KARAF_HOME/bin/client "unomi:start"
> echo "Started Unomi"
> tail -f $KARAF_HOME/data/log/karaf.log
>
> And in the logs I get this:
>
> start: Ignoring predefined value for KARAF_HOME
> client: Ignoring predefined value for KARAF_HOME
> *Failed to get the session.*
> Started Unomi
>
> The "Failed to get the session." seems to be the client failing to connect
> to Karaf before it's ready? Is there a better way to start Unomi on
> container startup? I'm new to Karaf and spent the last week pouring over
> the docs looking for something to help with this. I tried to do an if
> statment with bin/status but that wasn't working out.

Re: Rebase GraphQL branch on master

[Serge Huber]

Don't get too excited it's just a skeleton at this point to test ideas
from the specification :)

cheers,
  Serge...


On Wed, Nov 21, 2018 at 3:40 PM Francois Papon
 wrote:
>
> Hi,
>
> Thanks Serge!
>
> It's a great new feature, congratulations!
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 21/11/2018 à 18:00, Serge Huber a écrit :
> > Hi all,
> >
> > Just in case you're wondering what all of those commits are, I just
> > rebase the GraphQL implementation branch on the master to be up to
> > date with the latest changes. Much to my surprise the rebase worked on
> > the first try (but I didn't try to compile yet though :))
> >
> > Regards,
> >   Serge...
>

Rebase GraphQL branch on master

[Serge Huber]

Hi all,

Just in case you're wondering what all of those commits are, I just
rebase the GraphQL implementation branch on the master to be up to
date with the latest changes. Much to my surprise the rebase worked on
the first try (but I didn't try to compile yet though :))

Regards,
  Serge...

Re: Towards graduation

[Serge Huber]

Hello,

I've updated the updated list of proposed initial members :

     * Serge Huber 
 * Jean-Baptiste Onofré 
 * Thomas Draier 
 * Sergiy Shyrkov 
 * Kevan Jahanshahi 
 * Chris Laprun 
 * David Griffon 
 * Abdelkader Midani 
 * François Papon 
 * Damien Gaillard 

I hope this is now ok so we can move forward with the draft.

Regards,
  Serge
On Tue, Oct 9, 2018 at 1:06 PM Bertrand Delacretaz
 wrote:
>
> Hi,
>
> On Sat, Oct 6, 2018 at 6:28 AM Jean-Baptiste Onofré  wrote:
> > ...I prepared a graduation resolution draft...
>
> You need to list the @apache.org addresses of all PMC members in
> there, apart from that it looks good to me, thanks!
>
> -Bertrand

Re: November Unomi board report

[Serge Huber]

Thanks JB !

cheers,
  Serge...


On Sat, Nov 3, 2018 at 6:29 AM Jean-Baptiste Onofré  wrote:
>
> Done
>
> Regards
> JB
>
> On 02/11/2018 17:27, Serge Huber wrote:
> > If it's ok can you post it on the Wiki JB ? I don't have the kharma.
> >
> > Regards,
> >   Serge...
> >
> >
> > On Fri, Nov 2, 2018 at 4:55 PM Jean-Baptiste Onofré  
> > wrote:
> >>
> >> +1
> >>
> >> it sounds good to me. Thanks !
> >> Sorry I was on vacation the last two weeks, and I didn't help.
> >>
> >> Regards
> >> JB
> >>
> >> On 02/11/2018 10:19, Serge Huber wrote:
> >>> Hello,
> >>>
> >>> As we are a bit late for the graduation process, I have prepared a
> >>> board report for Unomi. Please review and comment :
> >>>
> >>> Unomi
> >>>
> >>> Unomi is a reference implementation of the OASIS Context Server 
> >>> specification
> >>> currently being worked on by the OASIS Context Server Technical 
> >>> Committee. It
> >>> provides a high-performance user profile and event tracking server.
> >>>
> >>> Unomi has been incubating since 2015-10-05.
> >>>
> >>> Three most important issues to address in the move towards graduation:
> >>>
> >>>   1. Clarify IP clearance (on-going)
> >>>   2. Finalized graduation proposal draft
> >>>   3. Podling graduation vote once step 1 and 2 are complete
> >>>
> >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >>> aware of?
> >>>
> >>> No
> >>>
> >>> How has the community developed since the last report?
> >>>
> >>> We have added a new committer and PPMC member : François Papon and we
> >>> have prepared a list of PMC members for post-graduation.
> >>>
> >>> How has the project developed since the last report?
> >>>
> >>> After the release of Apache Unomi 1.3.0, we are now focused on
> >>> graduation. The maturity model report has been completed, the website
> >>> has been greatly expanded to clarify community joining and
> >>> communication, and a draft of the graduation proposal is being
> >>> discussed right now.
> >>>
> >>> How would you assess the podling's maturity?
> >>> Please feel free to add your own commentary.
> >>>
> >>>   [ ] Initial setup
> >>>   [ ] Working towards first release
> >>>   [ ] Community building
> >>>   [ X ] Nearing graduation
> >>>   [ ] Other:
> >>>
> >>> Date of last release:
> >>>
> >>>   2018-09-10
> >>>
> >>> When were the last committers or PPMC members elected?
> >>>
> >>>   2018-09-19
> >>>
> >>> Have your mentors been helpful and responsive or are things falling
> >>> through the cracks? In the latter case, please list any open issues
> >>> that need to be addressed.
> >>>
> >>> Our mentors are very helpful and responsive and are doing their best
> >>> to assist the project when asked.
> >>>
> >>> Signed-off-by:
> >>>
> >>>   [ ](unomi) Bertrand Delacretaz
> >>>  Comments:
> >>>   [ ](unomi) Jean-Baptiste Onofre
> >>>  Comments:
> >>>
> >>> IPMC/Shepherd notes:
> >>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: November Unomi board report

[Serge Huber]

If it's ok can you post it on the Wiki JB ? I don't have the kharma.

Regards,
  Serge...


On Fri, Nov 2, 2018 at 4:55 PM Jean-Baptiste Onofré  wrote:
>
> +1
>
> it sounds good to me. Thanks !
> Sorry I was on vacation the last two weeks, and I didn't help.
>
> Regards
> JB
>
> On 02/11/2018 10:19, Serge Huber wrote:
> > Hello,
> >
> > As we are a bit late for the graduation process, I have prepared a
> > board report for Unomi. Please review and comment :
> >
> > Unomi
> >
> > Unomi is a reference implementation of the OASIS Context Server 
> > specification
> > currently being worked on by the OASIS Context Server Technical Committee. 
> > It
> > provides a high-performance user profile and event tracking server.
> >
> > Unomi has been incubating since 2015-10-05.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Clarify IP clearance (on-going)
> >   2. Finalized graduation proposal draft
> >   3. Podling graduation vote once step 1 and 2 are complete
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > No
> >
> > How has the community developed since the last report?
> >
> > We have added a new committer and PPMC member : François Papon and we
> > have prepared a list of PMC members for post-graduation.
> >
> > How has the project developed since the last report?
> >
> > After the release of Apache Unomi 1.3.0, we are now focused on
> > graduation. The maturity model report has been completed, the website
> > has been greatly expanded to clarify community joining and
> > communication, and a draft of the graduation proposal is being
> > discussed right now.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ X ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2018-09-10
> >
> > When were the last committers or PPMC members elected?
> >
> >   2018-09-19
> >
> > Have your mentors been helpful and responsive or are things falling
> > through the cracks? In the latter case, please list any open issues
> > that need to be addressed.
> >
> > Our mentors are very helpful and responsive and are doing their best
> > to assist the project when asked.
> >
> > Signed-off-by:
> >
> >   [ ](unomi) Bertrand Delacretaz
> >  Comments:
> >   [ ](unomi) Jean-Baptiste Onofre
> >  Comments:
> >
> > IPMC/Shepherd notes:
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

[jira] [Resolved] (UNOMI-208) Improve documentation flow & document tracker integration

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber resolved UNOMI-208.
---
Resolution: Fixed

> Improve documentation flow & document tracker integration
> -
>
> Key: UNOMI-208
> URL: https://issues.apache.org/jira/browse/UNOMI-208
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: website
>Affects Versions: 1.3.0-incubating, 1.4.0-incubating
>Reporter: Serge Huber
>Assignee: Serge Huber
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The idea is to improve the flow of subjects in the documentation as well as 
> add documentation for the new analytics.js tracker. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (UNOMI-208) Improve documentation flow & document tracker integration

[Serge Huber (JIRA)]

Serge Huber created UNOMI-208:
-

 Summary: Improve documentation flow & document tracker integration
 Key: UNOMI-208
 URL: https://issues.apache.org/jira/browse/UNOMI-208
 Project: Apache Unomi
  Issue Type: Improvement
  Components: website
Affects Versions: 1.3.0-incubating, 1.4.0-incubating
Reporter: Serge Huber
Assignee: Serge Huber
 Fix For: 1.4.0-incubating


The idea is to improve the flow of subjects in the documentation as well as add 
documentation for the new analytics.js tracker. 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

November Unomi board report

[Serge Huber]

Hello,

As we are a bit late for the graduation process, I have prepared a
board report for Unomi. Please review and comment :

Unomi

Unomi is a reference implementation of the OASIS Context Server specification
currently being worked on by the OASIS Context Server Technical Committee. It
provides a high-performance user profile and event tracking server.

Unomi has been incubating since 2015-10-05.

Three most important issues to address in the move towards graduation:

  1. Clarify IP clearance (on-going)
  2. Finalized graduation proposal draft
  3. Podling graduation vote once step 1 and 2 are complete

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No

How has the community developed since the last report?

We have added a new committer and PPMC member : François Papon and we
have prepared a list of PMC members for post-graduation.

How has the project developed since the last report?

After the release of Apache Unomi 1.3.0, we are now focused on
graduation. The maturity model report has been completed, the website
has been greatly expanded to clarify community joining and
communication, and a draft of the graduation proposal is being
discussed right now.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ X ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-09-10

When were the last committers or PPMC members elected?

  2018-09-19

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Our mentors are very helpful and responsive and are doing their best
to assist the project when asked.

Signed-off-by:

  [ ](unomi) Bertrand Delacretaz
 Comments:
  [ ](unomi) Jean-Baptiste Onofre
 Comments:

IPMC/Shepherd notes:

[jira] [Updated] (UNOMI-206) Add endpoint to search in events

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber updated UNOMI-206:
--
Description: 
The idea is to add an endpoint to be able to search events. This can be very 
useful to retrieve for example all the view events generate by a specific 
profile.

Here's an example of what such a query could look like : 

 

POST /cxs/events/search
{code:java}
{
  "limit" : 5,
  "condition" : {
"type" : "booleanCondition", 
"parameterValues" : {
  "operator" : "and",
  "subConditions" : [ 
{
  "type" : "eventTypeCondition",
  "parameterValues" : {
"eventTypeId" : "view"
  }
},
{
  "type" : "eventPropertyCondition",
  "parameterValues" : {
"propertyName" : "profileId", 
"comparisonOperator" : "equals", 
"propertyValue" : "0daab9e1-fc20-48a5-bfd7-a9dc634d8b9e"
  }
}
  ]
}
  }
}{code}
 

  was:
The idea is to add an endpoint to be able to search events. This can be very 
useful to retrieve for example all the view events generate by a specific 
profile.

Here's an example of what such a query could look like : 

 

POST /cxs/events/search
{code:java}
{
"limit" : 5,
"condition" : {
"type" : "booleanCondition", 
"parameterValues" : {
"operator" : "and",
"subConditions" : [ 
{
"type" : "eventTypeCondition",
"parameterValues" : {
"eventTypeId" : "view"
}
},
{
"type" : "eventPropertyCondition",
"parameterValues" : {
"propertyName" : "profileId", 
"comparisonOperator" : "equals", 
"propertyValue" : "0daab9e1-fc20-48a5-bfd7-a9dc634d8b9e"
}
}
]
}
}
}{code}
 


> Add endpoint to search in events
> 
>
> Key: UNOMI-206
> URL: https://issues.apache.org/jira/browse/UNOMI-206
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.1.0-incubating, 1.2.0-incubating, 1.3.0-incubating
>Reporter: Serge Huber
>Assignee: Serge Huber
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The idea is to add an endpoint to be able to search events. This can be very 
> useful to retrieve for example all the view events generate by a specific 
> profile.
> Here's an example of what such a query could look like : 
>  
> POST /cxs/events/search
> {code:java}
> {
>   "limit" : 5,
>   "condition" : {
> "type" : "booleanCondition", 
> "parameterValues" : {
>   "operator" : "and",
>   "subConditions" : [ 
> {
>   "type" : "eventTypeCondition",
>   "parameterValues" : {
> "eventTypeId" : "view"
>   }
> },
> {
>   "type" : "eventPropertyCondition",
>   "parameterValues" : {
> "propertyName" : "profileId", 
> "comparisonOperator" : "equals", 
> "propertyValue" : "0daab9e1-fc20-48a5-bfd7-a9dc634d8b9e"
>   }
> }
>   ]
> }
>   }
> }{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (UNOMI-206) Add endpoint to search in events

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber resolved UNOMI-206.
---
Resolution: Fixed

> Add endpoint to search in events
> 
>
> Key: UNOMI-206
> URL: https://issues.apache.org/jira/browse/UNOMI-206
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.1.0-incubating, 1.2.0-incubating, 1.3.0-incubating
>    Reporter: Serge Huber
>Assignee: Serge Huber
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The idea is to add an endpoint to be able to search events. This can be very 
> useful to retrieve for example all the view events generate by a specific 
> profile.
> Here's an example of what such a query could look like : 
>  
> POST /cxs/events/search
> {code:java}
> {
> "limit" : 5,
> "condition" : {
> "type" : "booleanCondition", 
> "parameterValues" : {
> "operator" : "and",
> "subConditions" : [ 
> {
> "type" : "eventTypeCondition",
> "parameterValues" : {
> "eventTypeId" : "view"
> }
> },
> {
> "type" : "eventPropertyCondition",
> "parameterValues" : {
> "propertyName" : "profileId", 
> "comparisonOperator" : "equals", 
> "propertyValue" : "0daab9e1-fc20-48a5-bfd7-a9dc634d8b9e"
> }
> }
> ]
> }
> }
> }{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (UNOMI-206) Add endpoint to search in events

[Serge Huber (JIRA)]

Serge Huber created UNOMI-206:
-

 Summary: Add endpoint to search in events
 Key: UNOMI-206
 URL: https://issues.apache.org/jira/browse/UNOMI-206
 Project: Apache Unomi
  Issue Type: Improvement
  Components: core
Affects Versions: 1.3.0-incubating, 1.2.0-incubating, 1.1.0-incubating
Reporter: Serge Huber
Assignee: Serge Huber
 Fix For: 1.4.0-incubating


The idea is to add an endpoint to be able to search events. This can be very 
useful to retrieve for example all the view events generate by a specific 
profile.

Here's an example of what such a query could look like : 

 

POST /cxs/events/search
{code:java}
{
"limit" : 5,
"condition" : {
"type" : "booleanCondition", 
"parameterValues" : {
"operator" : "and",
"subConditions" : [ 
{
"type" : "eventTypeCondition",
"parameterValues" : {
"eventTypeId" : "view"
}
},
{
"type" : "eventPropertyCondition",
"parameterValues" : {
"propertyName" : "profileId", 
"comparisonOperator" : "equals", 
"propertyValue" : "0daab9e1-fc20-48a5-bfd7-a9dc634d8b9e"
}
}
]
}
}
}{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [jenkins] - Build for PR

[Serge Huber]

Who's fox ?

But I'm +1 for this.

On Thu, Oct 18, 2018 at 7:25 AM Jean-Baptiste Onofré  wrote:
>
> If fox agrees,  I can  do that ;)
>
> Regards
> JB
>
> On 17/10/2018 14:34, Serge Huber wrote:
> > I'd love to help but I don't have the karma for Jenkins, not sure if I
> > can get it or if it is reserved to Apache Members ?
> >
> > Regards,
> >   Serge...
> > On Wed, Oct 17, 2018 at 2:23 PM Francois Papon
> >  wrote:
> >>
> >> Yes, we have this in Karaf :
> >>
> >> https://builds.apache.org/view/K/view/Karaf/
> >>
> >> May be JB can help to configure it.
> >>
> >> regards,
> >>
> >> François Papon
> >> fpa...@apache.org
> >>
> >> Le 17/10/2018 à 16:09, Serge Huber a écrit :
> >>> Is that actually possible with Jenkins ?
> >>>
> >>> Regards,
> >>>   Serge...
> >>> On Wed, Oct 17, 2018 at 1:44 PM Francois Papon
> >>>  wrote:
> >>>> Hi,
> >>>>
> >>>> I think it would be nice if we could have a Jenkins build dedicated to 
> >>>> PR.
> >>>>
> >>>> Thoughts ?
> >>>>
> >>>> regards,
> >>>>
> >>>> --
> >>>> François Papon
> >>>> fpa...@apache.org
> >>>>
> >>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: Towards graduation

[Serge Huber]

Hello Justin,

I meant to say the SGA for past contributions prior to joining the incubator.

As for the PMC roster they will be removed in the next draft.

Regards,
  Serge...
On Thu, Oct 18, 2018 at 3:03 AM Justin Mclean  wrote:
>
> Hi,
>
> >As for their commits prior to that they should be covered by the Corporate 
> >CLA, as I understand it.
>
> As I understand it that isn't the case.
>
> If they haven't made any contributions to the code at all why are they being 
> added to the PMC? Did they contribute in other ways?
>
> Thanks,
> Justin

Re: [jenkins] - Build for PR

[Serge Huber]

I'd love to help but I don't have the karma for Jenkins, not sure if I
can get it or if it is reserved to Apache Members ?

Regards,
  Serge...
On Wed, Oct 17, 2018 at 2:23 PM Francois Papon
 wrote:
>
> Yes, we have this in Karaf :
>
> https://builds.apache.org/view/K/view/Karaf/
>
> May be JB can help to configure it.
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 17/10/2018 à 16:09, Serge Huber a écrit :
> > Is that actually possible with Jenkins ?
> >
> > Regards,
> >   Serge...
> > On Wed, Oct 17, 2018 at 1:44 PM Francois Papon
> >  wrote:
> >> Hi,
> >>
> >> I think it would be nice if we could have a Jenkins build dedicated to PR.
> >>
> >> Thoughts ?
> >>
> >> regards,
> >>
> >> --
> >> François Papon
> >> fpa...@apache.org
> >>
>

Re: [jenkins] - Build for PR

[Serge Huber]

Is that actually possible with Jenkins ?

Regards,
  Serge...
On Wed, Oct 17, 2018 at 1:44 PM Francois Papon
 wrote:
>
> Hi,
>
> I think it would be nice if we could have a Jenkins build dedicated to PR.
>
> Thoughts ?
>
> regards,
>
> --
> François Papon
> fpa...@apache.org
>

Re: Towards graduation

[Serge Huber]

As these people didn’t have ICLAs they also didn’t have commit access and no 
code was therefore contributed by them. As for their commits prior to that they 
should be covered by the Corporate CLA, as I understand it.

Regards,
  Serge… 

> On 16 Oct 2018, at 02:02, Justin Mclean  wrote:
> 
> Hi,
> 
>> I have to check but IP Clearance has been done already.
> 
> I'm not sure that is the case, if you have contributors who haven't signed 
> ICLAs, then their code isn't covered by an agreement with the ASF.
> 
>> Let me double check today.
> 
> Please tell me what you find and CC me as I'm not subscribed to this list.
> 
> Thanks,
> Justin

Re: Towards graduation

[Serge Huber]

Hello Justin,

Concerning the two ICLAs being submitted they are actually from Kevan
& Mohamed (Cédric's was already on file but the account was not
created at the time I'm not sure why). We initiated the process of
making sure the roster was up to date on Whimsy and caught a few
inconsistencies we are now fixing. I asked Kevan & Cédric if they
wanted to stay on as committers and as they said yes so I told them to
submit updated ICLAs with the project's name and ids because somehow
it didn't go through properly the first time. As for Mohamed his vote
to become a committer had been completed a while ago (April 2018) and
his account had not been created so we again made sure that everything
was properly done and cleanup before graduation.

Over the weekend I also made sure that the project is compliant with
the Whimsy website checks (https://whimsy.apache.org/pods/, note that
even some TLPs are not fully compliant) and are trying our best to
make sure everything is checked and double checked for graduation.

Best regards,
  Serge...
On Sun, Oct 14, 2018 at 3:09 AM Justin Mclean  wrote:
>
> Hi,
>
> I have a couple of concerns that hopefully you can address.
>
> First off your podling doesn’t seem to have any PPMC or committers on the 
> roster. [1] I not sure how you even able to commit code but perhaps something 
> is broken on the reporting side?
>
> The following people (from a quick search so I could be mistaken) don’t seem 
> to be active in your project, is there any reason they are being added to the 
> PPMC? Often at graduation it's best to ask inactive PPMC members if they want 
> to continue with the project.
>
>   * Sergiy Shyrkov
>   * Kevan Jahanshahi
>   * Cédric Mailleux
>   * Régis Mora
>   * Quentin Lamerand
>   * David Griffon
>
> This shows a couple of those people active mid 2015 but not after that. [2]
>
> Three members of the proposed PPMC hasn’t even signed ICLAs (AFAIKS) which 
> seems a bit unusual.
>
> * Kevan Jahanshahi
> * Cédric Mailleux
> * Régis Mora
>
> And two others have only just signed them. Why are they signing them just 
> before graduation?
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/roster/ppmc/unomi
> 2. https://github.com/apache/incubator-unomi/graphs/contributors

Re: past events optimizations

[Serge Huber]

Sounds great ! +1

Do you have any ideas of potential impacts of these changes ? Do we
need to look at specific areas to test ?

Regards,
  Serge...
On Fri, Oct 12, 2018 at 4:28 PM Thomas Draier  wrote:
>
> Hi,
>
> I did different optimizations related as described in UNOMI-204 - they are
> currently in a branch, but in my opinion we can merge it (maybe still need
> to make some parameters configurable). What do you think ?
>
> Regards

Re: Please help review the maturity model report !

[Serge Huber]

Thanks JB,

I am welcoming all and any feedback because strangely this exercise is
not easy for me :)

Regards,
  Serge...
On Tue, Oct 9, 2018 at 12:41 PM Jean-Baptiste Onofré  wrote:
>
> I will take a look.
>
> Thanks
> JB
>
> Le 9 oct. 2018 à 13:29, à 13:29, Serge Huber  a écrit:
> >Hello,
> >
> >I have just updated (& completed !) the maturity model report page
> >available here:
> >http://unomi.apache.org/community-maturity-model-report.html
> >
> >I did my best to fill this in in an unbiased and objective way, but I
> >am only human. I also took some inspiration from the Apache Beam
> >maturity model report that is truly well produced.
> >
> >If the mentors (especially Bertrand since it's a little your baby this
> >report :)) could review this and give feedback this would be
> >fantastic.
> >
> >Thanks again for your help,
> >Regards,
> >  Serge...

Re: Please help review the maturity model report !

[Serge Huber]

Hello Bertrand, thank you for your feedback, I have adapted the CD30
entry to include your suggestion.

If you have any more please don't hesitate.

Regards,
  Serge...
On Tue, Oct 9, 2018 at 1:03 PM Bertrand Delacretaz
 wrote:
>
> Hi Serge,
>
> On Tue, Oct 9, 2018 at 12:29 PM Serge Huber  wrote:
> ...
> > http://unomi.apache.org/community-maturity-model-report.html
> ..
>
> Thanks for this! I think it looks great, just one comment/nitpick:
>
> For CD30 I'd prefer saying "Unomi can be built with Apache Maven in
> the usual way", the goal is to allow people to build it on their own,
> from released sources.
>
> -Bertrand

Please help review the maturity model report !

[Serge Huber]

Hello,

I have just updated (& completed !) the maturity model report page
available here:
http://unomi.apache.org/community-maturity-model-report.html

I did my best to fill this in in an unbiased and objective way, but I
am only human. I also took some inspiration from the Apache Beam
maturity model report that is truly well produced.

If the mentors (especially Bertrand since it's a little your baby this
report :)) could review this and give feedback this would be
fantastic.

Thanks again for your help,
Regards,
  Serge...

Re: Towards graduation

[Serge Huber]

Thanks for the correction François, I just merged them. I will
republish the site in a few minutes.

Regards,
  Serge...



On Mon, Oct 8, 2018 at 10:14 AM Francois Papon
 wrote:
>
> I made a PR to update the team members on the website, I saw that Damien
> was missing.
>
> @Serge : I can't add you as reviewer because my account is not yet in
> the incubator project LDAP...
>
> Regards,
>
> François Papon
> fpa...@apache.org
>
> Le 07/10/2018 à 20:46, Damien GAILLARD a écrit :
> > +1 for me and yes I'm missing in the list.
> >
> > Cheers
> > Damien
> >
> > On Sat, Oct 6, 2018 at 9:02 PM Serge Huber  wrote:
> >
> >> Thanks JB.
> >>
> >> Regards,
> >>   Serge...
> >> On Sat, Oct 6, 2018 at 6:16 PM Jean-Baptiste Onofré 
> >> wrote:
> >>> Hmm, my bad, let me update the proposal.
> >>>
> >>> Regards
> >>> JB
> >>>
> >>> On 06/10/2018 15:31, Serge Huber wrote:
> >>>> Hi, actually it was just brought to my attention that there is a
> >>>> committer/PPMC member missing in the list:
> >>>>
> >>>> Damien Gaillard, dgaill...@apache.org
> >>>>
> >>>> Regards,
> >>>>   Serge...
> >>>> On Sat, Oct 6, 2018 at 8:49 AM Serge Huber  wrote:
> >>>>> Everything looks good to me and I confirm I want to continue on the
> >>>>> PMC as well as I would be honored to serve as VP.
> >>>>>
> >>>>> +1 for me. Looking forward to the next big step !
> >>>>>
> >>>>> Regards,
> >>>>>   Serge...
> >>>>> On Sat, Oct 6, 2018 at 6:47 AM Francois Papon
> >>>>>  wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> +1 for me!
> >>>>>>
> >>>>>> Thanks JB,
> >>>>>>
> >>>>>> regards,
> >>>>>>
> >>>>>> François Papon
> >>>>>> fpa...@apache.org
> >>>>>>
> >>>>>> Le 06/10/2018 à 08:28, Jean-Baptiste Onofré a écrit :
> >>>>>>> Hi guys,
> >>>>>>>
> >>>>>>> We are now preparing the graduation of Unomi as TLP project.
> >>>>>>>
> >>>>>>> I prepared a graduation resolution draft:
> >>>>>>>
> >>>>>>>X. Establish the Apache Unomi Project
> >>>>>>>
> >>>>>>>WHEREAS, the Board of Directors deems it to be in the best
> >>>>>>>interests of the Foundation and consistent with the
> >>>>>>>Foundation's purpose to establish a Project Management
> >>>>>>>Committee charged with the creation and maintenance of
> >>>>>>>open-source software, for distribution at no charge to
> >>>>>>>the public, related to a customer data platform, a server
> >>>>>>>designed to manage customers, leads and visitors data, and
> >>>>>>>help personalize customers experiences while also offering
> >>>>>>>features to respect visitor privacy rules (such as GDPR).
> >>>>>>>
> >>>>>>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>>>>>>Committee (PMC), to be known as the "Apache Unomi Project",
> >>>>>>>be and hereby is established pursuant to Bylaws of the
> >>>>>>>Foundation; and be it further
> >>>>>>>
> >>>>>>>RESOLVED, that the Apache Unomi Project be and hereby is
> >>>>>>>responsible for the creation and maintenance of software
> >>>>>>>related to a custom data platform, a server designed to
> >>>>>>>manage customers, leads and visitors data, and help
> >>>>>>>personalize customers experiences while also offering
> >>>>>>>features to respect visitor privacy
> >>>>>>>rules (such as GDPR); and be it further
> >>>>>>>
> >>>>>>>RESOLVED, that the office of "Vice President, Apache Unomi"
> >> be
> &g

Re: Towards graduation

[Serge Huber]

Thanks JB.

Regards,
  Serge...
On Sat, Oct 6, 2018 at 6:16 PM Jean-Baptiste Onofré  wrote:
>
> Hmm, my bad, let me update the proposal.
>
> Regards
> JB
>
> On 06/10/2018 15:31, Serge Huber wrote:
> > Hi, actually it was just brought to my attention that there is a
> > committer/PPMC member missing in the list:
> >
> > Damien Gaillard, dgaill...@apache.org
> >
> > Regards,
> >   Serge...
> > On Sat, Oct 6, 2018 at 8:49 AM Serge Huber  wrote:
> >>
> >> Everything looks good to me and I confirm I want to continue on the
> >> PMC as well as I would be honored to serve as VP.
> >>
> >> +1 for me. Looking forward to the next big step !
> >>
> >> Regards,
> >>   Serge...
> >> On Sat, Oct 6, 2018 at 6:47 AM Francois Papon
> >>  wrote:
> >>>
> >>> Hi,
> >>>
> >>> +1 for me!
> >>>
> >>> Thanks JB,
> >>>
> >>> regards,
> >>>
> >>> François Papon
> >>> fpa...@apache.org
> >>>
> >>> Le 06/10/2018 à 08:28, Jean-Baptiste Onofré a écrit :
> >>>> Hi guys,
> >>>>
> >>>> We are now preparing the graduation of Unomi as TLP project.
> >>>>
> >>>> I prepared a graduation resolution draft:
> >>>>
> >>>>X. Establish the Apache Unomi Project
> >>>>
> >>>>WHEREAS, the Board of Directors deems it to be in the best
> >>>>interests of the Foundation and consistent with the
> >>>>Foundation's purpose to establish a Project Management
> >>>>Committee charged with the creation and maintenance of
> >>>>open-source software, for distribution at no charge to
> >>>>the public, related to a customer data platform, a server
> >>>>designed to manage customers, leads and visitors data, and
> >>>>help personalize customers experiences while also offering
> >>>>features to respect visitor privacy rules (such as GDPR).
> >>>>
> >>>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>>>Committee (PMC), to be known as the "Apache Unomi Project",
> >>>>be and hereby is established pursuant to Bylaws of the
> >>>>Foundation; and be it further
> >>>>
> >>>>RESOLVED, that the Apache Unomi Project be and hereby is
> >>>>responsible for the creation and maintenance of software
> >>>>related to a custom data platform, a server designed to
> >>>>manage customers, leads and visitors data, and help
> >>>>personalize customers experiences while also offering
> >>>>    features to respect visitor privacy
> >>>>rules (such as GDPR); and be it further
> >>>>
> >>>>RESOLVED, that the office of "Vice President, Apache Unomi" be
> >>>>and hereby is created, the person holding such office to
> >>>>serve at the direction of the Board of Directors as the chair
> >>>>of the Apache Unomi Project, and to have primary responsibility
> >>>>for management of the projects within the scope of
> >>>>responsibility of the Apache Unomi Project; and be it further
> >>>>
> >>>>RESOLVED, that the persons listed immediately below be and
> >>>>hereby are appointed to serve as the initial members of the
> >>>>Apache Unomi Project:
> >>>>
> >>>>  * Serge Huber 
> >>>>  * Jean-Baptiste Onofré 
> >>>>  * Thomas Draier 
> >>>>  * Sergiy Shyrkov
> >>>>  * Kevan Jahanshahi
> >>>>  * Cédric Mailleux
> >>>>  * Régis Mora
> >>>>  * Quentin Lamerand
> >>>>  * Chris Laprun 
> >>>>  * David Griffon
> >>>>  * Abdelkader Midani 
> >>>>  * François Papon 
> >>>>
> >>>>
> >>>>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber
> >>>>be appointed to the office of Vice President, Apache Unomi, to
> >>>>serve in accordance with and

Re: Towards graduation

[Serge Huber]

Hi, actually it was just brought to my attention that there is a
committer/PPMC member missing in the list:

Damien Gaillard, dgaill...@apache.org

Regards,
  Serge...
On Sat, Oct 6, 2018 at 8:49 AM Serge Huber  wrote:
>
> Everything looks good to me and I confirm I want to continue on the
> PMC as well as I would be honored to serve as VP.
>
> +1 for me. Looking forward to the next big step !
>
> Regards,
>   Serge...
> On Sat, Oct 6, 2018 at 6:47 AM Francois Papon
>  wrote:
> >
> > Hi,
> >
> > +1 for me!
> >
> > Thanks JB,
> >
> > regards,
> >
> > François Papon
> > fpa...@apache.org
> >
> > Le 06/10/2018 à 08:28, Jean-Baptiste Onofré a écrit :
> > > Hi guys,
> > >
> > > We are now preparing the graduation of Unomi as TLP project.
> > >
> > > I prepared a graduation resolution draft:
> > >
> > >X. Establish the Apache Unomi Project
> > >
> > >WHEREAS, the Board of Directors deems it to be in the best
> > >interests of the Foundation and consistent with the
> > >Foundation's purpose to establish a Project Management
> > >Committee charged with the creation and maintenance of
> > >open-source software, for distribution at no charge to
> > >the public, related to a customer data platform, a server
> > >designed to manage customers, leads and visitors data, and
> > >help personalize customers experiences while also offering
> > >features to respect visitor privacy rules (such as GDPR).
> > >
> > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >Committee (PMC), to be known as the "Apache Unomi Project",
> > >be and hereby is established pursuant to Bylaws of the
> > >Foundation; and be it further
> > >
> > >RESOLVED, that the Apache Unomi Project be and hereby is
> > >responsible for the creation and maintenance of software
> > >related to a custom data platform, a server designed to
> > >manage customers, leads and visitors data, and help
> > >personalize customers experiences while also offering
> > >features to respect visitor privacy
> > >rules (such as GDPR); and be it further
> > >
> > >RESOLVED, that the office of "Vice President, Apache Unomi" be
> > >and hereby is created, the person holding such office to
> > >serve at the direction of the Board of Directors as the chair
> > >of the Apache Unomi Project, and to have primary responsibility
> > >for management of the projects within the scope of
> > >responsibility of the Apache Unomi Project; and be it further
> > >
> > >RESOLVED, that the persons listed immediately below be and
> > >hereby are appointed to serve as the initial members of the
> > >    Apache Unomi Project:
> > >
> > >  * Serge Huber 
> > >  * Jean-Baptiste Onofré 
> > >  * Thomas Draier 
> > >  * Sergiy Shyrkov
> > >  * Kevan Jahanshahi
> > >  * Cédric Mailleux
> > >  * Régis Mora
> > >  * Quentin Lamerand
> > >  * Chris Laprun 
> > >  * David Griffon
> > >  * Abdelkader Midani 
> > >  * François Papon 
> > >
> > >
> > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber
> > >be appointed to the office of Vice President, Apache Unomi, to
> > >serve in accordance with and subject to the direction of the
> > >Board of Directors and the Bylaws of the Foundation until
> > >death, resignation, retirement, removal or disqualification,
> > >or until a successor is appointed; and be it further
> > >
> > >RESOLVED, that the initial Apache Unomi PMC be and hereby is
> > >tasked with the creation of a set of bylaws intended to
> > >encourage open development and increased participation in the
> > >Apache Unomi Project; and be it further
> > >
> > >RESOLVED, that the Apache Unomi Project be and hereby
> > >is tasked with the migration and rationalization of the Apache
> > >Incubator Unomi podling; and be it further
> > >
> > >RESOLVED, that all responsibilities pertaining to the Apache
> > >Incubator Unomi podling encumbered upon the Apache Incubator
> > >Project are hereafter discharged.
> > >
> > >
> > > Please review the draft and let me know if you have any comment.
> > >
> > > Regarding the proposed initial PMC member list, I invite any Unomi
> > > committer to confirm if they want to be PMC member. Please, do it asap
> > > as we would like to submit the graduation vote soon.
> > >
> > > Thanks
> > > Regards
> > > JB
> >

Re: Towards graduation

[Serge Huber]

Everything looks good to me and I confirm I want to continue on the
PMC as well as I would be honored to serve as VP.

+1 for me. Looking forward to the next big step !

Regards,
  Serge...
On Sat, Oct 6, 2018 at 6:47 AM Francois Papon
 wrote:
>
> Hi,
>
> +1 for me!
>
> Thanks JB,
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 06/10/2018 à 08:28, Jean-Baptiste Onofré a écrit :
> > Hi guys,
> >
> > We are now preparing the graduation of Unomi as TLP project.
> >
> > I prepared a graduation resolution draft:
> >
> >X. Establish the Apache Unomi Project
> >
> >WHEREAS, the Board of Directors deems it to be in the best
> >interests of the Foundation and consistent with the
> >Foundation's purpose to establish a Project Management
> >Committee charged with the creation and maintenance of
> >open-source software, for distribution at no charge to
> >the public, related to a customer data platform, a server
> >designed to manage customers, leads and visitors data, and
> >help personalize customers experiences while also offering
> >features to respect visitor privacy rules (such as GDPR).
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >Committee (PMC), to be known as the "Apache Unomi Project",
> >be and hereby is established pursuant to Bylaws of the
> >Foundation; and be it further
> >
> >RESOLVED, that the Apache Unomi Project be and hereby is
> >responsible for the creation and maintenance of software
> >related to a custom data platform, a server designed to
> >manage customers, leads and visitors data, and help
> >personalize customers experiences while also offering
> >features to respect visitor privacy
> >rules (such as GDPR); and be it further
> >
> >RESOLVED, that the office of "Vice President, Apache Unomi" be
> >and hereby is created, the person holding such office to
> >serve at the direction of the Board of Directors as the chair
> >of the Apache Unomi Project, and to have primary responsibility
> >for management of the projects within the scope of
> >responsibility of the Apache Unomi Project; and be it further
> >
> >RESOLVED, that the persons listed immediately below be and
> >hereby are appointed to serve as the initial members of the
> >Apache Unomi Project:
> >
> >  * Serge Huber 
> >  * Jean-Baptiste Onofré 
> >  * Thomas Draier 
> >  * Sergiy Shyrkov
> >  * Kevan Jahanshahi
> >  * Cédric Mailleux
> >  * Régis Mora
> >  * Quentin Lamerand
> >  * Chris Laprun 
> >  * David Griffon
> >  * Abdelkader Midani 
> >  * François Papon 
> >
> >
> >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber
> >be appointed to the office of Vice President, Apache Unomi, to
> >serve in accordance with and subject to the direction of the
> >Board of Directors and the Bylaws of the Foundation until
> >death, resignation, retirement, removal or disqualification,
> >or until a successor is appointed; and be it further
> >
> >RESOLVED, that the initial Apache Unomi PMC be and hereby is
> >tasked with the creation of a set of bylaws intended to
> >encourage open development and increased participation in the
> >Apache Unomi Project; and be it further
> >
> >RESOLVED, that the Apache Unomi Project be and hereby
> >is tasked with the migration and rationalization of the Apache
> >Incubator Unomi podling; and be it further
> >
> >RESOLVED, that all responsibilities pertaining to the Apache
> >Incubator Unomi podling encumbered upon the Apache Incubator
> >Project are hereafter discharged.
> >
> >
> > Please review the draft and let me know if you have any comment.
> >
> > Regarding the proposed initial PMC member list, I invite any Unomi
> > committer to confirm if they want to be PMC member. Please, do it asap
> > as we would like to submit the graduation vote soon.
> >
> > Thanks
> > Regards
> > JB
>

Re: Override/migration of predefined definition files

[Serge Huber]

of
> > >>> some "migration" or "update" json file wrapping the patch, within
> > >the same
> > >>> folder as the definitions :
> > >>>
> > >>> {
> > >>>   "itemId": "firstName",
> > >>>   "updateId": "firstName-patch1",
> > >>>   "operation": "patch",
> > >>>   "patch": [
> > >>> {
> > >>>   "op": "replace", "path": "/defaultValue", "value": "foo"
> > >>> }
> > >>>   ]
> > >>> }
> > >>>
> > >>>
> > >>> A removal :
> > >>>
> > >>> {
> > >>>   "itemId": "firstName",
> > >>>   "updateId": "firstName-patch1",
> > >>>   "operation": "remove"
> > >>> }
> > >>>
> > >>> Or a complete override :
> > >>>
> > >>> {
> > >>>   "itemId": "firstName",
> > >>>   "updateId": "firstName-patch1",
> > >>>   "operation": "override",
> > >>>   "definition": {
> > >>> "metadata": {
> > >>>   "id": "firstName",
> > >>>   "name": "First name",
> > >>>   "systemTags": [
> > >>> "properties",
> > >>> "profileProperties",
> > >>> "basicProfileProperties",
> > >>> "personalIdentifierProperties"
> > >>>   ]
> > >>> },
> > >>> "type": "string",
> > >>> "defaultValue": "",
> > >>> "automaticMappingsFrom": [ ],
> > >>> "rank": "101.0"
> > >>>   }
> > >>> }
> > >>>
> > >>>
> > >>> This could actually be extended with other type of operation.
> > >>>
> > >>> For now I do store "updateId" in the metadata of the item, so that
> > >it's
> > >>> not executed multiple times. But we have have an issue with the
> > >delete if
> > >>> the item is recreated after.. Maybe I should store the list of
> > >updates in a
> > >>> new structure ? That could also be accessible with karaf commands,
> > >to see
> > >>> which patch have been executed and reexecute them if needed.
> > >>>
> > >>> Thomas
> > >>>
> > >>>
> > >>> On Tue, Sep 18, 2018 at 11:46 AM Francois Papon <
> > >>> francois.pa...@openobject.fr> wrote:
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> Very interesting flow :)
> > >>>>
> > >>>> What is the format to update the definitions, it's just a new JSON,
> > >is
> > >>>> there some directives about the changes ?
> > >>>>
> > >>>> For example, in Karaf we have something like this to override
> > >>>> configuration files :
> > >>>>
> > >>>>
> > >>>>  
> > >>>>config.properties
> > >>>>put
> > >>>>karaf.framework
> > >>>>equinox
> > >>>>  
> > >>>>  
> > >>>>config.properties
> > >>>>extend
> > >>>>org.osgi.framework.system.capabilities
> > >>>>my-magic-capability
> > >>>>  
> > >>>>  
> > >>>>config.properties
> > >>>>remove
> > >>>>org.apache.karaf.security.providers
> > >>>>  
> > >>>>
> > >>>>
> > >>>> May be a solution is a file with a patch description of the changes
> > >?
> > >>>>
> > >>>> regards,
> > >>>>
> > >>>> Françoi

Re: [PROPOSAL] Apache Unomi roadmap and toward graduation

[Serge Huber]

That's fine with me, but check with JB also.

cheers,
  Serge...
On Fri, Sep 28, 2018 at 4:08 AM Francois Papon
 wrote:
>
> Hi,
>
> I just created a Jira about the KarafTestSupport :
>
> https://issues.apache.org/jira/browse/UNOMI-203
>
> If you are ok, I can take it ;)
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 28/09/2018 à 11:29, Serge Huber a écrit :
> > Ok JB,
> >
> > I look forward to it ! Thanks might be a little crazy (I have 4 talks
> > to present next week) but we'll make time to do this.
> >
> > Regards,
> >   Serge...
> > On Thu, Sep 27, 2018 at 4:19 PM Jean-Baptiste Onofré  
> > wrote:
> >> Thanks the update Serge.
> >>
> >> I will create Jira about blueprint to scr.
> >>
> >> I propose to discuss next week about GraphQL and unomi with Karaf vineyard.
> >>
> >> Thanks !
> >> Regards
> >> JB
> >>
> >> Le 27 sept. 2018 à 16:07, à 16:07, Serge Huber  a écrit:
> >>> Hello JB,
> >>>
> >>> Thanks for doing all that.
> >>>
> >>> Concerning the roadmap, we have issues in JIRA for everything except
> >>> the new UI contribution, but this will probably be opened as soon as
> >>> things are clearer on Jahia's side. I've attached each ticket to
> >>> future versions (1.4.0 or 2.0.0) so everything should be ok there.
> >>>
> >>> We actually are also missing a task to move from Blueprint to DS/SCR,
> >>> so the first step would be to create that ticket. Since you're
> >>> proposing to work on that could you also create the ticket ?
> >>>
> >>> I actually need to get back to work on the CDP GraphQL API
> >>> integration. I need to also update the branch because it's a bit
> >>> behind the latest commits.
> >>>
> >>> 2.4 would be fantastic, especially the new itests that have been very
> >>> difficult to get to work properly.
> >>>
> >>> Regards,
> >>>  Serge...
> >>>
> >>> On Thu, Sep 27, 2018 at 9:38 AM Jean-Baptiste Onofré 
> >>> wrote:
> >>>> Hi guys,
> >>>>
> >>>> as we already started to discuss all together, we are heading to
> >>>> graduation, proposing Apache Unomi as new Apache TLP project to the
> >>> IPMC.
> >>>> That's a process on which we are moving forward and we are on track.
> >>>>
> >>>> On the other hand, I would like also to discuss about more the
> >>> technical
> >>>> Unomi roadmap.
> >>>>
> >>>> I would split the roadmap in two topics:
> >>>>
> >>>> 1. Problems solved
> >>>>
> >>>> @Serge, can you  provide us some update about specification or new
> >>> end
> >>>> user features you have in mind in future Unomi releases ?
> >>>> Do we already have Jira about that ?
> >>>>
> >>>> 2. Unomi ecosystem
> >>>>
> >>>> I have few actions in progress in my bucket:
> >>>>
> >>>> 2.1. Refactore Unomi to use DS/SCR instead of blueprint and have a
> >>> more
> >>>> fine grained Karaf features, leveraging Karaf 4.2.1 (and probably
> >>> 4.2.2
> >>>> when it will be available).
> >>>> 2.2. Add the Unomi kafka "connector" injecting data in async mode to
> >>>> avoid bottleneck
> >>>> 2.3. PoC about Unomi with Karaf Vineyard (especially for GraphQL
> >>> part)
> >>>> 2.4. New devops/packaging of Unomi based on new features available in
> >>>> Karaf 4.2.x (docker, new way of building distribution, simplified
> >>> itests
> >>>> with "new" KarafTestSupport, ...)
> >>>>
> >>>> If you have actions or features in mind, please let us know.
> >>>>
> >>>> Thanks !
> >>>> Regards
> >>>> JB
> >>>> --
> >>>> Jean-Baptiste Onofré
> >>>> jbono...@apache.org
> >>>> http://blog.nanthrax.net
> >>>> Talend - http://www.talend.com
>

[jira] [Closed] (UNOMI-176) 1.3.0 Release Date

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber closed UNOMI-176.
-
   Resolution: Fixed
Fix Version/s: 1.3.0-incubating

1.3.0 has been released.

> 1.3.0 Release Date
> --
>
> Key: UNOMI-176
> URL: https://issues.apache.org/jira/browse/UNOMI-176
> Project: Apache Unomi
>  Issue Type: Wish
>Reporter: Don Hinshaw
>Priority: Minor
> Fix For: 1.3.0-incubating
>
>
> There are some changes that are going to be included in the 1.3.0 Release 
> that we are interested in.  Can you provide a rough estimate of when 1.3.0 
> will be released?
> Please let me know if there is a better way to ask these questions in the 
> future.
> Thanks,
> Donnie



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [jira] [Commented] (UNOMI-176) 1.3.0 Release Date

[Serge Huber]

Yes you're right François, I just closed it thanks !

Regards,
  Serge...

On Fri, Sep 28, 2018 at 4:01 AM Francois Papon (JIRA)  wrote:
>
>
> [ 
> https://issues.apache.org/jira/browse/UNOMI-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631499#comment-16631499
>  ]
>
> Francois Papon commented on UNOMI-176:
> --
>
> This issue can be closed as the 1.3.0 release has been released ?
>
> > 1.3.0 Release Date
> > --
> >
> > Key: UNOMI-176
> > URL: https://issues.apache.org/jira/browse/UNOMI-176
> > Project: Apache Unomi
> >  Issue Type: Wish
> >Reporter: Don Hinshaw
> >Priority: Minor
> >
> > There are some changes that are going to be included in the 1.3.0 Release 
> > that we are interested in.  Can you provide a rough estimate of when 1.3.0 
> > will be released?
> > Please let me know if there is a better way to ask these questions in the 
> > future.
> > Thanks,
> > Donnie
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)

Re: [PROPOSAL] Apache Unomi roadmap and toward graduation

[Serge Huber]

Ok JB,

I look forward to it ! Thanks might be a little crazy (I have 4 talks
to present next week) but we'll make time to do this.

Regards,
  Serge...
On Thu, Sep 27, 2018 at 4:19 PM Jean-Baptiste Onofré  wrote:
>
> Thanks the update Serge.
>
> I will create Jira about blueprint to scr.
>
> I propose to discuss next week about GraphQL and unomi with Karaf vineyard.
>
> Thanks !
> Regards
> JB
>
> Le 27 sept. 2018 à 16:07, à 16:07, Serge Huber  a écrit:
> >Hello JB,
> >
> >Thanks for doing all that.
> >
> >Concerning the roadmap, we have issues in JIRA for everything except
> >the new UI contribution, but this will probably be opened as soon as
> >things are clearer on Jahia's side. I've attached each ticket to
> >future versions (1.4.0 or 2.0.0) so everything should be ok there.
> >
> >We actually are also missing a task to move from Blueprint to DS/SCR,
> >so the first step would be to create that ticket. Since you're
> >proposing to work on that could you also create the ticket ?
> >
> >I actually need to get back to work on the CDP GraphQL API
> >integration. I need to also update the branch because it's a bit
> >behind the latest commits.
> >
> >2.4 would be fantastic, especially the new itests that have been very
> >difficult to get to work properly.
> >
> >Regards,
> >  Serge...
> >
> >On Thu, Sep 27, 2018 at 9:38 AM Jean-Baptiste Onofré 
> >wrote:
> >>
> >> Hi guys,
> >>
> >> as we already started to discuss all together, we are heading to
> >> graduation, proposing Apache Unomi as new Apache TLP project to the
> >IPMC.
> >>
> >> That's a process on which we are moving forward and we are on track.
> >>
> >> On the other hand, I would like also to discuss about more the
> >technical
> >> Unomi roadmap.
> >>
> >> I would split the roadmap in two topics:
> >>
> >> 1. Problems solved
> >>
> >> @Serge, can you  provide us some update about specification or new
> >end
> >> user features you have in mind in future Unomi releases ?
> >> Do we already have Jira about that ?
> >>
> >> 2. Unomi ecosystem
> >>
> >> I have few actions in progress in my bucket:
> >>
> >> 2.1. Refactore Unomi to use DS/SCR instead of blueprint and have a
> >more
> >> fine grained Karaf features, leveraging Karaf 4.2.1 (and probably
> >4.2.2
> >> when it will be available).
> >> 2.2. Add the Unomi kafka "connector" injecting data in async mode to
> >> avoid bottleneck
> >> 2.3. PoC about Unomi with Karaf Vineyard (especially for GraphQL
> >part)
> >> 2.4. New devops/packaging of Unomi based on new features available in
> >> Karaf 4.2.x (docker, new way of building distribution, simplified
> >itests
> >> with "new" KarafTestSupport, ...)
> >>
> >> If you have actions or features in mind, please let us know.
> >>
> >> Thanks !
> >> Regards
> >> JB
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com

Re: [PROPOSAL] Apache Unomi roadmap and toward graduation

[Serge Huber]

Hello JB,

Thanks for doing all that.

Concerning the roadmap, we have issues in JIRA for everything except
the new UI contribution, but this will probably be opened as soon as
things are clearer on Jahia's side. I've attached each ticket to
future versions (1.4.0 or 2.0.0) so everything should be ok there.

We actually are also missing a task to move from Blueprint to DS/SCR,
so the first step would be to create that ticket. Since you're
proposing to work on that could you also create the ticket ?

I actually need to get back to work on the CDP GraphQL API
integration. I need to also update the branch because it's a bit
behind the latest commits.

2.4 would be fantastic, especially the new itests that have been very
difficult to get to work properly.

Regards,
  Serge...

On Thu, Sep 27, 2018 at 9:38 AM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> as we already started to discuss all together, we are heading to
> graduation, proposing Apache Unomi as new Apache TLP project to the IPMC.
>
> That's a process on which we are moving forward and we are on track.
>
> On the other hand, I would like also to discuss about more the technical
> Unomi roadmap.
>
> I would split the roadmap in two topics:
>
> 1. Problems solved
>
> @Serge, can you  provide us some update about specification or new end
> user features you have in mind in future Unomi releases ?
> Do we already have Jira about that ?
>
> 2. Unomi ecosystem
>
> I have few actions in progress in my bucket:
>
> 2.1. Refactore Unomi to use DS/SCR instead of blueprint and have a more
> fine grained Karaf features, leveraging Karaf 4.2.1 (and probably 4.2.2
> when it will be available).
> 2.2. Add the Unomi kafka "connector" injecting data in async mode to
> avoid bottleneck
> 2.3. PoC about Unomi with Karaf Vineyard (especially for GraphQL part)
> 2.4. New devops/packaging of Unomi based on new features available in
> Karaf 4.2.x (docker, new way of building distribution, simplified itests
> with "new" KarafTestSupport, ...)
>
> If you have actions or features in mind, please let us know.
>
> Thanks !
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: Removal of context.js

[Serge Huber]

Forwarding this to the new Apache Unomi users mailing lists.

Are you using the context.js endpoint ? If yes please say so because
we were discussing the eventuality of removing it in the dev list !

Regards,
  Serge...
On Mon, Sep 24, 2018 at 11:36 AM Damien GAILLARD  wrote:
>
> It's okay for me to remove it but I think Grupo Globo could be using it.
>
> On Mon, Sep 24, 2018 at 10:44 AM Thomas Draier  wrote:
>
> > Hi,
> >
> > Since we now have a nice tracker integrated with unomi, i was wondering if
> > we could remove the context.js script (or base.js file) - actually I don't
> > know if anybody is using it ? All the methods provided there looks quite
> > outdated. What do you think  ?
> >
> > Thomas
> >
>
>
> --
> Damien GAILLARD
> Software Developer
> 
> 
> 8 rue du sentier | 75002 | France
> 
> 
> jahia.com 
> SKYPE | TWITTER  | VCARD
> 
>
> > JAHIA  empowers organizations to create
> sophisticated websites that drive their business growth

[jira] [Resolved] (UNOMI-200) New command line tools to view events, sessions and profiles

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber resolved UNOMI-200.
---
Resolution: Fixed

> New command line tools to view events, sessions and profiles
> 
>
> Key: UNOMI-200
> URL: https://issues.apache.org/jira/browse/UNOMI-200
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.4.0-incubating
>    Reporter: Serge Huber
>Assignee: Serge Huber
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The idea is to add new Karaf shell commands to :
>  * list the last modified profiles
>  * view a profile (JSON) given its identifier
>  * list the last modified sessions
>  * view a session (JSON) given its identifier
>  * a live (tail) of the incoming events in the server
>  * view a single event (JSON) given its identifier
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (UNOMI-200) New command line tools to view events, sessions and profiles

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623637#comment-16623637
 ] 

Serge Huber commented on UNOMI-200:
---

Along with the new commands, the old existing commands have been modified to 
use the unomi: scope, to avoid any conflict with other Karaf Shell commands

> New command line tools to view events, sessions and profiles
> 
>
> Key: UNOMI-200
> URL: https://issues.apache.org/jira/browse/UNOMI-200
> Project: Apache Unomi
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 1.4.0-incubating
>Reporter: Serge Huber
>Assignee: Serge Huber
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The idea is to add new Karaf shell commands to :
>  * list the last modified profiles
>  * view a profile (JSON) given its identifier
>  * list the last modified sessions
>  * view a session (JSON) given its identifier
>  * a live (tail) of the incoming events in the server
>  * view a single event (JSON) given its identifier
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (UNOMI-200) New command line tools to view events, sessions and profiles

[Serge Huber (JIRA)]

Serge Huber created UNOMI-200:
-

 Summary: New command line tools to view events, sessions and 
profiles
 Key: UNOMI-200
 URL: https://issues.apache.org/jira/browse/UNOMI-200
 Project: Apache Unomi
  Issue Type: Improvement
  Components: core
Affects Versions: 1.4.0-incubating
Reporter: Serge Huber
Assignee: Serge Huber
 Fix For: 1.4.0-incubating


The idea is to add new Karaf shell commands to :
 * list the last modified profiles
 * view a profile (JSON) given its identifier
 * list the last modified sessions
 * view a session (JSON) given its identifier
 * a live (tail) of the incoming events in the server
 * view a single event (JSON) given its identifier

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Override/migration of predefined definition files

[Serge Huber]

Not sure if you are talking about the patching system, but if yes you
would provide a patch file that removes all the contents of file.

If we are just using versions it is indeed a bit more tricky. We would
also need to have a way to list the definitions to remove.

Regards,
  Serge...

On Tue, Sep 18, 2018 at 11:23 AM Romain Gauthier  wrote:
>
> Hi Serge,
>
> In that context, how would we manage objects deletion from a plugin?
>
> Thanks!
>
> Romain
>
> On Tue, Sep 18, 2018 at 10:45 AM Serge Huber  wrote:
>
> > Sorry, I didn't get around to this discussion but I think that
> > versions would probably be cleaner. I was even looking at solutions
> > such as JSON patch (https://github.com/java-json-tools/json-patch) to
> > be able to perform modifications on parts of definitions instead of
> > having to deploy a whole definition again.
> >
> > We had discussions about adding lots of metadata, including last
> > modification dates, maybe even hashes for the definition files, to
> > know if a definition has been changed or not.
> >
> > I think that one of the advantages of the patch idea is that you could
> > try to patch something if it's compatible, and if it's not you would
> > not deploy it. But this idea would mostly be for use cases where you
> > are interested in modifying something that comes out of the box in
> > Unomi, not for upgrading a plugin.
> >
> > With versions at least we could also track if a definition is on the
> > "default" version or has been modified somehow.
> >
> > For the cfg idea it feels weird to use a config file that way, maybe
> > we should put the marker file elsewhere but to be honest I don't have
> > a better idea :)
> >
> > Would love some input from JB or other Karaf experts :)
> >
> > Regards,
> >   Serge...
> >
> > On Tue, Sep 18, 2018 at 9:51 AM Thomas Draier  wrote:
> > >
> > > Hi,
> > >
> > > I have to check, but the idea would be to be able to package this cfg
> > file
> > > beside the bundle. I'm not familiar with unomi:migrate command, but we
> > can
> > > imagine that this command would extract and deploy the cfg file from the
> > > bundle - which would make the packaging easier (cfg directly inside the
> > > plugin). The thing is that we need to be able to remove the file once the
> > > definition has been "overridden" so that it's only done once, so the cfg
> > > file should not be deployed automatically on each startup.
> > >
> > > Another idea I had was to store sort of "version" of the definition
> > inside
> > > the metadata, and check if the json file has a greater "version" defined.
> > > That makes things even more easier when developing plugin and looks a
> > > little more clean, but I don't know if it would cover correctly all use
> > > cases.
> > >
> > > We should also extends the DeployDefinition shell command to be able to
> > > redeploy all definitions of a bundle.
> > >
> > > Thomas
> > >
> > >
> > > On Tue, Sep 18, 2018 at 1:33 AM Romain Gauthier 
> > wrote:
> > >
> > > > Hello Thomas,
> > > >
> > > > Nice proposition.How would it work for developers that are building
> > > > plugins? Would we have to add our own cfg file or somehow update the
> > cfg
> > > > file that you want to add?
> > > >
> > > > Since there is already a "unomi:migrate" command would you reuse that
> > > > trigger to update / delete the definitions of the objects?
> > > >
> > > > Same question regarding the plugins, should we also implement "migrate"
> > > > command?
> > > >
> > > > Thanks,
> > > >
> > > > Romain
> > > >
> > > > On Thu, Sep 13, 2018 at 6:22 PM Thomas Draier 
> > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I'm having some issues with the deployment and redeployment of the
> > json
> > > > > files containing default definitions (segments, properties, etc..).
> > Many
> > > > > services have these loadPredefined* methods which load data into ES,
> > > > based
> > > > > on json definition files. These methods only load the content once,
> > if
> > > > the
> > > > > object does not exist yet in ES. So if a bundle comes with an update
> >

Re: Override/migration of predefined definition files

[Serge Huber]

Sorry, I didn't get around to this discussion but I think that
versions would probably be cleaner. I was even looking at solutions
such as JSON patch (https://github.com/java-json-tools/json-patch) to
be able to perform modifications on parts of definitions instead of
having to deploy a whole definition again.

We had discussions about adding lots of metadata, including last
modification dates, maybe even hashes for the definition files, to
know if a definition has been changed or not.

I think that one of the advantages of the patch idea is that you could
try to patch something if it's compatible, and if it's not you would
not deploy it. But this idea would mostly be for use cases where you
are interested in modifying something that comes out of the box in
Unomi, not for upgrading a plugin.

With versions at least we could also track if a definition is on the
"default" version or has been modified somehow.

For the cfg idea it feels weird to use a config file that way, maybe
we should put the marker file elsewhere but to be honest I don't have
a better idea :)

Would love some input from JB or other Karaf experts :)

Regards,
  Serge...

On Tue, Sep 18, 2018 at 9:51 AM Thomas Draier  wrote:
>
> Hi,
>
> I have to check, but the idea would be to be able to package this cfg file
> beside the bundle. I'm not familiar with unomi:migrate command, but we can
> imagine that this command would extract and deploy the cfg file from the
> bundle - which would make the packaging easier (cfg directly inside the
> plugin). The thing is that we need to be able to remove the file once the
> definition has been "overridden" so that it's only done once, so the cfg
> file should not be deployed automatically on each startup.
>
> Another idea I had was to store sort of "version" of the definition inside
> the metadata, and check if the json file has a greater "version" defined.
> That makes things even more easier when developing plugin and looks a
> little more clean, but I don't know if it would cover correctly all use
> cases.
>
> We should also extends the DeployDefinition shell command to be able to
> redeploy all definitions of a bundle.
>
> Thomas
>
>
> On Tue, Sep 18, 2018 at 1:33 AM Romain Gauthier  wrote:
>
> > Hello Thomas,
> >
> > Nice proposition.How would it work for developers that are building
> > plugins? Would we have to add our own cfg file or somehow update the cfg
> > file that you want to add?
> >
> > Since there is already a "unomi:migrate" command would you reuse that
> > trigger to update / delete the definitions of the objects?
> >
> > Same question regarding the plugins, should we also implement "migrate"
> > command?
> >
> > Thanks,
> >
> > Romain
> >
> > On Thu, Sep 13, 2018 at 6:22 PM Thomas Draier  wrote:
> >
> > > Hi,
> > >
> > > I'm having some issues with the deployment and redeployment of the json
> > > files containing default definitions (segments, properties, etc..). Many
> > > services have these loadPredefined* methods which load data into ES,
> > based
> > > on json definition files. These methods only load the content once, if
> > the
> > > object does not exist yet in ES. So if a bundle comes with an update of
> > one
> > > of these file, it will just be ignored.
> > >
> > > Actually there was one ticket about this :
> > > https://issues.apache.org/jira/browse/UNOMI-182 , where definitions are
> > > always redeployed when a bundle is in "snapshot" version - but never for
> > a
> > > release version. So that's nice when you are in development, but not
> > > possible when upgrading a production environment.
> > >
> > > There also a console command to manually deploy a definition - which is
> > > also nice but cannot be automated in a migration.
> > >
> > > Of course there's a reason - these objects can be modified afterwards by
> > > using the API, and so restarting should not overwrite the modifications
> > by
> > > reimporting the file. Even if a module is updated and object is modified,
> > > the user may not want to overwrite his changes.
> > >
> > > However in some cases the developer may want to force the update of some
> > > specific objects ( it actually happened to us ). I'm looking for some
> > > additional solution to force redeployment of a definition.
> > >
> > > So far i was thinking of adding a cfg file, which would list the
> > properties
> > > to redeploy. This file would be removed once the properties are updated,
> > so
> > > that they are reloaded only once and not on every startup.
> > >
> > > As a bonus, I would also need to be able to remove definitions the same
> > > way. There's no way to do that now except using the REST API , it could
> > be
> > > good to also have a console command and to be able to remove definitions
> > > with the same cfg file.
> > >
> > > What do you think .. ?
> > >
> > > Regards,
> > >
> >
> >
> > --
> > Romain Gauthier
> > Product Manager at Jahia
> > + 33 6 20 18 35 25 <+33%206%2020%2018%2035%2025>
> > 8 Rue du sentier | 75002 Paris 

[jira] [Commented] (UNOMI-196) Unable to start karaf instance on fresh installation - elasticsearch error : java.lang.IllegalStateException: Received message from unsupported version: [5.2.2] minimal

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612097#comment-16612097
 ] 

Serge Huber commented on UNOMI-196:
---

Thanks Daniel for closing the issue ! 

> Unable to start karaf instance on fresh installation - elasticsearch error : 
> java.lang.IllegalStateException: Received message from unsupported version: 
> [5.2.2] minimal compatible version is: [5.6.0]
> ---
>
> Key: UNOMI-196
> URL: https://issues.apache.org/jira/browse/UNOMI-196
> Project: Apache Unomi
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.2.0-incubating
> Environment: Debian GNU/Linux 7 \n \l
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> HOSTNAME=303fbb102b27
> TERM=xterm
> PATH=/usr/lib/jvm/java-8-oracle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> PWD=/home/unomi/unomi-1.2.0-incubating
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> SHLVL=1
> HOME=/root
> _=/usr/bin/printenv
> OLDPWD=/home/unomi
> {
>   "name" : "hjui3pv",
>   "cluster_name" : "contextElasticSearch",
>   "cluster_uuid" : "kokAP-m7TOac6UkDY0gmEg",
>   "version" : {
> "number" : "6.3.2",
> "build_flavor" : "default",
> "build_type" : "deb",
> "build_hash" : "053779d",
> "build_date" : "2018-07-20T05:20:23.451332Z",
> "build_snapshot" : false,
> "lucene_version" : "7.3.1",
> "minimum_wire_compatibility_version" : "5.6.0",
> "minimum_index_compatibility_version" : "5.0.0"
>   },
>   "tagline" : "You Know, for Search"
> }
>Reporter: Daniel Engelman
>Priority: Major
>
> Services do not go live on a fresh installation. 
>  
> 1. running "bin/karaf" results in karaf loading and then "Initializing 
> Unomi..." which never finished.
> 2. Looking into log:display - it says: "Unable to initialize bean 
> elasticSearchPersistenceServiceImpl"
> 2018-08-23 12:55:58,615 | INFO | FelixStartLevel | RegionsPersistenceImpl | 
> 49 - org.apache.karaf.region.persist - 3.0.8 | Loading region digraph 
> persistence
> 2018-08-23 12:55:58,899 | INFO | FelixStartLevel | SecurityUtils | 30 - 
> org.apache.sshd.core - 0.14.0 | BouncyCastle not registered, using the 
> default JCE provider
> 2018-08-23 12:55:59,110 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Starting JMX OSGi agent
> 2018-08-23 12:55:59,157 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering MBean with ObjectName 
> [osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9]
>  for service with service.id [15]
> 2018-08-23 12:55:59,194 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.ServiceStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=serviceState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.BundleStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=bundleState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,197 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.PackageStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=packageState,version=1.5,framewor

Re: Analytics.js Integrations

[Serge Huber]

That should be ok, just be careful not to commit anything that has
licenses that are not compatible with Apache.

cheers,
  Serge...
On Wed, Sep 12, 2018 at 11:21 AM Damien GAILLARD  wrote:
>
> Hi guys,
>
> As some of you already noticed I'm working on an integration with
> SegmentIO/analytics.js for Unomi, the JIRA ticket can be found here
> .
> To do so I created a bundle, web-tracker, in the extensions and I'm using
> modern javascript such a yarn to build the analytics.js file that contains
> our Unomi plugin and to keep on working I will need to add the following
> exclusion to the rat plugin:
>
> 
> **/node_modules/**/*
> **/yarn.lock
> **/*.min.js
>
> I would like to know if there are any objections to that.
>
> Cheers
>
> --
> Damien GAILLARD
> Software Developer
> 
> 
> 8 rue du sentier | 75002 | France
> 
> 
> jahia.com 
> SKYPE | TWITTER  | VCARD
> 
>
> > JAHIA  empowers organizations to create
> sophisticated websites that drive their business growth

Re: Issues with segments

[Serge Huber]

Yeah it seems like a bad idea. Do you have a list of the problematic actions ?



On Tue, Sep 11, 2018 at 11:28 AM Thomas Draier  wrote:
>
> Hi,
>
> I did a simple fix checking the recursion depth. This work in my case
> (segments) and probably most of the cases, but some actions directly call
> the EventService.send method - which will reset the recursion count.
> Actually I have no idea why these actions are sending the "profileUpdated"
> event by themselves, since it's sent anyway by the EventService itself
> after the execution of all rules. Seems a bad idea to me ?
>
> Thomas
>
>
> On Mon, Sep 10, 2018 at 4:37 PM Serge Huber  wrote:
>
> > Hello Thomas,
> >
> > Agreed the first one should be fixed.
> >
> > For the second one, I was thinking that maybe we should try to detect
> > the recursion and if so prevent it from happening. What do you think?
> > This would involve some kind of common contact and some kind of
> > tracing of which events are occurring so that we can detect this loop.
> >
> > cheers,
> >   Serge...
> > On Mon, Sep 10, 2018 at 4:13 PM Thomas Draier  wrote:
> > >
> > > Hi,
> > >
> > > I've found 2 issues with segments :
> > > https://issues.apache.org/jira/browse/UNOMI-197 and
> > > https://issues.apache.org/jira/browse/UNOMI-198 . First one can be
> > easily
> > > fixed, I don't know if you see any reason why the enabled value was not
> > > checked ? For the stack overflow issue, not sure what we should do .. the
> > > fact that it's recursive is not good (would be better with a queue of
> > > event) but won't change the infinite flow of events. Any idea  if we
> > should
> > > do something about it ?
> > >
> > > Thomas
> >

[jira] [Commented] (UNOMI-196) Unable to start karaf instance on fresh installation - elasticsearch error : java.lang.IllegalStateException: Received message from unsupported version: [5.2.2] minimal

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610284#comment-16610284
 ] 

Serge Huber commented on UNOMI-196:
---

Can we close this issue ? There has been no response on it ?

 

> Unable to start karaf instance on fresh installation - elasticsearch error : 
> java.lang.IllegalStateException: Received message from unsupported version: 
> [5.2.2] minimal compatible version is: [5.6.0]
> ---
>
> Key: UNOMI-196
> URL: https://issues.apache.org/jira/browse/UNOMI-196
> Project: Apache Unomi
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.2.0-incubating
> Environment: Debian GNU/Linux 7 \n \l
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> HOSTNAME=303fbb102b27
> TERM=xterm
> PATH=/usr/lib/jvm/java-8-oracle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> PWD=/home/unomi/unomi-1.2.0-incubating
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> SHLVL=1
> HOME=/root
> _=/usr/bin/printenv
> OLDPWD=/home/unomi
> {
>   "name" : "hjui3pv",
>   "cluster_name" : "contextElasticSearch",
>   "cluster_uuid" : "kokAP-m7TOac6UkDY0gmEg",
>   "version" : {
> "number" : "6.3.2",
> "build_flavor" : "default",
> "build_type" : "deb",
> "build_hash" : "053779d",
> "build_date" : "2018-07-20T05:20:23.451332Z",
> "build_snapshot" : false,
> "lucene_version" : "7.3.1",
> "minimum_wire_compatibility_version" : "5.6.0",
> "minimum_index_compatibility_version" : "5.0.0"
>   },
>   "tagline" : "You Know, for Search"
> }
>Reporter: Daniel Engelman
>Priority: Major
>
> Services do not go live on a fresh installation. 
>  
> 1. running "bin/karaf" results in karaf loading and then "Initializing 
> Unomi..." which never finished.
> 2. Looking into log:display - it says: "Unable to initialize bean 
> elasticSearchPersistenceServiceImpl"
> 2018-08-23 12:55:58,615 | INFO | FelixStartLevel | RegionsPersistenceImpl | 
> 49 - org.apache.karaf.region.persist - 3.0.8 | Loading region digraph 
> persistence
> 2018-08-23 12:55:58,899 | INFO | FelixStartLevel | SecurityUtils | 30 - 
> org.apache.sshd.core - 0.14.0 | BouncyCastle not registered, using the 
> default JCE provider
> 2018-08-23 12:55:59,110 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Starting JMX OSGi agent
> 2018-08-23 12:55:59,157 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering MBean with ObjectName 
> [osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9]
>  for service with service.id [15]
> 2018-08-23 12:55:59,194 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.ServiceStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=serviceState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.BundleStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=bundleState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,197 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.PackageStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=packageState,versio

[jira] [Updated] (UNOMI-198) Segment evaluation can go into infinite recursion

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber updated UNOMI-198:
--
Affects Version/s: 1.1.0-incubating
   1.2.0-incubating
   1.3.0-incubating
Fix Version/s: 1.4.0-incubating

> Segment evaluation can go into infinite recursion
> -
>
> Key: UNOMI-198
> URL: https://issues.apache.org/jira/browse/UNOMI-198
> Project: Apache Unomi
>  Issue Type: Bug
>Affects Versions: 1.1.0-incubating, 1.2.0-incubating, 1.3.0-incubating
>Reporter: Thomas Draier
>Assignee: Thomas Draier
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> Every time a profile is update, an updatedProfile event is sent and triggers 
> the segment evaluation rule. It's easy to create a segment of all users that 
> are not in this segment, which  will produce an infinite recursion and go 
> into StackOverflowError :
> {code:json}
> {
>   "itemId": "_3a71uuslk",
>   "itemType": "segment",
>   "version": 4,
>   "condition": {
> "parameterValues": {
>   "segments": ["_3a71uuslk"],
>   "matchType": "none"
> },
> "type": "profileSegmentCondition"
>   },
>   "metadata": {
> "id": "_3a71uuslk",
> "name": "test",
> "description": null,
> "scope": "systemscope",
> "tags": [],
> "systemTags": [],
> "enabled": false,
> "missingPlugins": false,
> "hidden": false,
> "readOnly": false
>   }
> }
> {code}
>  
> Probably other kind of rules can also go into StackOverflowError. We should 
> try to avoid going into this kind of recursion



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (UNOMI-187) Integrate analytics.js

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber updated UNOMI-187:
--
Fix Version/s: 1.4.0-incubating

> Integrate analytics.js 
> ---
>
> Key: UNOMI-187
> URL: https://issues.apache.org/jira/browse/UNOMI-187
> Project: Apache Unomi
>  Issue Type: New Feature
>  Components: web
>Affects Versions: 1.3.0-incubating
>Reporter: Romain Gauthier
>Assignee: Damien GAILLARD
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
>  
> To ease Unomi adoption, it would be great to add an integration with 
> analytics.js
> [https://segment.com/docs/sources/website/analytics.js/]
>  
> From what I understood, this integration would allow data collection from any 
> website with a simple tag.
> Code of anaytics.js is here:
> [https://github.com/segmentio/analytics.js]
> Sample code of other integrations available here:
> https://github.com/segment-integrations?q=analytics.js-integration
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (UNOMI-197) Disabling a segment has no impact when getting the list of segments of a user

[Serge Huber (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UNOMI-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber updated UNOMI-197:
--
Affects Version/s: 1.1.0-incubating
   1.2.0-incubating
   1.3.0-incubating
Fix Version/s: 1.4.0-incubating

> Disabling a segment has no impact when getting the list of segments of a user
> -
>
> Key: UNOMI-197
> URL: https://issues.apache.org/jira/browse/UNOMI-197
> Project: Apache Unomi
>  Issue Type: Bug
>Affects Versions: 1.1.0-incubating, 1.2.0-incubating, 1.3.0-incubating
>Reporter: Thomas Draier
>Assignee: Thomas Draier
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The method getSegmentsAndScoresForProfile, which is used by the rule to 
> evaluate the segments of a user, does not check the enabled/disabled status 
> of a segment ( although it does it for the scoring plans)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (UNOMI-197) Disabling a segment has no impact when getting the list of segments of a user

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610281#comment-16610281
 ] 

Serge Huber commented on UNOMI-197:
---

Thanks Thomas for fixing this this quickly !

> Disabling a segment has no impact when getting the list of segments of a user
> -
>
> Key: UNOMI-197
> URL: https://issues.apache.org/jira/browse/UNOMI-197
> Project: Apache Unomi
>  Issue Type: Bug
>Affects Versions: 1.1.0-incubating, 1.2.0-incubating, 1.3.0-incubating
>Reporter: Thomas Draier
>Assignee: Thomas Draier
>Priority: Major
> Fix For: 1.4.0-incubating
>
>
> The method getSegmentsAndScoresForProfile, which is used by the rule to 
> evaluate the segments of a user, does not check the enabled/disabled status 
> of a segment ( although it does it for the scoring plans)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Issues with segments

[Serge Huber]

Hello Thomas,

Agreed the first one should be fixed.

For the second one, I was thinking that maybe we should try to detect
the recursion and if so prevent it from happening. What do you think?
This would involve some kind of common contact and some kind of
tracing of which events are occurring so that we can detect this loop.

cheers,
  Serge...
On Mon, Sep 10, 2018 at 4:13 PM Thomas Draier  wrote:
>
> Hi,
>
> I've found 2 issues with segments :
> https://issues.apache.org/jira/browse/UNOMI-197 and
> https://issues.apache.org/jira/browse/UNOMI-198 . First one can be easily
> fixed, I don't know if you see any reason why the enabled value was not
> checked ? For the stack overflow issue, not sure what we should do .. the
> fact that it's recursive is not good (would be better with a queue of
> event) but won't change the infinite flow of events. Any idea  if we should
> do something about it ?
>
> Thomas

New website & documentation switch from markdown to asciidoc

[Serge Huber]

Hi all,

There are a few changes that I'd like to communicate today :
- The documentation format has shifted from Markdown to asciidoc. The
new format was just merged and the Markdown versions will be removed
asap. asciidoc is a much more powerful markup language that is
standardized (for example it supports tables out of the box). Along
with this format, the possibility to generate PDF documentation has
been added.
- A new git repository has been created to host the source code for
the new Apache Unomi website. This website will no longer be generated
from the Maven project but will be maintained separately. It is hosted
on gitbox.apache.org at the following URL:
https://gitbox.apache.org/repos/asf/incubator-unomi-site.git
The new website is built using the bootstrap framework and will go
live as soon as the next step is completed.
- Both changes were done in alignment with how things are done in the
Apache Karaf project so that we can simplify maintenance for people
working on both projects (such as JB or François Papon).
- The 1.3.0 release has been approved by the IPMC and will be
officially available on the new website once we publish it.
- All this work was done by François Papon that has done tremendous
work. Thanks a lot to him.

Please don't hesitate if you have any questions,
Regards,
  Serge...

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

That's great news ! Is the PR up to date ?

I think we can merge it now. We will need to ask for the git repo for
the website quickly.

Thanks & Regards,
  Serge...



On Thu, Sep 6, 2018 at 8:20 PM Francois Papon
 wrote:
>
> Hi Serge,
>
> I removed the SourceSansPro font and replaced it by the OpenSans in both
> HTML and PDF.
>
> It's looks pretty good :)
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 06/09/2018 à 20:36, francois.papon a écrit :
> > I don't think it's possible to load the font from a CDN for the pdf, we 
> > need to have it locally. I will search for a similar font in an Apache 
> > license.
> > Yes, for Karaf we have a separate git repository.
> > regards
> > François
> >
> >
> > Envoyé depuis mon smartphone Samsung Galaxy.
> >  Message d'origine De : Serge Huber  
> > Date : 06/09/2018  18:27  (GMT+04:00) À : dev@unomi.incubator.apache.org 
> > Objet : Re: [PROPOSAL] - Website and documentation
> > Hello Francois,
> >
> > - I'm not 100% sure it's a problem but I checked the Apache website
> > and they are actually loading the font from the googleapis CDN, so
> > they are not hosting it in the source code. Would there be a way to
> > load the fonts from a remote URL or do they have to be available
> > locally?
> >
> > - Thanks for the cleanup I'll look at the changes asap.
> >
> > - I forgot how Karaf handles the site, is there a separate git repository?
> >
> > cheers,
> >   Serge
> >
> > On Thu, Sep 6, 2018 at 9:38 AM Francois Papon
> >  wrote:
> >> Hi Serge,
> >>
> >> - For the fonts, it's the SourceSansPro that is using the SIL Open Font
> >> License and I'm use it because it's the font that is used by the ASF
> >> website. If it's a problem a can choose another one.
> >>
> >> - I removed directories and keep only the asciidoc, the PR is ok now ;)
> >>
> >> - My Github repository is up to date and I can do a PR for this. I
> >> remember that we discuss about creating a new Github repository for this
> >> (incubator-unomi-site for example), right ?
> >>
> >> regards,
> >>
> >> François Papon
> >> fpa...@apache.org
> >>
> >> Le 06/09/2018 à 10:24, Serge Huber a écrit :
> >>> Hello François,
> >>>
> >>> Thanks for all the work ! I have a coupled of questions after reviewing 
> >>> the PR :
> >>>
> >>> - I noticed you use a font that is using the SIL Open Font License. I
> >>> see that it should be possible (see
> >>> https://www.apache.org/legal/resolved.html#category-b) but I'm not
> >>> sure if that doesn't imply that we need to list this under the NOTICE
> >>> file. I'm wondering if we could replace this font with an Apache
> >>> license one instead?
> >>> - I think there are some HTML and PDF files that shouldn't be in the
> >>> source. I noticed these in the following directories :
> >>> src/site/archives/1.1/html/1.4.0-incubating-SNAPSHOT
> >>> src/site/archives/1.1/pdf
> >>> src/site/archives/1.2/pdf
> >>> src/site/archives/1.2/html
> >>> Could you please remove these from the PR?
> >>> - I was wondering if we should do a second PR for the website? Did you
> >>> update your Github repository?
> >>>
> >>> Thanks again,
> >>> cheers,
> >>>Serge...
> >>> On Wed, Sep 5, 2018 at 10:04 PM Francois Papon
> >>>  wrote:
> >>>> Hi Serge,
> >>>>
> >>>> I clean up the PR and I remove the WIP mention, you can start the review 
> >>>> :)
> >>>>
> >>>> regards,
> >>>>
> >>>> François Papon
> >>>> fpa...@apache.org
> >>>>
> >>>> Le 30/08/2018 à 23:08, Francois Papon a écrit :
> >>>>> Hi Serge,
> >>>>>
> >>>>> I pushed a PR (WIP) for the asciidoc documentation, the html generation
> >>>>> is ok.
> >>>>>
> >>>>> I'm checking now for the pdf generation.
> >>>>>
> >>>>> regards,
> >>>>>
> >>>>> François Papon
> >>>>> fpa...@apache.org
> >>>>>
> >>>>> Le 27/08/2018 à 13:52, Francois Papon a écrit :
> &

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Hello Francois,

- I'm not 100% sure it's a problem but I checked the Apache website
and they are actually loading the font from the googleapis CDN, so
they are not hosting it in the source code. Would there be a way to
load the fonts from a remote URL or do they have to be available
locally?

- Thanks for the cleanup I'll look at the changes asap.

- I forgot how Karaf handles the site, is there a separate git repository?

cheers,
  Serge

On Thu, Sep 6, 2018 at 9:38 AM Francois Papon
 wrote:
>
> Hi Serge,
>
> - For the fonts, it's the SourceSansPro that is using the SIL Open Font
> License and I'm use it because it's the font that is used by the ASF
> website. If it's a problem a can choose another one.
>
> - I removed directories and keep only the asciidoc, the PR is ok now ;)
>
> - My Github repository is up to date and I can do a PR for this. I
> remember that we discuss about creating a new Github repository for this
> (incubator-unomi-site for example), right ?
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 06/09/2018 à 10:24, Serge Huber a écrit :
> > Hello François,
> >
> > Thanks for all the work ! I have a coupled of questions after reviewing the 
> > PR :
> >
> > - I noticed you use a font that is using the SIL Open Font License. I
> > see that it should be possible (see
> > https://www.apache.org/legal/resolved.html#category-b) but I'm not
> > sure if that doesn't imply that we need to list this under the NOTICE
> > file. I'm wondering if we could replace this font with an Apache
> > license one instead?
> > - I think there are some HTML and PDF files that shouldn't be in the
> > source. I noticed these in the following directories :
> > src/site/archives/1.1/html/1.4.0-incubating-SNAPSHOT
> > src/site/archives/1.1/pdf
> > src/site/archives/1.2/pdf
> > src/site/archives/1.2/html
> > Could you please remove these from the PR?
> > - I was wondering if we should do a second PR for the website? Did you
> > update your Github repository?
> >
> > Thanks again,
> > cheers,
> >   Serge...
> > On Wed, Sep 5, 2018 at 10:04 PM Francois Papon
> >  wrote:
> >> Hi Serge,
> >>
> >> I clean up the PR and I remove the WIP mention, you can start the review :)
> >>
> >> regards,
> >>
> >> François Papon
> >> fpa...@apache.org
> >>
> >> Le 30/08/2018 à 23:08, Francois Papon a écrit :
> >>> Hi Serge,
> >>>
> >>> I pushed a PR (WIP) for the asciidoc documentation, the html generation
> >>> is ok.
> >>>
> >>> I'm checking now for the pdf generation.
> >>>
> >>> regards,
> >>>
> >>> François Papon
> >>> fpa...@apache.org
> >>>
> >>> Le 27/08/2018 à 13:52, Francois Papon a écrit :
> >>>> Hi Serge,
> >>>>
> >>>> Thanks ;)
> >>>>
> >>>> I fixed the Beam reference and for the documentation part, I will work
> >>>> on it this week and make a proposal.
> >>>>
> >>>> I'm agree, it would be great to put the new site online soon :)
> >>>>
> >>>> regards,
> >>>>
> >>>> François Papon
> >>>> fpa...@apache.org
> >>>>
> >>>> Le 27/08/2018 à 12:55, Serge Huber a écrit :
> >>>>> Hello François,
> >>>>>
> >>>>> Very nice work, I like all the new contribution content!
> >>>>>
> >>>>> The release guide will probably have to be merged with my current
> >>>>> notes that I am maintaining here, but we could do that at a later
> >>>>> stage:
> >>>>> https://docs.google.com/document/d/1H6d8AkavL0K8rlAEd7jHqDRAaq6MeaES54RXTHt805o/edit?usp=sharing
> >>>>>
> >>>>> I found a remaining Beam reference here:
> >>>>> Tardis:incubator-unomi-website loom$ grep -R -i beam *
> >>>>> src/main/webapp/contribute-pre-commit-test-policies.html:
> >>>>> A PR must pass pre-commit tests before being committed to the main
> >>>>> Beam repo.
> >>>>>
> >>>>> But amazing work and thanks for that. I am thinking we could put this
> >>>>> online soon, we just need to figure out how to handle the
> >>>>> documentation part ?
> >>>>>
> >>>>> cheers,
> >>>&g

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Hello François,

Thanks for all the work ! I have a coupled of questions after reviewing the PR :

- I noticed you use a font that is using the SIL Open Font License. I
see that it should be possible (see
https://www.apache.org/legal/resolved.html#category-b) but I'm not
sure if that doesn't imply that we need to list this under the NOTICE
file. I'm wondering if we could replace this font with an Apache
license one instead?
- I think there are some HTML and PDF files that shouldn't be in the
source. I noticed these in the following directories :
src/site/archives/1.1/html/1.4.0-incubating-SNAPSHOT
src/site/archives/1.1/pdf
src/site/archives/1.2/pdf
src/site/archives/1.2/html
Could you please remove these from the PR?
- I was wondering if we should do a second PR for the website? Did you
update your Github repository?

Thanks again,
cheers,
  Serge...
On Wed, Sep 5, 2018 at 10:04 PM Francois Papon
 wrote:
>
> Hi Serge,
>
> I clean up the PR and I remove the WIP mention, you can start the review :)
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 30/08/2018 à 23:08, Francois Papon a écrit :
> > Hi Serge,
> >
> > I pushed a PR (WIP) for the asciidoc documentation, the html generation
> > is ok.
> >
> > I'm checking now for the pdf generation.
> >
> > regards,
> >
> > François Papon
> > fpa...@apache.org
> >
> > Le 27/08/2018 à 13:52, Francois Papon a écrit :
> >> Hi Serge,
> >>
> >> Thanks ;)
> >>
> >> I fixed the Beam reference and for the documentation part, I will work
> >> on it this week and make a proposal.
> >>
> >> I'm agree, it would be great to put the new site online soon :)
> >>
> >> regards,
> >>
> >> François Papon
> >> fpa...@apache.org
> >>
> >> Le 27/08/2018 à 12:55, Serge Huber a écrit :
> >>> Hello François,
> >>>
> >>> Very nice work, I like all the new contribution content!
> >>>
> >>> The release guide will probably have to be merged with my current
> >>> notes that I am maintaining here, but we could do that at a later
> >>> stage:
> >>> https://docs.google.com/document/d/1H6d8AkavL0K8rlAEd7jHqDRAaq6MeaES54RXTHt805o/edit?usp=sharing
> >>>
> >>> I found a remaining Beam reference here:
> >>> Tardis:incubator-unomi-website loom$ grep -R -i beam *
> >>> src/main/webapp/contribute-pre-commit-test-policies.html:
> >>> A PR must pass pre-commit tests before being committed to the main
> >>> Beam repo.
> >>>
> >>> But amazing work and thanks for that. I am thinking we could put this
> >>> online soon, we just need to figure out how to handle the
> >>> documentation part ?
> >>>
> >>> cheers,
> >>>   Serge...
> >>> On Sat, Aug 25, 2018 at 6:32 PM Francois Papon
> >>>  wrote:
> >>>> Hi,
> >>>>
> >>>> I made some changes on the website :
> >>>>
> >>>>   * add content in the "contribute" page
> >>>>   * add content in the "community" page
> >>>>   * clean up the footer menu
> >>>>
> >>>> Some page may be complete/fix like the "release guide", I'm not sure of
> >>>> all the step for this section...
> >>>>
> >>>> regards,
> >>>>
> >>>> François Papon
> >>>> fpa...@apache.org
> >>>>
> >>>> Le 24/08/2018 à 15:06, Serge Huber a écrit :
> >>>>> Yes that's what I meant a new website subproject :)
> >>>>>
> >>>>> cheers,
> >>>>>   Serge...
> >>>>>
> >>>>> On Fri, Aug 24, 2018 at 12:22 PM Francois Papon
> >>>>>  wrote:
> >>>>>> Great for the graduation, I will copy :)
> >>>>>>
> >>>>>> For the PR I think it's better to add a new wsebsite sub-projetct.
> >>>>>>
> >>>>>> regards,
> >>>>>>
> >>>>>> François Papon
> >>>>>> fpa...@apache.org
> >>>>>>
> >>>>>> Le 24/08/2018 à 14:16, Serge Huber a écrit :
> >>>>>>> Just to be clear Apache Beam recently had to go through all the
> >>>>>>> graduation requirements so that's why I'm suggesting their site as a
> >>>>>

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Hello François,

Very nice work, I like all the new contribution content!

The release guide will probably have to be merged with my current
notes that I am maintaining here, but we could do that at a later
stage:
https://docs.google.com/document/d/1H6d8AkavL0K8rlAEd7jHqDRAaq6MeaES54RXTHt805o/edit?usp=sharing

I found a remaining Beam reference here:
Tardis:incubator-unomi-website loom$ grep -R -i beam *
src/main/webapp/contribute-pre-commit-test-policies.html:
A PR must pass pre-commit tests before being committed to the main
Beam repo.

But amazing work and thanks for that. I am thinking we could put this
online soon, we just need to figure out how to handle the
documentation part ?

cheers,
  Serge...
On Sat, Aug 25, 2018 at 6:32 PM Francois Papon
 wrote:
>
> Hi,
>
> I made some changes on the website :
>
>   * add content in the "contribute" page
>   * add content in the "community" page
>   * clean up the footer menu
>
> Some page may be complete/fix like the "release guide", I'm not sure of
> all the step for this section...
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 24/08/2018 à 15:06, Serge Huber a écrit :
> > Yes that's what I meant a new website subproject :)
> >
> > cheers,
> >   Serge...
> >
> > On Fri, Aug 24, 2018 at 12:22 PM Francois Papon
> >  wrote:
> >> Great for the graduation, I will copy :)
> >>
> >> For the PR I think it's better to add a new wsebsite sub-projetct.
> >>
> >> regards,
> >>
> >> François Papon
> >> fpa...@apache.org
> >>
> >> Le 24/08/2018 à 14:16, Serge Huber a écrit :
> >>> Just to be clear Apache Beam recently had to go through all the
> >>> graduation requirements so that's why I'm suggesting their site as a
> >>> template. As it is all Apache licensed content we can copy it without
> >>> any problem :)
> >>>
> >>> For the PR that seems fine, should we add a new website sub-project?
> >>>
> >>> cheers,
> >>>   Serge...
> >>> On Fri, Aug 24, 2018 at 10:58 AM francois.papon
> >>>  wrote:
> >>>> Hi Serge,
> >>>> Ok for the graduation requirements, I will add the content.
> >>>> For the source repository, I think it would be great to put it on Git. I 
> >>>> will easily push a PR ;)
> >>>> Regards,
> >>>>
> >>>>
> >>>> Envoyé depuis mon smartphone Samsung Galaxy.
> >>>>  Message d'origine De : Serge Huber  
> >>>> Date : 24/08/2018  11:50  (GMT+04:00) À : dev@unomi.incubator.apache.org 
> >>>> Objet : Re: [PROPOSAL] - Website and documentation
> >>>> Hello François,
> >>>>
> >>>> Thanks for all the changes, I really like them.
> >>>>
> >>>> For the graduation requirements, we have a maturity report here:
> >>>> http://unomi.apache.org/maturity-model-report.html
> >>>>
> >>>> You will see that most of the content needed is for example available
> >>>> on the Apache Beam website in the URLs I sent in my previous message
> >>>> in this thread (for example how to handle security issues).
> >>>>
> >>>> Also I had a question about where we would put the new website ? Would
> >>>> we directly host it in the Subversion or would we put it somewhere in
> >>>> the Git repository ?
> >>>>
> >>>> Regards,
> >>>>   Serge...
> >>>>
> >>>> ps: the 1.3.0 release was just approved, I need to put it on the
> >>>> website today :)
> >>>>
> >>>> On Fri, Aug 24, 2018 at 4:15 AM Francois Papon
> >>>>  wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I made some change on the website after have a look to the Apache Beam
> >>>>> website :
> >>>>>
> >>>>> - update the home page header
> >>>>>
> >>>>> - remove news page, may be not necessary because we already have a
> >>>>> section news on the home page
> >>>>>
> >>>>> - add a "get started" page for the newcomers, I will write some section
> >>>>> for how to a new user can install and start using Apache Unomi. We could
> >>>>> add some examples for how to use after install.
> >>>>>
> >&g

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Yes that's what I meant a new website subproject :)

cheers,
  Serge...

On Fri, Aug 24, 2018 at 12:22 PM Francois Papon
 wrote:
>
> Great for the graduation, I will copy :)
>
> For the PR I think it's better to add a new wsebsite sub-projetct.
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 24/08/2018 à 14:16, Serge Huber a écrit :
> > Just to be clear Apache Beam recently had to go through all the
> > graduation requirements so that's why I'm suggesting their site as a
> > template. As it is all Apache licensed content we can copy it without
> > any problem :)
> >
> > For the PR that seems fine, should we add a new website sub-project?
> >
> > cheers,
> >   Serge...
> > On Fri, Aug 24, 2018 at 10:58 AM francois.papon
> >  wrote:
> >> Hi Serge,
> >> Ok for the graduation requirements, I will add the content.
> >> For the source repository, I think it would be great to put it on Git. I 
> >> will easily push a PR ;)
> >> Regards,
> >>
> >>
> >> Envoyé depuis mon smartphone Samsung Galaxy.
> >>  Message d'origine De : Serge Huber  
> >> Date : 24/08/2018  11:50  (GMT+04:00) À : dev@unomi.incubator.apache.org 
> >> Objet : Re: [PROPOSAL] - Website and documentation
> >> Hello François,
> >>
> >> Thanks for all the changes, I really like them.
> >>
> >> For the graduation requirements, we have a maturity report here:
> >> http://unomi.apache.org/maturity-model-report.html
> >>
> >> You will see that most of the content needed is for example available
> >> on the Apache Beam website in the URLs I sent in my previous message
> >> in this thread (for example how to handle security issues).
> >>
> >> Also I had a question about where we would put the new website ? Would
> >> we directly host it in the Subversion or would we put it somewhere in
> >> the Git repository ?
> >>
> >> Regards,
> >>   Serge...
> >>
> >> ps: the 1.3.0 release was just approved, I need to put it on the
> >> website today :)
> >>
> >> On Fri, Aug 24, 2018 at 4:15 AM Francois Papon
> >>  wrote:
> >>> Hi,
> >>>
> >>> I made some change on the website after have a look to the Apache Beam
> >>> website :
> >>>
> >>> - update the home page header
> >>>
> >>> - remove news page, may be not necessary because we already have a
> >>> section news on the home page
> >>>
> >>> - add a "get started" page for the newcomers, I will write some section
> >>> for how to a new user can install and start using Apache Unomi. We could
> >>> add some examples for how to use after install.
> >>>
> >>> - add a "contribute" page (need to be complete)
> >>>
> >>> - update the "community" page
> >>>
> >>> Their is a lot of content in the Apache Beam website and have to see
> >>> what we have to keep to be compliant for the graduation : where can I
> >>> find the informations about the graduation requirements ?
> >>>
> >>> regards,
> >>>
> >>> François Papon
> >>> fpa...@apache.org
> >>>
> >>> Le 23/08/2018 à 18:48, francois.papon a écrit :
> >>>> Ok, I will take a look on the Beam website and see how to use it as 
> >>>> inspiration :)
> >>>> regards,
> >>>> François
> >>>>
> >>>>
> >>>> Envoyé depuis mon smartphone Samsung Galaxy.
> >>>>  Message d'origine De : Serge Huber  
> >>>> Date : 23/08/2018  18:26  (GMT+04:00) À : dev@unomi.incubator.apache.org 
> >>>> Objet : Re: [PROPOSAL] - Website and documentation
> >>>> Looks much better thanks! And I tested in a mobile format it works
> >>>> except for the bottom footer that looks a bit garbled (see attached
> >>>> image). Btw I'm using Safari's Responsive Design mode to test this (in
> >>>> the develop menu).
> >>>>
> >>>> For the main documentation is the idea (still) to copy this over at a
> >>>> later stage?
> >>>>
> >>>> Thanks again for all the work.
> >>>>
> >>>> We will also need to add more contribution pages to be compliant with
> >>>> the requ

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Just to be clear Apache Beam recently had to go through all the
graduation requirements so that's why I'm suggesting their site as a
template. As it is all Apache licensed content we can copy it without
any problem :)

For the PR that seems fine, should we add a new website sub-project?

cheers,
  Serge...
On Fri, Aug 24, 2018 at 10:58 AM francois.papon
 wrote:
>
> Hi Serge,
> Ok for the graduation requirements, I will add the content.
> For the source repository, I think it would be great to put it on Git. I will 
> easily push a PR ;)
> Regards,
>
>
> Envoyé depuis mon smartphone Samsung Galaxy.
> ---- Message d'origine De : Serge Huber  Date 
> : 24/08/2018  11:50  (GMT+04:00) À : dev@unomi.incubator.apache.org Objet : 
> Re: [PROPOSAL] - Website and documentation
> Hello François,
>
> Thanks for all the changes, I really like them.
>
> For the graduation requirements, we have a maturity report here:
> http://unomi.apache.org/maturity-model-report.html
>
> You will see that most of the content needed is for example available
> on the Apache Beam website in the URLs I sent in my previous message
> in this thread (for example how to handle security issues).
>
> Also I had a question about where we would put the new website ? Would
> we directly host it in the Subversion or would we put it somewhere in
> the Git repository ?
>
> Regards,
>   Serge...
>
> ps: the 1.3.0 release was just approved, I need to put it on the
> website today :)
>
> On Fri, Aug 24, 2018 at 4:15 AM Francois Papon
>  wrote:
> >
> > Hi,
> >
> > I made some change on the website after have a look to the Apache Beam
> > website :
> >
> > - update the home page header
> >
> > - remove news page, may be not necessary because we already have a
> > section news on the home page
> >
> > - add a "get started" page for the newcomers, I will write some section
> > for how to a new user can install and start using Apache Unomi. We could
> > add some examples for how to use after install.
> >
> > - add a "contribute" page (need to be complete)
> >
> > - update the "community" page
> >
> > Their is a lot of content in the Apache Beam website and have to see
> > what we have to keep to be compliant for the graduation : where can I
> > find the informations about the graduation requirements ?
> >
> > regards,
> >
> > François Papon
> > fpa...@apache.org
> >
> > Le 23/08/2018 à 18:48, francois.papon a écrit :
> > > Ok, I will take a look on the Beam website and see how to use it as 
> > > inspiration :)
> > > regards,
> > > François
> > >
> > >
> > > Envoyé depuis mon smartphone Samsung Galaxy.
> > >  Message d'origine De : Serge Huber  
> > > Date : 23/08/2018  18:26  (GMT+04:00) À : dev@unomi.incubator.apache.org 
> > > Objet : Re: [PROPOSAL] - Website and documentation
> > > Looks much better thanks! And I tested in a mobile format it works
> > > except for the bottom footer that looks a bit garbled (see attached
> > > image). Btw I'm using Safari's Responsive Design mode to test this (in
> > > the develop menu).
> > >
> > > For the main documentation is the idea (still) to copy this over at a
> > > later stage?
> > >
> > > Thanks again for all the work.
> > >
> > > We will also need to add more contribution pages to be compliant with
> > > the requirements for graduation, for example, we should copy the
> > > contents of the beam site for these pages:
> > > https://beam.apache.org/contribute/ and
> > > https://beam.apache.org/community/contact-us/
> > >
> > > Btw, in general, I really like the Apache Beam site. Maybe we could
> > > use it as inspiration?
> > >
> > > Serge Huber
> > > CTO & Co-Founder
> > >
> > > T +41 22 361 3424
> > > 9 route des Jeunes | 1227 Acacias | Switzerland
> > > jahia.com
> > > SKYPE | LINKEDIN | TWITTER | VCARD
> > >
> > >
> > >> JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia is 
> > >> a leading User Experience Platform (UXP) for Digital Transformation.
> > > On Thu, Aug 23, 2018 at 2:55 PM Francois Papon
> > >  wrote:
> > >> Hi,
> > >>
> > >> I pushed an update for the mobile responsive menu and I reduced the
> > >> font-size and space.
> > >>
> > >> regards,
> > >>
>

[jira] [Commented] (UNOMI-196) Unable to start karaf instance on fresh installation - elasticsearch error : java.lang.IllegalStateException: Received message from unsupported version: [5.2.2] minimal

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591284#comment-16591284
 ] 

Serge Huber commented on UNOMI-196:
---

Hello,

I'm not sure what the status of the install is here but I would recommend you 
erase and restart the Apache Unomi install and make sure all data is erased in 
the ElasticSearch 5.1.2 instance. If you are using the same install you were 
using with ES 5.6 maybe something got messed up in the startup process.

Regards,

  Serge... 

> Unable to start karaf instance on fresh installation - elasticsearch error : 
> java.lang.IllegalStateException: Received message from unsupported version: 
> [5.2.2] minimal compatible version is: [5.6.0]
> ---
>
> Key: UNOMI-196
> URL: https://issues.apache.org/jira/browse/UNOMI-196
> Project: Apache Unomi
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.2.0-incubating
> Environment: Debian GNU/Linux 7 \n \l
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> HOSTNAME=303fbb102b27
> TERM=xterm
> PATH=/usr/lib/jvm/java-8-oracle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> PWD=/home/unomi/unomi-1.2.0-incubating
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> SHLVL=1
> HOME=/root
> _=/usr/bin/printenv
> OLDPWD=/home/unomi
> {
>   "name" : "hjui3pv",
>   "cluster_name" : "contextElasticSearch",
>   "cluster_uuid" : "kokAP-m7TOac6UkDY0gmEg",
>   "version" : {
> "number" : "6.3.2",
> "build_flavor" : "default",
> "build_type" : "deb",
> "build_hash" : "053779d",
> "build_date" : "2018-07-20T05:20:23.451332Z",
> "build_snapshot" : false,
> "lucene_version" : "7.3.1",
> "minimum_wire_compatibility_version" : "5.6.0",
> "minimum_index_compatibility_version" : "5.0.0"
>   },
>   "tagline" : "You Know, for Search"
> }
>Reporter: Daniel Engelman
>Priority: Major
>
> Services do not go live on a fresh installation. 
>  
> 1. running "bin/karaf" results in karaf loading and then "Initializing 
> Unomi..." which never finished.
> 2. Looking into log:display - it says: "Unable to initialize bean 
> elasticSearchPersistenceServiceImpl"
> 2018-08-23 12:55:58,615 | INFO | FelixStartLevel | RegionsPersistenceImpl | 
> 49 - org.apache.karaf.region.persist - 3.0.8 | Loading region digraph 
> persistence
> 2018-08-23 12:55:58,899 | INFO | FelixStartLevel | SecurityUtils | 30 - 
> org.apache.sshd.core - 0.14.0 | BouncyCastle not registered, using the 
> default JCE provider
> 2018-08-23 12:55:59,110 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Starting JMX OSGi agent
> 2018-08-23 12:55:59,157 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering MBean with ObjectName 
> [osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9]
>  for service with service.id [15]
> 2018-08-23 12:55:59,194 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.ServiceStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=serviceState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.BundleStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=bundleState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Hello François,

Thanks for all the changes, I really like them.

For the graduation requirements, we have a maturity report here:
http://unomi.apache.org/maturity-model-report.html

You will see that most of the content needed is for example available
on the Apache Beam website in the URLs I sent in my previous message
in this thread (for example how to handle security issues).

Also I had a question about where we would put the new website ? Would
we directly host it in the Subversion or would we put it somewhere in
the Git repository ?

Regards,
  Serge...

ps: the 1.3.0 release was just approved, I need to put it on the
website today :)

On Fri, Aug 24, 2018 at 4:15 AM Francois Papon
 wrote:
>
> Hi,
>
> I made some change on the website after have a look to the Apache Beam
> website :
>
> - update the home page header
>
> - remove news page, may be not necessary because we already have a
> section news on the home page
>
> - add a "get started" page for the newcomers, I will write some section
> for how to a new user can install and start using Apache Unomi. We could
> add some examples for how to use after install.
>
> - add a "contribute" page (need to be complete)
>
> - update the "community" page
>
> Their is a lot of content in the Apache Beam website and have to see
> what we have to keep to be compliant for the graduation : where can I
> find the informations about the graduation requirements ?
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 23/08/2018 à 18:48, francois.papon a écrit :
> > Ok, I will take a look on the Beam website and see how to use it as 
> > inspiration :)
> > regards,
> > François
> >
> >
> > Envoyé depuis mon smartphone Samsung Galaxy.
> >  Message d'origine De : Serge Huber  Date 
> > : 23/08/2018  18:26  (GMT+04:00) À : dev@unomi.incubator.apache.org Objet : 
> > Re: [PROPOSAL] - Website and documentation
> > Looks much better thanks! And I tested in a mobile format it works
> > except for the bottom footer that looks a bit garbled (see attached
> > image). Btw I'm using Safari's Responsive Design mode to test this (in
> > the develop menu).
> >
> > For the main documentation is the idea (still) to copy this over at a
> > later stage?
> >
> > Thanks again for all the work.
> >
> > We will also need to add more contribution pages to be compliant with
> > the requirements for graduation, for example, we should copy the
> > contents of the beam site for these pages:
> > https://beam.apache.org/contribute/ and
> > https://beam.apache.org/community/contact-us/
> >
> > Btw, in general, I really like the Apache Beam site. Maybe we could
> > use it as inspiration?
> >
> > Serge Huber
> > CTO & Co-Founder
> >
> > T +41 22 361 3424
> > 9 route des Jeunes | 1227 Acacias | Switzerland
> > jahia.com
> > SKYPE | LINKEDIN | TWITTER | VCARD
> >
> >
> >> JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia is a 
> >> leading User Experience Platform (UXP) for Digital Transformation.
> > On Thu, Aug 23, 2018 at 2:55 PM Francois Papon
> >  wrote:
> >> Hi,
> >>
> >> I pushed an update for the mobile responsive menu and I reduced the
> >> font-size and space.
> >>
> >> regards,
> >>
> >> François Papon
> >> fpa...@apache.org
> >>
> >> Le 23/08/2018 à 08:50, Francois Papon a écrit :
> >>> Hi Serge,
> >>>
> >>> Thanks for your feedback !
> >>>
> >>> For the maven pom, we use it in Karaf to deploy via scm, I can remove it
> >>> if no needs.
> >>>
> >>> For the getting start part, I put the 5 minutes quick start on the main
> >>> page, if you are talking about part in the main documentation, it's
> >>> normal but I can add it.
> >>>
> >>> I will down the font size and reduce some space as you say.
> >>>
> >>> The CSS is Bootstrap 4, I will check for the menu on mobile (it work
> >>> well on Karaf website and I just forked the site).
> >>>
> >>> I tried to update quickly ;)
> >>>
> >>> It's a good idea the have animation or video, and we also have some
> >>> highlight on the caroussel at the top of the main page. The "use cases"
> >>> page can also have some additional content to explain how users can
> >>> integrate Unomi in their legacy system easily.
> >>>
> >>&g

[RESULT][VOTE] Release Apache Unomi 1.3.0 (incubating) [TAKE2]

[Serge Huber]

Hi all,

The vote to release Unomi 1.3.0-incubating, having been open for 27
days is now closed.

There were three binding +1s and no -1 votes.

Here's the vote summary :

3 binding votes +1 :
- Justin Mclean
- Bertrand Delacretaz
- Jean-Baptiste Onofré

No 0 or -1.

The release is approved.

Vote thread can be found here :
https://lists.apache.org/thread.html/03223c09f5f0f4dcb384dbcceb87486a83f6ed030ebca2dbc685e86a@%3Cgeneral.incubator.apache.org%3E

Thank you for your votes and reviews!

Regards,

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Looks much better thanks! And I tested in a mobile format it works
except for the bottom footer that looks a bit garbled (see attached
image). Btw I'm using Safari's Responsive Design mode to test this (in
the develop menu).

For the main documentation is the idea (still) to copy this over at a
later stage?

Thanks again for all the work.

We will also need to add more contribution pages to be compliant with
the requirements for graduation, for example, we should copy the
contents of the beam site for these pages:
https://beam.apache.org/contribute/ and
https://beam.apache.org/community/contact-us/

Btw, in general, I really like the Apache Beam site. Maybe we could
use it as inspiration?

Serge Huber
CTO & Co-Founder

T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
jahia.com
SKYPE | LINKEDIN | TWITTER | VCARD


> JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia is a 
> leading User Experience Platform (UXP) for Digital Transformation.
On Thu, Aug 23, 2018 at 2:55 PM Francois Papon
 wrote:
>
> Hi,
>
> I pushed an update for the mobile responsive menu and I reduced the
> font-size and space.
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 23/08/2018 à 08:50, Francois Papon a écrit :
> > Hi Serge,
> >
> > Thanks for your feedback !
> >
> > For the maven pom, we use it in Karaf to deploy via scm, I can remove it
> > if no needs.
> >
> > For the getting start part, I put the 5 minutes quick start on the main
> > page, if you are talking about part in the main documentation, it's
> > normal but I can add it.
> >
> > I will down the font size and reduce some space as you say.
> >
> > The CSS is Bootstrap 4, I will check for the menu on mobile (it work
> > well on Karaf website and I just forked the site).
> >
> > I tried to update quickly ;)
> >
> > It's a good idea the have animation or video, and we also have some
> > highlight on the caroussel at the top of the main page. The "use cases"
> > page can also have some additional content to explain how users can
> > integrate Unomi in their legacy system easily.
> >
> > regards,
> >
> > François Papon
> > fpa...@apache.org
> >
> > Le 22/08/2018 à 23:19, Serge Huber a écrit :
> >> Hi François,
> >>
> >> Thanks for your work. I tried to compile the project but I got the
> >> following error :
> >>
> >> [INFO] Scanning for projects...
> >> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> >> [FATAL] 'version' is missing. @ line 23, column 106
> >>  @
> >> [ERROR] The build could not read 1 project -> [Help 1]
> >> [ERROR]
> >> [ERROR]   The project org.apache.unomi:site:[unknown-version]
> >> (/Users/loom/temp/incubator-unomi-website/pom.xml) has 1 error
> >> [ERROR] 'version' is missing. @ line 23, column 106
> >> [ERROR]
> >> [ERROR] To see the full stack trace of the errors, re-run Maven with
> >> the -e switch.
> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >> [ERROR]
> >> [ERROR] For more information about the errors and possible solutions,
> >> please read the following articles:
> >> [ERROR] [Help 1]
> >> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> >>
> >> After adding a version however it worked fine !
> >>
> >> I like the overall result although it seems like it is using a lot of
> >> space and some fonts seem really large. Also it seems some stuff is
> >> missing like the getting started (I couldn't find it).
> >>
> >> I like the new documentation part, some nice ideas there.
> >>
> >> My biggest concern is on-boarding newcomers with the site, and I think
> >> they shouldn't have to read through a lot of content to understand
> >> what the project does. Ideally maybe we should look into producing
> >> some kind of video or a quick animation.
> >>
> >> Finally I tried the site on a mobile device and it seems the
> >> navigation completely disappears.
> >>
> >> Anyway thanks for the effort I like it !
> >>
> >> cheers,
> >>   Serge...
> >> On Wed, Aug 22, 2018 at 12:12 PM Francois Papon
> >>  wrote:
> >>> Hi,
> >>>
> >>> I worked on a preview version of the website and published it on my
> >>> github repo :
> >>>
> >>> https://github.com/fpapon/incubator-unomi-

[jira] [Commented] (UNOMI-196) Unable to start karaf instance on fresh installation - elasticsearch error : java.lang.IllegalStateException: Received message from unsupported version: [5.2.2] minimal

[Serge Huber (JIRA)]

[ 
https://issues.apache.org/jira/browse/UNOMI-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590211#comment-16590211
 ] 

Serge Huber commented on UNOMI-196:
---

Hello,

Thanks for trying out Apache Unomi. 

Which version of ElasticSearch are you using ? For Unomi 1.2 you need to use 
ElasticSearch 5.1.2 which you can get here : 
[https://www.elastic.co/downloads/past-releases/elasticsearch-5-1-2]

Regards,

  Serge... 

> Unable to start karaf instance on fresh installation - elasticsearch error : 
> java.lang.IllegalStateException: Received message from unsupported version: 
> [5.2.2] minimal compatible version is: [5.6.0]
> ---
>
> Key: UNOMI-196
> URL: https://issues.apache.org/jira/browse/UNOMI-196
> Project: Apache Unomi
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.2.0-incubating
> Environment: Debian GNU/Linux 7 \n \l
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> HOSTNAME=303fbb102b27
> TERM=xterm
> PATH=/usr/lib/jvm/java-8-oracle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> PWD=/home/unomi/unomi-1.2.0-incubating
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> SHLVL=1
> HOME=/root
> _=/usr/bin/printenv
> OLDPWD=/home/unomi
> {
>   "name" : "hjui3pv",
>   "cluster_name" : "contextElasticSearch",
>   "cluster_uuid" : "kokAP-m7TOac6UkDY0gmEg",
>   "version" : {
> "number" : "6.3.2",
> "build_flavor" : "default",
> "build_type" : "deb",
> "build_hash" : "053779d",
> "build_date" : "2018-07-20T05:20:23.451332Z",
> "build_snapshot" : false,
> "lucene_version" : "7.3.1",
> "minimum_wire_compatibility_version" : "5.6.0",
> "minimum_index_compatibility_version" : "5.0.0"
>   },
>   "tagline" : "You Know, for Search"
> }
>Reporter: Daniel Engelman
>Priority: Major
>
> Services do not go live on a fresh installation. 
>  
> 1. running "bin/karaf" results in karaf loading and then "Initializing 
> Unomi..." which never finished.
> 2. Looking into log:display - it says: "Unable to initialize bean 
> elasticSearchPersistenceServiceImpl"
> 2018-08-23 12:55:58,615 | INFO | FelixStartLevel | RegionsPersistenceImpl | 
> 49 - org.apache.karaf.region.persist - 3.0.8 | Loading region digraph 
> persistence
> 2018-08-23 12:55:58,899 | INFO | FelixStartLevel | SecurityUtils | 30 - 
> org.apache.sshd.core - 0.14.0 | BouncyCastle not registered, using the 
> default JCE provider
> 2018-08-23 12:55:59,110 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Starting JMX OSGi agent
> 2018-08-23 12:55:59,157 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering MBean with ObjectName 
> [osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9]
>  for service with service.id [15]
> 2018-08-23 12:55:59,194 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.ServiceStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=serviceState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,196 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1.1.6 | Registering 
> org.osgi.jmx.framework.BundleStateMBean to MBeanServer 
> com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name 
> osgi.core:type=bundleState,version=1.7,framework=org.apache.felix.framework,uuid=987fafb7-71a9-42eb-afcb-8ad75973c0c9
> 2018-08-23 12:55:59,197 | INFO | FelixStartLevel | core | 60 - 
> org.apache.aries.jmx.core - 1

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Oh and another thing, I would prefer we use Asciidoc than Markdown, if
possible. Markdown has way to many variants and ways of doing things.
Plus Asciidoc is already used for Karaf documentation.

cheers,
  Serge...
On Wed, Aug 22, 2018 at 9:20 PM Serge Huber  wrote:
>
> Forgot to answer for the Maven stuff. Not sure what to do about this.
> Maybe we don't even need it ? What does Karaf do here ?
>
> cheers,
>   Serge...
> On Wed, Aug 22, 2018 at 9:19 PM Serge Huber  wrote:
> >
> > Hi François,
> >
> > Thanks for your work. I tried to compile the project but I got the
> > following error :
> >
> > [INFO] Scanning for projects...
> > [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> > [FATAL] 'version' is missing. @ line 23, column 106
> >  @
> > [ERROR] The build could not read 1 project -> [Help 1]
> > [ERROR]
> > [ERROR]   The project org.apache.unomi:site:[unknown-version]
> > (/Users/loom/temp/incubator-unomi-website/pom.xml) has 1 error
> > [ERROR] 'version' is missing. @ line 23, column 106
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with
> > the -e switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> >
> > After adding a version however it worked fine !
> >
> > I like the overall result although it seems like it is using a lot of
> > space and some fonts seem really large. Also it seems some stuff is
> > missing like the getting started (I couldn't find it).
> >
> > I like the new documentation part, some nice ideas there.
> >
> > My biggest concern is on-boarding newcomers with the site, and I think
> > they shouldn't have to read through a lot of content to understand
> > what the project does. Ideally maybe we should look into producing
> > some kind of video or a quick animation.
> >
> > Finally I tried the site on a mobile device and it seems the
> > navigation completely disappears.
> >
> > Anyway thanks for the effort I like it !
> >
> > cheers,
> >   Serge...
> > On Wed, Aug 22, 2018 at 12:12 PM Francois Papon
> >  wrote:
> > >
> > > Hi,
> > >
> > > I worked on a preview version of the website and published it on my
> > > github repo :
> > >
> > > https://github.com/fpapon/incubator-unomi-website
> > >
> > > I also started to work on a easy way to publish the documentation from
> > > markdown to HTML and PDF.
> > >
> > > May be it could be nice to archive the documentation related to the
> > > maven project with git tag because today it's on differents folder in
> > > the src/ of the project.
> > >
> > > Thoughts ?
> > >
> > > regards,
> > >
> > > François Papon
> > > fpa...@apache.org
> > >
> > > Le 03/08/2018 à 00:14, Serge Huber a écrit :
> > > > Thanks François, looking forward to the PR !
> > > >
> > > > If you want to work on the website you're more than welcome to start
> > > > working on it, as I said the more people get involved the better for
> > > > the project !
> > > >
> > > > Regards,
> > > >Serge..
> > > > On Wed, Aug 1, 2018 at 8:48 PM Francois Papon
> > > >  wrote:
> > > >> Ok for Swagger, I will post a PR.
> > > >>
> > > >> About the website, let me know when you want me to start working on it
> > > >> (I already have a repo on my github account).
> > > >>
> > > >> regards,
> > > >>
> > > >> François Papon
> > > >> fpa...@apache.org
> > > >>
> > > >> Le 01/08/2018 à 18:25, Serge Huber a écrit :
> > > >>> Feel free to help out on Swagger, I have little to no experience with 
> > > >>> it.
> > > >>>
> > > >>> As for the GraphQL side, it's very experimental code that is
> > > >>> constantly changing right now, so be warned that things might change
> > > >>> quite significantly at any point but feel free to look at it and give
> > > >>> feedback or even contribute!
> > > >>>
> 

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Forgot to answer for the Maven stuff. Not sure what to do about this.
Maybe we don't even need it ? What does Karaf do here ?

cheers,
  Serge...
On Wed, Aug 22, 2018 at 9:19 PM Serge Huber  wrote:
>
> Hi François,
>
> Thanks for your work. I tried to compile the project but I got the
> following error :
>
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] 'version' is missing. @ line 23, column 106
>  @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.apache.unomi:site:[unknown-version]
> (/Users/loom/temp/incubator-unomi-website/pom.xml) has 1 error
> [ERROR] 'version' is missing. @ line 23, column 106
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
>
> After adding a version however it worked fine !
>
> I like the overall result although it seems like it is using a lot of
> space and some fonts seem really large. Also it seems some stuff is
> missing like the getting started (I couldn't find it).
>
> I like the new documentation part, some nice ideas there.
>
> My biggest concern is on-boarding newcomers with the site, and I think
> they shouldn't have to read through a lot of content to understand
> what the project does. Ideally maybe we should look into producing
> some kind of video or a quick animation.
>
> Finally I tried the site on a mobile device and it seems the
> navigation completely disappears.
>
> Anyway thanks for the effort I like it !
>
> cheers,
>   Serge...
> On Wed, Aug 22, 2018 at 12:12 PM Francois Papon
>  wrote:
> >
> > Hi,
> >
> > I worked on a preview version of the website and published it on my
> > github repo :
> >
> > https://github.com/fpapon/incubator-unomi-website
> >
> > I also started to work on a easy way to publish the documentation from
> > markdown to HTML and PDF.
> >
> > May be it could be nice to archive the documentation related to the
> > maven project with git tag because today it's on differents folder in
> > the src/ of the project.
> >
> > Thoughts ?
> >
> > regards,
> >
> > François Papon
> > fpa...@apache.org
> >
> > Le 03/08/2018 à 00:14, Serge Huber a écrit :
> > > Thanks François, looking forward to the PR !
> > >
> > > If you want to work on the website you're more than welcome to start
> > > working on it, as I said the more people get involved the better for
> > > the project !
> > >
> > > Regards,
> > >Serge..
> > > On Wed, Aug 1, 2018 at 8:48 PM Francois Papon
> > >  wrote:
> > >> Ok for Swagger, I will post a PR.
> > >>
> > >> About the website, let me know when you want me to start working on it
> > >> (I already have a repo on my github account).
> > >>
> > >> regards,
> > >>
> > >> François Papon
> > >> fpa...@apache.org
> > >>
> > >> Le 01/08/2018 à 18:25, Serge Huber a écrit :
> > >>> Feel free to help out on Swagger, I have little to no experience with 
> > >>> it.
> > >>>
> > >>> As for the GraphQL side, it's very experimental code that is
> > >>> constantly changing right now, so be warned that things might change
> > >>> quite significantly at any point but feel free to look at it and give
> > >>> feedback or even contribute!
> > >>>
> > >>> cheers,
> > >>>   Serge...
> > >>>
> > >>> Serge Huber
> > >>> CTO & Co-Founder
> > >>>
> > >>> T +41 22 361 3424
> > >>> 9 route des Jeunes | 1227 Acacias | Switzerland
> > >>> jahia.com
> > >>> SKYPE | LINKEDIN | TWITTER | VCARD
> > >>>
> > >>>
> > >>>> JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia 
> > >>>> is a leading User Experience Platform (UXP) for Digital Transformation.
> > >>> On Wed, Aug 1, 2018 at 9:00 AM Francois Papon
> > >>>  wrote:
> > >>>> Cool,
> > >>>>
> >

Re: [PROPOSAL] - Website and documentation

[Serge Huber]

Hi François,

Thanks for your work. I tried to compile the project but I got the
following error :

[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] 'version' is missing. @ line 23, column 106
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.apache.unomi:site:[unknown-version]
(/Users/loom/temp/incubator-unomi-website/pom.xml) has 1 error
[ERROR] 'version' is missing. @ line 23, column 106
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

After adding a version however it worked fine !

I like the overall result although it seems like it is using a lot of
space and some fonts seem really large. Also it seems some stuff is
missing like the getting started (I couldn't find it).

I like the new documentation part, some nice ideas there.

My biggest concern is on-boarding newcomers with the site, and I think
they shouldn't have to read through a lot of content to understand
what the project does. Ideally maybe we should look into producing
some kind of video or a quick animation.

Finally I tried the site on a mobile device and it seems the
navigation completely disappears.

Anyway thanks for the effort I like it !

cheers,
  Serge...
On Wed, Aug 22, 2018 at 12:12 PM Francois Papon
 wrote:
>
> Hi,
>
> I worked on a preview version of the website and published it on my
> github repo :
>
> https://github.com/fpapon/incubator-unomi-website
>
> I also started to work on a easy way to publish the documentation from
> markdown to HTML and PDF.
>
> May be it could be nice to archive the documentation related to the
> maven project with git tag because today it's on differents folder in
> the src/ of the project.
>
> Thoughts ?
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 03/08/2018 à 00:14, Serge Huber a écrit :
> > Thanks François, looking forward to the PR !
> >
> > If you want to work on the website you're more than welcome to start
> > working on it, as I said the more people get involved the better for
> > the project !
> >
> > Regards,
> >Serge..
> > On Wed, Aug 1, 2018 at 8:48 PM Francois Papon
> >  wrote:
> >> Ok for Swagger, I will post a PR.
> >>
> >> About the website, let me know when you want me to start working on it
> >> (I already have a repo on my github account).
> >>
> >> regards,
> >>
> >> François Papon
> >> fpa...@apache.org
> >>
> >> Le 01/08/2018 à 18:25, Serge Huber a écrit :
> >>> Feel free to help out on Swagger, I have little to no experience with it.
> >>>
> >>> As for the GraphQL side, it's very experimental code that is
> >>> constantly changing right now, so be warned that things might change
> >>> quite significantly at any point but feel free to look at it and give
> >>> feedback or even contribute!
> >>>
> >>> cheers,
> >>>   Serge...
> >>>
> >>> Serge Huber
> >>> CTO & Co-Founder
> >>>
> >>> T +41 22 361 3424
> >>> 9 route des Jeunes | 1227 Acacias | Switzerland
> >>> jahia.com
> >>> SKYPE | LINKEDIN | TWITTER | VCARD
> >>>
> >>>
> >>>> JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia is 
> >>>> a leading User Experience Platform (UXP) for Digital Transformation.
> >>> On Wed, Aug 1, 2018 at 9:00 AM Francois Papon
> >>>  wrote:
> >>>> Cool,
> >>>>
> >>>> If needed, I can help on the Swagger and the GraphQL integration ;)
> >>>>
> >>>> regards,
> >>>>
> >>>> François Papon
> >>>> fpa...@apache.org
> >>>> Yupiik - https://www.yupiik.com
> >>>>
> >>>> Le 31/07/2018 à 23:01, Serge Huber a écrit :
> >>>>> Hello François,
> >>>>>
> >>>>> Thanks for clarifying that I wasn't aware that you could use Swagger
> >>>>> that way. That makes sense.
> >>>>>
> >>>>> For GraphQL yes the final version of the CXS specification I'm also
> >>>>> co-developing has switched from REST to GraphQL,