[ANNOUNCE] Apache Teaclave (incubating) 0.1.0 Release

[Mingshen Sun]

Hi all,

The Apache Teaclave (incubating) community is happy to announce Apache
Teaclave (incubating) version 0.1.0!

This is the first Apache Incubator release of Teaclave. Apache Teaclave
(incubating) is an open source universal secure computing platform, making
computation on privacy-sensitive data safe and simple.

Apache Teaclave (incubating) has following highlights:

  - Security: Teaclave adopts multiple security technologies to enable
secure computing, in  particular, Teaclave uses Intel SGX to serve the most
security-sensitive tasks  with *hardware-based isolation*, *memory
encryption* and *attestation*.  Also, Teaclave is written in Rust to
prevent *memory-safety* issues.
  - Functionality: Teaclave is provided as a *function-as-a-service
platform*. With many built-in  functions, it supports tasks like machine
learning, private set intersection,  crypto computation, etc. In addition,
developers can also deploy and execute  Python scripts in Teaclave. More
importantly, unlike traditional FaaS,  Teaclave supports both general
secure computing tasks and *flexible single- and multi-party secure
computation*.
- Usability: Teaclave builds its components in containers, therefore,
it supports deployment both locally and within cloud infrastructures.
Teaclave also provides convenient endpoint APIs, client SDKs and command
line tools.
- Modularity: Components in Teaclave are designed in modular, and some like
remote attestation can be easily embedded in other projects. In addition,
Teaclave SGX SDK can also be used separately to write standalone SGX
enclaves for other purposes.

Release notes can be found here:
https://github.com/apache/incubator-teaclave/releases/tag/v0.1.0

A link to the download can be found here:
https://dist.apache.org/repos/dist/release/incubator/teaclave/0.1.0/

The release tag: https://github.com/apache/incubator-teaclave/tree/v0.1.0

Teaclave resources:
  - Teaclave dev mailing list (
https://lists.apache.org/list.html?d...@teaclave.apache.org)
  - Teaclave website (https://teaclave.apache.org/)
  - Github issues (https://github.com/apache/incubator-teaclave/issues)
  - Twitter (https://twitter.com/ApacheTeaclave)

Best regards,
Apache Teaclave (incubating) Team

--
Mingshen Sun

Re: [ANNOUNCE] Apache TVM (incubating) v0.7.0 Release

[Henry Saputra]

Congrats to Apache TVM incubating community!

- Henry

On Fri, Oct 9, 2020 at 5:42 PM Ziheng Jiang  wrote:

> Hi all,
>
> The Apache TVM (incubating) community is happy to announce Apache TVM
> (incubating) version 0.7.0!
>
> Apache TVM (incubating) is an open deep learning compiler stack for
> CPUs, GPUs, and specialized accelerators. It aims to close the gap
> between the productivity-focused deep learning frameworks, and the
> performance- or efficiency-oriented hardware backends.
>
> 0.7.0 is a major release with many new features. All users of Apache TVM
> (incubating) 0.6 are advised to upgrade. This release is co-managed by Zhi
> Chen.
>
> A full list of the changes in this release can be found in the release
> notes:
> https://github.com/apache/incubator-tvm/releases/tag/v0.7.0
>
> A link to the download can be found here:
> https://tvm.apache.org/download
>
> The Release Tag:
> https://github.com/apache/incubator-tvm/tree/v0.7.0
>
> TVM Resources
> - Our discussion forum (https://discuss.tvm.apache.org/)
> - TVM dev mailing list (
> https://lists.apache.org/list.html?d...@tvm.apache.org)
> - TVM website (https://tvm.apache.org/)
> - Github issues (https://github.com/apache/incubator-tvm/issues)
>
> Best regards,
> Apache TVM (incubating) Team
>
> --
> Ziheng
>

[DISCUSS] Graduate Apache TVM as a TLP

[Tianqi Chen]

Dear Incubator:

A month ago we brought up the discussion about graduating TVM as TLP.
After great discussions in the apache way [1], we get good support from the
incubator and also get helpful feedback about producing another release.
The TVM PPMC always focused on getting consensus, and is fully committed to
building a better community, as a result, we decided to withdraw
the graduation until there has been another release.
Now that the community has produced another release by two new release
managers from different organizations.

We feel it is the right time to bring up this topic.

Here is the summary of the state:

Compliance

Compliance is what every project is required to do. These policies are set
to protect Apache’s brand,
encourage community over code and set a common foundation for the projects.
Usually compliance is well documented (as per-apache way, what is not
documented did not happen).
The TVM PPMC has been diligently upholding compliances, including, but not
limited to

- T0 Project website hosted at ASF https://tvm.apache.org/.
- T1 Produce apache release, no cat-X code.
- T2 No advertising non-release items as Apache release.
- T3 Protect Apache brand, working with trademark to resolve branding
concerns.
- T4 Clearly marks third party artifacts and makes sure they comply with
trademark policies.
- T5 Open development: everyone happens (also) happens on dev@
- T6 Consider all forms of contributions for committer nomination.
- T7 Make sure release processes are clearly documented, reproducible by
any committers.

Community

The “community over code” is one of the most important factors of
the Apache way.
The TVM PPMC has been working very hard to foster a healthy, diverse and
independent community,
and will continue to do so.

- C0: Consider all forms of contributions as merit.
- C1: Encourage community diversity by only nominating people from
different organizations.
- C2: Actively discusses, and brings in new committers from diverse
backgrounds.
The community grows healthily and is quite vibrant.

Thank you!

- [1]
https://lists.apache.org/thread.html/r215d3ecbd9bbf4db20dcaffa4fa2ec00e49e71fdcec7fa954d75f84a%40%3Cgeneral.incubator.apache.org%3E
- [2] Maturity
https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing

[ANNOUNCE] Apache TVM (incubating) v0.7.0 Release

[Ziheng Jiang]

Hi all,

The Apache TVM (incubating) community is happy to announce Apache TVM
(incubating) version 0.7.0!

Apache TVM (incubating) is an open deep learning compiler stack for
CPUs, GPUs, and specialized accelerators. It aims to close the gap
between the productivity-focused deep learning frameworks, and the
performance- or efficiency-oriented hardware backends.

0.7.0 is a major release with many new features. All users of Apache TVM
(incubating) 0.6 are advised to upgrade. This release is co-managed by Zhi
Chen.

A full list of the changes in this release can be found in the release
notes:
https://github.com/apache/incubator-tvm/releases/tag/v0.7.0

A link to the download can be found here:
https://tvm.apache.org/download

The Release Tag:
https://github.com/apache/incubator-tvm/tree/v0.7.0

TVM Resources
- Our discussion forum (https://discuss.tvm.apache.org/)
- TVM dev mailing list (
https://lists.apache.org/list.html?d...@tvm.apache.org)
- TVM website (https://tvm.apache.org/)
- Github issues (https://github.com/apache/incubator-tvm/issues)

Best regards,
Apache TVM (incubating) Team

--
Ziheng

Re: [VOTE] Release Apache Teaclave (incubating) v0.1.0-rc2

[Mingshen Sun]

Thanks to everyone that participated. The vote to release Apache Teaclave
(incubating) version 0.1.0 is now closed.

The vote PASSED with 4 binding +1, 0 non binding +1 and 0 -1 votes:

Binding votes:
- Yu Ding
- Yulong Zhang
- Zhaofeng Chen
- Tongxin Li

We will work to complete the release process.

On Tue, Oct 6, 2020 at 10:57 PM Tongxin Li  wrote:

> +1 approve
>
> On 2020/10/06 21:57:47, Mingshen Sun  wrote:
> > Dear community,
> >
> > This is a call for a vote to release Apache Teaclave (incubating) version
> > 0.1.0. This is the first Apache release since Teaclave entered the
> > incubator.
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with four +1 votes from IPMC members (Tongxin Li, Yu Ding,
> Furkan
> > Kamaci, and Pei Wang).
> >
> > Vote/result thread:
> >   -
> >
> https://lists.apache.org/thread.html/r78add66efd8eb43be2f7e4548ea516528112bdd1d00a4626f095ca94%40%3Cdev.teaclave.apache.org%3E
> >
> > The release candidate to be voted over is available at:
> >   -
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.1.0-rc.2/
> >
> > The release candidate is signed with a GPG key available at:
> >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> >
> > The Git commit for this release is:
> >   -
> >
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=05769c80fd15612003d629603cadd2ecddbfca46
> >
> > The Release Note is available in:
> >   -
> https://github.com/apache/incubator-teaclave/releases/tag/v0.1.0-rc.2
> >
> > Build guide and get started instructions can be found at:
> >   -
> >
> https://github.com/apache/incubator-teaclave/blob/v0.1.0-rc.2/docs/my-first-function.md
> >
> > The short version of building Teaclave from the source tarball:
> >
> > ```
> > $ wget
> >
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.1.0-rc.2/apache-teaclave-0.1.0-rc.2-incubating.tar.gz
> > $ tar zxvf apache-teaclave-0.1.0-rc.2-incubating.tar.gz && cd
> > apache-teaclave-0.1.0-rc.2-incubating
> > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> >bash -c ". /root/.cargo/env && \
> >  . /opt/sgxsdk/environment && \
> >  mkdir -p build && cd build && \
> >  cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> >  make"
> > ```
> >
> > The vote will be open for at least 72 hours.
> >
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Mingshen Sun
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT][VOTE] Release Apache TVM (incubating) v0.7.0

[Ziheng Jiang]

Dear community,

I'm glad to announce the results of the vote for Apache TVM (incubating)
version v0.7.0 release. This is a major release with new features. All
users of Apache TVM (incubating) 0.6 are advised to upgrade. This release
is co-managed by Zhi Chen.

This vote passes with five +1 votes (4 binding), no 0 votes, and 0 -1 vote.

+1 votes

   - Tianqi Chen (binding)
   - Yizhi Liu
   - Byung-Gon Chun (binding)
   - Markus Weimer (binding)
   - Henry Saputra (binding)

0 votes

   - No votes

-1 votes

   - No votes

Vote thread can be found here [1].

[1]
https://lists.apache.org/thread.html/r040652cd7303c850ca83cc579b7890eb7609fd6fa2f81e597848ab97%40%3Cgeneral.incubator.apache.org%3E


Thanks,

Ziheng

[jira] [Resolved] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Dave Fisher (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher resolved INCUBATOR-256.
---
Resolution: Fixed

A new Jenkins job was created and tested.

Trigger Clutch Analysis on SVN Change. If an SVN Change has occurred then 
Incubator-SVN-Clutch-Analysis-part-1 is triggered.

Incubator-GIT-Site-part-2 job is no longer scheduled daily. Instead it is 
triggered by  Incubator-SVN-Clutch-Analysis-part-1. It is still triggered by 
Git changes.

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Dave Fisher
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Assigned] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Dave Fisher (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher reassigned INCUBATOR-256:
-

Assignee: Dave Fisher

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Dave Fisher
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-256:


It should be sufficient to watch 
https://svn.apache.org/repos/asf/incubator/public/trunk/content.

No point trying to narrow it further - there are unlikely to be other changes, 
and it does not matter too much if there are.

Rather than trigger on every change, an hourly check would be a great 
improvement

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Dave Fisher (Jira)]

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

Dave Fisher commented on INCUBATOR-256:
---

The job uses GIT as the SCM so a dummy job is a better idea.

Would want to watch podlings.xml, projects/*, and podlings/*

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Comment Edited] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Dave Fisher (Jira)]

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

Dave Fisher edited comment on INCUBATOR-256 at 10/9/20, 3:52 PM:
-

The job uses GIT as the SCM so a dummy job is a better idea.

Would want to watch podlings.xml, projects/., and podlings/.


was (Author: wave):
The job uses GIT as the SCM so a dummy job is a better idea.

Would want to watch podlings.xml, projects/*, and podlings/*

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-256:


Or perhaps could set up a dummy job that watches SVN and triggers the existing 
job

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-256:


Configure
Build Trigger / Poll SCM

This assumes the SCM is defined as the SVN source of the data

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Dave Fisher (Jira)]

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

Dave Fisher commented on INCUBATOR-256:
---

If you want to let me know how to setup a svn trigger in a Jenkins job, I’ll 
give it a try.

> Jenkins Clutch job does not trigger on source changes
> -
>
> Key: INCUBATOR-256
> URL: https://issues.apache.org/jira/browse/INCUBATOR-256
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
> detect changes to SVN.
> It would help keep the site up to date if there was a regular check of SVN
> Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Created] (INCUBATOR-256) Jenkins Clutch job does not trigger on source changes

[Sebb (Jira)]

Sebb created INCUBATOR-256:
--

 Summary: Jenkins Clutch job does not trigger on source changes
 Key: INCUBATOR-256
 URL: https://issues.apache.org/jira/browse/INCUBATOR-256
 Project: Incubator
  Issue Type: Bug
Reporter: Sebb


AFAICT, the Jenkins clutch job which builds the data still in SVN does not 
detect changes to SVN.

It would help keep the site up to date if there was a regular check of SVN

Perhaps someone with karma could see to this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: BlueMarlin Slow Bootstrap into Incubator

[John D. Ament]

On Fri, Oct 9, 2020 at 1:37 AM Justin Mclean 
wrote:

> HI,
>
> > It is out of date and COMPLETELY misses DNS requests!
>
> I believe it’s up to date, but as always PRs welcome.
>
> It's mentioned under Resources:
> "The first resources to be created are LDAP and DNS. These should be
> requested via Apache Infra JIRA → New Podling Parent Request”
>
> The podlings.xml file need to updated before that can be done as described
> in the document.
>

Mostly FYI, from when I last updated that doc, I believe the expectation
from infra is that both podlings.xml and projects/{podling}.xml is created
and at least one build has been run to see the podling live on the
incubator site, but they may be OK just checking in podlings.xml.

What looks suspect to me is that we had documented this as "New Podling
Parent Request" but I no longer see that issue type in JIRA.  Is that on
purpose?


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

Re: [VOTE] Apache Tuweni 1.2.0 release

[Michael Wall]

Antoine,

I'll take a look this weekend.

Mike

On Fri, Oct 9, 2020 at 2:12 AM Antoine Toulme  wrote:
>
> Any chance we may get more votes from the incubator? Please advise.
>
> Cheers,
>
> Antoine
>
> > On Sep 30, 2020, at 23:58, Furkan KAMACI  wrote:
> >
> > Hi,
> >
> > +1 from me (binding, carrying over my vote).
> >
> > I checked:
> >
> > - Incubating in name
> > - DISCLAIMER exists
> > - LICENSE and NOTICE are fine
> > - No unexpected binary files
> > - Checked PGP signatures
> > - Checked checksums
> > - Code compiles
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> >> On Wed, Sep 30, 2020 at 9:34 AM Antoine Toulme  wrote:
> >>
> >> Hi all,
> >>
> >> We're voting on the source distributions available here:
> >> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.2.0-incubating/
> >>  >>>
> >> The release tag is present here:
> >> https://github.com/apache/incubator-tuweni/releases/tag/v1.2.0-incubating
> >>  >>>
> >>
> >> This release includes the following changes:
> >> New:
> >> * Ethash hashing support
> >> * EVMC support
> >> * Simplify distribution down to one binary and source artifacts
> >> * Added doc build
> >> Changes:
> >> * Refactor discv5, testing it with an eth2 client
> >> * Simplified and streamlined LES to match ETH devp2p subprotocols
> >> Bug fixes:
> >> * Fixes #141 - Generated Maven pom.xml have incorrect information
> >> * Fix SecureScuttlebutt setup.
> >> Misc:
> >> * Added codecov and tests adding coverage
> >>
> >> Here is the release thread on the d...@tuweni.apache.org  >> d...@tuweni.apache.org> list:
> >>
> >> https://lists.apache.org/thread.html/re9128953304e3bdc3a80012e623b63e0d122b5aa261410f24c7041bf%40%3Cdev.tuweni.apache.org%3E
> >> <
> >> https://lists.apache.org/thread.html/re9128953304e3bdc3a80012e623b63e0d122b5aa261410f24c7041bf@%3Cdev.tuweni.apache.org%3E
> >>>
> >>
> >> The release vote has passed with the following votes (
> >> https://lists.apache.org/thread.html/r47854c9fe57147b12f9158504c9310650a9abfae0c8daf35347d1f03%40%3Cdev.tuweni.apache.org%3E
> >> <
> >> https://lists.apache.org/thread.html/r47854c9fe57147b12f9158504c9310650a9abfae0c8daf35347d1f03@%3Cdev.tuweni.apache.org%3E
> >>> )
> >> 3 +1:
> >> Antoine Toulme
> >> Furkan Kamaci
> >> Vinayakumar B
> >> 0 +0
> >> 0 -1
> >>
> >> The release vote is open at least until 10/3 12pm PST time.
> >>
> >> Cheers,
> >>
> >> Antoine
> >>
> >>
>
>
> -
> 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

[jira] [Commented] (INCUBATOR-255) Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html

[John D. Ament (Jira)]

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

John D. Ament commented on INCUBATOR-255:
-

[~vvitanska] you should reach out to your mentors to do this.

> Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html
> --
>
> Key: INCUBATOR-255
> URL: https://issues.apache.org/jira/browse/INCUBATOR-255
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Vira Vitanska
>Priority: Major
> Attachments: Rename.png
>
>
> This ticket follows 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-145 and 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-184.
> So now our podling is in process of replacing old name by new one from DLab 
> to DataLab.
> 
> There is a page [https://incubator.apache.org/clutch/datalab.html]
> Could you replace dlab by datalab in:
>  # project website link name
>  # issue tracker link name
>  # wiki link name?
> I guess that I've reported to an appropriate side (Project Incubator) if I am 
> wrong please correct me.
> Thanks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Created] (INCUBATOR-255) Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html

[Vira Vitanska (Jira)]

Vira Vitanska created INCUBATOR-255:
---

 Summary: Rename "DLab" to "DataLab" on 
https://incubator.apache.org/clutch/datalab.html
 Key: INCUBATOR-255
 URL: https://issues.apache.org/jira/browse/INCUBATOR-255
 Project: Incubator
  Issue Type: Task
  Components: site
Reporter: Vira Vitanska
 Attachments: Rename.png

This ticket follows https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-145 
and https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-184.

So now our podling is in process of replacing old name by new one from DLab to 
DataLab.

There is a page [https://incubator.apache.org/clutch/datalab.html]

Could you replace dlab by datalab in:
 # project website link name
 # issue tracker link name
 # wiki link name?

I guess that I've reported to an appropriate side (Project Incubator) if I am 
wrong please correct me.

Thanks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

> (1) PPMC members not subscribed to the private list.
> 
> I have no way to see who is or isn’t on the list

Whimsey should show that to PMC member with a * next to their name. Currnly 
still not subscribed are:
Aaron Suddjian
Bogdan Kyryliuk
Chris Williams
Daniel Gaspar
Serena Jiang

There is also a ralme...@gmail.com subscribed who doesn’t seem to be on your 
PPMC, they probably should be removed.

> (2) Synchronous Meetings

The biggest issue I see is the this is not being announced or discussed on the 
mailing list and what is discussed in those meetings is not brought back to the 
list. Having these external discussions is a huge barrier to people who want to 
contribute to the project but for one reason or another (e.g. time zones or day 
job or other commitments) can’t attend that meeting. By having these you are 
basically limiting people who can attend to full time employees paid to work on 
the project in a similar time zone, that excludes a lot of people.This was 
mentioned as an issue in a previous board report but nothing seems to have been 
done about it. One of the core values of Apache projects is that discussions 
need to be asynchronous and inclusive. It would be helpful if your mentors 
added their thoughts about this.

> (3) Links to other companies
> 
> I’ve reached out to our mentors (via the private@ list, in case we can get 
> any other input as well) on the issue, and hope to hear back soon about how 
> other TLPs (e.g. Drill, Airflow, Beam, and surely more), have surmounted this 
> logo usage issue.

I’ve seen this handled in a few ways, either it put on a page other than the 
main page or they don’t link to those companies. also be aware that some 
companies are more protective of their trademarks and you may even need to get 
permission to use their logos in this way.

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 TVM (incubating) v0.7.0.rc0

[Byung-Gon Chun]

+1 (binding), carrying over my vote on the dev list

-Gon

On Fri, Oct 9, 2020 at 2:34 PM Henry Saputra 
wrote:

> NOTICE file looks good
> LICENSE file looks good
> DISCLAIMER file exists and looks good
> Signature file looks good
> Hash file looks good
> No binary files in source artifact
> License header exist in files
>
> +1 (binding)
>
> On Wed, Oct 7, 2020 at 11:29 AM Markus Weimer  wrote:
>
> > +1 (binding) , carrying over my vote on the dev list
> >
> > Markus
> >
> > On Wed, Oct 7, 2020 at 10:51 AM Yizhi Liu  wrote:
> > >
> > > +1
> > >
> > > On Wed, Oct 7, 2020 at 6:02 AM Tianqi Chen  wrote:
> > > >
> > > > +1, carrying over my vote (binding).
> > > >
> > > > TQ
> > > >
> > > > On Tue, Oct 6, 2020 at 4:31 PM Ziheng Jiang 
> wrote:
> > > >
> > > > > Dear community,
> > > > >
> > > > > This is a call for a vote to release Apache TVM (incubating)
> version
> > > > > 0.7.0. This is a maintenance release incorporating important bug
> > > > > fixes. All users of Apache TVM (incubating) 0.6 are advised to
> > > > > upgrade. This release is co-managed by Zhi Chen.
> > > > >
> > > > > Apache TVM (incubating) community has voted and approved the
> release,
> > > > > with three +1 votes from IPMC members (Tianqi Chen, Byung-Gon Chun,
> > Markus
> > > > > Weimer).
> > > > >
> > > > > Vote thread:
> > > > >
> > > > >
> >
> https://lists.apache.org/thread.html/re73cf4c733c0671bdc893fecf038c14ce7dd34c43a3e712660bca35e%40%3Cdev.tvm.apache.org%3E
> > > > >
> > > > > Result thread:
> > > > >
> > > > >
> >
> https://lists.apache.org/thread.html/r929370e94c8385cbc151fb86c74629f34fb19708cb22fc1d235d2215%40%3Cdev.tvm.apache.org%3E
> > > > >
> > > > > 1) Link to release notes:
> > > > > https://github.com/apache/incubator-tvm/releases/tag/v0.7.0.rc0
> > > > >
> > > > > 2) Link to release candidate:
> > > > >
> https://dist.apache.org/repos/dist/dev/incubator/tvm/tvm-v0.7.0-rc0
> > > > >
> > > > > The vote will be open for at least 72 hours.
> > > > >
> > > > > +1 = approve
> > > > > +0 = no opinion
> > > > > -1 = disapprove (provide reason)
> > > > >
> > > > > Thanks,
> > > > > Ziheng
> > > > >
> > >
> > >
> > >
> > > --
> > > Yizhi Liu
> > >
> > > --
> > > Yizhi Liu
> > >
> > > -
> > > 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
> >
> >
>


-- 
Byung-Gon Chun

Re: [VOTE] Apache Tuweni 1.2.0 release

[Antoine Toulme]

Any chance we may get more votes from the incubator? Please advise.

Cheers,

Antoine

> On Sep 30, 2020, at 23:58, Furkan KAMACI  wrote:
> 
> Hi,
> 
> +1 from me (binding, carrying over my vote).
> 
> I checked:
> 
> - Incubating in name
> - DISCLAIMER exists
> - LICENSE and NOTICE are fine
> - No unexpected binary files
> - Checked PGP signatures
> - Checked checksums
> - Code compiles
> 
> Kind Regards,
> Furkan KAMACI
> 
>> On Wed, Sep 30, 2020 at 9:34 AM Antoine Toulme  wrote:
>> 
>> Hi all,
>> 
>> We're voting on the source distributions available here:
>> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.2.0-incubating/
>> >> 
>> The release tag is present here:
>> https://github.com/apache/incubator-tuweni/releases/tag/v1.2.0-incubating
>> >> 
>> 
>> This release includes the following changes:
>> New:
>> * Ethash hashing support
>> * EVMC support
>> * Simplify distribution down to one binary and source artifacts
>> * Added doc build
>> Changes:
>> * Refactor discv5, testing it with an eth2 client
>> * Simplified and streamlined LES to match ETH devp2p subprotocols
>> Bug fixes:
>> * Fixes #141 - Generated Maven pom.xml have incorrect information
>> * Fix SecureScuttlebutt setup.
>> Misc:
>> * Added codecov and tests adding coverage
>> 
>> Here is the release thread on the d...@tuweni.apache.org > d...@tuweni.apache.org> list:
>> 
>> https://lists.apache.org/thread.html/re9128953304e3bdc3a80012e623b63e0d122b5aa261410f24c7041bf%40%3Cdev.tuweni.apache.org%3E
>> <
>> https://lists.apache.org/thread.html/re9128953304e3bdc3a80012e623b63e0d122b5aa261410f24c7041bf@%3Cdev.tuweni.apache.org%3E
>>> 
>> 
>> The release vote has passed with the following votes (
>> https://lists.apache.org/thread.html/r47854c9fe57147b12f9158504c9310650a9abfae0c8daf35347d1f03%40%3Cdev.tuweni.apache.org%3E
>> <
>> https://lists.apache.org/thread.html/r47854c9fe57147b12f9158504c9310650a9abfae0c8daf35347d1f03@%3Cdev.tuweni.apache.org%3E
>>> )
>> 3 +1:
>> Antoine Toulme
>> Furkan Kamaci
>> Vinayakumar B
>> 0 +0
>> 0 -1
>> 
>> The release vote is open at least until 10/3 12pm PST time.
>> 
>> Cheers,
>> 
>> Antoine
>> 
>> 


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