Re: JPMS Projects?

[Serge Huber]

I was also going to mention OSGi. It enforces better lifecycle management
than JPMS. If you can do it with OSGi you can certainly use it with JPMS

Regards,
  Serge...

On Thu, Mar 18, 2021 at 3:19 PM Matt Sicker  wrote:

> Perhaps the various OSGi-related projects here might be similar to what
> you’re looking for since those have enforced modularity for a long time.
> That module system is more advanced than JPMS, but the concepts are fairly
> similar.
>
> We’ve also been looking into this for log4j 3.0, but that’s not out yet.
>
> On Thu, Mar 18, 2021 at 01:06 Daniel Widdis  wrote:
>
> > After considering this email I wrote, I regret sending it and want to
> > apologize if I have overstepped any bounds.
> >
> > I am not a member of the IPMC or associated in any formal way with Apache
> > and am certainly not in any position to make any judgments regarding code
> > quality or your wise choice to begin your search with such projects.
> >
> > I'll back out of this conversation now and let others answer or redirect
> > you to other resources.
> >
> > Dan
> >
> >
> > On 3/17/21, 10:21 PM, "Daniel Widdis"  wrote:
> >
> > Thanks for your clarifications.
> >
> > Regarding "Apache" = "Quality", I'd be careful.  Apache asserts [1] a
> > maxim of "Community over code".  While certainly a broad community
> > inevitably leads to better code, and Apache is a good starting point,
> given
> > the specificity of your request I might start there but not exclude other
> > established projects (not random code) which follow many of the same
> > principles.
> >
> > I do hope those on this list are aware of some projects they can
> > recommend to you!
> >
> > As for the technical specifications, I'd also recommend you'd
> separate
> > those out as well.  Some of your concerns seem to deal with native code
> > access which seems a separate issue than modular design of code.  I have
> > also been looking around for good Panama/FMA examples and haven't seen
> > anything non-trivial yet.  But even those can be done with/without the
> Java
> > Module System (JPMS).
> >
> > Looking forward to any other replies with interest.
> >
> > Dan
> >
> > [1] - https://www.apache.org/theapacheway/
> >
> > On 3/17/21, 10:08 PM, "leerho"  wrote:
> >
> > Daniel,
> > Thank you for your reply.
> >
> >
> > > Can you clarify what you mean by an "Apache Java project"?
> >
> >
> > I would prefer to examine a project that has a formal release
> > process and
> > an active community. So a TLP or incubating project would be
> > great.  In
> > this case I was equating "Apache" = "Quality"  :)
> >
> > I'm not so interested in random code on the Internet that just
> > happens to
> > be Apache licensed :)
> >
> > Is there a particular use case you are interested in?
> >
> >
> > I am seriously looking at *redesigning* our JDK8 Library using
> > Java Modules
> > leveraging JDK16+/Panama/FMA and completely replacing the need
> for
> > Unsafe,
> > etc.  (Not just adapting our JDK8 code to run on JDK9+ and
> > accessing Java
> > internals using JVM args.)
> >
> > This is a major undertaking so being able to look at projects
> that
> > have
> > already gone through that process would be helpful.
> >
> > Thank you,
> >
> > Lee.
> >
> > On Wed, Mar 17, 2021 at 3:42 PM Daniel B. Widdis <
> wid...@gmail.com>
> > wrote:
> >
> > > Can you clarify what you mean by an "Apache Java project"?
> > >  - A TLP?
> > >  - An incubating project?
> > >  - A project anywhere that is released under the Apache
> license?
> > >
> > > There's actually no need to "migrate code" in many cases, just
> > add some
> > > files. Is there a particular use case you are interested in?
> > >
> > > On Wed, Mar 17, 2021 at 3:11 PM leerho 
> wrote:
> > >
> > > > Folks,
> > > > Is anyone aware of an Apache Java project that has actually
> > migrated
> > > their
> > > > code from Java 8 to the Java Platform Module System (JPMS)?
> > > >
> > > > Thanks,
> > > > Lee.
> > > >
> > >
> > >
> > > --
> > > Dan Widdis
> > >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Podling use of StackOverflow

[Serge Huber]

If I may contribute my view here.

Using StackOverflow is mostly great for StackOverflow. The more people go
there to post questions and get answers really helps mostly StackOverflow's
bottom line. Also, StackOverflow does NOT allow to simply link to sites for
answers, which is smart on their part but very annoying for communities
such as Apache (can't link to an Apache project's site for example).
Instead the "answers content" must be directly in the answer, so you never
leave StackOverflow.

I usually get the following responses when encouraging somebody to post on
a mailing list:
- a mailing list? Those still exist?
- I don't like mailing lists, I have a single question, I don't want to
subscribe just to ask a single question
- why can't I use StackOverflow?
- don't make this harder for me
- I don't have time for this
- I give up, you're just some nostalgic oldtimer that wants everyone to use
Newsgroups, text files, and IRC :)

I also agree that if StackOverflow goes bankrupt one day, potentially all
the content is lost forever, whereas Apache now has been very good at
demonstrating it is resilient.

Ideally, content should be easy to search, so better indexing of the
mailing lists would be great, and it should be easier to ask just a
question and get an answer.

Therefore if we had an alternative to StackOverflow that was well indexed,
rightly available and hosted at Apache it would be the best of both worlds.

In the meantime, I think it is a necessary evil to have to answer questions
on StackOverflow, and at the same time find ways to encourage people to use
the mailing lists more. I try to encourage the usage of PonyMail as much as
possible.

Regards,
  Serge...


On Fri, Apr 5, 2019 at 4:11 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Fri, Apr 5, 2019 at 3:35 PM James Bognar 
> wrote:
> > ...Apache is sorely in need of a portal similar to StackOverflow...
>
> What makes you think we need our own service, as opposed to helping
> our users where they are?
>
> As Ted said in this thread:
>
> > Just subscribe to appropriate tags on stack overflow and direct
> > notifications to the dev list.
>
> > ...Using mailing lists for
> > everything is one of the top Apache-Way principles
>
> All decisions related to project development must happen on a
> project's dev list, or be relayed there.
>
> But apart from that projects are welcome to use any channels that help
> them reach their users.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Cava] Suitable name search

[Serge Huber]

I agree that it doesn't matter if it "meant" something, you can simply
forget the original meaning.

So it could mean "Cryptographic Java"

Here are other suggestions, because I like have the block and/or in the name :)

- Blockava
- Blockva
- Chainava

Please note I didn't do any proper name search for the above :)

Regards,
  Serge...

On Mon, Feb 18, 2019 at 5:32 PM Jim Jagielski  wrote:
>
> Consensus Java :)
>
> > On Feb 16, 2019, at 1:59 PM, Antoine Toulme  wrote:
> >
> > I explained it in the proposal and the original thread, Cava stands for 
> > “ConsenSys Java”, after Guava.
> >
> > It’s not a bad name per se, so let’s add it to the proposals.
> >
> >> On Feb 16, 2019, at 9:58 AM, Henry Saputra  wrote:
> >>
> >> From last thread, I was not sure why Cava was not a suitable name?
> >>
> >> If there is a concern about trademarked name, the community can always go
> >> with Apache Cava name.
> >>
> >> - Henry
> >>
> >> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme  >>
> >>> Thank you Anu.
> >>>
> >>> I’ll add your proposal to mine and start a vote Monday if that’s 
> >>> agreeable.
> >>>
> >>> Cheers,
> >>>
> >>> Antoine
> >>>
>  On Feb 13, 2019, at 12:03 PM, Anu Engineer 
> >>> wrote:
> 
>  I would like to suggest “Jal”, in reference to Indra’s net (or Indra
> >>> jal) https://en.wikipedia.org/wiki/Indra%27s_net
> 
>  From the link:
>  "Imagine a multidimensional spider's web in the early morning covered
> >>> with dew drops. And every dew drop contains the reflection of all the 
> >>> other
> >>> dew drops.
>  And, in each reflected dew drop, the reflections of all the other dew
> >>> drops in that reflection. And so ad infinitum. That is the Buddhist
> >>> conception of the universe in an image." –Alan Watts[1]
> 
>  And for what it is worth, it is the ultimate connected chain or graph (
> 
>  --Anu
> 
> 
> 
> 
> 
>  On 2/13/19, 10:58 AM, "Antoine Toulme"  wrote:
> 
>   Hello all,
> 
>   As discussed previously, Cava is not a proper name for the proposal
> >>> discussed last week on this list and published to the wiki [0].
> 
>   I humbly would like to ask the community for feedback and proposals
> >>> on a suitable name for this proposal, in line with the guidelines [1].
> 
>   In preparation for this search, I have put together a list of names:
> 
>   - Rainbow (after the name of my kid’s favorite toy, and in line with
> >>> the crypto community unicorn punk theme [2].
>   - Winch (a mechanical device used to wind up or wind out wires
> >>> (Wikipedia) , in the chain theme)
>   - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a
> >>> chain, track or other perforated or indented material. (Wikipedia), in the
> >>> chain theme as well)
> 
>   I have researched those names lightly and I have not seen them used
> >>> heavily by an open source project in crypto. I followed the guidelines to
> >>> search across different open source communities.
> 
>   Please provide your own proposal and let’s work together towards a
> >>> rough consensus. If one of the proposals above registers, please let us
> >>> know as well.
> 
>   Cheers,
> 
>   Antoine
> 
>   [0]: https://wiki.apache.org/incubator/CavaProposal
>   [1]: https://incubator.apache.org/guides/names.html <
> >>> https://incubator.apache.org/guides/names.html>
>   [2]: https://www.urbandictionary.com/define.php?term=unicorn%20punk
> 
> 
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

Hi all,

Here are the results for the Apache Unomi graduation vote :

+1 x 17
+1 (binding) x 10
+1 (non-binding) x 7

No -1 or 0 votes.

You can find the thread for the vote here :
https://lists.apache.org/thread.html/64f097e7b0afe050cc9849fec40573039164e91fb059c95d08b36171@%3Cgeneral.incubator.apache.org%3E

This vote PASSES.

Here is the vote tally:

+1:
Binding:
- Bertrand Delacretaz
- Jean-Baptiste Onofré
- Myrle Krantz
- David Fisher
- Daniel Gruno
- Matt Sicker
- Willem Ning Jiang
- Mohammad Asif Siddiqui
- Woonsan Ko
- Lionel Liu

Non-binding:
- Serge Huber
- Pierre Smits
- Steve Blackmon
- Huxing Zhang
- Xin Wang
- Hongtao Gao
- William Guo

The resolution will be submitted to the board for the next meeting.

Thanks everybody for voting.

Best Regards,

  Serge Huber.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

Hello all,

This VOTE is closed and passes.  It was open for 14 days (mostly
because of PNS search).

I'll create a separate RESULT thread for the voting details but here's
the summary :

+1 x 17
+1 (binding) x 10
+1 (non-binding) x 7

Thanks, everyone for helping Apache Unomi reach this great milestone.

Regards,
  Serge...

On Mon, Feb 4, 2019 at 11:31 AM Serge Huber  wrote:
>
> Thanks Daniel for replying so quickly, greatly appreciated.
>
> Regards,
>   Serge...
>
> On Mon, Feb 4, 2019 at 11:25 AM Daniel Gruno  wrote:
> >
> > +1 - still in brussels, so lagging behind on email :)
> >
> > On 04/02/2019 11.10, Serge Huber wrote:
> > > Hello Daniel,
> > >
> > > I'd like to close the vote soon but as you voted -1 because of the
> > > lack of PNS we need your new vote.
> > >
> > > For your information, here's the completed and accepted PNS [1].
> > >
> > > Best regards,
> > >Serge Huber.
> > >
> > > [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-161
> > >
> > > On Tue, Jan 22, 2019 at 3:12 PM Daniel Gruno  wrote:
> > >>
> > >> On 1/22/19 3:09 PM, Mark Thomas wrote:
> > >>> On 22/01/2019 00:37, Greg Stein wrote:
> > >>>> On Mon, Jan 21, 2019 at 3:21 PM Dave Fisher  
> > >>>> wrote:
> > >>>>
> > >>>>>-0 (binding) - This podling has never completed a suitable podling 
> > >>>>> name
> > >>>>> search. It seems that people no longer consider that relevant as it 
> > >>>>> is not
> > >>>>> in the Maturity model and I’m not sure why. It could be because that 
> > >>>>> is
> > >>>>> ComDev and not the IPMC.
> > >>>>>
> > >>>>
> > >>>> The "Maturity Model" (MM) is just a thing developed by ComDev peeps. 
> > >>>> It has
> > >>>> no bearing within the Foundation, other than as a lens for individuals 
> > >>>> to
> > >>>> view projects. That lens is not part of the Incubator, or any other 
> > >>>> PMC.
> > >>>>
> > >>>> Personally, I do not view the "podling name search" (PNS) as a gate. 
> > >>>> That
> > >>>> is another imposition, from outside the Incubator, that has crept into 
> > >>>> the
> > >>>> "Must Be Performed(tm)" guidelines for graduation. The Board is the
> > >>>> ultimate arbiter of whether a podling can graduate, and a name search 
> > >>>> is
> > >>>> informative for them, rather than gating for us [on the IPMC]. If a 
> > >>>> podling
> > >>>> wants to be called "Apache Acme", and "gee, there are a lot of Acme
> > >>>> products out there", then that is on the community. Not something for 
> > >>>> the
> > >>>> Incubator to demand they change; just something for them to deal with. 
> > >>>> A
> > >>>> community problem, rather than one for the Incubator or the Foundation
> > >>>> itself.
> > >>>
> > >>> I disagree on that point - as VP Brand I would, wouldn't I ;)
> > >>>
> > >>> If there is an issue with the name (that the PNS would have uncovered)
> > >>> then the likely solution is that the (now graduated) project will have
> > >>> to rename. That has a cost for both the community and the foundation.
> > >>>
> > >>> While in some cases there are clearly no conflicts, in others it is not
> > >>> quite so clear cut. The aim of the PNS is to enable both the podling and
> > >>> the foundation (delegated to the Branding Committee) to decide if the
> > >>> choice of name is acceptable given the degree of risk associated with
> > >>> any potential conflict and the associated costs of a rename should that
> > >>> risk materialise.
> > >>>
> > >>> (There is an assumption here that early renames result in lower costs
> > >>> for both the community and the foundation).
> > >>>
> > >>> As VP Brand I am likely recommend against a podling graduating without a
> > >>> PNS on the basis that it represents an unknown level of risk. The board
> > >>> may approve the resolution anyway but I suspect it 

Re: [VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

Thanks Daniel for replying so quickly, greatly appreciated.

Regards,
  Serge...

On Mon, Feb 4, 2019 at 11:25 AM Daniel Gruno  wrote:
>
> +1 - still in brussels, so lagging behind on email :)
>
> On 04/02/2019 11.10, Serge Huber wrote:
> > Hello Daniel,
> >
> > I'd like to close the vote soon but as you voted -1 because of the
> > lack of PNS we need your new vote.
> >
> > For your information, here's the completed and accepted PNS [1].
> >
> > Best regards,
> >Serge Huber.
> >
> > [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-161
> >
> > On Tue, Jan 22, 2019 at 3:12 PM Daniel Gruno  wrote:
> >>
> >> On 1/22/19 3:09 PM, Mark Thomas wrote:
> >>> On 22/01/2019 00:37, Greg Stein wrote:
> >>>> On Mon, Jan 21, 2019 at 3:21 PM Dave Fisher  
> >>>> wrote:
> >>>>
> >>>>>-0 (binding) - This podling has never completed a suitable podling 
> >>>>> name
> >>>>> search. It seems that people no longer consider that relevant as it is 
> >>>>> not
> >>>>> in the Maturity model and I’m not sure why. It could be because that is
> >>>>> ComDev and not the IPMC.
> >>>>>
> >>>>
> >>>> The "Maturity Model" (MM) is just a thing developed by ComDev peeps. It 
> >>>> has
> >>>> no bearing within the Foundation, other than as a lens for individuals to
> >>>> view projects. That lens is not part of the Incubator, or any other PMC.
> >>>>
> >>>> Personally, I do not view the "podling name search" (PNS) as a gate. That
> >>>> is another imposition, from outside the Incubator, that has crept into 
> >>>> the
> >>>> "Must Be Performed(tm)" guidelines for graduation. The Board is the
> >>>> ultimate arbiter of whether a podling can graduate, and a name search is
> >>>> informative for them, rather than gating for us [on the IPMC]. If a 
> >>>> podling
> >>>> wants to be called "Apache Acme", and "gee, there are a lot of Acme
> >>>> products out there", then that is on the community. Not something for the
> >>>> Incubator to demand they change; just something for them to deal with. A
> >>>> community problem, rather than one for the Incubator or the Foundation
> >>>> itself.
> >>>
> >>> I disagree on that point - as VP Brand I would, wouldn't I ;)
> >>>
> >>> If there is an issue with the name (that the PNS would have uncovered)
> >>> then the likely solution is that the (now graduated) project will have
> >>> to rename. That has a cost for both the community and the foundation.
> >>>
> >>> While in some cases there are clearly no conflicts, in others it is not
> >>> quite so clear cut. The aim of the PNS is to enable both the podling and
> >>> the foundation (delegated to the Branding Committee) to decide if the
> >>> choice of name is acceptable given the degree of risk associated with
> >>> any potential conflict and the associated costs of a rename should that
> >>> risk materialise.
> >>>
> >>> (There is an assumption here that early renames result in lower costs
> >>> for both the community and the foundation).
> >>>
> >>> As VP Brand I am likely recommend against a podling graduating without a
> >>> PNS on the basis that it represents an unknown level of risk. The board
> >>> may approve the resolution anyway but I suspect it would be tabled
> >>> (delayed) until the following meeting to allow a PNS or something along
> >>> those lines to take place.
> >>>
> >>> As an aside, the policy docs still say a PNS is required to graduate. If
> >>> this view has changed (I'm not sure it has - I don't recall a
> >>> discussion) then those docs need updating.
> >>
> >> I haven't heard of any policy change either, and with that in mind, I am
> >> -1 (binding) on graduation till a PNS has been resolved. As Mark stated,
> >> there are costs involved with name changes, on multiple fronts, and
> >> making sure that we don't clash is quite important.
> >>
> >> With that said, there is plenty of time till the next board meeting, a
> >> PNS _could_ be done in time for that, and I'd remove my -1. :)
> >>
> >>>
> &

Re: [VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

Hello Daniel,

I'd like to close the vote soon but as you voted -1 because of the
lack of PNS we need your new vote.

For your information, here's the completed and accepted PNS [1].

Best regards,
  Serge Huber.

[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-161

On Tue, Jan 22, 2019 at 3:12 PM Daniel Gruno  wrote:
>
> On 1/22/19 3:09 PM, Mark Thomas wrote:
> > On 22/01/2019 00:37, Greg Stein wrote:
> >> On Mon, Jan 21, 2019 at 3:21 PM Dave Fisher  wrote:
> >>
> >>>   -0 (binding) - This podling has never completed a suitable podling name
> >>> search. It seems that people no longer consider that relevant as it is not
> >>> in the Maturity model and I’m not sure why. It could be because that is
> >>> ComDev and not the IPMC.
> >>>
> >>
> >> The "Maturity Model" (MM) is just a thing developed by ComDev peeps. It has
> >> no bearing within the Foundation, other than as a lens for individuals to
> >> view projects. That lens is not part of the Incubator, or any other PMC.
> >>
> >> Personally, I do not view the "podling name search" (PNS) as a gate. That
> >> is another imposition, from outside the Incubator, that has crept into the
> >> "Must Be Performed(tm)" guidelines for graduation. The Board is the
> >> ultimate arbiter of whether a podling can graduate, and a name search is
> >> informative for them, rather than gating for us [on the IPMC]. If a podling
> >> wants to be called "Apache Acme", and "gee, there are a lot of Acme
> >> products out there", then that is on the community. Not something for the
> >> Incubator to demand they change; just something for them to deal with. A
> >> community problem, rather than one for the Incubator or the Foundation
> >> itself.
> >
> > I disagree on that point - as VP Brand I would, wouldn't I ;)
> >
> > If there is an issue with the name (that the PNS would have uncovered)
> > then the likely solution is that the (now graduated) project will have
> > to rename. That has a cost for both the community and the foundation.
> >
> > While in some cases there are clearly no conflicts, in others it is not
> > quite so clear cut. The aim of the PNS is to enable both the podling and
> > the foundation (delegated to the Branding Committee) to decide if the
> > choice of name is acceptable given the degree of risk associated with
> > any potential conflict and the associated costs of a rename should that
> > risk materialise.
> >
> > (There is an assumption here that early renames result in lower costs
> > for both the community and the foundation).
> >
> > As VP Brand I am likely recommend against a podling graduating without a
> > PNS on the basis that it represents an unknown level of risk. The board
> > may approve the resolution anyway but I suspect it would be tabled
> > (delayed) until the following meeting to allow a PNS or something along
> > those lines to take place.
> >
> > As an aside, the policy docs still say a PNS is required to graduate. If
> > this view has changed (I'm not sure it has - I don't recall a
> > discussion) then those docs need updating.
>
> I haven't heard of any policy change either, and with that in mind, I am
> -1 (binding) on graduation till a PNS has been resolved. As Mark stated,
> there are costs involved with name changes, on multiple fronts, and
> making sure that we don't clash is quite important.
>
> With that said, there is plenty of time till the next board meeting, a
> PNS _could_ be done in time for that, and I'd remove my -1. :)
>
> >
> > Mark
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

I assume we can (resume) the voting process. If it's ok to do it here here's my

+1 (non-binding)

Regards,
  Serge...

On Thu, Jan 31, 2019 at 2:39 PM Serge Huber  wrote:
>
> Name has been approved. Thanks Mark for doing this quickly.
>
> Regards,
>   Serge...
>
> On Tue, Jan 29, 2019 at 2:10 PM Serge Huber  wrote:
> >
> > Ok I've created the ticket here:
> >
> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-161
> >
> > Please let me know if there is more to be done, I've done my best to
> > make it as extensive as possible.
> >
> > Best regards,
> >   Serge...
> >
> > On Tue, Jan 22, 2019 at 4:19 PM Jean-Baptiste Onofré  
> > wrote:
> > >
> > > Thanks Bertrand.
> > >
> > > Serge and I will deal with that.
> > >
> > > Regards
> > > JB
> > >
> > > On 22/01/2019 16:18, Bertrand Delacretaz wrote:
> > > > On Tue, Jan 22, 2019 at 4:17 PM Jean-Baptiste Onofré 
> > > >  wrote:
> > > >> ...I think we still have time to launch a PNS, and the idea was to do 
> > > >> this
> > > >> as part of the graduation...
> > > >
> > > > Yes that should work - you basically just need to create a ticket at
> > > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH and there are
> > > > many examples there.
> > > >
> > > > Details at https://incubator.apache.org/guides/names.html
> > > >
> > > > -Bertrand
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

Name has been approved. Thanks Mark for doing this quickly.

Regards,
  Serge...

On Tue, Jan 29, 2019 at 2:10 PM Serge Huber  wrote:
>
> Ok I've created the ticket here:
>
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-161
>
> Please let me know if there is more to be done, I've done my best to
> make it as extensive as possible.
>
> Best regards,
>   Serge...
>
> On Tue, Jan 22, 2019 at 4:19 PM Jean-Baptiste Onofré  
> wrote:
> >
> > Thanks Bertrand.
> >
> > Serge and I will deal with that.
> >
> > Regards
> > JB
> >
> > On 22/01/2019 16:18, Bertrand Delacretaz wrote:
> > > On Tue, Jan 22, 2019 at 4:17 PM Jean-Baptiste Onofré  
> > > wrote:
> > >> ...I think we still have time to launch a PNS, and the idea was to do 
> > >> this
> > >> as part of the graduation...
> > >
> > > Yes that should work - you basically just need to create a ticket at
> > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH and there are
> > > many examples there.
> > >
> > > Details at https://incubator.apache.org/guides/names.html
> > >
> > > -Bertrand
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

Ok I've created the ticket here:

https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-161

Please let me know if there is more to be done, I've done my best to
make it as extensive as possible.

Best regards,
  Serge...

On Tue, Jan 22, 2019 at 4:19 PM Jean-Baptiste Onofré  wrote:
>
> Thanks Bertrand.
>
> Serge and I will deal with that.
>
> Regards
> JB
>
> On 22/01/2019 16:18, Bertrand Delacretaz wrote:
> > On Tue, Jan 22, 2019 at 4:17 PM Jean-Baptiste Onofré  
> > wrote:
> >> ...I think we still have time to launch a PNS, and the idea was to do this
> >> as part of the graduation...
> >
> > Yes that should work - you basically just need to create a ticket at
> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH and there are
> > many examples there.
> >
> > Details at https://incubator.apache.org/guides/names.html
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Graduate Apache Unomi to TLP

[Serge Huber]

Hello,

The Apache Unomi podling community has successfully[0] VOTEd[1] to
graduate to a top-level project. Accordingly, I'm bringing the
resolution up for an IPMC VOTE.

The podling vote result was:
Overall: 8 x +1 votes, 0 x -1 votes

7 binding +1 votes: Jean-Baptiste Onofré, Bertrand Delacretaz, Thomas
Draier, Serge Huber, , François Papon, Kevan Jahanshahi, David Griffon
1 non-binding +1 vote: Damien Gaillard

No 0 or -1.

Since entering the Incubator in 2015, the Apache Unomi community has:
   * sent 3984 emails by 88 participants in the mailing lists [2]
   * successfully produced 3 major project releases
   * setup a complete website including project documentation
   * added 3 new committers/PPMC members
   * built a diverse group of committers from multiple different employers
   * had more than 214 JIRA tickets opened with 176 closed
   * completed the project maturity model with positive responses [3]

Here's my non-binding +1.  The VOTE will run for at least 72 hours.

Thanks & best regards,
  Serge Huber.

[0] 
https://lists.apache.org/thread.html/336164cecff397630eb6715004af36770b7ab00b010daa2484167c76@%3Cdev.unomi.apache.org%3E
[1] 
https://lists.apache.org/thread.html/095d94557746fdd1b8d33f87feab939c70abbf22fd732980a2e7c59e@%3Cdev.unomi.apache.org%3E
[2] https://lists.apache.org/trends.html?*@unomi.apache.org:lte=5y:
[3] 
https://lists.apache.org/thread.html/68d590ef4262f533f485cf360787129e5898a2a45bd2499f9be22703@%3Cdev.unomi.apache.org%3E


Here is 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.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: NOTICE required for PPMC members

[Serge Huber]

Just so I'm very clear, as initial committers are PPMC members
according to [1] this means that no NOTICE needs to be sent right and
initial committers are automatically full-fledged PPMC members.

The text reads: "The Podling Project Management Committee (PPMC) helps
a Podling learn how to govern itself. It works like a PMC but reports
to the Incubator PMC instead of to the ASF Board. Initially, it is
composed of the Podling’s mentors and initial committers."

If this is correct this means we do have all the PPMC members we need
to graduate the Apache Unomi project. I misunderstood that somehow we
should have had notices for the initial committers as well.

Regards,
  Serge...

[1] 
https://incubator.apache.org/guides/ppmc.html#podling_project_management_committee_ppmc
On Sat, Nov 24, 2018 at 7:04 AM Justin Mclean  wrote:
>
> HI,
>
> > It does not apply to initial committers/PPMC members named in the 
> > PodlingProposal.
>
> Yep that’s my understanding as well.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Getting through the hoops

[Serge Huber]

Indeed that would be really nice, and we could imagine a form that would give 
people through the process, and also sent expectations in terms of what happens 
next and how much time it might take.

Regards,
  Serge… 

> On 16 Oct 2018, at 10:33, Bertrand Delacretaz  
> wrote:
> 
> On Tue, Oct 16, 2018 at 10:29 AM Daniel Gruno  wrote:
>> ...Thinking out loud here...what if we made a form that better explains
>> things and checks if the userid is available etc, and then it generates
>> a PDF to review/sign with all the fields filled out?...
> 
> That would be fantastic - onboarding instructions that consist of a
> single persistent URL are a Good Thing!
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Getting through the hoops (was: Mentors wanted...)

[Serge Huber]

Actually I think there is a lot of documentation and in itself it can be a bit 
daunting. Also for the committer request, it would be great if it could be 
streamlined by doing some kind of online form but there is the question of the 
digital signature that might be an issue.

Also, some of the optional fields such as the Apache ID or the project name 
should maybe be explained as less than optional. I’ve had the problem recently 
that committers filled the ICLA without the optional fields, and then the 
secretary asked for the ID and the project name. So this is putting additional 
work on the secretary which could be avoided.

In other words, it’s not that hard when you know the process, but when you’re 
learning it and want to do the right thing by not bothering mentors for 
everything, I think it is less straightforward than setting up an account on 
Github, which I think is what a lot of people are comparing the experience too 
(at least that’s the feedback I get usually).

Regards,
  Serge… 

> On 16 Oct 2018, at 10:06, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
> On Mon, Oct 15, 2018 at 7:29 PM Benjamin Young  wrote:
>> ...I've continued to reach out to other initial committers to get them 
>> through the
>> hoops here at Apache--which took  a few weeks of setup, 
>> reading, etc...
>> Mostly, I think folks find the process daunting. :-/...
> 
> I'm curious what's so hard, maybe we aren't explaining things properly?
> 
> IMO an initial or elected committer needs to choose an Apache ID,
> register their iCLA, wait for their account to be created, sign up to
> their project's dev (and maybe private) list and they're in business.
> Ok, for now they also need to create accounts on Jira and Confluence
> if the project uses that.
> 
> Is this what's considered too hard, or did I miss something?
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Unomi mentors

[Serge Huber]

Hello all,

Thanks for your help and interest in Apache Unomi. Yes, we are trying
to get to graduation as quickly as possible, I'm not sure if we need
another mentor but our next steps are to make sure we have everything
ready for graduation.

Regards,
  Serge...
On Tue, Sep 4, 2018 at 9:23 AM Justin Mclean  wrote:
>
> Hi,
>
> > I am interested in mentoring Unomi. Having mentored Trafodion during
> > incubation and my interest in the impact of GDPR will surely help.
>
> Thanks for your interest but only incubator PMC members can officially mentor 
> projects.[1] Usually that means only ASF member can be mentors, a couple of 
> people managed to get voted into the IPMC without being members but it’s 
> uncommon. That of course doesn't stop you from helping out in other ways.
>
> Thanks,
> Justin
>
> 1. https://incubator.apache.org/guides/mentor.html#mentors_must_be_on_the_ipmc
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[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,

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

I believe we have the votes we need I will now close the vote and post
a result post.

Regards,
  Serge...
On Thu, Aug 23, 2018 at 4:33 PM Serge Huber  wrote:
>
> Thanks a lot, Bertrand, for your review.
>
> Sorry about that "surprise" about the keystore. I'll see if we can
> somehow generate the key from a Maven script or something for the next
> release, but I'm not sure how acceptable that is. I wonder how other
> projects handle this type of things?
>
> Regards,
>   Serge...
> On Tue, Aug 21, 2018 at 4:44 PM Bertrand Delacretaz
>  wrote:
> >
> > Hi,
> >
> > On Fri, Jul 27, 2018 at 4:21 PM Serge Huber  wrote:
> > > ...Source distribution is here :
> > > https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip
> > >  ...
> >
> > +1 for that release, with
> > SHA1(unomi-1.3.0-incubating-src.zip)= 
> > 31c08369672b0b150c2c11bbae0b12ba6bcdeec7
> >
> > Checked the signature, digest, LICENSE, NOTICE, DISCLAIMER and the build.
> >
> > Looking for binary files in the distribution,
> > package/src/main/resources/etc/keystore raised my attention. The Git
> > history leads to https://issues.apache.org/jira/browse/UNOMI-138,
> > which very briefly explains what that's about and somewhat reassured
> > me ;-)
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

Thanks a lot, Bertrand, for your review.

Sorry about that "surprise" about the keystore. I'll see if we can
somehow generate the key from a Maven script or something for the next
release, but I'm not sure how acceptable that is. I wonder how other
projects handle this type of things?

Regards,
  Serge...
On Tue, Aug 21, 2018 at 4:44 PM Bertrand Delacretaz
 wrote:
>
> Hi,
>
> On Fri, Jul 27, 2018 at 4:21 PM Serge Huber  wrote:
> > ...Source distribution is here :
> > https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip
> >  ...
>
> +1 for that release, with
> SHA1(unomi-1.3.0-incubating-src.zip)= 31c08369672b0b150c2c11bbae0b12ba6bcdeec7
>
> Checked the signature, digest, LICENSE, NOTICE, DISCLAIMER and the build.
>
> Looking for binary files in the distribution,
> package/src/main/resources/etc/keystore raised my attention. The Git
> history leads to https://issues.apache.org/jira/browse/UNOMI-138,
> which very briefly explains what that's about and somewhat reassured
> me ;-)
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

Thanks Bertrand I appreciate that.
On Tue, Aug 21, 2018 at 3:48 PM Bertrand Delacretaz
 wrote:
>
> Hi Serge,
>
> On Tue, Aug 21, 2018 at 3:41 PM Serge Huber  wrote:
> > ...This vote has been almost open for a month now and has only 2 binding
> > IPMC votes. Is this ok and can we close the vote or do we need a third
> > one?...
>
> You need 3 votes to release - I'll review this release later today!
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

Hello all,

Just a doubt about the IPMC voting process.

This vote has been almost open for a month now and has only 2 binding
IPMC votes. Is this ok and can we close the vote or do we need a third
one?

Regards,
  Serge...

ps : not blaming anyone, it is vacation time so I voluntarily left it
open longer, just checking what we should do now.
On Mon, Aug 20, 2018 at 11:24 AM Serge Huber  wrote:
>
> Hi Justin,
>
> Thanks a lot for the review!
>
> On Tue, Aug 14, 2018 at 10:20 AM Justin Mclean  
> wrote:
> >
> > Hi,
> >
> > I’m a little confused why the directory in the source zip is called 
> > unomi-root-1.3.0-incubating.
>
> Because of the current build process, I rename the project source
> manually at the end, but I think we could improve this process. Thanks
> for catching that.
>
> >
> > But I checked:
> > - incubating in name
> > - signature and hashes file (note however that .sha1 is no long considered 
> > secure and you should be using sha 256 or 512)
> > - DISCLAIMER exists
> > - LICENSE and NOTICE file OK
> > - All source files have ASF headers
> > - No unexpected binary files in source release
> > - Can compile from source
> >
> > BTW Is this file supposed to be in the source release? [1]
>
> I think this file should be removed, but it's not a blocking problem
> for the release.
>
> Thanks for the review and the vote!
>
> cheers,
>   Serge...

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

Hi Justin,

Thanks a lot for the review!

On Tue, Aug 14, 2018 at 10:20 AM Justin Mclean  wrote:
>
> Hi,
>
> I’m a little confused why the directory in the source zip is called 
> unomi-root-1.3.0-incubating.

Because of the current build process, I rename the project source
manually at the end, but I think we could improve this process. Thanks
for catching that.

>
> But I checked:
> - incubating in name
> - signature and hashes file (note however that .sha1 is no long considered 
> secure and you should be using sha 256 or 512)
> - DISCLAIMER exists
> - LICENSE and NOTICE file OK
> - All source files have ASF headers
> - No unexpected binary files in source release
> - Can compile from source
>
> BTW Is this file supposed to be in the source release? [1]

I think this file should be removed, but it's not a blocking problem
for the release.

Thanks for the review and the vote!

cheers,
  Serge...

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

Hi guys just a reminder we would love some more IPMC votes for this release!

Thanks & regards,
  Serge...
On Tue, Jul 31, 2018 at 2:38 AM Jean-Baptiste Onofré  wrote:
>
> +1 (binding)
>
> Casting my vote here.
>
> Regards
> JB
>
> On 27/07/2018 16:21, Serge Huber wrote:
> > Hi all,
> >
> > The Unomi community has voted again for the release of Apache Unomi 1.3.0
> > (incubating) [TAKE2].
> >
> > The following corrections were done since TAKE1:
> > - NOTICE year (2016) has been updated to 2018
> > - unexpected binaries inside zip file [1]: zip file has been completely 
> > removed
> > - All artifacts are now signed in an Apache email address
> >
> > The vote thread can be found at :
> > http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAV0N729Nb9cZXNiGh%3DvQx0ncSLToVEO%3Dd_jR%3DFqrGJyig%40mail.gmail.com%3E
> >
> > and the result is at:
> > http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAW%3D2hO_1h_sPM6rJpG0TeONDgQm9Tvax1AUcdSkX%3DFQyQ%40mail.gmail.com%3E
> >
> > We kindly ask the IPMC to vote on this release.
> >
> > The artifacts to be voted on are located at:
> > https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating
> > Source distribution is here :
> > https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip
> >
> > With signature :
> > https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip.asc
> >
> > The keys used to sign the released artifacts can be found in :
> > https://dist.apache.org/repos/dist/release/incubator/unomi/KEYS
> >
> > The tag is at:
> > *https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.3.0-incubating
> > <https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.3.0-incubating>*
> > ( 98ef47a9a71c9f31ba55d01f01370265bcb5a557 )
> >
> > This vote will be open for at least 72 hours, or until the necessary number
> > of votes (3 +1) is reached.
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > Regards,
> >   Serge
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

Btw here's my

+1 (non-binding)

Regards,
  Serge...
On Fri, Jul 27, 2018 at 4:21 PM Serge Huber  wrote:
>
> Hi all,
>
> The Unomi community has voted again for the release of Apache Unomi 1.3.0
> (incubating) [TAKE2].
>
> The following corrections were done since TAKE1:
> - NOTICE year (2016) has been updated to 2018
> - unexpected binaries inside zip file [1]: zip file has been completely 
> removed
> - All artifacts are now signed in an Apache email address
>
> The vote thread can be found at :
> http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAV0N729Nb9cZXNiGh%3DvQx0ncSLToVEO%3Dd_jR%3DFqrGJyig%40mail.gmail.com%3E
>
> and the result is at:
> http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAW%3D2hO_1h_sPM6rJpG0TeONDgQm9Tvax1AUcdSkX%3DFQyQ%40mail.gmail.com%3E
>
> We kindly ask the IPMC to vote on this release.
>
> The artifacts to be voted on are located at:
> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating
> Source distribution is here :
> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip
>
> With signature :
> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip.asc
>
> The keys used to sign the released artifacts can be found in :
> https://dist.apache.org/repos/dist/release/incubator/unomi/KEYS
>
> The tag is at:
> *https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.3.0-incubating
> <https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.3.0-incubating>*
> ( 98ef47a9a71c9f31ba55d01f01370265bcb5a557 )
>
> This vote will be open for at least 72 hours, or until the necessary number
> of votes (3 +1) is reached.
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> Regards,
>   Serge

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]

[Serge Huber]

Hi all,

The Unomi community has voted again for the release of Apache Unomi 1.3.0
(incubating) [TAKE2].

The following corrections were done since TAKE1:
- NOTICE year (2016) has been updated to 2018
- unexpected binaries inside zip file [1]: zip file has been completely removed
- All artifacts are now signed in an Apache email address

The vote thread can be found at :
http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAV0N729Nb9cZXNiGh%3DvQx0ncSLToVEO%3Dd_jR%3DFqrGJyig%40mail.gmail.com%3E

and the result is at:
http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAW%3D2hO_1h_sPM6rJpG0TeONDgQm9Tvax1AUcdSkX%3DFQyQ%40mail.gmail.com%3E

We kindly ask the IPMC to vote on this release.

The artifacts to be voted on are located at:
https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating
Source distribution is here :
https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip

With signature :
https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip.asc

The keys used to sign the released artifacts can be found in :
https://dist.apache.org/repos/dist/release/incubator/unomi/KEYS

The tag is at:
*https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.3.0-incubating
*
( 98ef47a9a71c9f31ba55d01f01370265bcb5a557 )

This vote will be open for at least 72 hours, or until the necessary number
of votes (3 +1) is reached.

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

Regards,
  Serge

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release

[Serge Huber]

Ok I see it it's only in the report. Is there a way to make the build
fail if an unwanted archive is detected?  Sorry to bother you with
this but I don't find much doc about the Apache Rat Plugin (maybe I'm
not looking in the right place
http://creadur.apache.org/rat/apache-rat-plugin/usage.html ?)

Thanks for the help.

cheers,
  Serge...
On Mon, Jul 16, 2018 at 10:36 AM Justin Mclean  wrote:
>
> Hi,
>
> > Yes I was wondering if RAT could help catch that because it is in
> > place on the project but I wasn't sure if it performed those types of
> > checks.
>
>
> It helps a little it will flag the zip file as a binary file but it won’t 
> look in it’s contents.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release

[Serge Huber]

Yes I was wondering if RAT could help catch that because it is in
place on the project but I wasn't sure if it performed those types of
checks.

cheers,
  Serge...
On Sun, Jul 15, 2018 at 3:17 PM Justin Mclean  wrote:
>
> HI,
>
> > Thanks Justin for the review and catching that, somehow I missed this sorry 
> > about that.
>
> No issue. You might want to check that your rat exclusions haven’t been set a 
> little too wide, it happens reasonably frequently, even with some TLP 
> projects.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release

[Serge Huber]

Thanks Justin for the review and catching that, somehow I missed this
sorry about that.

Regards,
  Serge...
On Sat, Jul 14, 2018 at 9:49 AM Justin Mclean  wrote:
>
> Hi,
>
> Sorry but it;’s -1 binding as the source release contains compile code. This 
> zip [1] contains compiled class files and a jar with compiled class files.
>
> Everything else is good I checked:
> - incubating in name
> - signatures and hash correct
> - LICENSE is good
> - NOTICE year (2016) needs updating
> - All source file have ASF headers
> - unexpected binaries inside zip file [1]
> - can compile from source
>
> It a good idea to sign the artefacts with an apache email address.
>
> Thanks,
> Justin
>
> 1. unomi-root-1.3.0-incubating/samples/trainingplugin.zip
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Unomi 1.3.0-incubating release

[Serge Huber]

Here's my +1 (non-binding)

Also I have removed the MD5 from the artifacts (thanks for catching that Henk)

Regards,
  Serge...

On Thu, Jul 12, 2018 at 11:49 AM Henk P. Penning  wrote:
>
> On Thu, 12 Jul 2018, Serge Huber wrote:
>
> > Date: Thu, 12 Jul 2018 11:16:20 +0200
> > From: Serge Huber 
> > To: general@incubator.apache.org
> > Subject: [VOTE] Apache Unomi 1.3.0-incubating release
>
> > We kindly ask the IPMC to vote on this release.
> >
> > The artifacts to be voted on are located at:
> > https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating
>
>Please don't publish .md5's anymore ; please remove them.
>
>This does not affect the VOTE ; please continue ...
>
>Regards,
>
>Henk Penning
>
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Apache Unomi 1.3.0-incubating release

[Serge Huber]

Hi all,

The Unomi community has voted again for the release of Apache Unomi 1.3.0
(incubating). This release contains a lot of improvements, notable
migration to Apache Karaf 4 as well as the introduction of consent
management to help projects with GDPR compliancy.

The vote thread can be found at :
http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAWkFsE%2BTNfzcpMW8QavcWr6Bc8Zm35RTR-tzsf%3D%3DBYBVw%40mail.gmail.com%3E

and the result is at:
http://mail-archives.apache.org/mod_mbox/unomi-dev/201807.mbox/%3CCACR6SAXYELTHhWwWo8TWzupzGkSpzJ-nOngqxawheQBa%2BuZ6-g%40mail.gmail.com%3E

We kindly ask the IPMC to vote on this release.

The artifacts to be voted on are located at:
https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating
Source distribution is here :
https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip

With signature :
https://dist.apache.org/repos/dist/dev/incubator/unomi/1.3.0-incubating/unomi-1.3.0-incubating-src.zip.asc

The keys used to sign the released artifacts can be found in :
https://dist.apache.org/repos/dist/release/incubator/unomi/KEYS

The tag is at:
*https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.3.0-incubating
*
( 4fa32f793d21f1613312a575aa72f84e44804f84 )

This vote will be open for at least 72 hours, or until the necessary number
of votes (3 +1) is reached.

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

Regards,
  Serge...

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Unomi 1.2.0-incubating Release

[Serge Huber]

The Apache Unomi team would like to announce the release of Apache

Unomi 1.2.0-incubating.

Release notes are here:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220=12338361

Apache Unomi (incubating) is a Java Open Source customer data platform, a
Java server designed to manage customers, leads and visitors’ data and help
personalize customers’ experiences.

More details regarding Apache Unomi (incubating) can be found here:

http://unomi.incubator.apache.org/

The release artifacts can be downloaded here:

https://dist.apache.org/repos/dist/release/incubator/unomi/1.2.0-incubating/

All JIRAs completed for this release are tagged with 'FixVersion =

1.2.0-incubating'; the JIRA release notes can be found here:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220=12338361

Thanks!

The Apache Unomi Team

DISCLAIMER

Apache Unomi (incubating) is an effort undergoing incubation at the

Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.

Incubation is required of all newly accepted projects until a further

review indicates that the infrastructure, communications, and decision

making process have stabilized in a manner consistent with other successful

ASF projects. While incubation status is not necessarily a reflection of

the completeness or stability of the code, it does indicate that the

project has yet to be fully endorsed by the ASF.

[RESULT][VOTE] Release Apache Unomi 1.2.0 (incubating)

[Serge Huber]

Hi all,

The IPMC has voted for Unomi 1.2.0-incubating release. Here's the vote
summary :

3 binding votes +1 :
- Steve Blackmon
- John D. Ament
- Jean-Baptiste Onofré

No 0 or -1.

Vote thread can be found here :

http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCACR6SAW1pY7MCZCg_Z4GSycySe4LH%2Bm%2Bck5x%3Du2J7d-56xeMYw%40mail.gmail.com%3E

Thank you for your votes and reviews ! I will now complete the release
process.

Regards,
  Serge Huber.

Re: [VOTE] Apache Unomi 1.2.0-incubating release

[Serge Huber]

Thanks all, we have enough votes now I will close the vote.

Regards,
  Serge...

Serge Huber
CTO & Co-Founder
T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
jahia.com <http://www.jahia.com/>
SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber> | TWITTER
<https://twitter.com/sergehuber> | VCARD
<http://www.jahia.com/vcard/HuberSerge.vcf>


> JOIN OUR COMMUNITY <http://www.jahia.com/> to evaluate, get trained and
to discover why Jahia is a leading User Experience Platform (UXP) for
Digital Transformation.

On Wed, Sep 27, 2017 at 2:05 PM, John D. Ament <johndam...@apache.org>
wrote:

> Here's my +1
>
> On Wed, Sep 27, 2017 at 3:42 AM Serge Huber <shu...@jahia.com> wrote:
>
> > Hi all,
> >
> > If we could just get one more binding vote this would be great so we
> could
> > have the minimum quorum for the release.
> >
> > Thanks for your help,
> > Regards,
> >   Serge...
> >
> > Hello Steve,
> >
> > >
> > > Thanks for your vote and validations.
> > >
> > > Sorry I missed that problem. As you voted +1 I take it this is not
> > blocker
> > > for the release ? (we could indicate this on the download page for the
> > > source for example ?).
> > >
> > > I have created the following ticket to track the issue and fix it for
> the
> > > next release : https://issues.apache.org/jira/browse/UNOMI-125
> > >
> > > Regards,
> > >   Serge...
> > >
> > >
> > > Serge Huber
> > > CTO & Co-Founder
> > > T +41 22 361 3424 <+41%2022%20361%2034%2024> <+41%2022%20361%2034%2
> > <https://maps.google.com/?q=%252022%2520361%252034%252;
> entry=gmail=g>
> > 024>
> > > 9 route des Jeunes | 1227 Acacias | Switzerland
> > > jahia.com <http://www.jahia.com/>
> > > SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber> | TWITTER
> > > <https://twitter.com/sergehuber> | VCARD
> > > <http://www.jahia.com/vcard/HuberSerge.vcf>
> > >
> > >
> > > > JOIN OUR COMMUNITY <http://www.jahia.com/> to evaluate, get trained
> > and
> > > to discover why Jahia is a leading User Experience Platform (UXP) for
> > > Digital Transformation.
> > >
> > > On Mon, Sep 25, 2017 at 7:13 PM, Steve Blackmon <sblack...@apache.org>
> > > wrote:
> > >
> > >>  +1 (binding)
> > >>
> > >> - verified checksums
> > >> - verified signatures
> > >> - verified source builds
> > >> - verified tests passing
> > >>
> > >> P.S.
> > >> I had to add -Drat.skip=true to ‘mvn clean install’ because by the
> time
> > >> rat
> > >> startup up, a non-compliant DEPENDENCIES file had been added.
> > >> A few ways to fix this - bind rat plugin only to validate phase,
> and/or
> > >> add
> > >> DEPENDENCIES to the rat black-list.
> > >>
> > >>
> > >>
> > >> On Sep 25, 2017 at 8:55 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
> > wrote:
> > >>
> > >>
> > >> +1 (binding)
> > >>
> > >> Gently reminder to the other IPMC, if you can have time to review and
> > vote
> > >> for
> > >> this release.
> > >>
> > >> Thanks !
> > >> Regards
> > >> JB
> > >>
> > >> On 09/19/2017 01:47 PM, Serge Huber wrote:
> > >>
> > >> Hi all,
> > >>
> > >> The Unomi community has voted for the release of Apache Unomi 1.2.0
> > >>
> > >> (incubating).
> > >>
> > >> The vote thread can be found at :
> > >>
> > >> http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev
> > >> /201709.mbox/%3CCACR6SAW9HPLwi%3DcPhAnxUxmFTXThn6RH8BsUwGpYO
> > >> qcqyEWvhA%40mail.gmail.com%3E
> > >>
> > >> and the result is at:
> > >>
> > >> http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev
> > >> /201709.mbox/%3CCACR6SAXuKT2EtauNC0oBfV%3DS2SVV-TMrAR3nRN2P7%
> 3DbLxMWAXA%
> > >> 40mail.gmail.com%3E
> > >>
> > >> We ask the IPMC to vote on this release.
> > >>
> > >> The artifacts to be voted on are located at:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.
> 0-incubating
> > >>
> > &

Re: [VOTE] Apache Unomi 1.2.0-incubating release

[Serge Huber]

Hi all,

If we could just get one more binding vote this would be great so we could
have the minimum quorum for the release.

Thanks for your help,
Regards,
  Serge...

Hello Steve,

>
> Thanks for your vote and validations.
>
> Sorry I missed that problem. As you voted +1 I take it this is not blocker
> for the release ? (we could indicate this on the download page for the
> source for example ?).
>
> I have created the following ticket to track the issue and fix it for the
> next release : https://issues.apache.org/jira/browse/UNOMI-125
>
> Regards,
>   Serge...
>
>
> Serge Huber
> CTO & Co-Founder
> T +41 22 361 3424 <+41%2022%20361%2034%2024>
> 9 route des Jeunes | 1227 Acacias | Switzerland
> jahia.com <http://www.jahia.com/>
> SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber> | TWITTER
> <https://twitter.com/sergehuber> | VCARD
> <http://www.jahia.com/vcard/HuberSerge.vcf>
>
>
> > JOIN OUR COMMUNITY <http://www.jahia.com/> to evaluate, get trained and
> to discover why Jahia is a leading User Experience Platform (UXP) for
> Digital Transformation.
>
> On Mon, Sep 25, 2017 at 7:13 PM, Steve Blackmon <sblack...@apache.org>
> wrote:
>
>>  +1 (binding)
>>
>> - verified checksums
>> - verified signatures
>> - verified source builds
>> - verified tests passing
>>
>> P.S.
>> I had to add -Drat.skip=true to ‘mvn clean install’ because by the time
>> rat
>> startup up, a non-compliant DEPENDENCIES file had been added.
>> A few ways to fix this - bind rat plugin only to validate phase, and/or
>> add
>> DEPENDENCIES to the rat black-list.
>>
>>
>>
>> On Sep 25, 2017 at 8:55 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
>>
>>
>> +1 (binding)
>>
>> Gently reminder to the other IPMC, if you can have time to review and vote
>> for
>> this release.
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 09/19/2017 01:47 PM, Serge Huber wrote:
>>
>> Hi all,
>>
>> The Unomi community has voted for the release of Apache Unomi 1.2.0
>>
>> (incubating).
>>
>> The vote thread can be found at :
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev
>> /201709.mbox/%3CCACR6SAW9HPLwi%3DcPhAnxUxmFTXThn6RH8BsUwGpYO
>> qcqyEWvhA%40mail.gmail.com%3E
>>
>> and the result is at:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev
>> /201709.mbox/%3CCACR6SAXuKT2EtauNC0oBfV%3DS2SVV-TMrAR3nRN2P7%3DbLxMWAXA%
>> 40mail.gmail.com%3E
>>
>> We ask the IPMC to vote on this release.
>>
>> The artifacts to be voted on are located at:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.0-incubating
>>
>> Source distribution is here :
>>
>> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.0
>> -incubating/unomi-1.2.0-incubating-src.zip
>>
>> With signature :
>>
>> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.0
>> -incubating/unomi-1.2.0-incubating-src.zip.asc
>>
>> The keys used to sign the released artifacts can be found in :
>>
>> https://dist.apache.org/repos/dist/release/incubator/unomi/KEYS
>>
>> The tag is at:
>>
>> *
>> https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.gi
>> t;a=tag;h=refs/tags/unomi-root-1.2.0-incubating
>>
>> <
>> https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.gi
>> t;a=tag;h=refs/tags/unomi-root-1.2.0-incubating
>>
>> *
>>
>>
>> ( 42e4fa3d6912f35c791c790a71ccb4a96dce01fd )
>>
>> This vote will be open for at least 72 hours, or until the necessary
>> number
>>
>> of votes (3 +1) is reached.
>>
>> [ ] +1 Approve the release
>>
>> [ ] -1 Don't approve the release (please provide specific comments)
>>
>>
>> Thanks for your help,
>>
>> Regards,
>>
>> Serge
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>

Re: [VOTE] Apache Unomi 1.2.0-incubating release

[Serge Huber]

Hello Steve,

Thanks for your vote and validations.

Sorry I missed that problem. As you voted +1 I take it this is not blocker
for the release ? (we could indicate this on the download page for the
source for example ?).

I have created the following ticket to track the issue and fix it for the
next release : https://issues.apache.org/jira/browse/UNOMI-125

Regards,
  Serge...


Serge Huber
CTO & Co-Founder
T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
jahia.com <http://www.jahia.com/>
SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber> | TWITTER
<https://twitter.com/sergehuber> | VCARD
<http://www.jahia.com/vcard/HuberSerge.vcf>


> JOIN OUR COMMUNITY <http://www.jahia.com/> to evaluate, get trained and
to discover why Jahia is a leading User Experience Platform (UXP) for
Digital Transformation.

On Mon, Sep 25, 2017 at 7:13 PM, Steve Blackmon <sblack...@apache.org>
wrote:

>  +1 (binding)
>
> - verified checksums
> - verified signatures
> - verified source builds
> - verified tests passing
>
> P.S.
> I had to add -Drat.skip=true to ‘mvn clean install’ because by the time rat
> startup up, a non-compliant DEPENDENCIES file had been added.
> A few ways to fix this - bind rat plugin only to validate phase, and/or add
> DEPENDENCIES to the rat black-list.
>
>
>
> On Sep 25, 2017 at 8:55 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
>
>
> +1 (binding)
>
> Gently reminder to the other IPMC, if you can have time to review and vote
> for
> this release.
>
> Thanks !
> Regards
> JB
>
> On 09/19/2017 01:47 PM, Serge Huber wrote:
>
> Hi all,
>
> The Unomi community has voted for the release of Apache Unomi 1.2.0
>
> (incubating).
>
> The vote thread can be found at :
>
> http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev/201709.mbox/%
> 3CCACR6SAW9HPLwi%3DcPhAnxUxmFTXThn6RH8BsUwGpYOq
> cqyEWvhA%40mail.gmail.com%3E
>
> and the result is at:
>
> http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev/201709.mbox/%
> 3CCACR6SAXuKT2EtauNC0oBfV%3DS2SVV-TMrAR3nRN2P7%
> 3DbLxMWAXA%40mail.gmail.com%3E
>
> We ask the IPMC to vote on this release.
>
> The artifacts to be voted on are located at:
>
> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.0-incubating
>
> Source distribution is here :
>
> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.
> 0-incubating/unomi-1.2.0-incubating-src.zip
>
> With signature :
>
> https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.
> 0-incubating/unomi-1.2.0-incubating-src.zip.asc
>
> The keys used to sign the released artifacts can be found in :
>
> https://dist.apache.org/repos/dist/release/incubator/unomi/KEYS
>
> The tag is at:
>
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.
> git;a=tag;h=refs/tags/unomi-root-1.2.0-incubating
>
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.
> git;a=tag;h=refs/tags/unomi-root-1.2.0-incubating
>
> *
>
>
> ( 42e4fa3d6912f35c791c790a71ccb4a96dce01fd )
>
> This vote will be open for at least 72 hours, or until the necessary number
>
> of votes (3 +1) is reached.
>
> [ ] +1 Approve the release
>
> [ ] -1 Don't approve the release (please provide specific comments)
>
>
> Thanks for your help,
>
> Regards,
>
> Serge
>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

[VOTE] Apache Unomi 1.2.0-incubating release

[Serge Huber]

Hi all,

The Unomi community has voted for the release of Apache Unomi 1.2.0

(incubating).

The vote thread can be found at :

http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev/201709.mbox/%3CCACR6SAW9HPLwi%3DcPhAnxUxmFTXThn6RH8BsUwGpYOqcqyEWvhA%40mail.gmail.com%3E

and the result is at:

http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev/201709.mbox/%3CCACR6SAXuKT2EtauNC0oBfV%3DS2SVV-TMrAR3nRN2P7%3DbLxMWAXA%40mail.gmail.com%3E

We ask the IPMC to vote on this release.

The artifacts to be voted on are located at:

https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.0-incubating

Source distribution is here :

https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.0-incubating/unomi-1.2.0-incubating-src.zip

With signature :

https://dist.apache.org/repos/dist/dev/incubator/unomi/1.2.0-incubating/unomi-1.2.0-incubating-src.zip.asc

The keys used to sign the released artifacts can be found in :

https://dist.apache.org/repos/dist/release/incubator/unomi/KEYS

The tag is at:

*
https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.2.0-incubating

<
https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=tag;h=refs/tags/unomi-root-1.2.0-incubating
>*

( 42e4fa3d6912f35c791c790a71ccb4a96dce01fd )

This vote will be open for at least 72 hours, or until the necessary number

of votes (3 +1) is reached.

[ ] +1 Approve the release

[ ] -1 Don't approve the release (please provide specific comments)


Thanks for your help,

Regards,

  Serge

Re: [VOTE] Release Apache Unomi 1.0.0-incubating (take 4)

[Serge Huber]

> On 16 févr. 2016, at 07:10, Justin Mclean  wrote:
> 
> I got this error when compiling - looks like a path may be wrong:
> [INFO] Apache Unomi :: Distribution Package ... FAILURE [  0.568 
> s]
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (copy-karaf) on project 
> unomi: An Ant BuildException has occured: 
> /Users/justinmclean/Downloads/ApacheUnomi/unomi-1.0.0-incubating/package/target/assembly/elasticsearch-1.6.2/lib/sigar
>  does not exist.
> 
> Everything else compiled fine it just looks like creating the distribution 
> package failed, I’m assuming this is not a big issue.
> 
> I think the path should be??
> ./unomi-1.0.0-incubating/package/target/assembly/lib/sigar/

Hello Justin,

I’m having trouble reproducing this from the TAR.GZ and ZIP source packages. I 
tested both on my Mac and a Windows machine and couldn’t reproduce this 
problem. Did you use the links that JB sent out or others ?

cheers,
  Serge… 

The src distributions are located:
* 
https://repository.apache.org/content/repositories/orgapacheunomi-1004/org/apache/unomi/unomi/1.0.0-incubating/unomi-1.0.0-incubating-src.tar.gz
 

* 
https://repository.apache.org/content/repositories/orgapacheunomi-1004/org/apache/unomi/unomi/1.0.0-incubating/unomi-1.0.0-incubating-src.zip
 

Re: [VOTE] Release Apache Unomi 1.0.0-incubating (take 4)

[Serge Huber]

Hi Justin,

Thank you so much for this detailed testing and report.

Normally we should only have dual licensed GPL/CDDL unless I have missed 
something. We are working on a plugin legal-maven-plugin that actually does 
recursively go down into embedded JARs to make sure we collect everything but 
it’s a work in progress.

Honestly I would have never thought this process was so complex nor so long, 
and I truly wonder how many projects at Apache actually go through all of this 
(my guess is not many apart from yours of course :)). 

That compilation issue is strange, I tested this many times locally so maybe 
something is depending on the environment.

cheers,
  Serge… 

> On 16 févr. 2016, at 07:54, Justin Mclean  wrote:
> 
> HI,
> 
>> thanks for this awesome review !
> 
> No problem, binaries with than many jars are hard to get right. Hopefully 
> none of the jars with jars inside than have more jars inside them :-)
> 
> I did’t take a huge amount of care so made of made a mistake or two - just 
> trying to find the obvious issues. I think some of the GPL stuff I pointed 
> out may actually be GPL/CDDL dual licensed (which is OK in a binary) but 
> always good to double check.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Confusion over NOTICE vs LICENSE files

[Serge Huber]

As an engineer that's not an expert at legal stuff I was wondering if there 
isn't a way to solve this with tooling ?

I've seen a few Maven plugins out there but they don't seem to work properly, 
especially for binary distributions.

I've started a plugin myself here [1] but it's still in heavy development. 
Basically it's aimed at help building license and notice files for binary 
distributions by scanning all the jars in a directory recursively, trying to 
find notice, license or Pom.xml files and I was even then looking at connecting 
it to scm systems or using search.maven.org to find project metadata.

But better conventions on the format and content of the files that would make 
automated processing easier would also be a great thing, but that might be too 
late already.

Cheers,
  Serge

[1] https://github.com/sergehuber/Legal-Maven-Plugin


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.

> Le 3 févr. 2016 à 19:54, Justin Mclean <jus...@classsoftware.com> a écrit :
> 
> HI,
> 
>> [4] https://nifi.apache.org/licensing-guide.html 
>> <https://nifi.apache.org/licensing-guide.html>
> BTW nicely put together, it's well worth a read and clearly explains quite 
> tricky LICENSE and NOTICE issues.
> 
> Thanks,
> Justin

Re: [DISCUSS] Apache Dataflow Incubator Proposal

[Serge Huber]

On a lighter side… 

Just to mess with you guys if you’re looking at an alternative name I might 
suggest : 

Apache Arrow

I thought of this because I was thinking of how an arrow flows through the air, 
might be deviated, and it also associates with something sharp, dangerous and 
fast :) And of course an Apache would use an arrow more than a beam :)

But maybe Beam is more appropriate, but I just thought I’d put this out there.

cheers,
  Serge… 

> On 28 janv. 2016, at 11:01, Bertrand Delacretaz  
> wrote:
> 
> On Wed, Jan 27, 2016 at 6:22 PM, James Malone
>  wrote:
>> ...To that end, the name we propose to use is:
>> 
>> Apache Beam
> 
> The name sounds good to me and it's indeed a good idea to set it now.
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache Dataflow Incubator Proposal

[Serge Huber]

Please ignore my last message, I missed the fact that a project was already 
existing with the name “Arrow”.

cheers,
  Serge… 


> On 28 janv. 2016, at 11:01, Bertrand Delacretaz  
> wrote:
> 
> On Wed, Jan 27, 2016 at 6:22 PM, James Malone
>  wrote:
>> ...To that end, the name we propose to use is:
>> 
>> Apache Beam
> 
> The name sounds good to me and it's indeed a good idea to set it now.
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Unomi 1.0.0-incubating

[Serge Huber]

Hello Niall (and Daniel),

Thanks for spending time on checking this. Wow that email from Roy seemed quite 
aggressive in tone, but I have heard this before and should have remembered it. 
I also feel partly responsible for this because I setup the initial build 
project and didn’t do this initially.

JB has been really working hard on helping this project getting off the ground 
and it’s a shame this was caught so late (but it’s good that it was caught 
nonetheless). I’d like to keep him as motivated as possible so I take the 
opportunity to thank him here for all his hard work.

What is the best next step now ? Retract the release and build a source package 
and resubmit that for approval ? Wait for the vote to complete and get 
rejected, build a source package and re-open a vote for approval ?

Regards,
  Serge… 

> On 28 déc. 2015, at 21:28, Niall Pemberton  wrote:
> 
> On Mon, Dec 28, 2015 at 8:15 PM, Jean-Baptiste Onofré 
> wrote:
> 
>> My bad, I forgot to include unomi--src.[tar.gz|zip] artifact as I do
>> for other project.
>> 
>> Anyway, the source are on git based on the tag:
>> 
>> https://github.com/apache/incubator-unomi/tree/unomi-root-1.0.0-incubating
>> 
>> (I paste github mirror there as it's easier to read).
>> 
>> Let see what the others think about that. If we consider as blocker, I
>> will include a source artifacts.
>> 
> 
> "The Apache Software Foundation exists to create open source software.
> Thus, the fundamental requirement for a release is that it consist of the
> necessary source code to build the project."
> 
> See http://www.apache.org/dev/release-publishing.html#valid
> 
> So, yes its a complete blocker.
> 
> Also worth reading: http://s.apache.org/srcrel
> 
> Niall
> 
> 
>> 
>> Anyway, I will add the source artifacts for 1.0.1-incubating release.
>> 
>> Regards
>> JB
>> 
>> 
>> On 12/28/2015 09:05 PM, Daniel Gruno wrote:
>> 
>>> On 12/28/2015 08:56 PM, Jean-Baptiste Onofré wrote:
>>> 
 The unomi-1.0.0-incubating.tar.gz (or zip) is the unomi distribution.
 
 It assembles all "binaries" and provide ready to run runtime.
 
 Do you want a description of each artifact ? I can prepare that if it
 helps.
 
>>> 
>>> I'd prefer what other projects produce - a source release that contains
>>> source only, no binary applications. I cannot vote on a binary release.
>>> 
>>> I'll refer to the Incubator release draft[1] which reasons:
>>> 
>>> "Each Apache release must contain a source package. This package may not
>>> contain compiled components (such as "jar" files) because compiled
>>> components are not open source, even if they were built from open source."
>>> 
>>> This also begs the question of how you managed to get approval in the
>>> podling to do this release if you have not voted on a source package.
>>> One would think this is a do-over with a source package to be voted on
>>> in the podling and then passed to the IPMC for approval.
>>> 
>>> With regards,
>>> Daniel.
>>> 
>>> 
>>> [1] http://incubator.apache.org/guides/releasemanagement.html#check-list
>>> 
>>> 
 Regards
 JB
 
 On 12/28/2015 07:48 PM, Daniel Gruno wrote:
 
> Thanks Jean-Baptiste,
> howeverthere are no less than 215 java binaries in that RC - I
> couldn't possibly vote +1 on something I don't know what is, and I'm not
> about to go reverse engineer it to find out.
> 
> Other than that it seems okay, but consider this a tentative -1.
> 
> With regards,
> Daniel.
> 
> On 12/28/2015 07:40 PM, Jean-Baptiste Onofré wrote:
> 
>> Hi Daniel,
>> 
>> sorry, it's on the staging repo:
>> 
>> 
>> https://repository.apache.org/content/repositories/orgapacheunomi-1002/org/apache/unomi/unomi/1.0.0-incubating/
>> 
>> 
>> 
>> I will upload to dist.apache.org when the release vote will pass.
>> 
>> Regards
>> JB
>> 
>> On 12/28/2015 07:31 PM, Daniel Gruno wrote:
>> 
>>> On 12/28/2015 07:26 PM, Jean-Baptiste Onofré wrote:
>>> 
 Hi all,
 
 I submit Apache Unomi 1.0.0-incubating release to your vote.
 
 A vote was held on developer mailing list and it passed with 7 +1s.
 
 Vote thread:
 
 http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev/201512.mbox/%3c5679aace.1080...@nanthrax.net%3E
 
 
 
 Result thread:
 
 http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev/201512.mbox/%3C5680CAAF.7080304%40nanthrax.net%3E
 
 
 
 
 The vote is open for 72 hours:
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 Thanks,
 Regards
 JB
 
>>> 
>>> Where are the release artifacts located? I'd like to do my usual
>>> tests,
>>> but I can't 

Re: [VOTE] Release Apache Unomi 1.0.0-incubating

[Serge Huber]

Hi John,

> Le 29 déc. 2015 à 00:24, John D. Ament <johndam...@apache.org> a écrit :
> 
> Hi Serge,
> 
>> On Mon, Dec 28, 2015 at 5:58 PM Serge Huber <shu...@jahia.com> wrote:
>> 
>> Hello Niall (and Daniel),
>> 
>> Thanks for spending time on checking this. Wow that email from Roy seemed
>> quite aggressive in tone, but I have heard this before and should have
>> remembered it. I also feel partly responsible for this because I setup the
>> initial build project and didn’t do this initially.
> I'm not sure who Roy is.  Maybe you could share a link to some email?
> Hopefully we're not coming across too tough here :-(

I was talking about this email from Roy Fielding that Niall referenced here: 
http://s.apache.org/srcrel but it's not really important.

> 
> 
>> JB has been really working hard on helping this project getting off the
>> ground and it’s a shame this was caught so late (but it’s good that it was
>> caught nonetheless). I’d like to keep him as motivated as possible so I
>> take the opportunity to thank him here for all his hard work.
> 
> JB's a great guy to have on any project.

+1 :)

> 
> 
>> 
>> What is the best next step now ? Retract the release and build a source
>> package and resubmit that for approval ? Wait for the vote to complete and
>> get rejected, build a source package and re-open a vote for approval ?
> 
> You kind of have to in this case.  You don't have a valid release.  We vote
> on the source release, the binary release is a convenience for end users so
> they don't need to compile the sources.
> 
> 
>> 
>> Regards,
>>  Serge…
>> 
>>>> On 28 déc. 2015, at 21:28, Niall Pemberton <niall.pember...@gmail.com>
>>> wrote:
>>> 
>>> On Mon, Dec 28, 2015 at 8:15 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
>>> wrote:
>>> 
>>>> My bad, I forgot to include unomi--src.[tar.gz|zip] artifact as I do
>>>> for other project.
>>>> 
>>>> Anyway, the source are on git based on the tag:
>> https://github.com/apache/incubator-unomi/tree/unomi-root-1.0.0-incubating
>>>> 
>>>> (I paste github mirror there as it's easier to read).
>>>> 
>>>> Let see what the others think about that. If we consider as blocker, I
>>>> will include a source artifacts.
>>> 
>>> "The Apache Software Foundation exists to create open source software.
>>> Thus, the fundamental requirement for a release is that it consist of the
>>> necessary source code to build the project."
>>> 
>>> See http://www.apache.org/dev/release-publishing.html#valid
>>> 
>>> So, yes its a complete blocker.
>>> 
>>> Also worth reading: http://s.apache.org/srcrel
>>> 
>>> Niall
>>> 
>>> 
>>>> 
>>>> Anyway, I will add the source artifacts for 1.0.1-incubating release.
>>>> 
>>>> Regards
>>>> JB
>>>> 
>>>> 
>>>>> On 12/28/2015 09:05 PM, Daniel Gruno wrote:
>>>>> 
>>>>>> On 12/28/2015 08:56 PM, Jean-Baptiste Onofré wrote:
>>>>>> 
>>>>>> The unomi-1.0.0-incubating.tar.gz (or zip) is the unomi distribution.
>>>>>> 
>>>>>> It assembles all "binaries" and provide ready to run runtime.
>>>>>> 
>>>>>> Do you want a description of each artifact ? I can prepare that if it
>>>>>> helps.
>>>>> 
>>>>> I'd prefer what other projects produce - a source release that contains
>>>>> source only, no binary applications. I cannot vote on a binary release.
>>>>> 
>>>>> I'll refer to the Incubator release draft[1] which reasons:
>>>>> 
>>>>> "Each Apache release must contain a source package. This package may
>> not
>>>>> contain compiled components (such as "jar" files) because compiled
>>>>> components are not open source, even if they were built from open
>> source."
>>>>> 
>>>>> This also begs the question of how you managed to get approval in the
>>>>> podling to do this release if you have not voted on a source package.
>>>>> One would think this is a do-over with a source package to be voted on
>>>>> in the podling and then passed to the IPMC for approval.
>>>>> 
>>>>> With regards,
>>>>> Daniel.
>>>>>

Re: [RESULT][VOTE] Accept Unomi into the Apache Incubator

[Serge Huber]

Yes the resources have been created. We’ve been hard at work on creating the 
web site and working on the codebase to get it imported asap. 

Regards,
  Serge… 

> On 20 nov. 2015, at 15:42, Bertrand Delacretaz  wrote:
> 
> Hi,
> 
> On Mon, Oct 5, 2015 at 4:47 AM, Jean-Baptiste Onofré  
> wrote:
>> ...I will continue with the bootstrap process to bring Unomi into Apache
>> incubator
> 
> Unless I missed something I haven't seen more news about this here,
> but it looks like the Unomi lists have been created and discussions
> are now starting there:
> 
> http://mail-archives.apache.org/mod_mbox/incubator-unomi-dev/
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

[Serge Huber]

I’ll get right on creating one for Unomi, I’ve been wanting to use this since 
you first told me about it Bertrand :) 

cheers,
  Serge… 

> On 19 nov. 2015, at 20:33, Bertrand Delacretaz  wrote:
> 
> Hi,
> 
> On Thu, Oct 15, 2015 at 5:46 AM, Bertrand Delacretaz
>  wrote:
>> FYI I have started an experiment at
>> https://github.com/apache/incubator-groovy/blob/master/MATURITY.adoc ,
>> using our maturity model to evaluate Groovy...
> 
> Groovy graduated now and doesn't have a good place to keep that
> document, so I'm pasting it below in case other podlings want to use
> it as an example.
> 
> It will also stay at
> 
> https://github.com/apache/incubator-groovy/blob/576b3c5d6a7022ac4a8df1ef118666456ce627fb/MATURITY.adoc
> 
> -Bertrand
> 
>  GROOVY MATURITY *
> 
> = Groovy Podling Maturity Assessment
> 
> == Overview
> 
> This is an assessment of the Groovy podling's maturity, meant to help inform
> the decision (of the mentors, community, Incubator PMC and ASF Board of
> Directors) to graduate it as a top-level Apache project.
> 
> It is based on the ASF project maturity model at
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> 
> Maintaining such a file is a new, experimental idea as part of the continuous
> improvement of the ASF incubation process. Groovy is the first podling where
> that happens.
> 
> == Status of this document
> All open items resolved, ready for PPMC approval voting.
> 
> == Overall assessment
> All the below items are marked OK, Groovy looks ready to graduate,
> discussions and votes
> are ongoing on the project's dev list as I write this (October 2015).
> 
> == Maturity model assessment
> Mentors and community members are encouraged to contribute to this
> and comment on it.
> 
> === Code
> 
>  CD10
> _The project produces Open Source software, for distribution to the
> public at no charge._
> 
> OK: of course.
> 
>  CD20
> _The project's code is easily discoverable and publicly accessible._
> 
> OK: http://groovy-lang.org/ (see CO10) includes a "fork me on Github" banner.
> 
>  CD30
> _The code can be built in a reproducible way using widely available
> standard tools._
> 
> OK: the build uses Gradle and continuous integration is used.
> 
>  CD40
> _The full history of the project's code is available via a source code
> control system, in a way that allows any released version to be
> recreated._
> 
> OK: Using Git, main repository at
> https://git-wip-us.apache.org/repos/asf/incubator-groovy.git, releases
> are cut
> from that repository.
> 
>  CD50
> _The provenance of each line of code is established via the source
> code control system, in a reliable way based on strong authentication
> of the committer.
> When third-party contributions are committed, commit messages provide
> reliable information about the code provenance._
> 
> OK, see CD40
> 
> === Licenses and Copyright
> 
>  LC10
> _The code is released under the Apache License, version 2._0._
> 
> OK, LICENSE file has been accepted in release votes.
> 
>  LC20
> _Libraries that are mandatory dependencies of the project's code do
> not create more restrictions than the Apache License does._
> 
> OK: The list of dependencies at
> https://wiki.apache.org/incubator/GroovyProposal has been verified
> when entering incubation.
> 
> The current dependency licenses (including build, runtime and optional
> dependencies) are found at
> https://github.com/apache/incubator-groovy/tree/master/licenses
> 
> Assembling the licenses depending on the artifacts is done here:
> https://github.com/apache/incubator-groovy/blob/master/gradle/assemble.gradle
> so that the various artifacts get their correct sets of licenses.
> 
> Release reviews have not shown any incompatible licenses.
> 
>  LC30
> _The libraries mentioned in LC20 are available as Open Source software._
> 
> OK, see LC20
> 
>  LC40
> _Committers are bound by an Individual Contributor Agreement (the
> "Apache iCLA") that defines which code they are allowed to commit and
> how they need to identify code that is not their own._
> 
> OK, all committers have iCLAs on file.
> 
>  LC50
> _The copyright ownership of everything that the project produces is
> clearly defined and documented._
> 
> OK, obvious for an ASF project.
> 
> === Releases
> 
>  RE10
> _Releases consist of source code, distributed using standard and open
> archive formats that are expected to stay readable in the long term._
> 
> OK, verified in release votes.
> 
>  RE20
> _Releases are approved by the project's PMC (see CS10), in order to
> make them an act of the Foundation._
> 
> OK, releases have been voted by the Incubator PMC.
> 
>  RE30
> _Releases are signed and/or distributed along with digests that can be
> reliably used to validate the downloaded archives._
> 
> OK, verified in release votes.
> 
>  RE40
> _Convenience binaries can be distributed alongside source 

Re: [RESULT][VOTE] Accept Unomi into the Apache Incubator

[Serge Huber]

Thanks a lot JB for helping me through this process. It's still a little
new to me :)

cheers,
  Serge...

- -- --- -=[ shuber at jahia dot com ]= --- -- -
CTO & Co-founder - Jahia Solutions Group, 9 Routes de Jeunes, 1227 Acacias,
Switzerland
twitter: @sergehuber <https://twitter.com/sergehuber>

Jahia is a leading open source User eXperience Platform (UXP) vendor,
relentlessly working at transforming a siloed industry into a user-driven
one, beyond technology constraints - http://www.jahia.com


On Mon, Oct 5, 2015 at 10:47 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi all,
>
> this vote passed with the following result:
>
> +1 (binding): Jean-Baptiste Onofré, Bertrand Delacretaz, Seetharam
> Venkatesh, Chris Mattmann, John D. Ament, Roman Shaposhnik, Hadrian
> Zbarcea, Henry Saputra
> +1 (non-binding): Serge Huber, Raul Kripalani
> 0: none
> -1: none
>
> Thanks everyone for participating and warm welcome for the Unomi project
> proposal.
>
> I will continue with the bootstrap process to bring Unomi into Apache
> incubator.
>
> Thanks again !
>
> Regards
> JB
>
>
> On 09/23/2015 11:14 AM, Jean-Baptiste Onofré wrote:
>
>> Hi all,
>>
>> following the discussion about Unomi, I would like to call a vote for
>> accepting Unomi as a new incubator project.
>>
>> The proposal text is included below, and available on the wiki:
>> http://wiki.apache.org/incubator/UnomiProposal
>>
>> The discussion thread about Unomi is available here:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C36A4090C-7444-4A20-8C85-3C7B990D9502%40jahia.com%3E
>>
>>
>> The vote is open for 72 hours:
>>
>> [ ] +1 accept Unomi in the Incubator
>> [ ] ±0
>> [ ] -1 (please give reason)
>>
>> Thanks,
>> Regards
>> JB
>> --
>>
>> = Apache Unomi incubation proposal =
>> == Abstract ==
>> 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.
>>
>> == Proposal ==
>> The server is a data management platform that provides real-time user
>> profile and event storage as well as a rule engine and fully featured
>> REST+JSON interfaces which make integration with very different systems
>> easier.
>>
>> One of the main objectives of this implementation is to be modular and
>> flexible enough to relatively easily build integration into systems such
>> as CMS, WCM, CRM or even ERP. Built using Apache Karaf and
>> ElasticSearch, it is designed to also be easily clusterable to address
>> high-traffic scenarios where lots of profile data will need to be
>> updated at a high frequency.
>>
>> == Background ==
>> Unomi was built from scratch to serve as a reference implementation for
>> the OASIS Context Server proposal. It has been developed by Jahia
>> Software.
>>
>> It initially served as a test-bed while working on the specifics of the
>> new proposal, to make sure that the concepts being discussed and decided
>> would make sense in an actual implementation. At the same time, Jahia,
>> one of the companies involved in the standardization work, needed a
>> basis to build their new Marketing Factory product, so it made a lot of
>> sense to start this way. Thanks to a lot of work done in the standard,
>> the implementation was produced relatively quickly and this made it
>> possible to build a commercial product on top of this implementation
>> that will be released in Winter 2015. This implies that the core of the
>> commercial product being proposed here will undergo a full set of QA
>> tests, including and scalability tests.
>>
>> Another important objective was to provide a platform that deals with
>> user data in an “ethical” way, in order to make the usage of personal
>> data more transparent and to improve privacy. Through the work in the
>> standard and this open source implementation, it is the hope of the
>> original designers that it will be easier for all users of this
>> technology to fully understand how the data is being used and what type
>> of control is exercised over it. A transparent usage of customer data
>> could become, in the near future, a key tool to keep customer loyalty.
>> Companies would then be able to leverage digital marketing frameworks
>> capabilities such as Unomi, but, as a fair - and quite possibly legally
>> mandatory - counterpart, should allow end users to understand the data
>&g

Re: [VOTE] Accept Unomi into the Apache Incubator

[Serge Huber]

Thanks everyone for your involvment, it is highly appreciated.

Looking forward to seeing you real soon now :)

Regards,
  Serge… 

ps : flying in tomorrow

> On 29 sept. 2015, at 13:45, Roman Shaposhnik  wrote:
> 
> On Tue, Sep 29, 2015 at 2:18 PM, Bertrand Delacretaz
>  wrote:
>> On Tue, Sep 29, 2015 at 12:56 PM, Jean-Baptiste Onofré  
>> wrote:
>>> ...Gently reminder, I "extend" the vote for 24 hours...
>> 
>> Why? It looks like we have 3 binding +1s, and the 72 hour period is over.
> 
> True, but at least it gave me a push to finally get the review/vote done ;-)
> 
> Thanks,
> Roman.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Unomi into the Apache Incubator

[Serge Huber]

gt; 
>> == Homogeneous Developers ==
>> While most of the initial committers are employed by Jahia, we have
>> already seen a healthy level of interest from our existing customers and
>> partners. We intend to convert that interest directly into participation
>> and will be investing in activities to recruit additional committers from
>> other companies.
>> 
>> == Reliance on Salaried Developers ==
>> Most of the contributors are paid to work in web marketing/web content
>> management space. While they might wander from their current employers,
>> they are unlikely to venture far from their core expertises and thus will
>> continue to be engaged with the project regardless of their current
>> employers.
>> 
>> == Relationships with Other Apache Products ==
>> As mentioned in the Alignment section, Unomi may consider various degrees
>> of integration and code exchange with Apache Karaf, Apache Mahout, Apache
>> Pistachio (incubating), and many others. We look forward to collaborating
>> with these communities as well as other communities under the Apache
>> umbrella.
>> 
>> == An Excessive Fascination with the Apache Brand ==
>> While we intend to leverage the Apache ‘branding’ when talking to other
>> projects as testament of our project’s ‘neutrality’, we have no plans for
>> making use of Apache brand in press releases nor posting billboards
>> advertising acceptance of Unomi into Apache Incubator.
>> 
>> == Interaction with the OASIS standard ==
>> In order to properly implement the standard and possibly use the feedback
>> from the implementation as a way to improve the specifications, currently
>> the co-chair of the technical committee is also the proposer on the Apache
>> proposal. This relationship makes it easy for communication between the two
>> works, and will hopefully grow as the community grows around both the
>> standard and the implementation. This is quite similar to the situation
>> with the Apache Chemistry project, that is an open source implementation of
>> the CMIS specification that is also an OASIS standard.
>> 
>> == Documentation ==
>> See documentation for the current state of the project documentation
>> available as part of the GitHub repository at
>> https://github.com/Jahia/unomi
>> 
>> == Initial Source ==
>> Jahia is releasing the source code for Unomi under the ASF license at
>> https://github.com/Jahia/unomi . We encourage ASF community members
>> interested in this proposal to download the source code, review and try out
>> the software.
>> 
>> == Source and Intellectual Property Submission Plan ==
>> As soon as Unomi is approved to join Apache Incubator, the source code
>> will be transitioned via the Software Grant Agreement onto ASF
>> infrastructure and in turn made available under the Apache License, version
>> 2.0. We know of no legal encumberments that would inhibit the transfer of
>> source code to the ASF.
>> 
>> == External Dependencies ==
>> Embedded dependencies (relocated):
>> 
>> * None
>> 
>> Runtime dependencies:
>> 
>> * apache-karaf
>> * pax-web
>> * apache-cxf
>> * slf4j
>> * org.apache.httpcomponents:httpclient-osgi
>> * org.apache.httpcomponents:httpcore-osgi
>> * org.apache.servicemix.bundles.jakarta-regexp
>> * pax-cdi
>> * javax.servlet-api
>> * jackson
>> * org.osgi.core
>> * commons-lang3
>> * commons-collections
>> * org.mvel:mvel2
>> * commons-beanutils
>> * commons-ognl
>> * commons-email
>> * commons-logging
>> * commons-codec
>> * commons-io
>> * geronimo-jcdi
>> * geronimo-atinject
>> * geronimo-annotations
>> * string-template (BSD)
>> * javax.json
>> * net.sf.uadetector
>> * net.sf.quality-check
>> * com.maxmind.geoip2:geoip2 (Commons Commons Attribution-ShareAlike 3.0
>> Unported, http://dev.maxmind.com/geoip/geoip2/geolite2/#License)
>> * elasticsearch
>> * spatial4j (optional)
>> * org.ow2.asm:asm
>> * groovy (optional)
>> * com.vividsolutions:jts (lgpl, optional)
>> * net.java.dev.jna (optional)
>> * org.fusesource:sigar (optional)
>> 
>> Module or optional dependencies:
>> 
>> * None
>> 
>> Build only dependencies:
>> 
>> * None
>> 
>> Test only dependencies:
>> 
>> * org.ops4j.pax.exam:pax-exam-container-karaf
>> * org.ops4j.pax.exam:pax-exam-junit4
>> * org.ops4j.pax.exam:pax-exam
>> * org.ops4j.pax.url:pax-url-aether
>> * javax.inject
>> * junit
>> * com.carrotsearch:junit-benchmarks
>> * com.h2database:h2
>> * gatling
>> * scala library
>> 
>> Cryptography N/A
>> 
>> == Required Resources ==
>> === Mailing lists ===
>> * priv...@unomi.incubator.apache.org (moderated subscriptions)
>> * comm...@unomi.incubator.apache.org
>> * d...@unomi.incubator.apache.org
>> * iss...@unomi.incubator.apache.org
>> * u...@unomi.incubator.apache.org
>> 
>> === Git Repository ===
>> * https://git-wip-us.apache.org/repos/asf/incubator-unomi.git
>> 
>> === Issue Tracking ===
>> * JIRA Project Unomi (UNOMI)
>> 
>> === Other Resources ===
>> Means of setting up regular builds for Unomi on builds.apache.org
>> 
>> == Initial Committers ==
>> * Serge Huber
>> * Thomas Draier
>> * Sergiy Shyrkov
>> * Kevan Jahanshahi
>> * Cédric Mailleux
>> * Régis Mora
>> * Quentin Lamerand
>> * Chris Laprun
>> * David Griffon
>> * Jean-Baptiste Onofré
>> 
>> == Affiliations ==
>> * Jahia Solutions: everyone else on this proposal
>> * NASA JPL: Chris Mattmann
>> * Talend : Jean-Baptiste Onofré
>> * Pivotal : Roman Shaposhnik
>> 
>> == Sponsors ==
>> == Champion ==
>> * Jean-Baptiste Onofré - Apache Member, Talend
>> 
>> == Mentors ==
>> The initial mentors are listed below:
>> 
>> * Bertrand Delacretaz - Apache Member, Adobe
>> * Roman Shaposhnik - Apache Member, Pivotal
>> * Chris Mattmann - Apache Member, NASA JPL
>> 
>> == Sponsoring Entity ==
>> We would like to propose Apache incubator to sponsor this project.
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Unomi into the Apache Incubator

[Serge Huber]

verage the Apache ‘branding’ when talking to other 
> projects as testament of our project’s ‘neutrality’, we have no plans for 
> making use of Apache brand in press releases nor posting billboards 
> advertising acceptance of Unomi into Apache Incubator.
> 
> == Interaction with the OASIS standard ==
> In order to properly implement the standard and possibly use the feedback 
> from the implementation as a way to improve the specifications, currently the 
> co-chair of the technical committee is also the proposer on the Apache 
> proposal. This relationship makes it easy for communication between the two 
> works, and will hopefully grow as the community grows around both the 
> standard and the implementation. This is quite similar to the situation with 
> the Apache Chemistry project, that is an open source implementation of the 
> CMIS specification that is also an OASIS standard.
> 
> == Documentation ==
> See documentation for the current state of the project documentation 
> available as part of the GitHub repository at https://github.com/Jahia/unomi
> 
> == Initial Source ==
> Jahia is releasing the source code for Unomi under the ASF license at 
> https://github.com/Jahia/unomi . We encourage ASF community members 
> interested in this proposal to download the source code, review and try out 
> the software.
> 
> == Source and Intellectual Property Submission Plan ==
> As soon as Unomi is approved to join Apache Incubator, the source code will 
> be transitioned via the Software Grant Agreement onto ASF infrastructure and 
> in turn made available under the Apache License, version 2.0. We know of no 
> legal encumberments that would inhibit the transfer of source code to the ASF.
> 
> == External Dependencies ==
> Embedded dependencies (relocated):
> 
> * None
> 
> Runtime dependencies:
> 
> * apache-karaf
> * pax-web
> * apache-cxf
> * slf4j
> * org.apache.httpcomponents:httpclient-osgi
> * org.apache.httpcomponents:httpcore-osgi
> * org.apache.servicemix.bundles.jakarta-regexp
> * pax-cdi
> * javax.servlet-api
> * jackson
> * org.osgi.core
> * commons-lang3
> * commons-collections
> * org.mvel:mvel2
> * commons-beanutils
> * commons-ognl
> * commons-email
> * commons-logging
> * commons-codec
> * commons-io
> * geronimo-jcdi
> * geronimo-atinject
> * geronimo-annotations
> * string-template (BSD)
> * javax.json
> * net.sf.uadetector
> * net.sf.quality-check
> * com.maxmind.geoip2:geoip2 (Commons Commons Attribution-ShareAlike 3.0 
> Unported, http://dev.maxmind.com/geoip/geoip2/geolite2/#License)
> * elasticsearch
> * spatial4j (optional)
> * org.ow2.asm:asm
> * groovy (optional)
> * com.vividsolutions:jts (lgpl, optional)
> * net.java.dev.jna (optional)
> * org.fusesource:sigar (optional)
> 
> Module or optional dependencies:
> 
> * None
> 
> Build only dependencies:
> 
> * None
> 
> Test only dependencies:
> 
> * org.ops4j.pax.exam:pax-exam-container-karaf
> * org.ops4j.pax.exam:pax-exam-junit4
> * org.ops4j.pax.exam:pax-exam
> * org.ops4j.pax.url:pax-url-aether
> * javax.inject
> * junit
> * com.carrotsearch:junit-benchmarks
> * com.h2database:h2
> * gatling
> * scala library
> 
> Cryptography N/A
> 
> == Required Resources ==
> === Mailing lists ===
> * priv...@unomi.incubator.apache.org (moderated subscriptions)
> * comm...@unomi.incubator.apache.org
> * d...@unomi.incubator.apache.org
> * iss...@unomi.incubator.apache.org
> * u...@unomi.incubator.apache.org
> 
> === Git Repository ===
> * https://git-wip-us.apache.org/repos/asf/incubator-unomi.git
> 
> === Issue Tracking ===
> * JIRA Project Unomi (UNOMI)
> 
> === Other Resources ===
> Means of setting up regular builds for Unomi on builds.apache.org
> 
> == Initial Committers ==
> * Serge Huber
> * Thomas Draier
> * Sergiy Shyrkov
> * Kevan Jahanshahi
> * Cédric Mailleux
> * Régis Mora
> * Quentin Lamerand
> * Chris Laprun
> * David Griffon
> * Jean-Baptiste Onofré
> 
> == Affiliations ==
> * Jahia Solutions: everyone else on this proposal
> * NASA JPL: Chris Mattmann
> * Talend : Jean-Baptiste Onofré
> * Pivotal : Roman Shaposhnik
> 
> == Sponsors ==
> == Champion ==
> * Jean-Baptiste Onofré - Apache Member, Talend
> 
> == Mentors ==
> The initial mentors are listed below:
> 
> * Bertrand Delacretaz - Apache Member, Adobe
> * Roman Shaposhnik - Apache Member, Pivotal
> * Chris Mattmann - Apache Member, NASA JPL
> 
> == Sponsoring Entity ==
> We would like to propose Apache incubator to sponsor this project.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Unomi incubation proposal

[Serge Huber]

Actually Bertrand already did it thanks !

Cheers,
  Serge

> Le 15 sept. 2015 à 21:25, Jean-Baptiste Onofré <j...@nanthrax.net> a écrit :
> 
> Hi Serge,
> 
> what's your username on the wiki ?
> 
> Thanks,
> Regards
> JB
> 
>> On 09/14/2015 11:45 AM, Serge Huber wrote:
>> I don’t have write access to the wiki, would you mind making that change ?
>> 
>> cheers,
>>   Serge…
>> 
>>> On 14 sept. 2015, at 11:28, Bertrand Delacretaz <bdelacre...@apache.org> 
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> The proposal at https://wiki.apache.org/incubator/UnomiProposal
>>> requests a u...@unomi.incubator.apache.org, does Unomi really need
>>> that?
>>> 
>>> My preference is to start with just a dev list, and only split if this
>>> becomes too busy.
>>> 
>>> -Bertrand
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Unomi incubation proposal

[Serge Huber]

Thanks Bertrand !

> On 14 sept. 2015, at 11:25, Bertrand Delacretaz <bdelacre...@apache.org> 
> wrote:
> 
> On Wed, Sep 9, 2015 at 5:58 PM, Serge Huber <shu...@jahia.com> wrote:
>> ...As a Karaf and CXF application I think that Unomi could definitely benefit
>> from your involvement ! So welcome on board !
> 
> I have added Raul Kripalani as an initial committer at
> https://wiki.apache.org/incubator/UnomiProposal
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Unomi incubation proposal

[Serge Huber]

Hi Bertrand, 

No that was a copy-paste from another proposal, we can remove that. Thanks for 
noticing that.

cheers,
  Serge… 

> On 14 sept. 2015, at 11:28, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
> The proposal at https://wiki.apache.org/incubator/UnomiProposal
> requests a u...@unomi.incubator.apache.org, does Unomi really need
> that?
> 
> My preference is to start with just a dev list, and only split if this
> becomes too busy.
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Unomi incubation proposal

[Serge Huber]

I don’t have write access to the wiki, would you mind making that change ?

cheers,
  Serge… 

> On 14 sept. 2015, at 11:28, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
> The proposal at https://wiki.apache.org/incubator/UnomiProposal
> requests a u...@unomi.incubator.apache.org, does Unomi really need
> that?
> 
> My preference is to start with just a dev list, and only split if this
> becomes too busy.
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[DISCUSS] Unomi incubation proposal

[Serge Huber]

Hi!

I would like to start a discussion on accepting UNOMI into ASF Incubator. The 
proposal is available at:
   https://wiki.apache.org/incubator/UnomiProposal
and is also attached to the end of this email.

This is a bit of a first for me and I’d like to thank all the people that have 
so far contributed to bringing to fruition. Of course this is the beginning of 
the process so I welcome all feedback and questions to make this better. I am 
planning to present the results of these efforts at ApacheCon EU.

Best regards,
  Serge Huber.

= Apache Unomi incubation proposal =
== Abstract ==
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.

== Proposal ==
The server is a data management platform that provides real-time user profile 
and event storage as well as a rule engine and fully featured REST+JSON 
interfaces which make integration with very different systems easier.

One of the main objectives of this implementation is to be modular and flexible 
enough to relatively easily build integration into systems such as CMS, WCM, 
CRM or even ERP. Built using Apache Karaf and ElasticSearch, it is designed to 
also be easily clusterable to address high-traffic scenarios where lots of 
profile data will need to be updated at a high frequency.

== Background ==
Unomi was built from scratch to serve as a reference implementation for the 
OASIS Context Server proposal. It has been developed by Jahia Software.

It initially served as a test-bed while working on the specifics of the new 
proposal, to make sure that the concepts being discussed and decided would make 
sense in an actual implementation. At the same time, Jahia, one of the 
companies involved in the standardization work, needed a basis to build their 
new Marketing Factory product, so it made a lot of sense to start this way. 
Thanks to a lot of work done in the standard, the implementation was produced 
relatively quickly and this made it possible to build a commercial product on 
top of this implementation that will be released in Winter 2015. This implies 
that the core of the commercial product being proposed here will undergo a full 
set of QA tests, including and scalability tests.

Another important objective was to provide a platform that deals with user data 
in an “ethical” way, in order to make the usage of personal data more 
transparent and to improve privacy. Through the work in the standard and this 
open source implementation, it is the hope of the original designers that it 
will be easier for all users of this technology to fully understand how the 
data is being used and what type of control is exercised over it. A transparent 
usage of customer data could become, in the near future, a key tool to keep 
customer loyalty. Companies would then be able to leverage digital marketing 
frameworks capabilities such as Unomi, but, as a fair - and quite possibly 
legally mandatory - counterpart, should allow end users to understand the data 
being used, as well as the way it is used, in order to give them more control 
over which data to share or to anonymise.

The purpose is to bring Jahia Marketing Factory codebase into the Apache 
Software Foundation (ASF) in order to build a vibrant, diverse and 
self-governed open source community around the technology. Jahia will continue 
to market and sell Jahia Marketing Factory based on Unomi. Unomi and Jahia 
Marketing Factory will be managed separately. This proposal covers the Unomi 
source code (mainly written in Java), Unomi documentation and other materials 
currently available on GitHub. Unomi is our primary choice for a name of the 
project.

== Rationale ==
Building highly scalable, performant and flexible personalization architectures 
requires major efforts. The complexities of requirements, integrations and use 
cases is directly related to the number of users, and Apache projects usually 
get a lot of visibility and usage. Therefore it was a goal from the start to 
share this project with the ASF, as it is believed this is the best way to 
achieve the true potential of this codebase, to make it highly visible and 
continually improve on its design and implementation to make it the best tool 
for the job for a wide variety of use cases.

The project, as it sits a bit higher than usual BigData frameworks, could be 
used a front-end to a lot of existing Apache project that could be integrated 
to help deliver more power into the platform. For example Unomi doesn’t 
currently include machine learning but it could very well be expanded to 
include a module that would use Apache Mahout. In the same way, for the 
persistence layer, an already existing Service Provider Interface could be used 
to provide other backends such as HDFS, Cassandra, Solr or any other.

== Initial Goals ==
Our initial goals are to bring Unomi

Re: [DISCUSS] Unomi incubation proposal

[Serge Huber]

Hello Raul,

Thanks for your quick reply and interest ! As a Karaf and CXF application I 
think that Unomi could definitely benefit from your involvement ! So welcome on 
board !

I don't have write permissions on the Wiki but maybe JB could add you ?

Best regards,
  Serge

Envoyé de mon iPhone

> Le 9 sept. 2015 à 17:47, Raul Kripalani <ra...@apache.org> a écrit :
> 
> Sounds great! I'd like to participate in this incubation.
> 
> My profile in the ASF and with regards to the projects cited in your
> proposal: PMC Member of Apache Camel, getting involved in Apache Ignite,
> with 4+ years experience with Apache Karaf at debug level, contributor at
> OPS4j, 8+ years with CXF user-level.
> 
> I hope you'd like to have me in the team ;-)
> 
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
> 
>> On Wed, Sep 9, 2015 at 4:29 PM, Serge Huber <shu...@jahia.com> wrote:
>> 
>> Hi!
>> 
>> I would like to start a discussion on accepting UNOMI into ASF Incubator.
>> The proposal is available at:
>>   https://wiki.apache.org/incubator/UnomiProposal
>> and is also attached to the end of this email.
>> 
>> This is a bit of a first for me and I’d like to thank all the people that
>> have so far contributed to bringing to fruition. Of course this is the
>> beginning of the process so I welcome all feedback and questions to make
>> this better. I am planning to present the results of these efforts at
>> ApacheCon EU.
>> 
>> Best regards,
>>  Serge Huber.
>> 
>> = Apache Unomi incubation proposal =
>> == Abstract ==
>> 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.
>> 
>> == Proposal ==
>> The server is a data management platform that provides real-time user
>> profile and event storage as well as a rule engine and fully featured
>> REST+JSON interfaces which make integration with very different systems
>> easier.
>> 
>> One of the main objectives of this implementation is to be modular and
>> flexible enough to relatively easily build integration into systems such as
>> CMS, WCM, CRM or even ERP. Built using Apache Karaf and ElasticSearch, it
>> is designed to also be easily clusterable to address high-traffic scenarios
>> where lots of profile data will need to be updated at a high frequency.
>> 
>> == Background ==
>> Unomi was built from scratch to serve as a reference implementation for
>> the OASIS Context Server proposal. It has been developed by Jahia Software.
>> 
>> It initially served as a test-bed while working on the specifics of the
>> new proposal, to make sure that the concepts being discussed and decided
>> would make sense in an actual implementation. At the same time, Jahia, one
>> of the companies involved in the standardization work, needed a basis to
>> build their new Marketing Factory product, so it made a lot of sense to
>> start this way. Thanks to a lot of work done in the standard, the
>> implementation was produced relatively quickly and this made it possible to
>> build a commercial product on top of this implementation that will be
>> released in Winter 2015. This implies that the core of the commercial
>> product being proposed here will undergo a full set of QA tests, including
>> and scalability tests.
>> 
>> Another important objective was to provide a platform that deals with user
>> data in an “ethical” way, in order to make the usage of personal data more
>> transparent and to improve privacy. Through the work in the standard and
>> this open source implementation, it is the hope of the original designers
>> that it will be easier for all users of this technology to fully understand
>> how the data is being used and what type of control is exercised over it. A
>> transparent usage of customer data could become, in the near future, a key
>> tool to keep customer loyalty. Companies would then be able to leverage
>> digital marketing frameworks capabilities such as Unomi, but, as a fair -
>> and quite possibly legally mandatory - counterpart, should allow end users
>> to understand the data being used, as well as the way it is used, in order
>> to give them more control over which data to share or to anonymise.
>> 
>> The purpose is to bring Jahia Marketing F