Re: Images in source code.

[Craig Russell]

Hi James,

Everything that is not explicitly called out in the top level NOTICE and 
LICENSE files are licensed under the Apache 2.0 license.

Adding a file to this directory might mislead people into thinking that they 
need to perform more due diligence with other files in other directories.

My advice is to *not* add anything. Let the images be licensed per the terms 
the top level LICENSE file.

Craig

> On Jun 2, 2017, at 2:20 PM, James Bognar  wrote:
> 
> Thanks!
> 
> I haven't found a metadata editor that works yet, so I'll just add a
> LICENSE.txt file to the directory.  Hopefully that's enough.
> 
> On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser  wrote:
> 
>> On 6/2/17 1:15 PM, James Bognar wrote:
>> 
>>> I just added several png files to the source tree of our podling.  I
>>> created them myself.  Are there any best-practices on how to mark these as
>>> Apache licensed?
>>> 
>>> 
>> I'm not sure of a good way to track this. I'm not sure if png supports
>> arbitrary metadata which could be edited. Some ways I've seen used
>> elsewhere to try to better propagate license/ownership:
>> 
>> * Comments on the issue-tracker issue that introduced them citing
>> origin/source (typically for images that are copied, not created)
>> * Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course)
>> * A README in the same directory with relevant info
>> 
>> If the images are of the podling's creation, I wouldn't be particularly
>> worried. The copyright notice on your source-release and LICENSE are
>> sufficient to inform downstream consumers.
>> 
>> Probably not the answer you're looking for, but hope it helps :)
>> 
>> - Josh
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> 
> -- 
> James Bognar

Craig L Russell
c...@apache.org


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

Request for write access to Apache Incubator Wiki

[Vinod Kumar Vavilapalli]

Hi,

I just volunteered to be a mentor for the Apache Slider incubator project. 
Please grant me write access to Apache Incubator Wiki.

My apache ID is vinodkv and my wiki user-name  
VinodKumarVavilapalli 
(old account but mysteriously deleted, just recreated it).

Thanks
+Vinod

Re: [DISCUSS] Graduate Apache Mynewt from podling to TLP

[Greg Stein]

On Fri, Jun 2, 2017 at 2:37 PM, aditi hilbert  wrote:

> > On Jun 3, 2017, at 1:37 AM, sebb  wrote:
>
>...

> > Please also remove the non-current releases.
>
> The links to the source? or all reference altogether? Some orgs are still
> working with 0.9 version, for example.
>

The tarballs in dist.apache.org. You can still link to old versions from
your project pages (they'll always be at
https://archive.apache.org/dist/incubator/mynewt/ ). Something like "Prior release (0.9; archived)"

Current release via the mirror network, and old releases on archive.a.o

Cheers,
-g

Re: Images in source code.

[Josh Elser]

Agreed. If I wasn't clear the first time, I did not mean to suggest to 
add a file named LICENSE* in the same directory as the images.


This would be confusing for the reason Ted also mentioned. I concur with 
his suggestion of "README" :)


On 6/2/17 6:16 PM, Ted Dunning wrote:

I think a README would be a better name for the explanatory file.



On Fri, Jun 2, 2017 at 11:20 PM, James Bognar 
wrote:


Thanks!

I haven't found a metadata editor that works yet, so I'll just add a
LICENSE.txt file to the directory.  Hopefully that's enough.

On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser  wrote:


On 6/2/17 1:15 PM, James Bognar wrote:


I just added several png files to the source tree of our podling.  I
created them myself.  Are there any best-practices on how to mark these

as

Apache licensed?



I'm not sure of a good way to track this. I'm not sure if png supports
arbitrary metadata which could be edited. Some ways I've seen used
elsewhere to try to better propagate license/ownership:

* Comments on the issue-tracker issue that introduced them citing
origin/source (typically for images that are copied, not created)
* Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course)
* A README in the same directory with relevant info

If the images are of the podling's creation, I wouldn't be particularly
worried. The copyright notice on your source-release and LICENSE are
sufficient to inform downstream consumers.

Probably not the answer you're looking for, but hope it helps :)

- Josh

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





--
James Bognar





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

Re: Images in source code.

[Ted Dunning]

I think a README would be a better name for the explanatory file.



On Fri, Jun 2, 2017 at 11:20 PM, James Bognar 
wrote:

> Thanks!
>
> I haven't found a metadata editor that works yet, so I'll just add a
> LICENSE.txt file to the directory.  Hopefully that's enough.
>
> On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser  wrote:
>
> > On 6/2/17 1:15 PM, James Bognar wrote:
> >
> >> I just added several png files to the source tree of our podling.  I
> >> created them myself.  Are there any best-practices on how to mark these
> as
> >> Apache licensed?
> >>
> >>
> > I'm not sure of a good way to track this. I'm not sure if png supports
> > arbitrary metadata which could be edited. Some ways I've seen used
> > elsewhere to try to better propagate license/ownership:
> >
> > * Comments on the issue-tracker issue that introduced them citing
> > origin/source (typically for images that are copied, not created)
> > * Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course)
> > * A README in the same directory with relevant info
> >
> > If the images are of the podling's creation, I wouldn't be particularly
> > worried. The copyright notice on your source-release and LICENSE are
> > sufficient to inform downstream consumers.
> >
> > Probably not the answer you're looking for, but hope it helps :)
> >
> > - Josh
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> James Bognar
>

Re: Images in source code.

[Mark Thomas]

On 02/06/2017 22:20, James Bognar wrote:
> Thanks!
> 
> I haven't found a metadata editor that works yet, so I'll just add a
> LICENSE.txt file to the directory.  Hopefully that's enough.

That is more than is necessary. It might even cause confusion at some
point in the future. I would recommend against doing that. The concern
is that folks have a tendency to attempt to reverse engineer ASF policy
from what they see other projects do which leads them to assume all
sorts of things are required when they are not. That in turn can consume
effort that could have been better spent on other things.

Any file in the project's source tree is ALv2 licensed unless explicitly
called out otherwise in the LICENSE file at the root of the source tree.

Where we can add a header to a file we do, but if we can't (easily),
then we don't and that is fine.

Mark


> 
> On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser  wrote:
> 
>> On 6/2/17 1:15 PM, James Bognar wrote:
>>
>>> I just added several png files to the source tree of our podling.  I
>>> created them myself.  Are there any best-practices on how to mark these as
>>> Apache licensed?
>>>
>>>
>> I'm not sure of a good way to track this. I'm not sure if png supports
>> arbitrary metadata which could be edited. Some ways I've seen used
>> elsewhere to try to better propagate license/ownership:
>>
>> * Comments on the issue-tracker issue that introduced them citing
>> origin/source (typically for images that are copied, not created)
>> * Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course)
>> * A README in the same directory with relevant info
>>
>> If the images are of the podling's creation, I wouldn't be particularly
>> worried. The copyright notice on your source-release and LICENSE are
>> sufficient to inform downstream consumers.
>>
>> Probably not the answer you're looking for, but hope it helps :)
>>
>> - Josh
>>
>> -
>> 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: Images in source code.

[James Bognar]

Thanks!

I haven't found a metadata editor that works yet, so I'll just add a
LICENSE.txt file to the directory.  Hopefully that's enough.

On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser  wrote:

> On 6/2/17 1:15 PM, James Bognar wrote:
>
>> I just added several png files to the source tree of our podling.  I
>> created them myself.  Are there any best-practices on how to mark these as
>> Apache licensed?
>>
>>
> I'm not sure of a good way to track this. I'm not sure if png supports
> arbitrary metadata which could be edited. Some ways I've seen used
> elsewhere to try to better propagate license/ownership:
>
> * Comments on the issue-tracker issue that introduced them citing
> origin/source (typically for images that are copied, not created)
> * Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course)
> * A README in the same directory with relevant info
>
> If the images are of the podling's creation, I wouldn't be particularly
> worried. The copyright notice on your source-release and LICENSE are
> sufficient to inform downstream consumers.
>
> Probably not the answer you're looking for, but hope it helps :)
>
> - Josh
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
James Bognar

Re: Images in source code.

[Josh Elser]

On 6/2/17 1:15 PM, James Bognar wrote:

I just added several png files to the source tree of our podling.  I
created them myself.  Are there any best-practices on how to mark these as
Apache licensed?



I'm not sure of a good way to track this. I'm not sure if png supports 
arbitrary metadata which could be edited. Some ways I've seen used 
elsewhere to try to better propagate license/ownership:


* Comments on the issue-tracker issue that introduced them citing 
origin/source (typically for images that are copied, not created)

* Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course)
* A README in the same directory with relevant info

If the images are of the podling's creation, I wouldn't be particularly 
worried. The copyright notice on your source-release and LICENSE are 
sufficient to inform downstream consumers.


Probably not the answer you're looking for, but hope it helps :)

- Josh

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

[VOTE] Apache HTrace 4.3.0 incubating release (rc3)

[Mike Drob]

Hi IPMC,

Please consider the release of Apache HTrace 4.3.0 Incubating



Project [VOTE]:

https://lists.apache.org/thread.html/6e60ba2574a853da59c3a150f18cd9bbd52051785380a7cc837b583e@%3Cdev.htrace.apache.org%3E

Project [RESULT][VOTE]:

https://lists.apache.org/thread.html/fb2a68fcd9c80d9db4a483794112aecde486ca263384dec0bad38c34@%3Cdev.htrace.apache.org%3E

Artifacts staged at:

http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/

Staging maven repository at:

https://repository.apache.org/content/repositories/orgapachehtrace-1029

Source tree:

https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=2ca8767b38c83f0d2f46ce7f91373d9df69f7fb8;hb=a47398aea8d65fb544faba150beb49bb7654cb49


Please download and evaluate the release candidate.

This vote will remain open for minimum 5 days

[ ] +1 Approve the release

[ ] +0 No opinion

[ ] -1 Do not approve the release because ...


Thanks,

Mike

Re: [DISCUSS] Graduate Apache Mynewt from podling to TLP

[aditi hilbert]

> On Jun 3, 2017, at 1:37 AM, sebb  wrote:
> 
> On 2 June 2017 at 17:10, aditi hilbert  wrote:
>> Sebb,
>> 
>> Thanks for catching the errors! Not sure what happened exactly but parts of 
>> the text reverted back to another resolution we were using as a base 
>> template. We have fixed the project description: 
>> https://cwiki.apache.org/confluence/display/MYNEWT/Resolution 
>> 
>> 
>> (no mailto: links either and we’ll make sure the mailer doesn’t insert them 
>> in.)
>> 
>> I’ll be using the text from that page when we call the vote.
>> 
>> The release source download links have been added too: 
>> https://mynewt.apache.org/download/ 
> 
> Thanks.
> 
> Please also remove the non-current releases.

The links to the source? or all reference altogether? Some orgs are still 
working with 0.9 version, for example.
thanks!

> 
>> thanks,
>> aditi
>> 
>>> On Jun 1, 2017, at 5:26 AM, sebb  wrote:
>>> 
>>> On 31 May 2017 at 16:09, aditi hilbert  wrote:
 Hi,
 
 The Apache Mynewt podling just passed the vote within its community to 
 graduate it to a Top Level Project.
 An informational note was sent out earlier about the vote going on and it 
 was pointed out that the status page
 needed to be updated. We have done that.
 http://incubator.apache.org/projects/mynewt.html 
 
 
 I’d like to share the full text of the proposed resolution and open it up 
 to discussion for at least 72 hours
 before putting it to a formal vote.
 
 
 The incubating Apache Mynewt community believes it is time to graduate to 
 TLP.
 
 Apache Mynewt entered incubation in October of 2015.  Since then, we've 
 overcome technical challenges and built Apache's first Operating System 
 for IoT devices, and made 6 releases.  Our most recent releases include 
 NimBLE, OIC1.1 support, MCUbootloader. We are a very helpful and engaged 
 community, ready to answer all questions and feedback directed to us via 
 the user list.  We've added several committers from different 
 organizations, and are actively pursuing others. While we continue working 
 on maturity, all projects are ongoing processes, and we believe we no 
 longer need the incubator to continue.
 
 To inform the discussion, here is some basic project information:
 
 Project status:
 http://incubator.apache.org/projects/mynewt.html 
 
 
 Project website:
 http://mynewt.incubator.apache.org/ 
 
 Project documentation:
 https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Project 
 
 
 Maturity assessment:
 https://cwiki.apache.org/confluence/display/MYNEWT/Maturity+model 
 
 
 DRAFT of the board resolution is at the bottom of this email
 
 Proposed PMC size: 20 members
 
 Total number of committers: 20 members
 
 Various PMC/Committer affiliations (* indicated chair)
 Runtime (6)
 Google (1)
 Imagination Technologies (1)
 Codecoup (4)
 Adafruit (1)
 
 4,565 commits on develop
 280 closed PR”s on GitHub
 39 contributors across all branches
 92 forks on Github
 
 dev list averaged ~200 msgs/month in the last one year
 
 647 issues created
 465 issues resolved/closed
 
 --
 Resolution:
 
 Establish the Apache Mynewt Project
 
 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to the
 public, related to a data management platform that provides
 real-time, consistent access to data-intensive applications
 throughout widely distributed cloud architectures.
>>> 
>>> The project description does not look right.
>>> 
>>> Also I think there are some issues with the downloads.
>>> 
>>> There are some releases on the ASF mirror system, however there do not
>>> appear to be any links to the current release (or indeed to archives).
>>> The ASF releases *source*  (see previous paragraph) which must be
>>> published via the ASF mirror system.
>>> 
>>> Also obsolete downloads are not being tidied up.
>>> 
>>> 
 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Mynewt Project",
 be and hereby is established pursuant to 

Re: [DISCUSS] Graduate Apache Mynewt from podling to TLP

[sebb]

On 2 June 2017 at 17:10, aditi hilbert  wrote:
> Sebb,
>
> Thanks for catching the errors! Not sure what happened exactly but parts of 
> the text reverted back to another resolution we were using as a base 
> template. We have fixed the project description: 
> https://cwiki.apache.org/confluence/display/MYNEWT/Resolution 
> 
>
> (no mailto: links either and we’ll make sure the mailer doesn’t insert them 
> in.)
>
> I’ll be using the text from that page when we call the vote.
>
> The release source download links have been added too: 
> https://mynewt.apache.org/download/ 

Thanks.

Please also remove the non-current releases.

> thanks,
> aditi
>
>> On Jun 1, 2017, at 5:26 AM, sebb  wrote:
>>
>> On 31 May 2017 at 16:09, aditi hilbert  wrote:
>>> Hi,
>>>
>>> The Apache Mynewt podling just passed the vote within its community to 
>>> graduate it to a Top Level Project.
>>> An informational note was sent out earlier about the vote going on and it 
>>> was pointed out that the status page
>>> needed to be updated. We have done that.
>>> http://incubator.apache.org/projects/mynewt.html 
>>> 
>>>
>>> I’d like to share the full text of the proposed resolution and open it up 
>>> to discussion for at least 72 hours
>>> before putting it to a formal vote.
>>>
>>> 
>>> The incubating Apache Mynewt community believes it is time to graduate to 
>>> TLP.
>>>
>>> Apache Mynewt entered incubation in October of 2015.  Since then, we've 
>>> overcome technical challenges and built Apache's first Operating System for 
>>> IoT devices, and made 6 releases.  Our most recent releases include NimBLE, 
>>> OIC1.1 support, MCUbootloader. We are a very helpful and engaged community, 
>>> ready to answer all questions and feedback directed to us via the user 
>>> list.  We've added several committers from different organizations, and are 
>>> actively pursuing others. While we continue working on maturity, all 
>>> projects are ongoing processes, and we believe we no longer need the 
>>> incubator to continue.
>>>
>>> To inform the discussion, here is some basic project information:
>>>
>>> Project status:
>>> http://incubator.apache.org/projects/mynewt.html 
>>> 
>>>
>>> Project website:
>>> http://mynewt.incubator.apache.org/ 
>>>
>>> Project documentation:
>>> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Project 
>>> 
>>>
>>> Maturity assessment:
>>> https://cwiki.apache.org/confluence/display/MYNEWT/Maturity+model 
>>> 
>>>
>>> DRAFT of the board resolution is at the bottom of this email
>>>
>>> Proposed PMC size: 20 members
>>>
>>> Total number of committers: 20 members
>>>
>>> Various PMC/Committer affiliations (* indicated chair)
>>>  Runtime (6)
>>>  Google (1)
>>>  Imagination Technologies (1)
>>>  Codecoup (4)
>>>  Adafruit (1)
>>>
>>> 4,565 commits on develop
>>> 280 closed PR”s on GitHub
>>> 39 contributors across all branches
>>> 92 forks on Github
>>>
>>> dev list averaged ~200 msgs/month in the last one year
>>>
>>> 647 issues created
>>> 465 issues resolved/closed
>>>
>>> --
>>> Resolution:
>>>
>>> Establish the Apache Mynewt Project
>>>
>>> WHEREAS, the Board of Directors deems it to be in the best
>>> interests of the Foundation and consistent with the
>>> Foundation's purpose to establish a Project Management
>>> Committee charged with the creation and maintenance of
>>> open-source software, for distribution at no charge to the
>>> public, related to a data management platform that provides
>>> real-time, consistent access to data-intensive applications
>>> throughout widely distributed cloud architectures.
>>
>> The project description does not look right.
>>
>> Also I think there are some issues with the downloads.
>>
>> There are some releases on the ASF mirror system, however there do not
>> appear to be any links to the current release (or indeed to archives).
>> The ASF releases *source*  (see previous paragraph) which must be
>> published via the ASF mirror system.
>>
>> Also obsolete downloads are not being tidied up.
>>
>>
>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>> Committee (PMC), to be known as the "Apache Mynewt Project",
>>> be and hereby is established pursuant to Bylaws of the
>>> Foundation; and be it further
>>>
>>> RESOLVED, that the Apache Mynewt Project be and hereby is
>>> responsible for the creation and maintenance of software
>>> related to an embedded OS optimized for networking and built for remote 
>>> management of constrained devices that are incapable of running either 
>>> Linux or 

Images in source code.

[James Bognar]

I just added several png files to the source tree of our podling.  I
created them myself.  Are there any best-practices on how to mark these as
Apache licensed?

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[lewis john mcgibbney]

Hi Justin,
Excellent catch. Thank you for rebiewing the RC... it is really helping us
out.
To answer your question, I had to look back to the Joshua Tag for 6.0.4
(prior to it's entry into the Incubator as a podling) I managed to find the
commit history for the file(s) in question...
https://github.com/joshua-decoder/joshua/commit/aeaed01deb0688b0af5adcd01a0be0b9d4d51789
You will see that they were added to Joshua (at that time) in one commit,
the commit message would indicate that they came from the source you've
provided. e.g. "...Added parallelization files from cdec"
Where does this leave us now? The file(s) have bee altered since then,
please see
https://github.com/joshua-decoder/joshua/commit/0bee12805426fc5ac61b3fdb702a5a059404d64f
The copyright has been retained but the Apache Licence v2.0 header has also
been added.
Lewis

On Fri, Jun 2, 2017 at 8:59 AM, 
wrote:

>
> From: Justin Mclean 
> To: general@incubator.apache.org
> Cc:
> Bcc:
> Date: Fri, 2 Jun 2017 18:29:14 +1000
> Subject: Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1
> (rc4)
> Hi,
>
> Just wondering if the "All rights reserved” may imply that it's not
> licensed under a permissive license?
>
>  I’m unaware of the history / providence of that file so was enquiring if
> anyone on the project had any more info where it come from.
>
> Thanks,
> Justin
>



-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re: [DISCUSS] Graduate Apache Mynewt from podling to TLP

[aditi hilbert]

Sebb,

Thanks for catching the errors! Not sure what happened exactly but parts of the 
text reverted back to another resolution we were using as a base template. We 
have fixed the project description: 
https://cwiki.apache.org/confluence/display/MYNEWT/Resolution 


(no mailto: links either and we’ll make sure the mailer doesn’t insert them in.)

I’ll be using the text from that page when we call the vote.

The release source download links have been added too: 
https://mynewt.apache.org/download/ 

thanks,
aditi

> On Jun 1, 2017, at 5:26 AM, sebb  wrote:
> 
> On 31 May 2017 at 16:09, aditi hilbert  wrote:
>> Hi,
>> 
>> The Apache Mynewt podling just passed the vote within its community to 
>> graduate it to a Top Level Project.
>> An informational note was sent out earlier about the vote going on and it 
>> was pointed out that the status page
>> needed to be updated. We have done that.
>> http://incubator.apache.org/projects/mynewt.html 
>> 
>> 
>> I’d like to share the full text of the proposed resolution and open it up to 
>> discussion for at least 72 hours
>> before putting it to a formal vote.
>> 
>> 
>> The incubating Apache Mynewt community believes it is time to graduate to 
>> TLP.
>> 
>> Apache Mynewt entered incubation in October of 2015.  Since then, we've 
>> overcome technical challenges and built Apache's first Operating System for 
>> IoT devices, and made 6 releases.  Our most recent releases include NimBLE, 
>> OIC1.1 support, MCUbootloader. We are a very helpful and engaged community, 
>> ready to answer all questions and feedback directed to us via the user list. 
>>  We've added several committers from different organizations, and are 
>> actively pursuing others. While we continue working on maturity, all 
>> projects are ongoing processes, and we believe we no longer need the 
>> incubator to continue.
>> 
>> To inform the discussion, here is some basic project information:
>> 
>> Project status:
>> http://incubator.apache.org/projects/mynewt.html 
>> 
>> 
>> Project website:
>> http://mynewt.incubator.apache.org/ 
>> 
>> Project documentation:
>> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Project 
>> 
>> 
>> Maturity assessment:
>> https://cwiki.apache.org/confluence/display/MYNEWT/Maturity+model 
>> 
>> 
>> DRAFT of the board resolution is at the bottom of this email
>> 
>> Proposed PMC size: 20 members
>> 
>> Total number of committers: 20 members
>> 
>> Various PMC/Committer affiliations (* indicated chair)
>>  Runtime (6)
>>  Google (1)
>>  Imagination Technologies (1)
>>  Codecoup (4)
>>  Adafruit (1)
>> 
>> 4,565 commits on develop
>> 280 closed PR”s on GitHub
>> 39 contributors across all branches
>> 92 forks on Github
>> 
>> dev list averaged ~200 msgs/month in the last one year
>> 
>> 647 issues created
>> 465 issues resolved/closed
>> 
>> --
>> Resolution:
>> 
>> Establish the Apache Mynewt Project
>> 
>> WHEREAS, the Board of Directors deems it to be in the best
>> interests of the Foundation and consistent with the
>> Foundation's purpose to establish a Project Management
>> Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the
>> public, related to a data management platform that provides
>> real-time, consistent access to data-intensive applications
>> throughout widely distributed cloud architectures.
> 
> The project description does not look right.
> 
> Also I think there are some issues with the downloads.
> 
> There are some releases on the ASF mirror system, however there do not
> appear to be any links to the current release (or indeed to archives).
> The ASF releases *source*  (see previous paragraph) which must be
> published via the ASF mirror system.
> 
> Also obsolete downloads are not being tidied up.
> 
> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Mynewt Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>> 
>> RESOLVED, that the Apache Mynewt Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to an embedded OS optimized for networking and built for remote 
>> management of constrained devices that are incapable of running either Linux 
>> or Android.
> 
> Disagrees with the first paragraph
> 
>> RESOLVED, that the office of "Vice President, Apache Mynewt" be
>> and hereby is created, the person holding such office to
>> serve at the direction of the Board of Directors as 

Re: [VOTE] Livy to enter Apache Incubator

[Felix Cheung]

+1

On Thu, Jun 1, 2017 at 11:14 AM Hitesh Shah  wrote:

> +1
>
> -- Hitesh
>
> On Wed, May 31, 2017 at 6:03 AM, Sean Busbey  wrote:
>
> > Hi folks!
> >
> > I'm calling a vote to accept "Livy" into the Apache Incubator.
> >
> > The full proposal is available below, and is also available in the wiki:
> >
> > https://wiki.apache.org/incubator/LivyProposal
> >
> > For additional context, please see the discussion thread:
> >
> > https://s.apache.org/incubator-livy-proposal-thread
> >
> > Please cast your vote:
> >
> > [ ] +1, bring Livy into Incubator
> > [ ] -1, do not bring Livy into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> Incubator
> > PMC are binding.
> >
> > I start with my vote:
> > +1
> >
> > 
> >
> > = Abstract =
> >
> > Livy is web service that exposes a REST interface for managing long
> running
> > Apache Spark contexts in your cluster. With Livy, new applications can be
> > built on top of Apache Spark that require fine grained interaction with
> > many
> > Spark contexts.
> >
> > = Proposal =
> >
> > Livy is an open-source REST service for Apache Spark. Livy enables
> > applications to submit Spark applications and retrieve results without a
> > co-location requirement on the Spark cluster.
> >
> > We propose to contribute the Livy codebase and associated artifacts (e.g.
> > documentation, web-site context etc) to the Apache Software Foundation.
> >
> > = Background =
> >
> > Apache Spark is a fast and general purpose distributed compute engine,
> with
> > a versatile API. It enables processing of large quantities of static data
> > distributed over a cluster of machines, as well as processing of
> continuous
> > streams of data. It is the preferred distributed data processing engine
> for
> > data engineering, stream processing and data science workloads. Each
> Spark
> > application uses a construct called the SparkContext, which is the
> > application’s connection or entry point to the Spark engine. Each Spark
> > application will have its own SparkContext.
> >
> > Livy enables clients to interact with one or more Spark sessions through
> > the
> > Livy Server, which acts as a proxy layer. Livy Clients have fine grained
> > control over the lifecycle of the Spark sessions, as well as the ability
> to
> > submit jobs and retrieve results, all over HTTP. Clients have two modes
> of
> > interaction: RPC Client API, available in Java and Python, which allows
> > results to be retrieved as Java or Python objects. The serialization and
> > deserialization of the results is handled by the Livy framework. HTTP
> based
> > API that allows submission of code snippets, and retrieval of the results
> > in
> > different formats.
> >
> > Multi-tenant resource allocation and security: Livy enables multiple
> > independent Spark sessions to be managed simultaneously. Multiple clients
> > can also interact simultaneously with the same Spark session and share
> the
> > resources of that Spark session. Livy can also enforce secure,
> > authenticated
> > communication between the clients and their respective Spark sessions.
> >
> > More information on Livy can be found at the existing open source
> website:
> > http://livy.io/
> >
> > = Rationale =
> >
> > Users want to use Spark’s powerful processing engine and API as the data
> > processing backend for interactive applications. However, the job
> > submission
> > and application interaction mechanisms built into Apache Spark are
> > insufficient and cumbersome for multi-user interactive applications.
> >
> > The primary mechanism for applications to submit Spark jobs is via
> > spark-submit
> > (http://spark.apache.org/docs/latest/submitting-applications.html),
> which
> > is
> > available as a command line tool as well as a programmatic API. However,
> > spark-submit has the following limitations that make it difficult to
> build
> > interactive applications: It is slow: each invocation of spark-submit
> > involves a setup phase where cluster resources are acquired, new
> processes
> > are forked, etc. This setup phase runs for many seconds, or even minutes,
> > and hence is too slow for interactive applications. It is cumbersome and
> > lacks flexibility: application code and dependencies have to be
> > pre-compiled
> > and submitted as jars, and can not be submitted interactively.
> >
> > Apache Spark comes with an ODBC/JDBC server, which can be used to submit
> > SQL
> > queries to Spark. However, this solution is limited to SQL and does not
> > allow the client to leverage the rest of the Spark API, such as RDDs,
> MLlib
> > and Streaming.
> >
> > A third way of using Spark is via its command-line shell, which allows
> the
> > interactive submission of snippets of Spark code. However, the shell
> > entails
> > running Spark code on the client machine and hence is not a viable
> > mechanism
> > for remote clients to submit Spark jobs.
> >
> > Livy solves the 

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Justin Mclean]

Hi,

Just wondering if the "All rights reserved” may imply that it's not licensed 
under a permissive license? 

 I’m unaware of the history / providence of that file so was enquiring if 
anyone on the project had any more info where it come from.

Thanks,
Justin

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Justin Mclean]

Hi,

> The mentioned files should come from [1.2], which contains AL2 header.

Sure I can see that but where did the files original come from and how where 
they originally licensed?

For instance I can see the same(?) file here without an ASF header [1]

Thanks,
Justin

1. https://github.com/redpony/cdec/blob/master/training/utils/sentclient.cc
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE][CANCEL]: Apache Weex-incubating Release 0.12.0-RC4

[sospartan]

HI,
We'll cancel this vote and start a new RC later.

-- 
Best Regards!

sospartan
http://weex.apache.org/ 

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Tommaso Teofili]

thanks Justin for your vote.

The mentioned files should come from [1.2], which contains AL2 header.
When building Joshua you may found the compiled binaries, but they are not
shipped together with the source release; so if I understand things
correctly we should be fine.

Regards,
Tommaso

[1] :
https://github.com/apache/incubator-joshua/blob/master/scripts/training/parallelize/sentserver.c
[2] :
https://github.com/apache/incubator-joshua/blob/master/scripts/training/parallelize/sentclient.c


Il giorno gio 1 giu 2017 alle ore 03:29 Justin Mclean <
jus...@classsoftware.com> ha scritto:

> Hi,
>
> +1 binding
>
> I checked:
> - name includes incubating
> - signatures and hashes correct
> - disclaimer exists
> - LICENSE is OK
> - NOTICE contains wrong year please fix
> - no unexpected binary files
> - source files have ASF headers
> - can compile from source
>
> I’m curious to know where these files come from [1][2]. I found them
> elsewhere without Apache headers but was unable to find how they were
> licensed.
>
> Thanks,
> Justin
>
> 1. ./scripts/training/parallelize/sentclient.c
> 2../scripts/training/parallelize/sentserver.c
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>