[Discuss] Graduate Apache ECharts (incubating) as a top level project

[Ovilia]

Hi everyone,

After discussion with the community [1], and a positive vote result [2], we
believe
ECharts is ready for graduation to a TLP, and we'd like to bring up in
discussion with
the IPMC.

Please see the proposed board resolution below and let us know what you
think.

A few points to assist in the discussion:

- Released 9 official Apache releases by 3 release managers [3]
- Voted in 9 committers including 3 PPMC members
- Achieved 43556 stars (and counting) on GitHub
- Apache suitable name search has been approved [4]
- Completed the Podling Maturity Assessment, all items are passed [5]
- Our PPMC is diverse and consists of members from 9 organizations
- There have been 143 contributors to the codebase, 82 of whom contributed
during incubation
- Closed 11033+ issues
- Merged 603+ pull requests

We've resolved all branding issues which include Logo, GitHub repo,
documentation, website, and others.

Thank you!

*Ovilia*

[1]
https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
[2]
https://lists.apache.org/thread.html/r1179386814f4f99ccb3809527bc9436fe702e0e7573fb5de2c99151f%40%3Cdev.echarts.apache.org%3E
[3] https://dist.apache.org/repos/dist/release/incubator/echarts/
[4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
[5]
https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts




-

X. Establish the Apache ECharts Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to a charting and data visualization
library written in JavaScript.

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

RESOLVED, that the Apache ECharts Project be and hereby is
responsible for the creation and maintenance of software
related to a charting and data visualization
library written in JavaScript; and be it further

RESOLVED, that the office of "Vice President, Apache ECharts" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache ECharts Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache ECharts Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache ECharts Project:

* Houjin Huang  
* Deqing Li 
* Dong Rui  
* Kener Linfeng 
* Kevin A. McGrail  
* Wenli Zhang   
* Shen Yi   
* Shuang Su 
* Siwen Su  
* Junting Wang  
* Zhongxiang Wang   
* Dave Fisher   
* Sheng Wu  
* Zak Wu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
be appointed to the office of Vice President, Apache ECharts, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache ECharts PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache ECharts Project; and be it further

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

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

[NOTICE] DataSketches graduation to TLP VOTE is in process in the DataSketches community

[leerho]

Folks,

This notice is pursuant to the Incubator Guide to Successful Graduation

.

To those that may be interested, the DataSketches community is in the
process of voting on graduating the DataSketches project to a TLP.

Permalink

to the community vote thread.

Regards,

Lee Rhodes
lee...@apache.org

Re: [VOTE] Release Apache Daffodil (incubating) 3.0.0-rc1

[Steve Lawrence]

Thanks for the vote!

About the issues:

> - GPG signature has no trust chain

I've been to a couple signing parties, but unfortunately haven't yet
gotten verified by too many people yet. Still working on it.

> - No RELEASE_NOTES

We keep our release notes on each individual release page:

https://daffodil.apache.org/releases/3.0.0

Gives us more control over formatting, like linking to bugs, and the
ability to update if we realize we forgot a note. Can't really do that
if it's in the source releases.

> - running "sbt it:test" fails
> - running "sbt daffodil-cli/stage" fails
> - running "sbt clean coverage test it:test" fails (giving up now)

It would be helpful if you could post the failures on our dev list. I
suspect the issue has to do with Java 13. We have one bug report about
OpenJDK 13, and I think that might affect the above commands:

https://issues.apache.org/jira/browse/DAFFODIL-2332

> - running "sbt ratCheck" fails

This too would be useful to post the error on our dev list. We have a
pull request that that should fix one known issue with ratCheck.
Hopefully it's the same issue.

> - It would be cool, if you could remove all of the ".keep" files (most
are no longer needed and they do extend the list of rat findings quite a
bit)

We actually have a pull request ready for the next release to fix this.

> - The sources contains license file in:
apache-daffodil-3.0.0-incubating-src/daffodil-lib/src/main/scala/passera/BSD-LICENSE.txt
this should be moved to a more prominent location (I like to put these
license texts in a "licenses" directory in the root of the project and
inside I add to the end which files in the repo it applies to)

We have passera and the contents of that license listed in our main
LICENSE file. This is here because the passera repo contents is just
copied into this directory. Since it's in the LICENSE file, I guess we
could remove it if there's confusion.

> - It appears you manually added LICENSE and NOTICE files to every
artifact in the repo (this means editing the NOTICE files for every
first release of a year. Maven has a plugin to automatically add these
to artifacts, perhaps there's an SBT way to do that too?

Some of the LICENSES and NOTICES actually have slight variations since
different artifacts include different outside sources, so we feel its
important to maintain them separately. It's not too much of a hassle to
maintain since they aren't updated very often.


On 11/12/20 4:21 AM, Christofer Dutz wrote:
> +1 (binding) 
> 
> Tested on my Mac using java 13 using SBT 1.3.4
> 
> [OK] Download all staged artifacts under the url specified in the release 
> vote email into a directory we’ll now call download-dir.
> [OK] Verify the signature is correct: Additional Apache tutorial on how to 
> verify downloads can be found here.
> [MINOR] Check if the signature references an Apache email address.
> [OK] Verify the SHA512 hashes
> [OK] Unzip the archive
> [MINOR] Verify the existence of DISCLAIMER, LICENSE, NOTICE, README, 
> RELEASE_NOTES files in the extracted source bundle.
> [OK] Verify the content of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES 
> files in the extracted source bundle.
> [OK] Run RAT externally to ensure there are no surprises.
> [OK] Search for SNAPSHOT references:
> [OK] Search for Copyright references, and if they are in headers, make sure 
> these files containing them are mentioned in the LICENSE file.
> [MINOR] Build the project according to the information in the README.md file.
> 
> Generally as the "compile" and "test" builds worked, I consider this a 
> slightly-severe-MINOR ... however you should address that ASAP.
> 
> Notes:
> 
> - GPG signature has no trust chain
> - No RELEASE_NOTES
> - running "sbt it:test" fails
> - running "sbt daffodil-cli/stage" fails
> - running "sbt ratCheck" fails
> - running "sbt clean coverage test it:test" fails (giving up now)
> - It would be cool, if you could remove all of the ".keep" files (most are no 
> longer needed and they do extend the list of rat findings quite a bit)
> - The sources contains license file in: 
> apache-daffodil-3.0.0-incubating-src/daffodil-lib/src/main/scala/passera/BSD-LICENSE.txt
>  this should be moved to a more prominent location (I like to put these 
> license texts in a "licenses" directory in the root of the project and inside 
> I add to the end which files in the repo it applies to)
> - It appears you manually added LICENSE and NOTICE files to every artifact in 
> the repo (this means editing the NOTICE files for every first release of a 
> year. Maven has a plugin to automatically add these to artifacts, perhaps 
> there's an SBT way to do that too?
> 
> 
> Am 10.11.20, 13:51 schrieb "Steve Lawrence" :
> 
> Remdiner to please take a look at this vote if you get a chance. We only 
> have two mentors so we will need at least one vote from another IPMC member.
> 
> Thanks!
> 
> On 2020/11/04 16:30:28, Steve Lawrence  wrote: 
> > 
> > The Apache 

Re: [VOTE] Release Apache Daffodil (incubating) 3.0.0-rc1

[Christofer Dutz]

+1 (binding) 

Tested on my Mac using java 13 using SBT 1.3.4

[OK] Download all staged artifacts under the url specified in the release vote 
email into a directory we’ll now call download-dir.
[OK] Verify the signature is correct: Additional Apache tutorial on how to 
verify downloads can be found here.
[MINOR] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes
[OK] Unzip the archive
[MINOR] Verify the existence of DISCLAIMER, LICENSE, NOTICE, README, 
RELEASE_NOTES files in the extracted source bundle.
[OK] Verify the content of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES 
files in the extracted source bundle.
[OK] Run RAT externally to ensure there are no surprises.
[OK] Search for SNAPSHOT references:
[OK] Search for Copyright references, and if they are in headers, make sure 
these files containing them are mentioned in the LICENSE file.
[MINOR] Build the project according to the information in the README.md file.

Generally as the "compile" and "test" builds worked, I consider this a 
slightly-severe-MINOR ... however you should address that ASAP.

Notes:

- GPG signature has no trust chain
- No RELEASE_NOTES
- running "sbt it:test" fails
- running "sbt daffodil-cli/stage" fails
- running "sbt ratCheck" fails
- running "sbt clean coverage test it:test" fails (giving up now)
- It would be cool, if you could remove all of the ".keep" files (most are no 
longer needed and they do extend the list of rat findings quite a bit)
- The sources contains license file in: 
apache-daffodil-3.0.0-incubating-src/daffodil-lib/src/main/scala/passera/BSD-LICENSE.txt
 this should be moved to a more prominent location (I like to put these license 
texts in a "licenses" directory in the root of the project and inside I add to 
the end which files in the repo it applies to)
- It appears you manually added LICENSE and NOTICE files to every artifact in 
the repo (this means editing the NOTICE files for every first release of a 
year. Maven has a plugin to automatically add these to artifacts, perhaps 
there's an SBT way to do that too?


Am 10.11.20, 13:51 schrieb "Steve Lawrence" :

Remdiner to please take a look at this vote if you get a chance. We only 
have two mentors so we will need at least one vote from another IPMC member.

Thanks!

On 2020/11/04 16:30:28, Steve Lawrence  wrote: 
> 
> The Apache Daffodil community has voted and approved the proposed
> release of Apache Daffodil (incubating) 3.0.0-rc1.
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Daffodil is an open source implementation of the DFDL specification that
> uses DFDL schemas to parse fixed format data into an infoset, which is
> most commonly represented as either XML or JSON. This allows the use of
> well-established XML or JSON technologies and libraries to consume,
> inspect, and manipulate fixed format data in existing solutions.
> Daffodil is also capable of the reverse by serializing or "unparsing" an
> XML or JSON infoset back to the original data format.
> 
> Vote thread:
> 
https://lists.apache.org/thread.html/r4352b6907245d31b556d1fb977c7c7261487174f99e723c0cf77fad8%40%3Cdev.daffodil.apache.org%3E
> 
> Result thread:
> 
https://lists.apache.org/thread.html/rb08b144b848350c6f29af0bad64570a1cc77d37d296129d26aedbe0a%40%3Cdev.daffodil.apache.org%3E
> 
> All distribution packages, including signatures, digests, etc. can be
> found at:
> 
> https://dist.apache.org/repos/dist/dev/incubator/daffodil/3.0.0-rc1/
> 
> Staging artifacts can be found at:
> 
> https://repository.apache.org/content/repositories/orgapachedaffodil-1019/
> 
> This release has been signed with PGP key 36F3494B033AE661, corresponding
> to slawre...@apache.org, which is included in the KEYS file here:
> 
> https://downloads.apache.org/incubator/daffodil/KEYS
> 
> The release candidate has been tagged in git with v3.0.0-rc1.
> 
> For reference, here is a list of all closed JIRAs tagged with 3.0.0:
> 
> https://s.apache.org/daffodil-issues-3.0.0
> 
> For a summary of the changes in this release, see:
> 
> https://daffodil.apache.org/releases/3.0.0/
> 
> Please review and vote. The vote will be open for at least 72 hours
> (Saturday, 07 November 2019, 12 Noon EST).
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> -
> 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: