Re: [VOTE] Release of Apache Griffin 0.1.5-incubating [rc1]

[William Guo]

hi Justin,


> You also need to ask those some question about the test data files pointed 
> out in the last RC.


We have removed  demo-purposed test data files, just keep sample data for unit 
tests.



Thanks,

William


From: Justin Mclean 
Sent: Tuesday, July 4, 2017 12:23:41 PM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release of Apache Griffin 0.1.5-incubating [rc1]

Hi,

> We made big change since we bundled some 3rd party sources in our artifacts 
> before, which was not right,
> so, we remove those JavaScript files(toaster, charts, etc).

It fine to bundle things as long as the ASF license policy is followed.

> We are not good at license issue, what is your advice for following two cases?

Your mentors should be able to help you here but I’ll answer as well.

> 1 Not sure where this is right way to handle those JavaScript dependencies 
> license issue as above.

You need to add tree view MIT license info to the LICENSE file if it is 
bundled. [1] I would just remove LICENSE.md as it’s not correct and it easier 
to keep one file up to date than two but that’s up to you.

> 2 How to handle background.jpg?

In order to know that you need to find answers to the following. Where did the 
file come from? Who owns the copyright on it and how is it licensed? Do you 
have permission to use and distribute it?

You also need to ask those some question about the test data files pointed out 
in the last RC.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release of Apache Griffin 0.1.5-incubating [rc1]

[Justin Mclean]

Hi,

> We made big change since we bundled some 3rd party sources in our artifacts 
> before, which was not right, 
> so, we remove those JavaScript files(toaster, charts, etc).

It fine to bundle things as long as the ASF license policy is followed.

> We are not good at license issue, what is your advice for following two cases?

Your mentors should be able to help you here but I’ll answer as well.

> 1 Not sure where this is right way to handle those JavaScript dependencies 
> license issue as above.

You need to add tree view MIT license info to the LICENSE file if it is 
bundled. [1] I would just remove LICENSE.md as it’s not correct and it easier 
to keep one file up to date than two but that’s up to you.

> 2 How to handle background.jpg?

In order to know that you need to find answers to the following. Where did the 
file come from? Who owns the copyright on it and how is it licensed? Do you 
have permission to use and distribute it?

You also need to ask those some question about the test data files pointed out 
in the last RC.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release of Apache Griffin 0.1.5-incubating [rc1]

[William Guo]

--sorry, use my Apache account and sent it again.


Hi Justin,

Thanks a lot for your checking.

Ok, we will strictly follow license name to make it as License.

We made big change since we bundled some 3rd party sources in our artifacts 
before, which was not right,
so, we remove those JavaScript files(toaster, charts, etc).
Those dependencies, declared in bower.js, will be installed when deploying in 
user box.

We are not good at license issue, what is your advice for following two cases?

1 Not sure where this is right way to handle those JavaScript dependencies 
license issue as above.
2 How to handle background.jpg?

Will remove asf header in treeview.js.

Will file a ticket for this license thread.


William


From: William GUO 
Sent: Tuesday, July 4, 2017 12:09:15 PM
To: general@incubator.apache.org
Cc: d...@griffin.incubator.apache.org
Subject: Re: [VOTE] Release of Apache Griffin 0.1.5-incubating [rc1]

Hi Justin,

Thanks a lot for your checking.

Ok, we will strictly follow license name to make it as License.

We made big change since we bundled some 3rd party sources in our artifacts 
before, which was not right,
so, we remove those JavaScript files(toaster, charts, etc).
Those dependencies, declared in bower.js, will be installed when deploying in 
user box.

We are not good at license issue, what is your advice for following two cases?

1 Not sure where this is right way to handle those JavaScript dependencies 
license issue as above.
2 How to handle background.jpg?

Will remove asf header in treeview.js.

Will file a ticket for this license thread.


William

On 7/4/17, 9:55 AM, "Justin Mclean"  wrote:

Hi,

Sorry  -1 as the LICENSE file has not been fixed from last RC. The LICENSE 
file needs to be called LICENSE or LICENSE.txt and contain all 3rd party 
bundled licenses. [1][2] I’ll consider changing my vote if other IPMC members 
vote +1 on this and it fixed in the next release.

I can see that LICENSE doesn’t contain any mention of 3rd party bundled 
code and that they are instead mentioned in LICENSE.md.

I can see that LICENSE.md refers to 3rd party software that is no longer 
bundled in this RC i.e. angular toaster, charts, font awesome etc ect

In fact it seems just about all 3rd party software has been removed except 
for [4] which incorrectly has an ASF header and is MIT licensed. Why the big 
change from last time? IS there any reason all this 3rd party software is no 
longer required?

I checked:
- name includes incubating
- signature and hashes good
- LICENSE has issues (see above)
- NOTICE is good
- no unexpected binary
- source files have ASF headers
- don’t check compile form source due to complex requirements/setup

There are a couple of unresolved issues from the last RC - including for 
instance who own copyright on this file? [3] Has a JIRA been raised to sort 
these out?

Thanks,
Justin

1. http://www.apache.org/dev/apply-license.html#license-file-name
2. http://www.apache.org/legal/release-policy.html#license-file
3.  ./ui/login/background.jpg
4. ./ui/js/directives/treeview.js
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release of Apache Griffin 0.1.5-incubating [rc1]

[William GUO]

Hi Justin,

Thanks a lot for your checking.

Ok, we will strictly follow license name to make it as License.

We made big change since we bundled some 3rd party sources in our artifacts 
before, which was not right, 
so, we remove those JavaScript files(toaster, charts, etc).
Those dependencies, declared in bower.js, will be installed when deploying in 
user box. 

We are not good at license issue, what is your advice for following two cases?

1 Not sure where this is right way to handle those JavaScript dependencies 
license issue as above.
2 How to handle background.jpg?

Will remove asf header in treeview.js.

Will file a ticket for this license thread.


William

On 7/4/17, 9:55 AM, "Justin Mclean"  wrote:

Hi,

Sorry  -1 as the LICENSE file has not been fixed from last RC. The LICENSE 
file needs to be called LICENSE or LICENSE.txt and contain all 3rd party 
bundled licenses. [1][2] I’ll consider changing my vote if other IPMC members 
vote +1 on this and it fixed in the next release.

I can see that LICENSE doesn’t contain any mention of 3rd party bundled 
code and that they are instead mentioned in LICENSE.md.

I can see that LICENSE.md refers to 3rd party software that is no longer 
bundled in this RC i.e. angular toaster, charts, font awesome etc ect

In fact it seems just about all 3rd party software has been removed except 
for [4] which incorrectly has an ASF header and is MIT licensed. Why the big 
change from last time? IS there any reason all this 3rd party software is no 
longer required?

I checked:
- name includes incubating
- signature and hashes good
- LICENSE has issues (see above)
- NOTICE is good
- no unexpected binary
- source files have ASF headers
- don’t check compile form source due to complex requirements/setup

There are a couple of unresolved issues from the last RC - including for 
instance who own copyright on this file? [3] Has a JIRA been raised to sort 
these out?

Thanks,
Justin

1. http://www.apache.org/dev/apply-license.html#license-file-name
2. http://www.apache.org/legal/release-policy.html#license-file
3.  ./ui/login/background.jpg
4. ./ui/js/directives/treeview.js
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release of Apache Griffin 0.1.5-incubating [rc1]

[Justin Mclean]

Hi,

Sorry  -1 as the LICENSE file has not been fixed from last RC. The LICENSE file 
needs to be called LICENSE or LICENSE.txt and contain all 3rd party bundled 
licenses. [1][2] I’ll consider changing my vote if other IPMC members vote +1 
on this and it fixed in the next release.

I can see that LICENSE doesn’t contain any mention of 3rd party bundled code 
and that they are instead mentioned in LICENSE.md.

I can see that LICENSE.md refers to 3rd party software that is no longer 
bundled in this RC i.e. angular toaster, charts, font awesome etc ect

In fact it seems just about all 3rd party software has been removed except for 
[4] which incorrectly has an ASF header and is MIT licensed. Why the big change 
from last time? IS there any reason all this 3rd party software is no longer 
required?

I checked:
- name includes incubating
- signature and hashes good
- LICENSE has issues (see above)
- NOTICE is good
- no unexpected binary
- source files have ASF headers
- don’t check compile form source due to complex requirements/setup

There are a couple of unresolved issues from the last RC - including for 
instance who own copyright on this file? [3] Has a JIRA been raised to sort 
these out?

Thanks,
Justin

1. http://www.apache.org/dev/apply-license.html#license-file-name
2. http://www.apache.org/legal/release-policy.html#license-file
3.  ./ui/login/background.jpg
4. ./ui/js/directives/treeview.js
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Guidance on copyrights in sample code.

[Justin Mclean]

Hi,

> That's actually why I asked James to pose the question on the general
> list.  I wasn't particularly sure if he found the right file, based on the
> comments made by Justin and was hoping Justin could speak up to explain why
> it is or isn't an issue

I believe it wasn’t this example but that there were copyright lines in ASF 
headers - see [1].

Sorry but I’ve since deleted the RC I downloaded and it doesn’t look to be 
available anymore so not 100% were it was.

Thanks,
Justin

1. https://www.apache.org/legal/src-headers.html#headers
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Guidance on copyrights in sample code.

[Craig Russell]

> On Jul 3, 2017, at 5:08 PM, James Bognar  wrote:
> 
> Hrm...that sort of complicates the example.
> 
> Here's the example code that creates an Atom feed DTO with a copyright...
> 
File file = new File("fileName");
Charset charset = Charset.forName("utf-8");
// read the copyright notice from the file into the copyrightNotice string
String copyrightNotice =
org.apache.commons.io.FileUtils.readFileToString(file, charset);

> Feed f = new Feed()
>   ...
>   .rights(copyrightNotice);
>   ...
> 
> 
> How about just "Copyright (c) ..."?

My understanding of the problem is that RAT reports that there is a copyright 
notice in the code.

Craig
> 
> 
> On Mon, Jul 3, 2017 at 8:02 PM, Craig Russell  wrote:
> 
>> Hi James,
>> 
>> Instead of including "Copyright (c) 2001, Apache Foobar Foundation" in the
>> sample code, would it be possible/easy to "assume the copyright notice is
>> in a file and include the file contents here".
>> 
>> That is probably how you would want to do it anyway, considering the task
>> of updating copyright years should be limited to one file per distribution
>> in downstream users, similar to the single copyright notice that an Apache
>> project has in its distribution.
>> 
>> Craig
>> 
>>> On Jul 3, 2017, at 2:37 PM, James Bognar  wrote:
>>> 
>>> Need some quick guidance.
>>> 
>>> On the release vote for Juneau 6.3.0, Justin Mclean made this note...
>>> "There's a number of "Copyright (c) 2016, Apache Foundation” in the
>>> documentation you may want to update the year."
>>> 
>>> I tracked it down to sample code where the copyright statement itself was
>>> sample code.  (i.e. showing how to create an ATOM feed with an embedded
>>> copyright statement).
>>> 
>>> Can I change it to the following so that it's not flagged in the future?
>>> 
>>> "Copyright (c) 2001, Apache Foobar Foundation”
>>> 
>>> Or better ideas?
>> 
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> c...@apache.org http://db.apache.org/jdo
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


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

Re: Guidance on copyrights in sample code.

[James Bognar]

Hrm...that sort of complicates the example.

Here's the example code that creates an Atom feed DTO with a copyright...

Feed f = new Feed()
   ...
   .rights("Copyright (c) 2016, Apache Foundation")
   ...


How about just "Copyright (c) ..."?


On Mon, Jul 3, 2017 at 8:02 PM, Craig Russell  wrote:

> Hi James,
>
> Instead of including "Copyright (c) 2001, Apache Foobar Foundation" in the
> sample code, would it be possible/easy to "assume the copyright notice is
> in a file and include the file contents here".
>
> That is probably how you would want to do it anyway, considering the task
> of updating copyright years should be limited to one file per distribution
> in downstream users, similar to the single copyright notice that an Apache
> project has in its distribution.
>
> Craig
>
> > On Jul 3, 2017, at 2:37 PM, James Bognar  wrote:
> >
> > Need some quick guidance.
> >
> > On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> > "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> > documentation you may want to update the year."
> >
> > I tracked it down to sample code where the copyright statement itself was
> > sample code.  (i.e. showing how to create an ATOM feed with an embedded
> > copyright statement).
> >
> > Can I change it to the following so that it's not flagged in the future?
> >
> > "Copyright (c) 2001, Apache Foobar Foundation”
> >
> > Or better ideas?
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Guidance on copyrights in sample code.

[Craig Russell]

Hi James,

Instead of including "Copyright (c) 2001, Apache Foobar Foundation" in the 
sample code, would it be possible/easy to "assume the copyright notice is in a 
file and include the file contents here". 

That is probably how you would want to do it anyway, considering the task of 
updating copyright years should be limited to one file per distribution in 
downstream users, similar to the single copyright notice that an Apache project 
has in its distribution.

Craig

> On Jul 3, 2017, at 2:37 PM, James Bognar  wrote:
> 
> Need some quick guidance.
> 
> On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> documentation you may want to update the year."
> 
> I tracked it down to sample code where the copyright statement itself was
> sample code.  (i.e. showing how to create an ATOM feed with an embedded
> copyright statement).
> 
> Can I change it to the following so that it's not flagged in the future?
> 
> "Copyright (c) 2001, Apache Foobar Foundation”
> 
> Or better ideas?

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


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

Re: [VOTE] Release Apache Airflow 1.8.2 (incubating)

[John D. Ament]

Hi,

I have a few questions about the release contents.

I ran RAT, and found many unapproved files.  Are you maybe missing a few
things from your rat excludes?  https://paste.apache.org/jBql is the report
I got (ignore rat-output, it's the file I was piping to).  Note that there
is no rat-excludes file in the distribution yet there is one in the git
repo.  Also, I cannot follow the instructions in the email to run rat which
points to "sh scripts/ci/check-license.sh" which doesn't exist in the
release.

In addition, comparing the release contents to your git repository, are you
sure this is your source release and not your bdist (in pypi terms)?  While
its good to have the convenience binary around, we're looking to review and
approve the source release for compliance.  I've been working with the
AriaTosca podling, we've come up with a process to create the source
release, sdist and bdist that would be distributed via pypi.

John



On Mon, Jul 3, 2017 at 6:56 PM Maxime Beauchemin 
wrote:

> Hello Incubator PMC’ers,
>
> The Apache Airflow community has voted and approved the proposal to release
> Apache Airflow 1.8.2 (incubating) based on 1.8.2 Release Candidate 2. We
> now kindly request the Incubator PMC members to review and vote on this
> incubator release. If the vote is successful we will rename release
> candidate 2 to final.
>
> Airflow is a platform to programmatically author, schedule and monitor
> workflows. Use airflow to author workflows as directed acyclic graphs
> (DAGs) of tasks. The airflow scheduler executes your tasks on an array of
> workers while following the specified dependencies. Rich command line
> utilities make performing complex surgeries on DAGs a snap. The rich user
> interface makes it easy to visualize pipelines running in production,
> monitor progress, and troubleshoot issues when needed. When workflows are
> defined as code, they become more maintainable, versionable, testable, and
> collaborative.
>
> The Apache Airflow-1.8.2-incubating release candidate is now available with
> the following artifacts for a project vote:
>
> * [VOTE] Thread:*
> *
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201706.mbox/%3CCAHEEp7XRRk__hGUMjOCw%2BTW0Gc--78qEewcsAsQBLrv1x6j71w%40mail.gmail.com%3E
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201706.mbox/%3CCAHEEp7XRRk__hGUMjOCw%2BTW0Gc--78qEewcsAsQBLrv1x6j71w%40mail.gmail.com%3E
> >*
>
> TODO
>
> *The release candidate(s) to be voted on is available at:*
> https://dist.apache.org/repos/dist/dev/incubator/airflow/ or
> *
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz
> >*
>
> *Git branch*
> https://github.com/apache/incubator-airflow/tree/v1-8-test or
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-test
>
> *Git tag*
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=refs/tags/1.8.2rc2
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=refs/tags/1.8.2rc2
> >*
>
> *PGP signature*
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.asc
>
> *MD5/SHA Hashes*
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.md5
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.sha
>
> *Keys to verify the signature of the release artifacts are available at:*
> https://dist.apache.org/repos/dist/release/incubator/airflow/
>
> * RAT License checks*
>
> RAT is executed as part of the CI process (e.g.
> https://travis-ci.org/apache/incubator-airflow/builds/226568140) but can
> also be run manually by issuing “sh scripts/ci/check-license.sh” from the
> top level.
>
> Source code is always included, i.e. there is no binary release.
> Compilation and installation will happen by standard Python practices, e.g.
> pip install <> or python setup.py install.
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Members please be sure to indicate "(Binding)" with your vote which will
> help in tallying the vote(s).
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> *Here is my +1 (non-binding)*
>
> Cheers,
>
> Max
>

Re: Guidance on copyrights in sample code.

[James Bognar]

> Also, why make the example strange? Why not take a real copyright header
> for an example?

A real copyright header can be mistaken for an actual copyright which gets
flagged during releases.


On Mon, Jul 3, 2017 at 7:52 PM, Ted Dunning  wrote:

> On Jul 3, 2017 3:43 PM, "John D. Ament"  wrote:
>
> On Mon, Jul 3, 2017 at 6:28 PM Ted Dunning  wrote:
>
> > That's confusing. Here are some questions and thoughts.
> >
> ...
> >
> >
>
>
>
> wouldn't get flagged.  I had posed on the list "1955 - 1971, Fake Atom
> Enterprises" which obviously would be an invalid copyright used only for
> demonstration purposes.  (for those unfamiliar, US Copyright law started in
> 1976, entities prior to that date wouldn't have been valid).
>
>
> US copyright laws started with authorization in the Constitution followed
> by enabling legislation shortly after Independence.
>
> US laws *changed* several times after that point. A particularly big change
> occurred in 1989 when the US entered the Berne convention by passing
> implementing legislation.
>
> Not sure what you could be thinking relative to 1976.
>
> Also, why make the example strange? Why not take a real copyright header
> for an example?
>
>
>
> >
> > On Jul 3, 2017 2:38 PM, "James Bognar"  wrote:
> >
> > > Need some quick guidance.
> > >
> > > On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> > > "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> > > documentation you may want to update the year."
> > >
> > > I tracked it down to sample code where the copyright statement itself
> was
> > > sample code.  (i.e. showing how to create an ATOM feed with an embedded
> > > copyright statement).
> > >
> > > Can I change it to the following so that it's not flagged in the
> future?
> > >
> > > "Copyright (c) 2001, Apache Foobar Foundation”
> > >
> > > Or better ideas?
> > >
> >
>

Re: Guidance on copyrights in sample code.

[Ted Dunning]

On Jul 3, 2017 3:43 PM, "John D. Ament"  wrote:

On Mon, Jul 3, 2017 at 6:28 PM Ted Dunning  wrote:

> That's confusing. Here are some questions and thoughts.
>
...
>
>



wouldn't get flagged.  I had posed on the list "1955 - 1971, Fake Atom
Enterprises" which obviously would be an invalid copyright used only for
demonstration purposes.  (for those unfamiliar, US Copyright law started in
1976, entities prior to that date wouldn't have been valid).


US copyright laws started with authorization in the Constitution followed
by enabling legislation shortly after Independence.

US laws *changed* several times after that point. A particularly big change
occurred in 1989 when the US entered the Berne convention by passing
implementing legislation.

Not sure what you could be thinking relative to 1976.

Also, why make the example strange? Why not take a real copyright header
for an example?



>
> On Jul 3, 2017 2:38 PM, "James Bognar"  wrote:
>
> > Need some quick guidance.
> >
> > On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> > "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> > documentation you may want to update the year."
> >
> > I tracked it down to sample code where the copyright statement itself
was
> > sample code.  (i.e. showing how to create an ATOM feed with an embedded
> > copyright statement).
> >
> > Can I change it to the following so that it's not flagged in the future?
> >
> > "Copyright (c) 2001, Apache Foobar Foundation”
> >
> > Or better ideas?
> >
>

Re: Guidance on copyrights in sample code.

[James Bognar]

Yes...to clarify, it's not a real copyright.  It's an example of a
copyright.

So the question is what copyright should I use so that it's not mistaken
for a real copyright.


On Mon, Jul 3, 2017 at 6:43 PM, John D. Ament  wrote:

> On Mon, Jul 3, 2017 at 6:28 PM Ted Dunning  wrote:
>
> > That's confusing. Here are some questions and thoughts.
> >
> > A) 2001?
> >
> > B) the only Apache foundation is the Apache software foundation. What did
> > you mean by foobar?
> >
> > C) you don't need a copyright notice on code included in the
> documentation.
> > Save that for the copy of the sample code that you put into a separate
> > file.
> >
> >
> That's actually why I asked James to pose the question on the general
> list.  I wasn't particularly sure if he found the right file, based on the
> comments made by Justin and was hoping Justin could speak up to explain why
> it is or isn't an issue, and if there's a way to include a sample atom that
> wouldn't get flagged.  I had posed on the list "1955 - 1971, Fake Atom
> Enterprises" which obviously would be an invalid copyright used only for
> demonstration purposes.  (for those unfamiliar, US Copyright law started in
> 1976, entities prior to that date wouldn't have been valid).
>
>
> >
> > On Jul 3, 2017 2:38 PM, "James Bognar"  wrote:
> >
> > > Need some quick guidance.
> > >
> > > On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> > > "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> > > documentation you may want to update the year."
> > >
> > > I tracked it down to sample code where the copyright statement itself
> was
> > > sample code.  (i.e. showing how to create an ATOM feed with an embedded
> > > copyright statement).
> > >
> > > Can I change it to the following so that it's not flagged in the
> future?
> > >
> > > "Copyright (c) 2001, Apache Foobar Foundation”
> > >
> > > Or better ideas?
> > >
> >
>

[VOTE] Release Apache Airflow 1.8.2 (incubating)

[Maxime Beauchemin]

Hello Incubator PMC’ers,

The Apache Airflow community has voted and approved the proposal to release
Apache Airflow 1.8.2 (incubating) based on 1.8.2 Release Candidate 2. We
now kindly request the Incubator PMC members to review and vote on this
incubator release. If the vote is successful we will rename release
candidate 2 to final.

Airflow is a platform to programmatically author, schedule and monitor
workflows. Use airflow to author workflows as directed acyclic graphs
(DAGs) of tasks. The airflow scheduler executes your tasks on an array of
workers while following the specified dependencies. Rich command line
utilities make performing complex surgeries on DAGs a snap. The rich user
interface makes it easy to visualize pipelines running in production,
monitor progress, and troubleshoot issues when needed. When workflows are
defined as code, they become more maintainable, versionable, testable, and
collaborative.

The Apache Airflow-1.8.2-incubating release candidate is now available with
the following artifacts for a project vote:

* [VOTE] Thread:*
*http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201706.mbox/%3CCAHEEp7XRRk__hGUMjOCw%2BTW0Gc--78qEewcsAsQBLrv1x6j71w%40mail.gmail.com%3E
*

TODO

*The release candidate(s) to be voted on is available at:*
https://dist.apache.org/repos/dist/dev/incubator/airflow/ or
*https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz
*

*Git branch*
https://github.com/apache/incubator-airflow/tree/v1-8-test or
https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-test

*Git tag*
*https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=refs/tags/1.8.2rc2
*

*PGP signature*
https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.asc

*MD5/SHA Hashes*
https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.md5
https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.sha

*Keys to verify the signature of the release artifacts are available at:*
https://dist.apache.org/repos/dist/release/incubator/airflow/

* RAT License checks*

RAT is executed as part of the CI process (e.g.
https://travis-ci.org/apache/incubator-airflow/builds/226568140) but can
also be run manually by issuing “sh scripts/ci/check-license.sh” from the
top level.

Source code is always included, i.e. there is no binary release.
Compilation and installation will happen by standard Python practices, e.g.
pip install <> or python setup.py install.

The vote will be open for at least 72 hours or until necessary number of
votes are reached.

Members please be sure to indicate "(Binding)" with your vote which will
help in tallying the vote(s).

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

*Here is my +1 (non-binding)*

Cheers,

Max

Re: Guidance on copyrights in sample code.

[John D. Ament]

On Mon, Jul 3, 2017 at 6:28 PM Ted Dunning  wrote:

> That's confusing. Here are some questions and thoughts.
>
> A) 2001?
>
> B) the only Apache foundation is the Apache software foundation. What did
> you mean by foobar?
>
> C) you don't need a copyright notice on code included in the documentation.
> Save that for the copy of the sample code that you put into a separate
> file.
>
>
That's actually why I asked James to pose the question on the general
list.  I wasn't particularly sure if he found the right file, based on the
comments made by Justin and was hoping Justin could speak up to explain why
it is or isn't an issue, and if there's a way to include a sample atom that
wouldn't get flagged.  I had posed on the list "1955 - 1971, Fake Atom
Enterprises" which obviously would be an invalid copyright used only for
demonstration purposes.  (for those unfamiliar, US Copyright law started in
1976, entities prior to that date wouldn't have been valid).


>
> On Jul 3, 2017 2:38 PM, "James Bognar"  wrote:
>
> > Need some quick guidance.
> >
> > On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> > "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> > documentation you may want to update the year."
> >
> > I tracked it down to sample code where the copyright statement itself was
> > sample code.  (i.e. showing how to create an ATOM feed with an embedded
> > copyright statement).
> >
> > Can I change it to the following so that it's not flagged in the future?
> >
> > "Copyright (c) 2001, Apache Foobar Foundation”
> >
> > Or better ideas?
> >
>

Re: Guidance on copyrights in sample code.

[Ted Dunning]

That's confusing. Here are some questions and thoughts.

A) 2001?

B) the only Apache foundation is the Apache software foundation. What did
you mean by foobar?

C) you don't need a copyright notice on code included in the documentation.
Save that for the copy of the sample code that you put into a separate
file.


On Jul 3, 2017 2:38 PM, "James Bognar"  wrote:

> Need some quick guidance.
>
> On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> documentation you may want to update the year."
>
> I tracked it down to sample code where the copyright statement itself was
> sample code.  (i.e. showing how to create an ATOM feed with an embedded
> copyright statement).
>
> Can I change it to the following so that it's not flagged in the future?
>
> "Copyright (c) 2001, Apache Foobar Foundation”
>
> Or better ideas?
>

Re: Edit Access to the Wiki

[Dave Fisher]

Hi John,

Thanks. I will go with the new account and we can ignore the old one.

Regards,
Dave

> On Jul 3, 2017, at 1:05 PM, John D. Ament  wrote:
> 
> Added.
> 
> FWIW, there was a "David Fisher" account listed as well.  It wasn't
> properly bracketed, so it wouldn't have worked.  I can fix that one if you
> want, or just ignore it.
> 
> On Mon, Jul 3, 2017 at 2:13 PM Dave Fisher  wrote:
> 
>> Hi -
>> 
>> I lost track of my prior MoinMoin Wiki account and created a new one.
>> 
>> Please grant DavidFisher access to Edit the Incubator Wiki.
>> 
>> (My old one seems to be named "c-67-180-51-144” in the logs.)
>> 
>> Thanks and Regards,
>> Dave
>> 



signature.asc
Description: Message signed with OpenPGP

Guidance on copyrights in sample code.

[James Bognar]

Need some quick guidance.

On the release vote for Juneau 6.3.0, Justin Mclean made this note...
"There's a number of "Copyright (c) 2016, Apache Foundation” in the
documentation you may want to update the year."

I tracked it down to sample code where the copyright statement itself was
sample code.  (i.e. showing how to create an ATOM feed with an embedded
copyright statement).

Can I change it to the following so that it's not flagged in the future?

"Copyright (c) 2001, Apache Foobar Foundation”

Or better ideas?

Re: [DISCUSS] Fluo graduation as TLP

[Christopher]

On Mon, Jul 3, 2017 at 4:23 PM John D. Ament  wrote:

> Oh hmm did a bit more digging.
>
> Looks like you did add someone, but I guess due to timing it was missed in
> the last board report? Then nevermind, ignore my 2nd bullet point.
>
>
Correct. This was due to timing. If we don't graduate by then, the new
committer will appear on our next report. (And will appear on our first
board report if we do graduate.) Our podling status page does include him,
however.


> John
>
> On Mon, Jul 3, 2017 at 4:15 PM John D. Ament 
> wrote:
>
> > Hi Christopher,
> >
> > Thanks for the heads up.  A few nits on my part, but overall I would be
> > happy to see Fluo graduate.  When reading my notes, please also consult
> the
> > graduation guide at [1].
> >
> > - The discussion and vote should have happened on your public dev list,
> > not private.  It's good that at least discussion happened publicly, and
> the
> > actual vote isn't required so it's not a big deal.
> > - I don't see any sign that you added new committers or PPMC members
> since
> > incubating.  See also [2].  I don't see that as a show stopper, as it
> looks
> > like a diverse group.
>

It's not as diverse as we'd like. We recognize this and really want to do
better. This was raised in our DISCUSS thread, but it seems agreed that
remaining in Incubation is not going to help this situation much. It will
be something we will continue to work on, regardless, and something we'd
include in our board reports as a TLP.


> > - Of the proposed PMC, how many are actively committing to Fluo?  Was
> > there an ask at any point to see who was still interested?
>

At least three are actively committing. An additional one (myself) helps
out more with code reviews, build system maintenance, bug reports, and
releases rather than coding. At least one of the mentors was active with
reading issues and participating in discussions. Two others have mainly
been acting only as mentors.

I'm not sure I understand your second question.


> > - Only one mentor voted on the graduation.  Would be great to see if the
> > other mentors are equally on board.
> >
>

I don't want to speak for them, but to summarize what's in the podling
VOTE/DISCUSS threads: only one formally voted in the VOTE thread, but one
more gave their enthusiastic +1 in the DISCUSS thread. The third expressed
some hesitation based on the size of the community (see my response about
diversity/size above), but seemed to accept the argument I made in that
thread for us continuing to work on this and include our progress in our
regular board reports as a TLP.


> > John
> >
> > [1]: http://incubator.apache.org/guides/graduation.html#toplevel
> > [2]: https://whimsy.apache.org/board/minutes/Fluo
> >
> >
> > On Mon, Jul 3, 2017 at 2:12 PM Christopher  wrote:
> >
> >> Greetings Incubator,
> >>
> >> The Fluo podling has decided to pursue graduation to a TLP. The result
> of
> >> the internal PPMC vote is at [1] (apologies that it occurred on our
> >> private
> >> list instead of on our dev list; the discuss thread [2] which preceded
> it
> >> did occur on the dev list). Our podling status page has recently been
> >> updated and can be found here[3].
> >>
> >> Below, you can view the proposed TLP resolution which we'd like to
> present
> >> to the board with the support of the IPMC, after sufficient discussion
> >> here
> >> and subsequent IPMC vote.
> >>
> >> [1]:
> >>
> >>
> https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
> >> [2]:
> >>
> >>
> https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
> >> [3]: https://incubator.apache.org/projects/fluo
> >>
> >> **
> >> Establish the Apache Fluo 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 the storage and incremental processing of large data sets.
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Fluo Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >>
> >> RESOLVED, that the Apache Fluo Project be and hereby is responsible for
> >> the creation and maintenance of software related to the storage and
> >> incremental processing of large data sets; and be it further
> >>
> >> RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo Project, and to
> >> have primary responsibility for management of the 

RE: Edit access to wiki for Rya project report

[Lotts, David]

John,
I assume that it does not share my password from id.apache.org
I just noticed the "create account" , and now I did that with "dlotts", and I 
can edit!
Thanks!
david.

-Original Message-
From: John D. Ament [mailto:johndam...@apache.org] 
Sent: Monday, July 03, 2017 4:06 PM
To: general@incubator.apache.org
Subject: Re: Edit access to wiki for Rya project report

Added, but just to confirm wiki is a separate registration and is not 
necessarily your ASF user id.

On Mon, Jul 3, 2017 at 2:04 PM David Lotts  wrote:

> Can someone give me edit access to the wiki for incubator reports?
> I'd like to submit one for Rya. Username is:
>
> dlotts
>
> Thanks,
> david lotts.
>

[RESULT] Retire Sirona (was Re: [VOTE] Retire Sirona)

[John D. Ament]

All,

The vote to retire Sirona passes with 7 +1's to retire (6 from IPMC
members).

I'll move forward on getting the infra tickets in and various other
paperwork post holiday.

John

On Sat, Jul 1, 2017 at 12:48 AM Jean-Baptiste Onofré 
wrote:

> +1
>
> Regards
> JB
>
> On 06/26/2017 06:50 PM, John D. Ament wrote:
> > All,
> >
> > This is a call to vote the Sirona podling.
> >
> > A vote was called for on the dev list for Sirona [1], of which one mentor
> > commented and that's all.
> >
> > Sirona at this point is behind 6 months on reports, has shown little
> > activity since joining the incubator.  Its not clear there are 3 PPMCs
> > available for a vote if need be.  Based on the prior discussions ([2] &
> > [3]) and these items, I'd like to call for a vote and unilateral decision
> > by the IPMC to retire Sirona.
> >
> > [ ] +1 to retire Sirona
> > [ ] -1 don't retire Sirona because...
> >
> > Here is my +1.
> >
> > John
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/673daa1452150ed5ef0df4aa77f587dbac6e5a4a63670c6bf4809b17@%3Cdev.sirona.apache.org%3E
> > [2]:
> >
> https://lists.apache.org/thread.html/0a70d486680f0339bfcb4baae23c2540095fda90ca83eb414104a6fd@%3Cgeneral.incubator.apache.org%3E
> > [3]:
> >
> https://lists.apache.org/thread.html/438298290de9a3573b5e315b12e77191b27f8d91b50cf9f97e90cba8@%3Cgeneral.incubator.apache.org%3E
> >
>
> --
> 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: [DISCUSS] Fluo graduation as TLP

[John D. Ament]

Oh hmm did a bit more digging.

Looks like you did add someone, but I guess due to timing it was missed in
the last board report? Then nevermind, ignore my 2nd bullet point.

John

On Mon, Jul 3, 2017 at 4:15 PM John D. Ament  wrote:

> Hi Christopher,
>
> Thanks for the heads up.  A few nits on my part, but overall I would be
> happy to see Fluo graduate.  When reading my notes, please also consult the
> graduation guide at [1].
>
> - The discussion and vote should have happened on your public dev list,
> not private.  It's good that at least discussion happened publicly, and the
> actual vote isn't required so it's not a big deal.
> - I don't see any sign that you added new committers or PPMC members since
> incubating.  See also [2].  I don't see that as a show stopper, as it looks
> like a diverse group.
> - Of the proposed PMC, how many are actively committing to Fluo?  Was
> there an ask at any point to see who was still interested?
> - Only one mentor voted on the graduation.  Would be great to see if the
> other mentors are equally on board.
>
> John
>
> [1]: http://incubator.apache.org/guides/graduation.html#toplevel
> [2]: https://whimsy.apache.org/board/minutes/Fluo
>
>
> On Mon, Jul 3, 2017 at 2:12 PM Christopher  wrote:
>
>> Greetings Incubator,
>>
>> The Fluo podling has decided to pursue graduation to a TLP. The result of
>> the internal PPMC vote is at [1] (apologies that it occurred on our
>> private
>> list instead of on our dev list; the discuss thread [2] which preceded it
>> did occur on the dev list). Our podling status page has recently been
>> updated and can be found here[3].
>>
>> Below, you can view the proposed TLP resolution which we'd like to present
>> to the board with the support of the IPMC, after sufficient discussion
>> here
>> and subsequent IPMC vote.
>>
>> [1]:
>>
>> https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
>> [2]:
>>
>> https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
>> [3]: https://incubator.apache.org/projects/fluo
>>
>> **
>> Establish the Apache Fluo 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 the storage and incremental processing of large data sets.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache Fluo Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>>
>> RESOLVED, that the Apache Fluo Project be and hereby is responsible for
>> the creation and maintenance of software related to the storage and
>> incremental processing of large data sets; and be it further
>>
>> RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo Project, and to
>> have primary responsibility for management of the projects within the
>> scope of responsibility of the Apache Fluo 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 Fluo Project:
>>
>> * Billie Rinaldi 
>> * Chris McTague 
>> * Christopher Tubbs 
>> * Corey J. Nolet 
>> * Drew Farris 
>> * Josh Elser 
>> * Keith Turner 
>> * Mike Walch 
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
>> to the office of Vice President, Apache Fluo, 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 Fluo 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 Fluo Project; and be it
>> further
>>
>> RESOLVED, that the Apache Fluo Project be and hereby is tasked with the
>> migration and rationalization of the Apache Incubator Fluo podling; and
>> be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Fluo podling encumbered upon the Apache Incubator PMC are hereafter
>> discharged.
>>
>

Re: [DISCUSS] Fluo graduation as TLP

[John D. Ament]

Hi Christopher,

Thanks for the heads up.  A few nits on my part, but overall I would be
happy to see Fluo graduate.  When reading my notes, please also consult the
graduation guide at [1].

- The discussion and vote should have happened on your public dev list, not
private.  It's good that at least discussion happened publicly, and the
actual vote isn't required so it's not a big deal.
- I don't see any sign that you added new committers or PPMC members since
incubating.  See also [2].  I don't see that as a show stopper, as it looks
like a diverse group.
- Of the proposed PMC, how many are actively committing to Fluo?  Was there
an ask at any point to see who was still interested?
- Only one mentor voted on the graduation.  Would be great to see if the
other mentors are equally on board.

John

[1]: http://incubator.apache.org/guides/graduation.html#toplevel
[2]: https://whimsy.apache.org/board/minutes/Fluo

On Mon, Jul 3, 2017 at 2:12 PM Christopher  wrote:

> Greetings Incubator,
>
> The Fluo podling has decided to pursue graduation to a TLP. The result of
> the internal PPMC vote is at [1] (apologies that it occurred on our private
> list instead of on our dev list; the discuss thread [2] which preceded it
> did occur on the dev list). Our podling status page has recently been
> updated and can be found here[3].
>
> Below, you can view the proposed TLP resolution which we'd like to present
> to the board with the support of the IPMC, after sufficient discussion here
> and subsequent IPMC vote.
>
> [1]:
>
> https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
> [2]:
>
> https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
> [3]: https://incubator.apache.org/projects/fluo
>
> **
> Establish the Apache Fluo 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 the storage and incremental processing of large data sets.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Fluo Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Fluo Project be and hereby is responsible for
> the creation and maintenance of software related to the storage and
> incremental processing of large data sets; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Fluo 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 Fluo Project:
>
> * Billie Rinaldi 
> * Chris McTague 
> * Christopher Tubbs 
> * Corey J. Nolet 
> * Drew Farris 
> * Josh Elser 
> * Keith Turner 
> * Mike Walch 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
> to the office of Vice President, Apache Fluo, 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 Fluo 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 Fluo Project; and be it
> further
>
> RESOLVED, that the Apache Fluo Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Fluo podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Fluo podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: Edit access to wiki for Rya project report

[John D. Ament]

Added, but just to confirm wiki is a separate registration and is not
necessarily your ASF user id.

On Mon, Jul 3, 2017 at 2:04 PM David Lotts  wrote:

> Can someone give me edit access to the wiki for incubator reports?
> I'd like to submit one for Rya. Username is:
>
> dlotts
>
> Thanks,
> david lotts.
>

Re: Edit Access to the Wiki

[John D. Ament]

Added.

FWIW, there was a "David Fisher" account listed as well.  It wasn't
properly bracketed, so it wouldn't have worked.  I can fix that one if you
want, or just ignore it.

On Mon, Jul 3, 2017 at 2:13 PM Dave Fisher  wrote:

> Hi -
>
> I lost track of my prior MoinMoin Wiki account and created a new one.
>
> Please grant DavidFisher access to Edit the Incubator Wiki.
>
> (My old one seems to be named "c-67-180-51-144” in the logs.)
>
> Thanks and Regards,
> Dave
>

Edit Access to the Wiki

[Dave Fisher]

Hi -

I lost track of my prior MoinMoin Wiki account and created a new one.

Please grant DavidFisher access to Edit the Incubator Wiki.

(My old one seems to be named "c-67-180-51-144” in the logs.)

Thanks and Regards,
Dave


signature.asc
Description: Message signed with OpenPGP

[DISCUSS] Fluo graduation as TLP

[Christopher]

Greetings Incubator,

The Fluo podling has decided to pursue graduation to a TLP. The result of
the internal PPMC vote is at [1] (apologies that it occurred on our private
list instead of on our dev list; the discuss thread [2] which preceded it
did occur on the dev list). Our podling status page has recently been
updated and can be found here[3].

Below, you can view the proposed TLP resolution which we'd like to present
to the board with the support of the IPMC, after sufficient discussion here
and subsequent IPMC vote.

[1]:
https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
[2]:
https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
[3]: https://incubator.apache.org/projects/fluo

**
Establish the Apache Fluo 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 the storage and incremental processing of large data sets.

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

RESOLVED, that the Apache Fluo Project be and hereby is responsible for
the creation and maintenance of software related to the storage and
incremental processing of large data sets; and be it further

RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo Project, and to
have primary responsibility for management of the projects within the
scope of responsibility of the Apache Fluo 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 Fluo Project:

* Billie Rinaldi 
* Chris McTague 
* Christopher Tubbs 
* Corey J. Nolet 
* Drew Farris 
* Josh Elser 
* Keith Turner 
* Mike Walch 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
to the office of Vice President, Apache Fluo, 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 Fluo 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 Fluo Project; and be it
further

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

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

Edit access to wiki for Rya project report

[David Lotts]

Can someone give me edit access to the wiki for incubator reports?
I'd like to submit one for Rya. Username is:

dlotts

Thanks,
david lotts.

Re: svn commit: r1800695 - /incubator/public/trunk/content/podlings.xml

[John D. Ament]

Julien,

Does Heron intend to report this month (July)?

John

On Mon, Jul 3, 2017 at 12:09 PM  wrote:

> Author: julien
> Date: Mon Jul  3 16:09:08 2017
> New Revision: 1800695
>
> URL: http://svn.apache.org/viewvc?rev=1800695=rev
> Log:
> creating Heron podling
>
> Modified:
> incubator/public/trunk/content/podlings.xml
>
> Modified: incubator/public/trunk/content/podlings.xml
> URL:
> http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?rev=1800695=1800694=1800695=diff
>
> ==
> --- incubator/public/trunk/content/podlings.xml [utf-8] (original)
> +++ incubator/public/trunk/content/podlings.xml [utf-8] Mon Jul  3
> 16:09:08 2017
> @@ -1032,6 +1032,17 @@ and a set of useful extensions for this
>  Davanum Srinivas
>  
>  
> + sponsor="Incubator" startdate="2017-06-23">
> +A real-time, distributed, fault-tolerant stream
> processing engine.
> +
> +Julien Le Dem
> +
> +Jake Farrell
> +Jacques Nadeau
> +Julien Le Dem
> +P. Taylor Goetz
> +
> +
>   startdate="2009-11-05" enddate="2012-02-11">
>  HISE
>  Retired due to inactivity.
>
>
>
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
>
>

Re: Wiki Access

[John D. Ament]

Added, happy editing!

On Mon, Jul 3, 2017 at 3:30 AM Nikolai Stoilov 
wrote:

> Hello,
>
> I'd like to request write access to the Incubator wiki, so I can add the
> report for Milagro.
>
> My wiki ID is nstoilov
>
>
> Thanks,
>
> Nikolai Stoilov
> --
> Nikolai Stoilov
> NOC/Support Team Lead
> MIRACL
>

Wiki Access

[Nikolai Stoilov]

Hello,

I'd like to request write access to the Incubator wiki, so I can add the
report for Milagro.

My wiki ID is nstoilov


Thanks,

Nikolai Stoilov
-- 
Nikolai Stoilov
NOC/Support Team Lead
MIRACL