Following the discussion thread, I would like to call a
VOTE on accepting Hivemall into the Apache Incubator.
[] +1 Accept Hivemall into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Hivemall into the Apache Incubator because ...
This vote will be open until 11:59am PST 9th of September
Hi,
> I've seen Justin's video, but would be great to also have it written down.
The video [1] has closed captions if that helps. The steps to produce that
LICENSE and NOTICE are written down here [2] The github history may also be of
help as it shows each change via a single checkin. Also pull
Hi,
> I assume you've seen this:
> http://www.apache.org/dev/licensing-howto.html#mod-notice
See also [1] for what else need to go in license, the text about category b [2]
and how to handle 3rd party headers [3]. [4] is important if you are bundling
Apache v2 code.
Thanks,
Justin
1. http://
On 9/2/16, 12:08 PM, "John D. Ament" wrote:
>All,
>
>I was wondering if someone can point me to a resource that clearly
>identifies what goes into the NOTICES file for a source and binary
>release? I've seen Justin's video, but would be great to also have it
>written down.
I assume you've see
All,
I was wondering if someone can point me to a resource that clearly
identifies what goes into the NOTICES file for a source and binary
release? I've seen Justin's video, but would be great to also have it
written down.
John
On Fri, Sep 2, 2016 at 12:49 PM, John D. Ament wrote:
> On Fri, Sep 2, 2016 at 12:42 PM Sam Ruby wrote:
>
>> The first stage would be migrating existing lists to LDAP. This will
>> require some small changes to whimsy and the phone book application.
>> The whole effort will only take a few hours
On Fri, Sep 2, 2016 at 1:06 PM, Mark Thomas wrote:
> On 02/09/2016 17:41, Sam Ruby wrote:
>> To prepare, we will need to decide who gets to modify these lists, and
>> who gets notified. I propose that members of podlings be able to modify
>> the list, and the private list associated with that pod
On 02/09/2016 17:41, Sam Ruby wrote:
> To prepare, we will need to decide who gets to modify these lists, and
> who gets notified. I propose that members of podlings be able to modify
> the list, and the private list associated with that podling be notified
> on changes. Alternate choices would i
On Fri, Sep 2, 2016 at 12:42 PM Sam Ruby wrote:
> For background, if you go to the Apache phonebook
> (https://people.apache.org/phonebook.html) and click on the "Podling
> name" input field and click on enter you will see an incomplete list of
> podlings. If you click on a podling, you will see
For background, if you go to the Apache phonebook
(https://people.apache.org/phonebook.html) and click on the "Podling
name" input field and click on enter you will see an incomplete list of
podlings. If you click on a podling, you will see a list of members for
that podling.
The ultimate so
10 matches
Mail list logo