Re: Setting up Tuweni

[Antoine Toulme]

Never mind, I read the dos again and opened an infra ticket to open the git 
repository.

> On Mar 28, 2019, at 10:13 PM, Antoine Toulme  wrote:
> 
> Following up:
> 
> The DNS and LDAP requests are fulfilled. Using the self-serve portal I have 
> requested mailing lists dev, users, issues, private.
> I have requested the JIRA project creation with the key TUWENI.
> 
> I however will need help with the git repository creation:
> https://gitbox.apache.org/setup/newrepo.html 
> 
> 
> Would a mentor or someone with the appropriate credentials fill that form 
> please?
> 
> Cheers,
> 
> Antoine
> 
>> On Mar 26, 2019, at 4:43 PM, Antoine Toulme  wrote:
>> 
>> Hi all,
>> 
>> I have added Tuweni to podlings,xml [0].
>> I have also started tasks with infra to set up DNS and LDAP [1].
>> 
>> Please review and let me know if you see additional actions that may be 
>> taken.
>> 
>> I will request mailing lists, git repository and websites after DNS is 
>> granted.
>> 
>> Cheers,
>> 
>> Antoine
>> 
>> [0]: http://svn.apache.org/viewvc?view=revision&revision=1856351 
>> 
>> [1]: https://issues.apache.org/jira/browse/INFRA-18110 
>> 
>> 
> 


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

Re: Setting up Tuweni

[Antoine Toulme]

Following up:

The DNS and LDAP requests are fulfilled. Using the self-serve portal I have 
requested mailing lists dev, users, issues, private.
I have requested the JIRA project creation with the key TUWENI.

I however will need help with the git repository creation:
https://gitbox.apache.org/setup/newrepo.html 


Would a mentor or someone with the appropriate credentials fill that form 
please?

Cheers,

Antoine

> On Mar 26, 2019, at 4:43 PM, Antoine Toulme  wrote:
> 
> Hi all,
> 
> I have added Tuweni to podlings,xml [0].
> I have also started tasks with infra to set up DNS and LDAP [1].
> 
> Please review and let me know if you see additional actions that may be taken.
> 
> I will request mailing lists, git repository and websites after DNS is 
> granted.
> 
> Cheers,
> 
> Antoine
> 
> [0]: http://svn.apache.org/viewvc?view=revision&revision=1856351 
> 
> [1]: https://issues.apache.org/jira/browse/INFRA-18110 
> 
> 

Re: FYI, saved the current wiki.apache.org/incubator content to svn

[Dave Fisher]

Sent from my iPhone

>> On Mar 28, 2019, at 5:51 PM, sebb  wrote:
>> 
>>> On Thu, 28 Mar 2019 at 23:54, sebb  wrote:
>>> 
>>> On Thu, 28 Mar 2019 at 23:42, sebb  wrote:
>>> 
>>> On Thu, 28 Mar 2019 at 16:14, Bertrand Delacretaz
>>>  wrote:
 
 Hi,
 
> On Thu, Mar 28, 2019 at 4:14 PM sebb  wrote:
> ...OK to add the missing pages to the archive?...
 
 Sure - I did that quickly, too quickly apparently, thanks for fixing!
>>> 
>>> There's another issue.
>>> 
>>> wget by default downloads files with no extensions.
>>> 
>>> However there are some directories which have the same names as files, e.g.
>>> 
>>> https://wiki.apache.org/incubator/OpenOfficeProposal
>>> https://wiki.apache.org/incubator/OpenOfficeProposal/ja
>>> and
>>> https://wiki.apache.org/incubator/ProjectProposals
>>> https://wiki.apache.org/incubator/ProjectProposals/TamayaProposal
>>> 
>>> By the way there is also another TamayaProposal:
>>> 
>>> https://wiki.apache.org/incubator/TamayaProposal
>>> 
>>> Does the PMC want to fix these two clashes?
>>> An alternative is to rename the files as .html.
>> 
>> Turns out there are several more clashes which don't have obvious
>> fixes, so I will rename as .html.
> 
> OK, done, and the filenames that clashed have been added to SVN.
> 
> Would it be useful to also save the raw text versions of the pages?
> My Ruby script can easily download these.

It looks like the content that we care about is in the div with id=“page”.

> 
>> However it might be worth dropping the older TamayaProposal, i.e. the
>> one under ProjectProposals

Yes.

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


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

Re: FYI, saved the current wiki.apache.org/incubator content to svn

[sebb]

On Thu, 28 Mar 2019 at 23:54, sebb  wrote:
>
> On Thu, 28 Mar 2019 at 23:42, sebb  wrote:
> >
> > On Thu, 28 Mar 2019 at 16:14, Bertrand Delacretaz
> >  wrote:
> > >
> > > Hi,
> > >
> > > On Thu, Mar 28, 2019 at 4:14 PM sebb  wrote:
> > > > ...OK to add the missing pages to the archive?...
> > >
> > > Sure - I did that quickly, too quickly apparently, thanks for fixing!
> >
> > There's another issue.
> >
> > wget by default downloads files with no extensions.
> >
> > However there are some directories which have the same names as files, e.g.
> >
> > https://wiki.apache.org/incubator/OpenOfficeProposal
> > https://wiki.apache.org/incubator/OpenOfficeProposal/ja
> > and
> > https://wiki.apache.org/incubator/ProjectProposals
> > https://wiki.apache.org/incubator/ProjectProposals/TamayaProposal
> >
> > By the way there is also another TamayaProposal:
> >
> > https://wiki.apache.org/incubator/TamayaProposal
> >
> > Does the PMC want to fix these two clashes?
> > An alternative is to rename the files as .html.
>
> Turns out there are several more clashes which don't have obvious
> fixes, so I will rename as .html.

OK, done, and the filenames that clashed have been added to SVN.

Would it be useful to also save the raw text versions of the pages?
My Ruby script can easily download these.

> However it might be worth dropping the older TamayaProposal, i.e. the
> one under ProjectProposals
>
> > > -Bertrand
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >

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

Re: FYI, saved the current wiki.apache.org/incubator content to svn

[sebb]

On Thu, 28 Mar 2019 at 23:42, sebb  wrote:
>
> On Thu, 28 Mar 2019 at 16:14, Bertrand Delacretaz
>  wrote:
> >
> > Hi,
> >
> > On Thu, Mar 28, 2019 at 4:14 PM sebb  wrote:
> > > ...OK to add the missing pages to the archive?...
> >
> > Sure - I did that quickly, too quickly apparently, thanks for fixing!
>
> There's another issue.
>
> wget by default downloads files with no extensions.
>
> However there are some directories which have the same names as files, e.g.
>
> https://wiki.apache.org/incubator/OpenOfficeProposal
> https://wiki.apache.org/incubator/OpenOfficeProposal/ja
> and
> https://wiki.apache.org/incubator/ProjectProposals
> https://wiki.apache.org/incubator/ProjectProposals/TamayaProposal
>
> By the way there is also another TamayaProposal:
>
> https://wiki.apache.org/incubator/TamayaProposal
>
> Does the PMC want to fix these two clashes?
> An alternative is to rename the files as .html.

Turns out there are several more clashes which don't have obvious
fixes, so I will rename as .html.

However it might be worth dropping the older TamayaProposal, i.e. the
one under ProjectProposals

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

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

Re: FYI, saved the current wiki.apache.org/incubator content to svn

[sebb]

On Thu, 28 Mar 2019 at 16:14, Bertrand Delacretaz
 wrote:
>
> Hi,
>
> On Thu, Mar 28, 2019 at 4:14 PM sebb  wrote:
> > ...OK to add the missing pages to the archive?...
>
> Sure - I did that quickly, too quickly apparently, thanks for fixing!

There's another issue.

wget by default downloads files with no extensions.

However there are some directories which have the same names as files, e.g.

https://wiki.apache.org/incubator/OpenOfficeProposal
https://wiki.apache.org/incubator/OpenOfficeProposal/ja
and
https://wiki.apache.org/incubator/ProjectProposals
https://wiki.apache.org/incubator/ProjectProposals/TamayaProposal

By the way there is also another TamayaProposal:

https://wiki.apache.org/incubator/TamayaProposal

Does the PMC want to fix these two clashes?
An alternative is to rename the files as .html.

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

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

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[Marcelo Vanzin]

On Thu, Mar 28, 2019 at 3:57 PM Felix Cheung  wrote:

> I have LANG=“en_US.UTF-8”
> I tried a couple of things finally it passed when I use virtualenv - my
> python is Python 3, forcing that to Python 2 passed the test.


Hmmm, that tells me that the python 3 path in the fake shell might not be
as unicode-safe as it seems, and that this test should also be running
against python 3...

As a separate issue, things could be enhanced so that they force use of
"python2" when running the python 2 tests.

But in the spirit of "these are not regressions, just bugs", I'd rather not
block the release for that. (I filed a but for the ASCII thing already,
I'll file others for the above.)


> However, now
> another test failed (maybe connection blocked by firewall?)
>

That seems likely, if you have a local firewall? (8998 is Livy's default
port. Or maybe you have something running on that port and the tests should
be trying an ephemeral one...)


> error_msg = "Connection refused by Responses: POST
> http://machine:8998/sessions/ doesn't match Responses Mock"
> response = ConnectionError(u"Connection refused by Responses: POST
> http://machine:8998/sessions/doesn't match Responses Mock",)
>


-- 
Marcelo

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[Felix Cheung]

I have LANG=“en_US.UTF-8”
I tried a couple of things finally it passed when I use virtualenv - my
python is Python 3, forcing that to Python 2 passed the test. However, now
another test failed (maybe connection blocked by firewall?)


=== FAILURES
===
 test_create_new_session_without_default_config


def test_create_new_session_without_default_config():
> mock_and_validate_create_new_session(False)

src/test/python/livy-tests/client_test.py:105:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _
:3: in wrapper
???
src/test/python/livy-tests/client_test.py:48: in
mock_and_validate_create_new_session
load_defaults=defaults)
src/main/python/livy/client.py:88: in __init__
session_conf_dict).json()['id']
src/main/python/livy/client.py:388: in _create_new_session
headers=self._conn._JSON_HEADERS, data=data)
src/main/python/livy/client.py:500: in send_request
json=data, auth=self._spnego_auth())
.eggs/requests-2.21.0-py2.7.egg/requests/api.py:60: in request
return session.request(method=method, url=url, **kwargs)
.eggs/requests-2.21.0-py2.7.egg/requests/sessions.py:533: in request
resp = self.send(prep, **send_kwargs)
.eggs/requests-2.21.0-py2.7.egg/requests/sessions.py:646: in send
r = adapter.send(request, **kwargs)
.eggs/responses-0.10.6-py2.7.egg/responses.py:626: in unbound_on_send
return self._on_request(adapter, request, *a, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _

self = 
adapter = 
request = 
kwargs = {'cert': None, 'proxies': OrderedDict(), 'stream': False,
'timeout': 10, ...}
match = None, resp_callback = None
error_msg = "Connection refused by Responses: POST
http://machine:8998/sessions/ doesn't match Responses Mock"
response = ConnectionError(u"Connection refused by Responses: POST
http://machine:8998/sessions/doesn't match Responses Mock",)


On Thu, Mar 28, 2019 at 11:52 AM Marcelo Vanzin 
wrote:

> I can reproduce it with this:
>
>  LC_ALL=en_US.ASCII mvn -Pspark-2.4 -Pthriftserver test -pl :livy-repl_2.11
> -Dsuites=*.Python2*
>
> Seems that Livy's fake python shell expects UTF-8 when running on Python 2.
> This is not a new bug, so while we should fix it, not sure we need to fix
> it in this release.
>
>
> On Thu, Mar 28, 2019 at 11:24 AM sebb  wrote:
>
> > On Thu, 28 Mar 2019 at 17:02, Marcelo Vanzin  >
> > wrote:
> >
> > > Are you using a different encoding that UTF-8 in your environment?
> > >
> > > The source file contains unicode escapes, so that shouldn't be the
> > problem.
> > > It may be the test is expecting the output of child processes (in this
> > case
> > > the python interpreter) to be UTF-8.
> > >
> > >
> > If that is the case, then the test case ought to be fixed...
> >
> >
> > > On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung 
> > > wrote:
> > >
> > > > This test is consistently failing when I build, any idea what’s wrong
> > in
> > > my
> > > > setup?
> > > >
> > > > - should print unicode correctly *** FAILED *** (101 milliseconds)
> > > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not
> equal
> > > > ExecuteSuccess(JObject(List((text/plain,JString(☺)
> > > > (PythonInterpreterSpec.scala:272)
> > > >
> > > >
> > > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin
> > >  > > > >
> > > > wrote:
> > > >
> > > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> > > > release.
> > > > >
> > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission
> of
> > > > > Spark jobs from web/mobile apps (no Spark client needed). So,
> > multiple
> > > > > users can interact with your Spark cluster concurrently and
> reliably.
> > > > >
> > > > > Vote thread:
> > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> > > > >
> > > > > (Note I messed up the subject on the first e-mail, that thread is
> for
> > > > > the RC2 vote.)
> > > > >
> > > > > Result thread:
> > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> > > > >
> > > > > The RC is based on tag v0.6.0-incubating-rc2:
> > > > > https://github.com/apache/incubator-livy/commit/28be98cabc
> > > > >
> > > > > The release files can be found here:
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> > > > >
> > > > > The staged maven artifacts can be found here:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachelivy-1008
> > > > >
> > > > > The list of resolved JIRAs in this release can be found here:
> > > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> > > > >
> > > > > Vote will be open for at least 72 hours. Thanks!
> > > > >
> > > > > --
> > > > > Marcelo
> > > > >
> > > > >
> --

[jira] [Commented] (INCUBATOR-212) Incorrect bounce message for retired podling mailing lists

[Dave Fisher (JIRA)]

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

Dave Fisher commented on INCUBATOR-212:
---

The redirection should be https://incubator.apache.org/projects/#

For slider: https://incubator.apache.org/projects/#slider

> Incorrect bounce message for retired podling mailing lists
> --
>
> Key: INCUBATOR-212
> URL: https://issues.apache.org/jira/browse/INCUBATOR-212
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> When a podling is retired, the mailing lists are shut down.
> Mails to the lists are returned with a message which says:
> "Hi. This is the qmail-send program at apache.org.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> :
> The project is retired. See https://attic.apache.org";
> However podlings are not handled by Attic.
> The bounce message for podlings ought to be changed to something more useful.



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

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

Re: Request for Mentor

[Trevor Grant]

Looks like an awesome project, I'd be happy to help.

On Thu, Mar 28, 2019 at 1:50 PM lewis john mcgibbney 
wrote:

> Hi general@,
>
> The Apache Science Data Analytics Platform (SDAP) (Incubating) project is
> in need of an active mentor!
>
> What is SDAP?
> http://sdap.apache.org/
> SDAP is a technology software solution currently geared to better enable
> scientists involved in advancing the study of the Earth's physical
> oceanography.
> The platform is an orchestration of several previously funded NASA big
> ocean data solutions using cloud technology, which include:
>
>- data analysis (NEXUS)
>- anomaly detection (OceanXtremes)
>- matchup (DOMS)
>- subsetting
>- discovery (MUDROD)
>- visualization (VQSS)
>
> What state is the podling in?
> SDAP is working towards it's first formal release having encountered some
> issues with the initial release candidate. The Podling requires a mentor
> who can come on board and drive through the generation of Apache-compliant
> release candidates so that the project can continue to grow community
> through usage.
>
> Interested?
> Let us know by responding to this thread ensuring that you CC dev@sdap.a.o.
>
> Thank you
> Lewis
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

Re: Request for Mentor

[Gang(Gary) Wang]

It is a great valuable platform for our living environment, hope I have the
opportunity to help this project success.

Gary(Binding)



On Thu, Mar 28, 2019, 11:50 AM lewis john mcgibbney 
wrote:

> Hi general@,
>
> The Apache Science Data Analytics Platform (SDAP) (Incubating) project is
> in need of an active mentor!
>
> What is SDAP?
> http://sdap.apache.org/
> SDAP is a technology software solution currently geared to better enable
> scientists involved in advancing the study of the Earth's physical
> oceanography.
> The platform is an orchestration of several previously funded NASA big
> ocean data solutions using cloud technology, which include:
>
>- data analysis (NEXUS)
>- anomaly detection (OceanXtremes)
>- matchup (DOMS)
>- subsetting
>- discovery (MUDROD)
>- visualization (VQSS)
>
> What state is the podling in?
> SDAP is working towards it's first formal release having encountered some
> issues with the initial release candidate. The Podling requires a mentor
> who can come on board and drive through the generation of Apache-compliant
> release candidates so that the project can continue to grow community
> through usage.
>
> Interested?
> Let us know by responding to this thread ensuring that you CC dev@sdap.a.o.
>
> Thank you
> Lewis
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[Marcelo Vanzin]

I can reproduce it with this:

 LC_ALL=en_US.ASCII mvn -Pspark-2.4 -Pthriftserver test -pl :livy-repl_2.11
-Dsuites=*.Python2*

Seems that Livy's fake python shell expects UTF-8 when running on Python 2.
This is not a new bug, so while we should fix it, not sure we need to fix
it in this release.


On Thu, Mar 28, 2019 at 11:24 AM sebb  wrote:

> On Thu, 28 Mar 2019 at 17:02, Marcelo Vanzin 
> wrote:
>
> > Are you using a different encoding that UTF-8 in your environment?
> >
> > The source file contains unicode escapes, so that shouldn't be the
> problem.
> > It may be the test is expecting the output of child processes (in this
> case
> > the python interpreter) to be UTF-8.
> >
> >
> If that is the case, then the test case ought to be fixed...
>
>
> > On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung 
> > wrote:
> >
> > > This test is consistently failing when I build, any idea what’s wrong
> in
> > my
> > > setup?
> > >
> > > - should print unicode correctly *** FAILED *** (101 milliseconds)
> > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
> > > ExecuteSuccess(JObject(List((text/plain,JString(☺)
> > > (PythonInterpreterSpec.scala:272)
> > >
> > >
> > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin
> >  > > >
> > > wrote:
> > >
> > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> > > release.
> > > >
> > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > > > Spark jobs from web/mobile apps (no Spark client needed). So,
> multiple
> > > > users can interact with your Spark cluster concurrently and reliably.
> > > >
> > > > Vote thread:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> > > >
> > > > (Note I messed up the subject on the first e-mail, that thread is for
> > > > the RC2 vote.)
> > > >
> > > > Result thread:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> > > >
> > > > The RC is based on tag v0.6.0-incubating-rc2:
> > > > https://github.com/apache/incubator-livy/commit/28be98cabc
> > > >
> > > > The release files can be found here:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> > > >
> > > > The staged maven artifacts can be found here:
> > > >
> https://repository.apache.org/content/repositories/orgapachelivy-1008
> > > >
> > > > The list of resolved JIRAs in this release can be found here:
> > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> > > >
> > > > Vote will be open for at least 72 hours. Thanks!
> > > >
> > > > --
> > > > Marcelo
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > Marcelo
> >
>


-- 
Marcelo

Request for Mentor

[lewis john mcgibbney]

Hi general@,

The Apache Science Data Analytics Platform (SDAP) (Incubating) project is
in need of an active mentor!

What is SDAP?
http://sdap.apache.org/
SDAP is a technology software solution currently geared to better enable
scientists involved in advancing the study of the Earth's physical
oceanography.
The platform is an orchestration of several previously funded NASA big
ocean data solutions using cloud technology, which include:

   - data analysis (NEXUS)
   - anomaly detection (OceanXtremes)
   - matchup (DOMS)
   - subsetting
   - discovery (MUDROD)
   - visualization (VQSS)

What state is the podling in?
SDAP is working towards it's first formal release having encountered some
issues with the initial release candidate. The Podling requires a mentor
who can come on board and drive through the generation of Apache-compliant
release candidates so that the project can continue to grow community
through usage.

Interested?
Let us know by responding to this thread ensuring that you CC dev@sdap.a.o.

Thank you
Lewis

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[sebb]

On Thu, 28 Mar 2019 at 17:02, Marcelo Vanzin 
wrote:

> Are you using a different encoding that UTF-8 in your environment?
>
> The source file contains unicode escapes, so that shouldn't be the problem.
> It may be the test is expecting the output of child processes (in this case
> the python interpreter) to be UTF-8.
>
>
If that is the case, then the test case ought to be fixed...


> On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung 
> wrote:
>
> > This test is consistently failing when I build, any idea what’s wrong in
> my
> > setup?
> >
> > - should print unicode correctly *** FAILED *** (101 milliseconds)
> > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
> > ExecuteSuccess(JObject(List((text/plain,JString(☺)
> > (PythonInterpreterSpec.scala:272)
> >
> >
> > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin
>  > >
> > wrote:
> >
> > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> > release.
> > >
> > > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > > Spark jobs from web/mobile apps (no Spark client needed). So, multiple
> > > users can interact with your Spark cluster concurrently and reliably.
> > >
> > > Vote thread:
> > >
> > >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> > >
> > > (Note I messed up the subject on the first e-mail, that thread is for
> > > the RC2 vote.)
> > >
> > > Result thread:
> > >
> > >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> > >
> > > The RC is based on tag v0.6.0-incubating-rc2:
> > > https://github.com/apache/incubator-livy/commit/28be98cabc
> > >
> > > The release files can be found here:
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> > >
> > > The staged maven artifacts can be found here:
> > > https://repository.apache.org/content/repositories/orgapachelivy-1008
> > >
> > > The list of resolved JIRAs in this release can be found here:
> > > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> > >
> > > Vote will be open for at least 72 hours. Thanks!
> > >
> > > --
> > > Marcelo
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
>
> --
> Marcelo
>

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[Marcelo Vanzin]

Also is that failing when running the Python2 or the Python3 version of
that test? Maybe it doesn't work as expected in some newer version of
Python3...

On Thu, Mar 28, 2019 at 10:02 AM Marcelo Vanzin  wrote:

> Are you using a different encoding that UTF-8 in your environment?
>
> The source file contains unicode escapes, so that shouldn't be the
> problem. It may be the test is expecting the output of child processes (in
> this case the python interpreter) to be UTF-8.
>
> On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung 
> wrote:
>
>> This test is consistently failing when I build, any idea what’s wrong in
>> my
>> setup?
>>
>> - should print unicode correctly *** FAILED *** (101 milliseconds)
>> ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
>> ExecuteSuccess(JObject(List((text/plain,JString(☺)
>> (PythonInterpreterSpec.scala:272)
>>
>>
>> On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin
>> 
>> wrote:
>>
>> > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
>> release.
>> >
>> > Livy enables programmatic, fault-tolerant, multi-tenant submission of
>> > Spark jobs from web/mobile apps (no Spark client needed). So, multiple
>> > users can interact with your Spark cluster concurrently and reliably.
>> >
>> > Vote thread:
>> >
>> >
>> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
>> >
>> > (Note I messed up the subject on the first e-mail, that thread is for
>> > the RC2 vote.)
>> >
>> > Result thread:
>> >
>> >
>> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
>> >
>> > The RC is based on tag v0.6.0-incubating-rc2:
>> > https://github.com/apache/incubator-livy/commit/28be98cabc
>> >
>> > The release files can be found here:
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
>> >
>> > The staged maven artifacts can be found here:
>> > https://repository.apache.org/content/repositories/orgapachelivy-1008
>> >
>> > The list of resolved JIRAs in this release can be found here:
>> > https://issues.apache.org/jira/projects/LIVY/versions/12342736
>> >
>> > Vote will be open for at least 72 hours. Thanks!
>> >
>> > --
>> > Marcelo
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>> >
>>
>
>
> --
> Marcelo
>


-- 
Marcelo

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[Marcelo Vanzin]

Are you using a different encoding that UTF-8 in your environment?

The source file contains unicode escapes, so that shouldn't be the problem.
It may be the test is expecting the output of child processes (in this case
the python interpreter) to be UTF-8.

On Wed, Mar 27, 2019 at 10:25 PM Felix Cheung 
wrote:

> This test is consistently failing when I build, any idea what’s wrong in my
> setup?
>
> - should print unicode correctly *** FAILED *** (101 milliseconds)
> ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
> ExecuteSuccess(JObject(List((text/plain,JString(☺)
> (PythonInterpreterSpec.scala:272)
>
>
> On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin  >
> wrote:
>
> > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> release.
> >
> > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > Spark jobs from web/mobile apps (no Spark client needed). So, multiple
> > users can interact with your Spark cluster concurrently and reliably.
> >
> > Vote thread:
> >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> >
> > (Note I messed up the subject on the first e-mail, that thread is for
> > the RC2 vote.)
> >
> > Result thread:
> >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> >
> > The RC is based on tag v0.6.0-incubating-rc2:
> > https://github.com/apache/incubator-livy/commit/28be98cabc
> >
> > The release files can be found here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> >
> > The staged maven artifacts can be found here:
> > https://repository.apache.org/content/repositories/orgapachelivy-1008
> >
> > The list of resolved JIRAs in this release can be found here:
> > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> >
> > Vote will be open for at least 72 hours. Thanks!
> >
> > --
> > Marcelo
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


-- 
Marcelo

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[sebb]

On Thu, 28 Mar 2019 at 15:42, Felix Cheung  wrote:

> I see, thanks. Perhaps the way I unzip the src zip file then. Is it a
> better approach to unpack it?
>
>
Have a look at the test file source to see if it looks OK.


>
> On Thu, Mar 28, 2019 at 2:03 AM sebb  wrote:
>
> > On Thu, 28 Mar 2019 at 05:25, Felix Cheung 
> wrote:
> >
> > > This test is consistently failing when I build, any idea what’s wrong
> in
> > my
> > > setup?
> > >
> > > - should print unicode correctly *** FAILED *** (101 milliseconds)
> > > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
> > > ExecuteSuccess(JObject(List((text/plain,JString(☺)
> > > (PythonInterpreterSpec.scala:272)
> > >
> > >
> > I have seen such errors before; usually it is because the test source
> file
> > has been incorrectly encoded/decoded at some point.
> > Although they are harder to maintain, it may be worth coding the test
> files
> > using Unicode escapes rather than the non-ASCII characters.
> > ASCII is much harder to mangle...
> >
> >
> >
> > > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin
> >  > > >
> > > wrote:
> > >
> > > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> > > release.
> > > >
> > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > > > Spark jobs from web/mobile apps (no Spark client needed). So,
> multiple
> > > > users can interact with your Spark cluster concurrently and reliably.
> > > >
> > > > Vote thread:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> > > >
> > > > (Note I messed up the subject on the first e-mail, that thread is for
> > > > the RC2 vote.)
> > > >
> > > > Result thread:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> > > >
> > > > The RC is based on tag v0.6.0-incubating-rc2:
> > > > https://github.com/apache/incubator-livy/commit/28be98cabc
> > > >
> > > > The release files can be found here:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> > > >
> > > > The staged maven artifacts can be found here:
> > > >
> https://repository.apache.org/content/repositories/orgapachelivy-1008
> > > >
> > > > The list of resolved JIRAs in this release can be found here:
> > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> > > >
> > > > Vote will be open for at least 72 hours. Thanks!
> > > >
> > > > --
> > > > Marcelo
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Re: FYI, saved the current wiki.apache.org/incubator content to svn

[Bertrand Delacretaz]

Hi,

On Thu, Mar 28, 2019 at 4:14 PM sebb  wrote:
> ...OK to add the missing pages to the archive?...

Sure - I did that quickly, too quickly apparently, thanks for fixing!

-Bertrand

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

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[Felix Cheung]

I see, thanks. Perhaps the way I unzip the src zip file then. Is it a
better approach to unpack it?


On Thu, Mar 28, 2019 at 2:03 AM sebb  wrote:

> On Thu, 28 Mar 2019 at 05:25, Felix Cheung  wrote:
>
> > This test is consistently failing when I build, any idea what’s wrong in
> my
> > setup?
> >
> > - should print unicode correctly *** FAILED *** (101 milliseconds)
> > ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
> > ExecuteSuccess(JObject(List((text/plain,JString(☺)
> > (PythonInterpreterSpec.scala:272)
> >
> >
> I have seen such errors before; usually it is because the test source file
> has been incorrectly encoded/decoded at some point.
> Although they are harder to maintain, it may be worth coding the test files
> using Unicode escapes rather than the non-ASCII characters.
> ASCII is much harder to mangle...
>
>
>
> > On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin
>  > >
> > wrote:
> >
> > > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> > release.
> > >
> > > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > > Spark jobs from web/mobile apps (no Spark client needed). So, multiple
> > > users can interact with your Spark cluster concurrently and reliably.
> > >
> > > Vote thread:
> > >
> > >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> > >
> > > (Note I messed up the subject on the first e-mail, that thread is for
> > > the RC2 vote.)
> > >
> > > Result thread:
> > >
> > >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> > >
> > > The RC is based on tag v0.6.0-incubating-rc2:
> > > https://github.com/apache/incubator-livy/commit/28be98cabc
> > >
> > > The release files can be found here:
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> > >
> > > The staged maven artifacts can be found here:
> > > https://repository.apache.org/content/repositories/orgapachelivy-1008
> > >
> > > The list of resolved JIRAs in this release can be found here:
> > > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> > >
> > > Vote will be open for at least 72 hours. Thanks!
> > >
> > > --
> > > Marcelo
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Retirement Policy for Artifacts

[Dave Fisher]

> On Mar 27, 2019, at 9:30 AM, Henk P. Penning  wrote:
> 
> On Wed, 27 Mar 2019, Dave Fisher wrote:
> 
>> Date: Wed, 27 Mar 2019 16:10:00 +
>> From: Dave Fisher 
>> To: general@incubator.apache.org
>> Subject: [DISCUSS] Retirement Policy for Artifacts
>> In INCUBATOR-198 Infra asked us to clean up Release artifacts from
>> archive.apache.org  for retired podlings.
>> I created INCUBATOR-233 so that we can make sure we are clear about
>> the policy before we undertake proper cleanup.
> 
>  Nothing should be removed from archive.apache.org,
>  except, parhaps, for legal reasons.

Fair enough. Sorry I should have been more explicit.

Do we have Legal Concerns carrying archives, releases and repositories that 
have never had Podling IP Clearance signoff?

Has anything fallen through the cracks?

Regards,
Dave

> 
>  Groeten,
> 
>  HPP
> 
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> 
>> When a Podling retires from the Incubator there are two exit states that 
>> might happen:
>> 
>> (1) Development simply stops.
>> (2) Development moves elsewhere. Either back to the donating entity or 
>> simply elsewhere.
>> 
>> Artifacts that are left that relate to code that may or may not be compliant 
>> with Apache Policy are:
>> 
>> (A) Code Repositories.
>> (B) Release Archives.
>> (C) Release Distributions.
>> (D) Dev Distributions. (These should always be deleted.)
>> 
>> A simple answer would be to keep everything where it is, and that would be 
>> easy except when the code has not been cleared for licensing issues. 
>> Fortunately, assuming that the podling PPMC or its Mentors have maintained 
>> the Podling Status Page we do have dates for licensing clearance that can be 
>> used. These are the dates in the “Copyright” and “Verify Distribution 
>> Rights” sections. Are there other dates to check? Are we over to the dates 
>> in content/podlings/.yml. Once we agree on the correct “date" to 
>> use. I propose that we adopt the following policy for retiring podlings:
>> 
>> (1) If the “date” is empty then we remove every Release and Repository. (We 
>> can allow a delay for people to grab “historical” copies.)
>> (2) If the "date" is filled in then the Repositories are marked Read Only 
>> and all Releases prior to that “date" are removed.
>> 
>> The effect is that we only preserve artifacts and code that can be 
>> considered to be conforming with Apache Release Policy and Code that is 
>> likely to be in good shape with respect to licensing.
>> 
>> I’d like to go for LAZY CONSENSUS after discussion for the next week or so.
>> 
>> Regards,
>> Dave
>> 
>> 
> 
> -
> 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: FYI, saved the current wiki.apache.org/incubator content to svn

[sebb]

On Tue, 26 Mar 2019 at 08:25, Bertrand Delacretaz
 wrote:
>
> On Mon, Mar 25, 2019 at 10:16 AM Bertrand Delacretaz
>  wrote:
> > ...I have saved the contents of https://wiki.apache.org/incubator/ at
> > https://svn.apache.org/repos/private/pmc/incubator/wiki-archive-march-2019/ 
> > ...
>
> FWIW, as someone was asking how that was done, I just used
>
>wget -r -l5 -np https://wiki.apache.org/incubator/
>
> and then semi-manually removed the help pages based on their names,
> which are in several languages.

Unfortunately that does not seem to capture all the pages, for example
the following is missing:

https://wiki.apache.org/incubator/WookieProposal

Something must have gone wrong with the download.

I did another download using the following command:

wget -r -np -l1 --reject-regex '(.*)\?(.*)'
http://wiki.apache.org/incubator/TitleIndex

The TitleIndex should have links to every page, so there's no need to
follow links further.
Also the regex stops it from asking for raw pages etc.

Also used the following .wgetrc
header = Accept-Language: en-us,en;q=0.5
header = Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
header = Connection: keep-alive
referer = /
robots = off
random_wait = on
wait = 1

OK to add the missing pages to the archive?

S.



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

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

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[sebb]

On Thu, 28 Mar 2019 at 05:25, Felix Cheung  wrote:

> This test is consistently failing when I build, any idea what’s wrong in my
> setup?
>
> - should print unicode correctly *** FAILED *** (101 milliseconds)
> ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
> ExecuteSuccess(JObject(List((text/plain,JString(☺)
> (PythonInterpreterSpec.scala:272)
>
>
I have seen such errors before; usually it is because the test source file
has been incorrectly encoded/decoded at some point.
Although they are harder to maintain, it may be worth coding the test files
using Unicode escapes rather than the non-ASCII characters.
ASCII is much harder to mangle...



> On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin  >
> wrote:
>
> > The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy
> release.
> >
> > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > Spark jobs from web/mobile apps (no Spark client needed). So, multiple
> > users can interact with your Spark cluster concurrently and reliably.
> >
> > Vote thread:
> >
> >
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
> >
> > (Note I messed up the subject on the first e-mail, that thread is for
> > the RC2 vote.)
> >
> > Result thread:
> >
> >
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
> >
> > The RC is based on tag v0.6.0-incubating-rc2:
> > https://github.com/apache/incubator-livy/commit/28be98cabc
> >
> > The release files can be found here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
> >
> > The staged maven artifacts can be found here:
> > https://repository.apache.org/content/repositories/orgapachelivy-1008
> >
> > The list of resolved JIRAs in this release can be found here:
> > https://issues.apache.org/jira/projects/LIVY/versions/12342736
> >
> > Vote will be open for at least 72 hours. Thanks!
> >
> > --
> > Marcelo
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>