Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

2019-03-29 Thread Jan Lahoda 
Hi Justin,

Thanks for the comments. One particular question/comment at this time:

On Sat, Mar 30, 2019 at 2:43 AM Justin Mclean 
wrote:

> - There are a number (100’s) of source files that do not have ASF headers,
> Please run rat and please add headers to .java, .jsp and .php files that
> are missing the ASF headers.
>

I assume we are taking about files like:
https://github.com/apache/incubator-netbeans/blob/master/java/java.hints/test/unit/data/org/netbeans/test/java/hints/AddCast1.java

As this is an IDE, many features manipulate source code. And tests for the
features that manipulate have source code as an input. And input files for
these tests so resemble source code. There is this policy:
http://www.apache.org/legal/src-headers.html#faq-exceptions

Which says:
---
Test data for which the addition of a source header would cause the tests
to fail.
---

If I add the license header to the file above, there is a test somewhere
that will start to fail, so it seems this fits this exception. Or if it
does not, why not?

Frankly, if we were talking about a "handful" of tests, I wouldn't worry
about doing changes. But, a) we are probably talking about tens of
thousands of tests; b) I am really worried about tests that will not fail
after the header is added, but will not longer test the erroneous condition
they should be testing (i.e. "silent failure"), as only manual inspection
can detect these; c) I am worried that if the ASF header will ever change,
we will face test breakages again (for tens of thousands of tests).

Of course there are tricks that are being played for new tests to avoid
this, but here we are in some cases talking about tests that are more than
a decade old. (There are even tricks that could be played for existing test
(data files), but none of them really nice, and all of them having their
own issues.)

Thanks,
 Jan

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

2019-03-29 Thread Felix Cheung 
I’m happy to give +1 (binding)

But definitely ran into more problems with this and more time than I
anticipated.


checked:
- name includes incubating
- DISCLAIMER exists
Signature and hashes
- LICENSE and NOTICE all good
Copyright year, url to and copy full text for license
- No unexpected binary files (except below)
- All source files have ASF headers
- Can compile form source (with issues)


I switched to another environment, found out I needed to manually  pip
install configparser  just to build (skipTest)

And then without skipTest it failed even earlier on rsc  tests

Running org.apache.livy.rsc.TestSparkClient

Tests run: 19, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 30.948 sec
<<< FAILURE! - in org.apache.livy.rsc.TestSparkClient

testJobSubmission(org.apache.livy.rsc.TestSparkClient)  Time elapsed: 0.486
sec  <<< FAILURE!

org.mockito.exceptions.verification.WantedButNotInvoked:


Wanted but not invoked:

listener.onJobStarted(

org.apache.livy.rsc.JobHandleImpl@75805562

);

-> at org.apache.livy.rsc.TestSparkClient$1.call(TestSparkClient.java:101)

And then the earlier python2 utf-8 issue.

Quite a number of binary resources in the src release, ttf, svg etc
also this looks like standard bootstrap script, does it have to be in the
src release (vs to include in binary release)?
docs/assets/themes/apache/bootstrap/css/bootstrap.css

if that's doc only there's another copy similarly at
server/src/main/resources/org/apache/livy/server/ui/static/css/bootstrap.min.css



On Thu, Mar 28, 2019 at 4:05 PM Marcelo Vanzin 
wrote:

> 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: Voting on releases with serious unaddressed issues

2019-03-29 Thread Justin Mclean 
Hi,

> 1) If VP Legal or VP Infra says any of the issues are blockers then the 
> podling cannot do a release

I guess they well need to clarify that then, but AFAIK an an ex VP legal has 
said this, and VP infra has stated this for the exact issues mentioned in this 
release.

> 2) If IPMC members want to become contributors and help fix the problems with 
> pull requests,  or mentors (meaning real mentors not just folks pointing out 
> problems, then they should get started. As active members of the community 
> those individuals will have the right to vote -1 on a release.

So are you saying that IPMC members vote are only valid for +1 votes on 
podlings they are not actively involved in and their -1 votes are invalid? The 
risk I see there is IPMC votes when needed just become just a rubber stamping 
exercise.

> 3) If the podling is unable to gather three +1s among their active community 
> then they won't be able to do a release so the conversation is moot

Well in this case here that happened (they only had one binding vote) and they 
asked the IPMC to vote on it. Some podlings, for a number of reasons, are not 
going to be able to find 3 active IPMC members in their project to vote on 
every release. (Although I'm surprised in this case given who the mentors are).

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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

2019-03-29 Thread Craig Russell 
The page http://echarts.apache.org/download.html is very close, but:

The Source link is fine.
The Signature link and SHA512 link must be changed from 
https://dist.apache.org/repos/dist/release/incubator/echarts/... to
https://www.apache.org/dist/incubator/echarts/...

The instructions in step 2 refer to downloading from Apache but these links are 
http links and must be https links.

Hope this helps,

Craig


> On Mar 29, 2019, at 9:46 PM, Ovilia  wrote:
> 
> The download link is http://echarts.apache.org/download.html
> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> Ovilia  于2019年3月30日周六 下午12:45写道：
> 
>> I've updated ECharts download page. Hopefully, it's been fixed correctly
>> this time.
>> If so, we will send an email to  annou...@apache.org for the release.
>> 
>> Zhang Wenli
>> http://zhangwenli.com
>> 
>> 
>> Craig Russell  于2019年3月21日周四 上午8:23写道：
>> 
>>> Hi Su Shuang,
>>> 
>>> You will need to modify your download page to conform to requirements (an
>>> announcement to incubator is not moderated but an announcement to
>>> annou...@apache.org will be moderated, and this announcement will not
>>> pass).
>>> 
>>> You should never refer in the announcement or your download page to
>>> dist.apache.org. For announcement emails, link to your download page.
>>> For download pages, link to the mirror chooser and link to the checksum and
>>> signature from www.apache.org/dist/incubator/echarts. Include a link to
>>> your project KEYS file and instructions how to verify the download.
>>> 
>>> There are many download pages you can model, e.g.
>>> https://hadoop.apache.org/releases.html
>>> 
>>> If you need help, your mentors will be able to assist.
>>> 
>>> Best regards
>>> 
>>> Craig
>>> 
 On Mar 20, 2019, at 1:24 PM, SHUANG SU  wrote:
 
 Hi all,
 
 The Apache ECharts (incubating) team is proud to announce Apache ECharts
 version 4.2.1-incubating.
 
 ECharts is a powerful, interactive charting and visualization library.
 
 Vote thread:
 
>>> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
 
 Download Links:
 https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
 
 Release Notes:
 http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
 
 Website: http://echarts.apache.org/
 
 ECharts Resources:
 - Issue: https://github.com/apache/incubator-echarts/issues
 - Mailing list: d...@echarts.incubator.apache.org
 
 Thanks
 
 --
 Su Shuang (100pah)
 --
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 

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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

2019-03-29 Thread Ovilia 
The download link is http://echarts.apache.org/download.html

Zhang Wenli
http://zhangwenli.com


Ovilia  于2019年3月30日周六 下午12:45写道：

> I've updated ECharts download page. Hopefully, it's been fixed correctly
> this time.
> If so, we will send an email to  annou...@apache.org for the release.
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> Craig Russell  于2019年3月21日周四 上午8:23写道：
>
>> Hi Su Shuang,
>>
>> You will need to modify your download page to conform to requirements (an
>> announcement to incubator is not moderated but an announcement to
>> annou...@apache.org will be moderated, and this announcement will not
>> pass).
>>
>> You should never refer in the announcement or your download page to
>> dist.apache.org. For announcement emails, link to your download page.
>> For download pages, link to the mirror chooser and link to the checksum and
>> signature from www.apache.org/dist/incubator/echarts. Include a link to
>> your project KEYS file and instructions how to verify the download.
>>
>> There are many download pages you can model, e.g.
>> https://hadoop.apache.org/releases.html
>>
>> If you need help, your mentors will be able to assist.
>>
>> Best regards
>>
>> Craig
>>
>> > On Mar 20, 2019, at 1:24 PM, SHUANG SU  wrote:
>> >
>> > Hi all,
>> >
>> > The Apache ECharts (incubating) team is proud to announce Apache ECharts
>> > version 4.2.1-incubating.
>> >
>> > ECharts is a powerful, interactive charting and visualization library.
>> >
>> > Vote thread:
>> >
>> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
>> >
>> > Download Links:
>> > https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
>> >
>> > Release Notes:
>> > http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
>> >
>> > Website: http://echarts.apache.org/
>> >
>> > ECharts Resources:
>> > - Issue: https://github.com/apache/incubator-echarts/issues
>> > - Mailing list: d...@echarts.incubator.apache.org
>> >
>> > Thanks
>> >
>> > --
>> > Su Shuang (100pah)
>> > --
>>
>> Craig L Russell
>> c...@apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

2019-03-29 Thread Ovilia 
I've updated ECharts download page. Hopefully, it's been fixed correctly
this time.
If so, we will send an email to  annou...@apache.org for the release.

Zhang Wenli
http://zhangwenli.com


Craig Russell  于2019年3月21日周四 上午8:23写道：

> Hi Su Shuang,
>
> You will need to modify your download page to conform to requirements (an
> announcement to incubator is not moderated but an announcement to
> annou...@apache.org will be moderated, and this announcement will not
> pass).
>
> You should never refer in the announcement or your download page to
> dist.apache.org. For announcement emails, link to your download page. For
> download pages, link to the mirror chooser and link to the checksum and
> signature from www.apache.org/dist/incubator/echarts. Include a link to
> your project KEYS file and instructions how to verify the download.
>
> There are many download pages you can model, e.g.
> https://hadoop.apache.org/releases.html
>
> If you need help, your mentors will be able to assist.
>
> Best regards
>
> Craig
>
> > On Mar 20, 2019, at 1:24 PM, SHUANG SU  wrote:
> >
> > Hi all,
> >
> > The Apache ECharts (incubating) team is proud to announce Apache ECharts
> > version 4.2.1-incubating.
> >
> > ECharts is a powerful, interactive charting and visualization library.
> >
> > Vote thread:
> >
> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
> >
> > Download Links:
> > https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
> >
> > Release Notes:
> > http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
> >
> > Website: http://echarts.apache.org/
> >
> > ECharts Resources:
> > - Issue: https://github.com/apache/incubator-echarts/issues
> > - Mailing list: d...@echarts.incubator.apache.org
> >
> > Thanks
> >
> > --
> > Su Shuang (100pah)
> > --
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Setting up Tuweni

2019-03-29 Thread Antoine Toulme 
Thank you Dave. I have emailed all initial committers and mentors (includes 
you) a detailed version of those instructions to engage.

I have Bcced people to create an incentive to come chat on the dev list.

Cheers!

Antoine

> On Mar 29, 2019, at 12:48 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> The next steps are to email all the mentors and initial committers as follows:
> 
> (1) Subscribe to the dev@ and commits@ lists.
> (2) To the initial committers who are not yet apache committers they will 
> need to sign an ICLA and return that to the secretary@. This will start their 
> id process. https://www.apache.org/dev/pmc.html#newcommitter 
> 
> (3) Once an account is established then the Initial Committers will need be 
> added to the PPMC LDAP through Whimsy.
> (4) Subscribe to private@ list. The moderator will need to make sure that 
> they have their apache account already and are either a Mentor or an Initial 
> Committer.
> 
> Once people are subscribed to the dev@ list we can continue the discussion 
> there.
> 
> Regards,
> Dave
> 
>> On Mar 29, 2019, at 12:27 PM, Antoine Toulme  wrote:
>> 
>> Awesome, thanks!
>> 
>>> On Mar 29, 2019, at 12:11 PM, Dave Fisher  wrote:
>>> 
>>> Hi Antoine,
>>> 
>>> The repos is now created.
>>> 
>>> Regards,
>>> Dave
>>> 
 On Mar 29, 2019, at 10:45 AM, Antoine Toulme  wrote:
 
 The ticket was closed with this message:
 
 This is mainly self-serve, ask a mentor or  a pmc chair to use 
 selfserve.apache.org  to create a new repos.
 
 Would you please help and perform this task if you can, and report back 
 here?
 
 Cheers,
 
 Antoine
 
> On Mar 28, 2019, at 10:49 PM, Antoine Toulme  wrote:
> 
> 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=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
>>> 
>> 
>> 
>> -
>> 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: Voting on releases with serious unaddressed issues

2019-03-29 Thread Ross Gardler 
Three comments, each of which I phrase as my opinion on the correct way to do 
this. Each comment is independent from the other:

1) If VP Legal or VP Infra says any of the issues are blockers then the podling 
cannot do a release

2) If IPMC members want to become contributors and help fix the problems with 
pull requests,  or mentors (meaning real mentors not just folks pointing out 
problems, then they should get started. As active members of the community 
those individuals will have the right to vote -1 on a release.

3) If the podling is unable to gather three +1s among their active community 
then they won't be able to do a release so the conversation is moot

Ross


From: Justin Mclean 
Sent: Friday, March 29, 2019 7:24 PM
To: general@incubator.apache.org
Subject: Voting on releases with serious unaddressed issues

Hi,

The  Netbeans RC is an interesting one as they:
- Have made several releases before.
- Have been given advice from the IPMC on serious issues and what to fix.
- Looks like nothing has been done to correct those issues.

Now I know we’re trying to be more lenient on releases but we still have to 
draw the line somewhere and this is not their first release. The the binary in 
source code, license issues copyright issues on the cute cat and rabbit photos 
[1] probably mean that they cannot put that release in the ASF distribution 
area even if they do get 3 +1s without legal and infra approval.

What do other IPMC members think?

Thanks,
Justin

1. Curiously this is the second time I’ve vote -1 because of a cat photo taken 
by a professional photographer has been included in a source release
-
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

2019-03-29 Thread Luciano Resende 
+1 (binding)

And thanks Marcelo for resolving the issues raised on rc1.

On Fri, Mar 29, 2019 at 19:13 Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> Released software can have bugs and failing tests, the only requirement
> from an ASF release point of view is that it can compile. Of course teh
> project may decided not to release it if the bug is serious.
>
> I checked:
> - incubating in name
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE good, but missing the license for the glyphicons halflings font
> [1] (and a few other files)
> - NOTICE needs year updating
> - No unpacked binary files
> - All source files have ASF headers
> - Can compile from source
>
> Thanks,
> Justin
>
> 1.
> apache-livy-0.6.0-incubating/docs/assets/themes/apache/bootstrap/fonts/glyphicons-halflings-regular.svg
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Sent from my Mobile device

Voting on releases with serious unaddressed issues

2019-03-29 Thread Justin Mclean 
Hi,

The  Netbeans RC is an interesting one as they:
- Have made several releases before.
- Have been given advice from the IPMC on serious issues and what to fix.
- Looks like nothing has been done to correct those issues.

Now I know we’re trying to be more lenient on releases but we still have to 
draw the line somewhere and this is not their first release. The the binary in 
source code, license issues copyright issues on the cute cat and rabbit photos 
[1] probably mean that they cannot put that release in the ASF distribution 
area even if they do get 3 +1s without legal and infra approval.

What do other IPMC members think?

Thanks,
Justin

1. Curiously this is the second time I’ve vote -1 because of a cat photo taken 
by a professional photographer has been included in a source release
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

2019-03-29 Thread Justin Mclean 
Hi,

+1 binding

I checked (in all 3 artefacts)
- incubating in name
- signatures and hashes match
- LICENSE and NOTICE files good
- DISCLAIMER exists
- ASF source files do not have the correct ASF header
- No unexpected binary files in source release
- Can compile from source

The source files (mainly .js and .sh files) don’t have the correct ASF header 
please fix for the next release. If you’re not sure what to do here please ask 
your mentors.

Thanks,
Justin
-
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

2019-03-29 Thread Justin Mclean 
Hi,

+1 (binding)

Released software can have bugs and failing tests, the only requirement from an 
ASF release point of view is that it can compile. Of course teh project may 
decided not to release it if the bug is serious.

I checked:
- incubating in name
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE good, but missing the license for the glyphicons halflings font [1] 
(and a few other files)
- NOTICE needs year updating
- No unpacked binary files
- All source files have ASF headers
- Can compile from source

Thanks,
Justin

1. 
apache-livy-0.6.0-incubating/docs/assets/themes/apache/bootstrap/fonts/glyphicons-halflings-regular.svg



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

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

2019-03-29 Thread Justin Mclean 
Hi,

Sorry but I’m -1 as there is binary code in the source release and possible 
copyright issues and there are a number of other issues as well.  Most of these 
issues have been brought up before on previous releases and have not been 
addressed e.g. [3] While each incubating release doesn’t need to be perfect, 
issues found, particularly serious ones, do need to be fixed. I suggest you 
speak to your mentors on how to correct this issues.

I will not however that my -1 vote is not a veto, and you can still release the 
software if you get 3 +1 IPMC votes and more +1’s than -1’s.

I checked:
- incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE need more work (see below)
- There are a number (100’s) of source files that do not have ASF headers, 
Please run rat and please add headers to .java, .jsp and .php files that are 
missing the ASF headers.
- Compiled code is included in the source release  (see below)
- I didn’t try to compile

Theres are the binary inclusions that seem to contain compiled code, an ASF 
release should not include this:
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/com-example-testmodule-cluster.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-brokendepending.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending_on_new_one_engine.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-1.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-2.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-executable-permissions.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-fragment.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent-1-1.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent.nbm
  B 
./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-refresh_providers_test.nbm

There are a number of other suspicious binary files as well, include one 
mentioned in [3].

I think there some more work to do on licensing here, and these will be needed 
to be fixed in a later release:
- You are not compiling with the terms of the licenses of the software you have 
bundled. Most licenses need for you to include the full text of the license and 
not just list it license. This is an issue with most of the dtd files, note 
that some licenses include a copyright line so a single copy of that type of 
license is not enough.
- As well as listing  the 3rd party files it would be to also see the product 
and version number included.
- As it is currently structured it’s not easily possible to check if you are 
including all of the needed licenses in LICENSES as you are also including the 
text of licenses of things that are not bundled but are dependancies, so I’m 
been unable to check if LICENSE and NOTICE are correct.
- A spot check show that things are bundled but not mentioned in LICENSE as 
they need to be, for example [1][2]. I would expect there to be others.
- It also look like you are including image file that you do not have 
permission to distribute

Give all of the above this release is almost impossible to check if it in 
compliance with ASF release, distribution or legal policies and some 
improvement need to be made so that it can be.

Thanks,
Justin

1. 
./ide/css.editor/test/unit/src/org/netbeans/modules/css/editor/module/main/properties/PropertiesATest.java
2. 
./php/php.editor/test/unit/data/testfiles/actions/testImportData/libs/nette.min.php
3. 
https://lists.apache.org/thread.html/2b6ad0d98a9342595da27902f25e7c43c4291738154eedc8b33afb5e@%3Cgeneral.incubator.apache.org%3E
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[NOTICE] Apache SensSoft INFRA migration to Apache Flagon name nearly complete

2019-03-29 Thread Joshua Poore 
Hello,

Writing to inform general@ that INFRA has migrated Apache SensSoft’s assets [1] 
to reflect our approved name change [2]. A complete list of migrated assets is 
below.

Please update list subscriptions.

The podling committers and mentors will be working to clean up podling.xml 
[3]/.yml [4] files. However, flagon.xml/.yml files have been created, but have 
not yet been pushed to incubator projects website.

The apache wiki page will also need to be modified.


INFRA’s heroic efforts are documented at [5]


Complete list of migrated assets:

Lists:

d...@flagon.incubator.apache.org
comm...@flagon.incubator.apache.org
u...@flagon.incubator.apache.org
priv...@flagon.incubator.apache.org

Repositories:

incubator-flagon.git
incubator-flagon-distill.git
incubator-flagon-stout.git
incubator-flagon-tap.git
incubator-flagon-user-ale.git
incubator-flagon-userale-pyqt5.git
incubator-flagon-useralejs.git

Website:

http://flagon.incubator.apache.org/ 

Confluence:

*pending Key update

JIRA:

https://issues.apache.org/jira/projects/FLAGON/summary

[1]  https://issues.apache.org/jira/browse/INFRA-18100 

[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154 

[3] 
http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/flagon.xml?view=markup
 

[4] 
http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings/flagon.yml?view=markup
 

[5] 
https://issues.apache.org/jira/browse/INFRA-18100?focusedCommentId=16805320=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16805320

Re: [VOTE]: Release Apache OpenWhisk Client JS (incubating) 3.19.0.

2019-03-29 Thread Justin Mclean 
Hi,

+0 (due to copyright content in downloaded in dependancy)

I checked:
- incubating in release
- signatures and hashes match
- disclaimer exists
- LICENSE and NOTICE fine
- DISCLAIMER exists
- source files don’t have correct ASF header
- no unexpected binary files

To fix in the next release:
- A large number of .js files in the test directory and many other places don’t 
have the correct ASF header.
- the LICENSE incorrectly includes "Copyright 2015-2016  IBM Corporation” in 
the appendix
- Info in package.json needs updating as it refers to the pre ASF project

I notice that the project when compiled it downloads this file [1] (and other 
places), the text of which is still under copyright, it’s currently unclear how 
to deal with this. There is a discussion on legal-discuss about it [2] that I 
suggest you follow.

Thanks,
Justin

1. ./node_modules/nyc/node_modules/wordwrap/test/idleness.txt
2. 
https://lists.apache.org/thread.html/346ea8ac79c1cdd91c6d7c6d5acb2360a1d84d3a3e8966f91d260cbf@%3Clegal-discuss.apache.org%3E
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

2019-03-29 Thread Matt Sicker 
+1 to the full checklist. Neat that there's an easy to use python
script for helping validate.

On Tue, 26 Mar 2019 at 07:48, David P Grove  wrote:
>
>
>
> The Apache OpenWhisk Community has voted to make the first Apache release
> of the OpenWhisk "Package Alarm", "Package Cloudant" and "Package Kafka"
> components.
>
> The OpenWhisk dev list voting thread is here:
> https://lists.apache.org/thread.html/e0fb73d8ca0d0c584650f4f5b8b02054f5c99d64895f3e5ace352234@%3Cdev.openwhisk.apache.org%3E
>
> We request that IPMC Members please review and vote on this incubator
> release as described below.
>
> These three Apache OpenWhisk packages provide basic event-based programming
> capabilities to an OpenWhisk deployment.
>
> This release comprises of source code distribution only. There are three
> components (git repos) included in this release of the OpenWhisk Packages
> Group. All release artifacts were built by PR#251 in the openwhisk-release
> repo from the following Git commit IDs:
> * openwhisk-package-alarms: dd6ab4d81c8893436e7242170d57951c089d5185
> * openwhisk-package-cloudant: ce5dac9cb0204fb2f78195d9e3f9364236613a31
> * openwhisk-package-kafka: 49820dd24170f24a37c02fae6ba7ec06e190423f
>
> openwhisk-package-alarms (C158D76 B5D9A53A AC10AC42 4CD5060C 7A6467D5
> E9624519 117E9C8C AB171590 CCC3505D 5C7E630D C41769B4 44F85F03 BBA40A6A
> E04D2264 79FFA78B B3C5BFB8)
> src.tar.gz:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz
> sha512 checksum:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz
> .sha512
> signature:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz
> .asc
>
> openwhisk-package-cloudant (380E1BA8 EC3C72A8 09B10DCF 03BC1D2D 4BFA7E4F
> 892995EE 39D26BBE 758AFD5D FA680E81 54A9C726 A0D386C5 B447C947 70D26385
> 2A8D07BF 5848318A 42A3BBDD)
> src.tar.gz:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz
> sha512 checksum:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz
> .sha512
> signature:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz
> .asc
>
> openwhisk-package-kafka (303B8286 AA9B945D 1A740FCB 0DE908D5 A287FAF5
> C20A9DF9 4BBD2F16 C488DF4B 3E82A75B 9D071B1A E1CCDB54 7B623A36 5AC88E5D
> 9994539B 00ECEA5D A066D156)
> src.tar.gz:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz
> sha512 checksum:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz
> .sha512
> signature:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz
> .asc
>
> All release artifacts were signed with key 72AF0CC22C4CF320.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
>
> How to verify the artifacts can be found at:
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the
> +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
>
> Please vote on releasing version 2.0.0-incubating of Apache OpenWhisk
> Package Alarm, Package Cloudant, and Package Kafka as described above.
>
> The vote will be open for at least 72 hours.
> [ ] +1 Release Apache OpenWhisk Package Alarm, Package Cloudant, and
> Package Kafka 2.0.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] DISCLAIMER is included.
> [ ] Source code artifacts have correct names matching the current release.
> [ ] LICENSE and NOTICE files are correct for each OpenWhisk repository.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
>
> regards,
>
> --dave



-- 
Matt Sicker 

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

Re: Setting up Tuweni

2019-03-29 Thread Dave Fisher 
Hi -

The next steps are to email all the mentors and initial committers as follows:

(1) Subscribe to the dev@ and commits@ lists.
(2) To the initial committers who are not yet apache committers they will need 
to sign an ICLA and return that to the secretary@. This will start their id 
process. https://www.apache.org/dev/pmc.html#newcommitter 

(3) Once an account is established then the Initial Committers will need be 
added to the PPMC LDAP through Whimsy.
(4) Subscribe to private@ list. The moderator will need to make sure that they 
have their apache account already and are either a Mentor or an Initial 
Committer.

Once people are subscribed to the dev@ list we can continue the discussion 
there.

Regards,
Dave

> On Mar 29, 2019, at 12:27 PM, Antoine Toulme  wrote:
> 
> Awesome, thanks!
> 
>> On Mar 29, 2019, at 12:11 PM, Dave Fisher  wrote:
>> 
>> Hi Antoine,
>> 
>> The repos is now created.
>> 
>> Regards,
>> Dave
>> 
>>> On Mar 29, 2019, at 10:45 AM, Antoine Toulme  wrote:
>>> 
>>> The ticket was closed with this message:
>>> 
>>> This is mainly self-serve, ask a mentor or  a pmc chair to use 
>>> selfserve.apache.org  to create a new repos.
>>> 
>>> Would you please help and perform this task if you can, and report back 
>>> here?
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
 On Mar 28, 2019, at 10:49 PM, Antoine Toulme  wrote:
 
 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=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
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: Setting up Tuweni

2019-03-29 Thread Antoine Toulme 
Awesome, thanks!

> On Mar 29, 2019, at 12:11 PM, Dave Fisher  wrote:
> 
> Hi Antoine,
> 
> The repos is now created.
> 
> Regards,
> Dave
> 
>> On Mar 29, 2019, at 10:45 AM, Antoine Toulme  wrote:
>> 
>> The ticket was closed with this message:
>> 
>> This is mainly self-serve, ask a mentor or  a pmc chair to use 
>> selfserve.apache.org  to create a new repos.
>> 
>> Would you please help and perform this task if you can, and report back here?
>> 
>> Cheers,
>> 
>> Antoine
>> 
>>> On Mar 28, 2019, at 10:49 PM, Antoine Toulme  wrote:
>>> 
>>> 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=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
> 


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

Re: Setting up Tuweni

2019-03-29 Thread Dave Fisher 
Hi Antoine,

The repos is now created.

Regards,
Dave

> On Mar 29, 2019, at 10:45 AM, Antoine Toulme  wrote:
> 
> The ticket was closed with this message:
> 
> This is mainly self-serve, ask a mentor or  a pmc chair to use 
> selfserve.apache.org  to create a new repos.
> 
> Would you please help and perform this task if you can, and report back here?
> 
> Cheers,
> 
> Antoine
> 
>> On Mar 28, 2019, at 10:49 PM, Antoine Toulme  wrote:
>> 
>> 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=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

2019-03-29 Thread Antoine Toulme 
The ticket was closed with this message:

This is mainly self-serve, ask a mentor or  a pmc chair to use 
selfserve.apache.org  to create a new repos.

Would you please help and perform this task if you can, and report back here?

Cheers,

Antoine

> On Mar 28, 2019, at 10:49 PM, Antoine Toulme  wrote:
> 
> 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=1856351 
>>> 
>>> [1]: https://issues.apache.org/jira/browse/INFRA-18110 
>>> 
>>> 
>> 
>

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

2019-03-29 Thread sebb 
On Fri, 29 Mar 2019 at 10:49, Bertrand Delacretaz
 wrote:
>
> On Fri, Mar 29, 2019 at 10:47 AM sebb  wrote:
> > ...I've committed an example page to show the difference:
> > QpidProposal_body.html ...
>
> Looks easy enough to parse, saving all pages like that would be great
> IMO, thanks!

OK, that can be left for later.

I've added the raw text files.

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

2019-03-29 Thread Bertrand Delacretaz 
On Fri, Mar 29, 2019 at 10:47 AM sebb  wrote:
> ...I've committed an example page to show the difference:
> QpidProposal_body.html ...

Looks easy enough to parse, saving all pages like that would be great
IMO, thanks!

-Bertrand

-
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

2019-03-29 Thread sebb 
On Fri, 29 Mar 2019 at 01:54, Dave Fisher  wrote:
>
>
>
> 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”.

Yes, the Ruby script starts there when scanning TitleIndex for page links.
This includes all titles except FrontPage.

I've committed an example page to show the difference:

QpidProposal_body.html

It should be relatively easy to strip out the header and footer if
required, as the surrounding header and footer have a standard layout.
[No need to parse the page as HTML]

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

I'll leave that as an exercise for the reader(s).

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

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

Re: Request for Mentor

2019-03-29 Thread Julian Feinauer 
Hi Lewis,

although, I cannot fulfill your requirement as a formal mentor (as I'm no IPMC 
member) I will join your list and will try to help you with performing the 
release as I've done several releases as RM in the past.

Julian

Am 28.03.19, 21:02 schrieb "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: FYI, saved the current wiki.apache.org/incubator content to svn

2019-03-29 Thread Bertrand Delacretaz 
Hi,

On Fri, Mar 29, 2019 at 1:51 AM sebb  wrote:
> ...Would it be useful to also save the raw text versions of the pages?
> My Ruby script can easily download these...

IMO yes, that's cheap to store and can be useful.

-Bertrand

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