[RESULT][VOTE] Release Apache Daffodil (incubating) 3.0.0-rc1
The VOTE to release Apache Daffodil (incubating) 3.0.0-rc1 is now closed. The vote passes with 3 +1 (binding) votes and no 0 or -1 votes. The VOTE thread: https://lists.apache.org/thread.html/rbdbc0144c43038ddf0d5b7983e00ffb4ccf013b6121c99a74b0a762c%40%3Cgeneral.incubator.apache.org%3E +1's were: Dave Fisher (binding) Christofer Dutz (binding) Kevin Ratnasekera (binding) Thanks to everyone who voted! We will proceed with the official release of 3.0.0. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 3.0.0-rc1
Thanks for the vote, Dave. Reminder to IPMC members that we only have two mentors, both of which have voted, so we'll need at least one of you to vote. This vote has been open for two weeks now--it would be greatly appreciated if you could take the time to review. We have many users that are patiently awaiting this release. Thanks, - Steve On 11/16/20 2:52 PM, Dave Fisher wrote: > +1 (binding) > > Checked signatures, hashes, incubating in name, NOTICE, LICENSE, and > DISCLAIMER. > > Compiled on macOS. > > Ratcheck is OK. > > Binary packages are as identical as possible. RPM is missing the BAT file as > expected. Did not check the MSI as I don’t have Windows. > >> On Nov 4, 2020, at 8:30 AM, 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: 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 Daffodil (incubating) 3.0.0-rc1
Still looking for 2 more votes. Reminder to please take a look if you get a chance. Thanks, - Steve On 11/10/20 7:51 AM, Steve Lawrence wrote: > 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: 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 Daffodil (incubating) 3.0.0-rc1
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 1
Re: [VOTE] Release Apache Daffodil (incubating) 3.0.0-rc1
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: general-h...@incubator.apache.org
[VOTE] Release Apache Daffodil (incubating) 3.0.0-rc1
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
Re: [VOTE] Release Apache Daffodil (incubating) 2.6.0-rc2
Thanks for the vote! One mentor voted a +0 for rc1. We chose to fix those issues which led to the rc2 vote. Neither mentor has voted for the rc2 release yet. - Steve On 4/17/20 8:12 PM, Justin Mclean wrote: > Hi, > > +1 (binding) > > Did any of your mentor votes on this release? > > I checked: > - incubating in name > - signatures and hashes are fine > - DISCLAIMER exists > - LICENSE and NOTICE are good > - No unexpected binary files > - All ASF files have ASF headers > - Can compile from source > > Thanks, > Justin > > - > 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
[RESULT][VOTE] Release Apache Daffodil (incubating) 2.5.0-rc2
Hi all, The vote to release Apache Daffodil (incubating) 2.5.0-rc2 is now closed. Thanks to those that took the time to review and vote. The release has passed with 4 +1 (binding) votes and no 0 or -1 votes. Binding: +1 David Meikle +1 Furkan Kamaci +1 Jean-Baptiste Onofré +1 Justin Mclean Vote thread: https://lists.apache.org/thread.html/r115073e1d474ff41aba9408dea07fce5c6d6b0df362cec8c885faefc%40%3Cgeneral.incubator.apache.org%3E We will proceed with the official release of 2.5.0. Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 2.5.0-rc2
Thanks for the vote Justin. To other IPMC members, I know both of our Daffodil mentors are pretty busy right now--if anyone else could find some spare cycles to take a look at this release, the Daffodil devs would be very appreciative. Thanks, - Steve On 1/7/20 8:21 PM, Justin Mclean wrote: > Hi, > > +1 (binding) > > I checked: > - incubating in name > - signatures and hashes good > - DISCLAIMER exists > - LICENSE and NOTICE fine > - no unexpected binary files > - all source files have ASF headers > - can compile from source > > Thanks, > Justin > > - > 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
[VOTE] Release Apache Daffodil (incubating) 2.5.0-rc2
Hi all, The Apache Daffodil community has voted and approved the proposed release of Apache Daffodil (incubating) 2.5.0-rc2. 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/c8df54668fbcb7b8285f3e2cc524eac7cb82a721fa823ea5ae7edbe3%40%3Cdev.daffodil.apache.org%3E Result thread: https://lists.apache.org/thread.html/r0f67389306e448058dea657c259aa3bc0ab943a27e390071c67d2b04%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/2.5.0-rc2/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachedaffodil-1012/ This release has been signed with PGP key 36F3494B033AE661, corresponding to slawre...@apache.org, which is included in the KEYS file here: https://www.apache.org/dist/incubator/daffodil/KEYS The release candidate has been tagged in git with v2.5.0-rc2. For reference, here is a list of all closed JIRAs tagged with 2.5.0: https://s.apache.org/daffodil-issues-2.5.0 For a summary of the changes in this release, see: https://daffodil.apache.org/releases/2.5.0/ Please review and vote. The vote will be open for at least 72 hours (Thursday 9 January, 2020, 3:00 PM EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Podling reports due today
Sorry for the delay. Daffodil's report has been added. - Steve On 12/4/19 1:57 AM, Justin Mclean wrote: > HI, > > We’re currently missing the following reports: > - Daffodil > - Marvin-AI > - Warble > > The following podlings have not answered all questions: > - DolphinScheduler > - MesaTEE > > I’ve notice a couple of the podlings have change the formatting, titles and > sign off area. Please don’t do this, we have automated tooling that reply on > these being is a certain way. > > Thanks, > Justin > - > 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: Showcase your project at ApacheCON at a Podling's Shark Tank
Daffodil is interested! We have a couple developers attending ApacheCON NA that are happy to take part. Thanks, - Steve On 8/15/19 10:05 AM, Antoine Toulme wrote: > Hello Roman, > > The Tuweni podling is interested. I am attending ApacheCon EU and would like > a chance to present. > > Cheers, > > Antoine > >> On Aug 14, 2019, at 1:45 PM, Roman Shaposhnik wrote: >> >> Hi Podlings! >> >> in less than a month we're going to have our first >> ApacheCON this year -- the one in Las Vegas. In >> about two month there will be one more in Berlin. >> >> These are not your regular ApacheCONs -- these are >> 20th Anniversary of ASF ApacehCONs! In other words, >> these are not to be missed! >> >> And even if your talk didn't get accepted -- you still >> get an opportunity to highlight your project to, what's >> likely going to be the biggest audience attending. >> >> Here's how: if you (or any community member who's >> passionate about your project) are going to be at either >> of those ApacheCONs consider signing up for >>Podling's Shark Tank >> events: >>https://www.apachecon.com/acna19/s/#/scheduledEvent/1038 >>https://aceu19.apachecon.com/session/podlings-shark-tank >> >> Each project presenting will get ~10 min for the pitch and ~5 min >> of panel grilling them on all sorts of things. Kind of like this ;-) >> https://www.youtube.com/watch?v=wmenN7NEdBc >> >> You've got nothing to lose (in fact, the opposite: you're likely to get >> a prize!) and you will get a chance to receive feedback that might >> actually help you grow your community and ultimately graduate to the >> TLP status. And! Given our awesome panel of judges: >> * Myrle Krantz >> * Justin Mclean >> * Craig Russel >> * Shane Curcuru >> We guarantee this to be a fun and useful event for your community! >> >> We will be tracking signups over here: >> https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank >> https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank >> but for now: >> >> SIMPLY REPLY TO THIS EMAIL if you're interested. >> >> It is first come, first serve -- so don't delay -- sign up today! >> >> Thanks, >> Roman. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tuweni.apache.org >> For additional commands, e-mail: dev-h...@tuweni.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
[RESULT][VOTE] Release Apache Daffodil (incubating) 2.4.0-rc1
Hi, The vote to release Apache Daffodil (incubating) 2.4.0-rc1 is now closed. Thanks to those that took the time to review and vote. It has passed with 3 +1 (binding) votes and no 0 or -1 votes. Binding: +1 Dave Fisher +1 Justin Mclean +1 Dave Meikle Vote thread: https://lists.apache.org/thread.html/024c31fb3c73b0f9ed773c3d5bfbb75444b76814c073bf767ad69659@%3Cgeneral.incubator.apache.org%3E I will proceed with the official release of 2.4.0. Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Daffodil (incubating) 2.4.0-rc1
The Apache Daffodil community has voted and approved the proposed release of Apache Daffodil (incubating) 2.4.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/baa7ec2c94e1ac1a2cf786a5e1f9d8c3d0253b7d944420767e42ebbf@%3Cdev.daffodil.apache.org%3E Result thread: https://lists.apache.org/thread.html/bcd15e3030196ed42cbd9e1a5fc3b0b7b8e2dba02ab0d51ed56a6f9a@%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/2.4.0-rc1/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachedaffodil-1009/ This release has been signed with PGP key 36F3494B033AE661, corresponding to slawre...@apache.org, which is included in the KEYS file here: https://www.apache.org/dist/incubator/daffodil/KEYS The release candidate has been tagged in git with v2.4.0-rc1. For reference, here is a list of all closed JIRAs tagged with 2.4.0: https://s.apache.org/daffodil-issues-2.4.0 For a summary of the changes in this release, see: https://daffodil.apache.org/releases/2.4.0/ One +1 (binding) vote from Dave Fisher will carry over from the dev list vote. Please review and vote. The vote will be open for at least 72 hours (Thursday, 11 July 2019, 8am EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1
Hi all, Thanks to everyone that participated. The vote to release Apache Daffodil 2.3.0-rc1 is now closed. It has passed with 3 +1 (binding) votes and no 0 or -1 votes. Binding: +1 Dave Fisher +1 Christofer Dutz +1 Sheng Wu Vote thread: https://lists.apache.org/thread.html/4cf4f51da5b0c858bbaf44924c559b315b632fb9be28d6d17caaa785@%3Cgeneral.incubator.apache.org%3E Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1
Thanks Chris. The Daffodil devs agree that the issues you found are not blockers and will be fixed for the next release. As a reminder to the IPMC, Daffodil really only has 1 active mentor so will likely need another vote from a non-mentor for the VOTE to pass. We would greatly appreciate it if the IPMC could take a look. Thanks, - Steve On 2/26/19 2:26 AM, Christofer Dutz wrote: > Changing my vote to +1 (binding) > > I found the reason for the failing tests on Mac and Windows ... the root > cause was the different locale and the way numeric values are encoded. > In Germany we separate the 1000s with "." and the decimal part with "," and > in the US it's the opposite way. If I enforce the locale en_US and increase > the memory, then all except one test succeed. > The one failing test is still related to this locale thing, so I guess this > is something that has to be documented and should not qualify for blocking > this release. > > So I would request to add suggested settings of "SBT_OPTS" to the readme for > further releases as with the current documentation it's impossible to build. > > Haven't tested the binary distributions though ... however with some help of > the community I have successfully updated my PLC4X dynamic drivers that > greatly utilize Daffodil to the maven artifacts of 2.3.0 > > Chris > > > Am 23.02.19, 17:11 schrieb "Steve Lawrence" : > > That's for all the response from everyone so far. We'll make sure to fix > the KEYS issue for the next release. DAFFODIL-2070 [1] was created to > track that issue, and we plan to fix it in the next release. Other > comments inline. > > On 2/22/19 3:45 PM, Christofer Dutz wrote: > > Hi all, > > > > I have started verifying this release ... however this is the first > time I am validating a project I'm not directly involved in. > > So I found some things that are different than with the other projects > (Not sure if this is bad or good though) > > > > So here goes: > > 1) No KEYS file (Think this has been reported) > > Ticket mentioned above, we plan to fix this for the next release. > > > 2) No README and RELEASE_NOTES in the RC directory > > We have a REAMDE.md in the root directory of the source release and the > convenience binaries. And we've been maintaining releases notes on our > website. For example, the release for this are at > https://daffodil.apache.org/releases/2.3.0/ > > Looking at a few other random incubator release candidates, I don't see > a README or RELEASE_NOTES in their directories, so maybe this isn't > required, and the readme in the source and release notes on the webpage > is sufficient? > > > 3) There are sha256 and 512 files ... is it OK to have the sha256 ones? > I remember us having to remove less "save" signature files > > We've recently removed md5 and sha1 for this reason. I haven't yet heard > the need to remove sha256, but I'm fine doing that if that's the right > thing to do. > > > 4) Is there a reason, why the "RPM" file is "2.3.0.incubating" instead > of "2.3.0-incubating" (dot instead of a dash). > > The tool we use to build RPMs is very particular about versios and > filenames RPM standards. Those standards require the dot instead of the > dash. It also requires the -1 at the end as well. > > > 5) It was impossible to import the GPG Key from pgp.mit.edu or any of > my known key servers (did it manually) > > I've had a lot of troubles getting keys from pgp.mit.edu, always seems > to be down for me. I have uploaded it in the past for previous releases, > so it should be up there when the server works. But I'm unable to > confirm right now--I get "service temporarily unavailable" errors. > > > 6) The PGP key used to sign doesn't have a valid trust chain (but the > signatures check out and refer to an apache email address) > > I haven't been able to attended any key signings or anything to get > someone to sign my key. Something on my TODO list to get done. > > > Formal download, hash and signature checks: All OK (see GPG remark) > > - I was able to download all artifacts > > - All 256sha hashes are valid > > - All 512sha hashes are valid > > - The signatures in the ASC files check-out (no trust chain though) > > > > Now to the source-bundle checks: > > - Was able to unpack the zip > > - Zip name contained "inc
Re: [VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1
That's for all the response from everyone so far. We'll make sure to fix the KEYS issue for the next release. DAFFODIL-2070 [1] was created to track that issue, and we plan to fix it in the next release. Other comments inline. On 2/22/19 3:45 PM, Christofer Dutz wrote: > Hi all, > > I have started verifying this release ... however this is the first time I am > validating a project I'm not directly involved in. > So I found some things that are different than with the other projects (Not > sure if this is bad or good though) > > So here goes: > 1) No KEYS file (Think this has been reported) Ticket mentioned above, we plan to fix this for the next release. > 2) No README and RELEASE_NOTES in the RC directory We have a REAMDE.md in the root directory of the source release and the convenience binaries. And we've been maintaining releases notes on our website. For example, the release for this are at https://daffodil.apache.org/releases/2.3.0/ Looking at a few other random incubator release candidates, I don't see a README or RELEASE_NOTES in their directories, so maybe this isn't required, and the readme in the source and release notes on the webpage is sufficient? > 3) There are sha256 and 512 files ... is it OK to have the sha256 ones? I > remember us having to remove less "save" signature files We've recently removed md5 and sha1 for this reason. I haven't yet heard the need to remove sha256, but I'm fine doing that if that's the right thing to do. > 4) Is there a reason, why the "RPM" file is "2.3.0.incubating" instead of > "2.3.0-incubating" (dot instead of a dash). The tool we use to build RPMs is very particular about versios and filenames RPM standards. Those standards require the dot instead of the dash. It also requires the -1 at the end as well. > 5) It was impossible to import the GPG Key from pgp.mit.edu or any of my > known key servers (did it manually) I've had a lot of troubles getting keys from pgp.mit.edu, always seems to be down for me. I have uploaded it in the past for previous releases, so it should be up there when the server works. But I'm unable to confirm right now--I get "service temporarily unavailable" errors. > 6) The PGP key used to sign doesn't have a valid trust chain (but the > signatures check out and refer to an apache email address) I haven't been able to attended any key signings or anything to get someone to sign my key. Something on my TODO list to get done. > Formal download, hash and signature checks: All OK (see GPG remark) > - I was able to download all artifacts > - All 256sha hashes are valid > - All 512sha hashes are valid > - The signatures in the ASC files check-out (no trust chain though) > > Now to the source-bundle checks: > - Was able to unpack the zip > - Zip name contained "incubating" > - Archive contains: DISCLAIMER, LICENSE, NOTICE, README(.md) > - There is no RELEASE_NOTES (Think this is required) As mentioned above, we maintain this on our website and in the release files. I'd prefer to not have to maintain two separate versions if having it there is sufficient. > - Content of the README.md: > - I it states the user list to be: u...@daffodil.apache.org, however > I'm subscribed to us...@daffodil.apache.org > - I think the ASF HipChat was replaced with Slack (Don't know if it's > still active) Good catch. I've opened DAFFODIL-2073 to resolve these issues. I'd prefer to fix these in our next release if these aren't considered blockers. Our website does mention the correct email address. > > Building > - Mac 10.14.3, SBT 1.2.8, Java Oracle 1.8.0_141-b15: > - sbt compile (success) > - sbt test (got out of memory errors, did a 'export > SBT_OPTS="-XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=2G -Xmx2G"' first to > make it run) > [error] Failed: Total 3311, Failed 35, Errors 0, Passed 3276 > - sbt it:test (all tests passed) > > - Windows 10, SBT 1.2.7, Java Oracle 1.8.0_101: > - sbt compile (success) > - sbt test (got out of memory errors, did a 'export > SBT_OPTS="-XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=2G -Xmx2G"' first to > make it run) > [error] Failed: Total 3311, Failed 35, Errors 0, Passed 3276 > - sbt it:test > Failed: 4 These failures are very interesting. All of our tests pass in TravisCI [3] and pass on my machine, so I'm guessing these are some sort of environment issue. I assume you're in Germany based on the .de email? I know we've had some issues in the past related to timezones or default encodings, so might be related to that. It would be really helpful if you could capture the output of sbt test and send it to dev@daffodil.a.o or create a Jira ticket for it. We can try to determine what the issue might be and see if they should be blockers. > ... I'll continue testing on Sunday evening ... > > So far I'll vote with a > > +0 (binding) as I don't quite know how bad the things I found are. > > Chris >
[VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1
Hi all, The Apache Daffodil community has voted and approved the proposed release of Apache Daffodil (incubating) 2.3.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/0ec1161ad296aebda54e86c219e3f1c4498a7de640c6342e6888aea1@%3Cdev.daffodil.apache.org%3E Result thread: https://lists.apache.org/thread.html/a195a77640235501109bdea5ec7fb9a34c6f50644c7173fb8a919989@%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/2.3.0-rc1/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachedaffodil-1008/ This release has been signed with PGP key 36F3494B033AE661, corresponding to slawre...@apache.org, which is included in the repository's KEYS file. This key can be found on keyservers, such as: http://pgp.mit.edu/pks/lookup?op=get=0x36F3494B033AE661 It is also listed here: https://people.apache.org/keys/committer/slawrence.asc The release candidate has been tagged in git with v2.3.0-rc1 on commit hash 193c84690401debd93c1f48e39e564fec09e9337. For reference, here is a list of all closed JIRAs tagged with 2.3.0: https://issues.apache.org/jira/browse/DAFFODIL-2067?jql=project%20%3D%20DAFFODIL%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%202.3.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC For a summary of the changes in this release, see: https://daffodil.apache.org/releases/2.3.0/ Please review and vote. The vote will be open for at least 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 2.2.0-rc2
Thanks for the votes. I've gone ahead and removed the sha1 checksums. I've also created tickets for the issues that Dave mentioned to be fixed in the next release. Regarding the last two copyright lines in the LICENSE file, those come from the "Full Copyright Notice" from the DFDL specification, of which we use some snippets in our tests: https://daffodil.apache.org/docs/dfdl/#_Toc398030837 In LEGAL-369, it was recommended that the full copyright notice be included in our LICENSE file. If those copyrights seem suspect, we can raise the issue with the DFDL working group. - Steve On 09/04/2018 04:50 AM, Justin Mclean wrote: > Hi, > > +1 (binding) > > I checked: > - incubating in name > - signatures and hashes correct > - DISCLAIMER exists > - NOTICE is good > - LICENSE looks OK but not sure of the purpose of the last two copyright > lines in LICENSE as usually license text goes in license not single copyright > lines > - All ASF source files have ASF headers > - No unexpected binary files > - Can compile from source > > Please remove the .sha1 checksum files as they are no longer secure / allowed > by policy. > > Thanks, > Justin > > > - > 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
[RESULT][VOTE] Release Apache Daffodil (incubating) 2.1.0
I am pleased to announce that the Incubator PMC has approved the release of Apache Daffodil (incubating) 2.1.0. The vote has passed with 4 binding +1 votes and no other votes. The votes were: +1 Matt Sicker (binding) +1 Justin Mclean (binding) +1 Dave Fisher (binding) +1 John D. Ament (binding) Vote thread: https://lists.apache.org/thread.html/bfa624a2eefb1c1c193f0c497f6dcc46172d9fa9a0e3fcd37464f95e@%3Cgeneral.incubator.apache.org%3E Thank you for your support! We'll continue with the release now. - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3
The only copyrights in LICENSE are related to BSD, W3C, and OGF
licenses. My understanding is that it is optional to add the copyrights
of these permissive licenses to the NOTICE [1]. And it's actually
preferred to not add them so as to keep the NOTICE as small as possible.
Maybe my understanding of this is wrong?
Regarding RPM diff, I've looked at the RPM vs tgz daffodil jars and the
internal class files all have the same md5sum. Doing a binary diff, it
looks like the only differences is the file modification time of the
class files--the contents are the same. I suspect the sbt plugin
building our rpm is moving files around or something and changing the
modification time, even though the file content isn't changing. We'll
look into this for the next release and see if it's something we can
fix. These jars really should have the same hash.
The other issues we plan the resolve in the next release.
Thanks,
- Steve
[1] https://www.apache.org/dev/licensing-howto.html#permissive-deps
On 05/10/2018 07:42 PM, Dave Fisher wrote:
> Hi -
>
> +1 (binding) with a couple of areas for improvement.
>
> Source - hashes and signatures are good.
>
> I’m finally reviewing this release and in looking at the NOTICE and LICENSE
> there are many copyrights/required notices that are in the LICENSE instead of
> the NOTICE. Breaking these apart properly is difficult, but needs to be done
> before your next release.
>
> RAT Check:
>
> ./daffodil-lib/src/main/scala/org/apache/daffodil/util/UniquenessCache.scala
>./daffodil-lib/src/main/scala/passera/numerics/package.scala
>./daffodil-lib/src/main/scala/passera/unsigned/package.scala
>./daffodil-lib/src/main/scala/passera/unsigned/SmallUInt.scala
>./daffodil-lib/src/main/scala/passera/unsigned/UByte.scala
>./daffodil-lib/src/main/scala/passera/unsigned/UInt.scala
>./daffodil-lib/src/main/scala/passera/unsigned/ULong.scala
>./daffodil-lib/src/main/scala/passera/unsigned/Unsigned.scala
>./daffodil-lib/src/main/scala/passera/unsigned/UShort.scala
> I recognize that all of these have headers that have been copied to the
> LICENSE.
>
> Binaries - hashes and signatures are good.
> LICENSE and NOTICE are more correct in the Binaries than the Source.
> Tgz and Zip unpack identical project jars, but for the NPM they are the same
> size but diff reports they are not identical. I’m going to think of this as
> an
> artifact of how I unpacked rpm2cpio | cpio
>
> TO DO:
> (1) Fix Source NOTICE and LICENSE
> (2) Handle the 2 test files.
> (3) Improve Rat Check. Probably by including sbt-rat in project with
> addSbtPlugin("org.musigma" % "sbt-rat" % "0.5.1”) and updating .rat-excludes.
>
> Regards,
> Dave
>
>> On May 10, 2018, at 11:39 AM, John D. Ament <johndam...@apache.org
>> <mailto:johndam...@apache.org>> wrote:
>>
>> Justin/Steve,
>>
>> Apologies as its very confusing looking at this email thread trying to
>> understand what the current state of the vote is.
>>
>> From what I understand:
>>
>> - Two files were included in the release that are Cat-X
>> - These were supposed to be relicensed, but doesn't sound like that happened
>>
>> Or was it corrected that these two files are UoI NCSA licensed? If these
>> files are Cat-X I would also vote a -1 since we cannot release with clear
>> Cat-X contents (we can release with Cat-X dependencies, but the contents
>> can't
>> be Cat-X).
>>
>> Thanks,
>>
>> John
>>
>> On 2018/04/30 11:52:22, Steve Lawrence <slawre...@apache.org
>> <mailto:slawre...@apache.org>> wrote:
>>> Hi all,
>>>
>>> We are still need at least one more +1. We'd really appreciate if if you
>>> could take a look.
>>>
>>> Thanks,
>>> - Steve
>>>
>>> On 04/09/2018 07:24 PM, Steve Lawrence wrote:
>>>> The Apache Daffodil community has voted and approved the proposed
>>>> release of Apache Daffodil (incubating) 2.1.0-rc3.
>>>>
>>>> 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
Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3
Sorry, this situation is a little confusing. The two files were originally developed by Mitre under the very restrictive Cat-X license. We requested that those files be open sourced for inclusion in the Daffodil test suite and the files went through Mitre's process for approval. None of us really understood the importance of licenses at the time, but the intention was that that files would be licensed the same as the rest of Daffodil--the University of Illinois/NCSA license, which is Cat-A. But due all or our inexperience with open source and licensing, changing the license header never happened. So the files were intended to be UoI/NCSA, but were mislabeled as Cat-X. Regardless if it's UoI/NCSA or Cat-X, we would still need an SGA from Mitre to relicense to Apache v2, which is more work than it's worth for these two files, so we planned to just remove them for the next release. Semi-related, this same mistake happened to a lot of DFDL schemas that Mitre created and and subsequently open sourced and put on github (unrelated to ASF) [1][2][3]. We're in talks to get them to fix those as well. - Steve [1] https://github.com/DFDLSchemas/GIF/ [2] https://github.com/DFDLSchemas/PNG/ [3] https://github.com/DFDLSchemas/JPEG/ On 05/10/2018 02:39 PM, John D. Ament wrote: > Justin/Steve, > > Apologies as its very confusing looking at this email thread trying to > understand what the current state of the vote is. > > From what I understand: > > - Two files were included in the release that are Cat-X > - These were supposed to be relicensed, but doesn't sound like that happened > > Or was it corrected that these two files are UoI NCSA licensed? If these > files are Cat-X I would also vote a -1 since we cannot release with clear > Cat-X contents (we can release with Cat-X dependencies, but the contents > can't be Cat-X). > > Thanks, > > John > > On 2018/04/30 11:52:22, Steve Lawrence <slawre...@apache.org> wrote: >> Hi all, >> >> We are still need at least one more +1. We'd really appreciate if if you >> could take a look. >> >> Thanks, >> - Steve >> >> On 04/09/2018 07:24 PM, Steve Lawrence wrote: >>> The Apache Daffodil community has voted and approved the proposed >>> release of Apache Daffodil (incubating) 2.1.0-rc3. >>> >>> 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/10811e8f520bf100a9250a3ae0610633e9018e0ae8fc422e2c0f097a@%3Cdev.daffodil.apache.org%3E >>> >>> Result thread: >>> https://lists.apache.org/thread.html/54a3e681b25f084e0dc46e19764cd19507ff502b927516093a3bd667@%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/2.1.0-rc3/ >>> >>> Staging artifacts can be found at: >>> >>> https://repository.apache.org/content/repositories/orgapachedaffodil-1002/ >>> >>> This release has been signed with PGP key 033AE661, corresponding to >>> slawre...@apache.org, which is included in the repository's KEYS file. >>> This key can be found on keyservers, such as: >>> >>> http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 >>> >>> It is also listed here: >>> >>> https://people.apache.org/keys/committer/slawrence.asc >>> >>> The release candidate has been tagged in git with v2.1.0-rc3. >>> >>> For reference, here is a list of all closed JIRAs tagged with 2.1.0: >>> >>> https://issues.apache.org/jira/browse/DAFFODIL-1897?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC >>> >>> For a summary of the changes in this release, see: >>> >>> https://daffodil.apache.org/releases/2.1.0/ >>> >>> Please review and vote. The vote will be open for at least 72 hours. >>> >>> [ ] +1 approve >>> [ ] +0 no opinion >>>
Apache Daffodil (incubating) in need of mentors
All, The Daffodil project has had a VOTE open for over a month [1], receiving two votes so far. We would greatly appreciate it if others could review the release so that can we get our first release out as an Apache incubator. That said, although our mentors have been incredibly helpful in getting Daffodil bootstrapped to this point, we think a core issue is that activity from our mentors has decreased in the past month to a point where it hinders our progress (we've had minimal response to emails and neither has voted on this release). Daffodil is already shorthanded with only 2 mentors, so having and extra mentor or two would provide a great benefit and help the project move forward. So, we are asking if anyone would be interested in becoming a mentor to the Daffodil project. The majority of the bootstrapping work has been completed, so we think the main focus will be on getting releases out and building the community. For some background on Daffodil and how it aligns with Apache, the Daffodil incubation proposal is available here: https://wiki.apache.org/incubator/DaffodilProposal and our website is at: https://daffodil.apache.org Thanks, - Steve [1] https://lists.apache.org/thread.html/bfa624a2eefb1c1c193f0c497f6dcc46172d9fa9a0e3fcd37464f95e@%3Cgeneral.incubator.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 Daffodil (incubating) 2.1.0-rc3
Hi all, We are still need at least one more +1. We'd really appreciate if if you could take a look. Thanks, - Steve On 04/09/2018 07:24 PM, Steve Lawrence wrote: > The Apache Daffodil community has voted and approved the proposed > release of Apache Daffodil (incubating) 2.1.0-rc3. > > 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/10811e8f520bf100a9250a3ae0610633e9018e0ae8fc422e2c0f097a@%3Cdev.daffodil.apache.org%3E > > Result thread: > https://lists.apache.org/thread.html/54a3e681b25f084e0dc46e19764cd19507ff502b927516093a3bd667@%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/2.1.0-rc3/ > > Staging artifacts can be found at: > > https://repository.apache.org/content/repositories/orgapachedaffodil-1002/ > > This release has been signed with PGP key 033AE661, corresponding to > slawre...@apache.org, which is included in the repository's KEYS file. > This key can be found on keyservers, such as: > > http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 > > It is also listed here: > > https://people.apache.org/keys/committer/slawrence.asc > > The release candidate has been tagged in git with v2.1.0-rc3. > > For reference, here is a list of all closed JIRAs tagged with 2.1.0: > > https://issues.apache.org/jira/browse/DAFFODIL-1897?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > For a summary of the changes in this release, see: > > https://daffodil.apache.org/releases/2.1.0/ > > Please review and vote. The vote will be open for at least 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks, > - Steve > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3
On 04/19/2018 12:29 AM, Justin Mclean wrote: > Hi, > >> I cannot reproduce the gpg failure. On a fresh CentOS install, I ran the >> following. > > I’ve double check again and it all checks out. Sorry about that must of been > something at my end. > >> The original license of these files was University of Illinois >> NCSA Open Source license [3], which is Cat A and compatible with ASLv2. > > I'm not 100% sure they are compatible and may be Category X. > > Did you look into: > NOTICE: This software was produced for the U. S. Government under > contract W15P7T-12-C-F600 > and is subject to the Rights in Data-General Clause 52.227-14 (JUNE > 1987). > > From what I read (and it’s far from clear to me) that possibly imply it can > only be used for noncommercial use? > After further inspection, I'd agree with you. The files were provided to to us with the intention of being included in Daffodil under the UoI NCSA license, but it looks like the license markings weren't updated to reflect that. These files look to be Cat X as is. The two test files should be removed. >> Is your vote still a +1 if we plan to remove these two files in the 2.2.0 >> release? DAFFODIL-1925 [4] tracks this issue. > > Yes if the above question is answered. > > Thanks, > Justin > > 1. https://www.mitre.org/sites/default/files/pdf/12_4811.pdf > - > 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 Daffodil (incubating) 2.1.0-rc3
I cannot reproduce the gpg failure. On a fresh CentOS install, I ran the following: $ wget https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.1.0-rc3/bin/apache-daffodil-2.1.0-incubating-bin.tgz $ wget https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.1.0-rc3/bin/apache-daffodil-2.1.0-incubating-bin.tgz.asc $ wget https://dist.apache.org/repos/dist/release/incubator/daffodil/KEYS $ gpg --import KEYS gpg: key 033AE661: public key "Steve Lawrence <slawre...@apache.org>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) $ gpg --verify apache-daffodil-2.1.0-incubating-bin.tgz.asc gpg: Signature made Thu 05 Apr 2018 12:27:15 PM EDT using RSA key ID 033AE661 gpg: Good signature from "Steve Lawrence <slawre...@apache.org>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: B58C 8114 2758 101A 43D5 B17D 36F3 494B 033A E661 Can you verify the sha sums? The sha256sum of the .asc file is: 63ebf795e4cfed85e4ef55e872a71f6f29696c4145d89c37aa5e1d74e29c08b2 I think you are correct that there is an issue regarding the [1][2] files. We did thoroughly go through our code and thought that all contributions from Mitre had been removed/replaced, but it looks like we missed these two. Because of this, we never attempted to get an SGA/CLA from Mitre, and so these files did have the ASLv2 header incorrectly added. The original license of these files was University of Illinois NCSA Open Source license [3], which is Cat A and compatible with ASLv2. These test files do not provide much value, and should just be removed. Is your vote still a +1 if we plan to remove these two files in the 2.2.0 release? DAFFODIL-1925 [4] tracks this issue. Thanks, - Steve [3] https://opensource.org/licenses/NCSA [4] https://issues.apache.org/jira/browse/DAFFODIL-1925 On 04/17/2018 12:58 AM, Justin Mclean wrote: > Hi, > > Ignoring the signing issues I would be +1 if the license of the files[1][2] > known and the LICENSE fixed in the next release. However a quick search > seems to imply that the two files below [1][2] may be licensed under terms > which are not compatible with the Apache license but I’m not 100% sure and > INAL. > > Re everything else: > - incubating in name. > - DISCLAIMER exists > - NOTICE is good > - LICENSE looks to be missing info on these files [1][2] Has an ASF header > has been added incorrectly? How are they licensed and is that compatable with > the ALv2? > - No unexpected binary files > - All source files have ASF headers > - Can compile from source > > Thanks, > Justin > > > 1. > apache-daffodil-2.1.0-incubating-src/daffodil-test/src/test/resources/org/apache/daffodil/usertests/json5.dfdl.xsd > 2. > apache-daffodil-2.1.0-incubating-src/daffodil-test/src/test/resources/org/apache/daffodil/usertests/testWSPStar.dfdl.xsd > - > 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 Daffodil (incubating) 2.1.0-rc3
Hi all, We are still in need of a couple more +1's. I'd appreciate it if you could find some time to take a look at our release. Thanks, - Steve On 04/09/2018 07:24 PM, Steve Lawrence wrote: > The Apache Daffodil community has voted and approved the proposed > release of Apache Daffodil (incubating) 2.1.0-rc3. > > 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/10811e8f520bf100a9250a3ae0610633e9018e0ae8fc422e2c0f097a@%3Cdev.daffodil.apache.org%3E > > Result thread: > https://lists.apache.org/thread.html/54a3e681b25f084e0dc46e19764cd19507ff502b927516093a3bd667@%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/2.1.0-rc3/ > > Staging artifacts can be found at: > > https://repository.apache.org/content/repositories/orgapachedaffodil-1002/ > > This release has been signed with PGP key 033AE661, corresponding to > slawre...@apache.org, which is included in the repository's KEYS file. > This key can be found on keyservers, such as: > > http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 > > It is also listed here: > > https://people.apache.org/keys/committer/slawrence.asc > > The release candidate has been tagged in git with v2.1.0-rc3. > > For reference, here is a list of all closed JIRAs tagged with 2.1.0: > > https://issues.apache.org/jira/browse/DAFFODIL-1897?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > For a summary of the changes in this release, see: > > https://daffodil.apache.org/releases/2.1.0/ > > Please review and vote. The vote will be open for at least 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks, > - Steve > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3
On 04/11/2018 02:51 PM, Matt Sicker wrote: > > On Wed, Apr 11, 2018 at 13:49, Steve Lawrence <slawre...@apache.org > <mailto:slawre...@apache.org>> wrote: > > The KEYS file was in dist/dev. I've moved it to dist/release, now > available here: > > https://www.apache.org/dist/incubator/daffodil/KEYS > > > Thanks! > > <https://www.apache.org/dist/incubator/daffodil/KEYS> > > Regarding the BSD-licenses, I don't believe the RAT CLI can detect BSD > licenses, or at least I haven't figured out how to get it to work if it > can. I'd love to hear if anyone knows. > > > I think we’d need to develop another header matcher instance for it. You can > add > custom license checks. I also published an sbt plugin that wraps rat into > your > build, so that might be easier since you could bundle the header matcher > itself > in your sbt build and add it to the configured licenses. I didn't see a way to add custom license checks via the CLI, but I may have missed it. The sbt plugin sounds very interesting--definitely something that could be useful to Daffodil, especially if it could add custom license checks. I'll take a look at it. > > > Thanks! > - Steve > > On 04/11/2018 01:32 PM, Matt Sicker wrote: > > * Signatures ok > > * License, disclaimer, notice ok > > * Rat check ok (using sbt-rat locally, though it doesn't seem to detect > > some BSD-licensed source files as such) > > * Builds/tests ok > > * But there's no KEYS file! This should be at > > https://www.apache.org/dist/incubator/daffodil/KEYS > > > > Please add the KEYS file to dist.a.o. > > > > On 9 April 2018 at 18:24, Steve Lawrence <slawre...@apache.org > <mailto:slawre...@apache.org>> wrote: > > > >> The Apache Daffodil community has voted and approved the proposed > >> release of Apache Daffodil (incubating) 2.1.0-rc3. > >> > >> 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/10811e8f520bf100a9250a3ae06106 > >> 33e9018e0ae8fc422e2c0f097a@%3Cdev.daffodil.apache.org > <http://3Cdev.daffodil.apache.org>%3E > >> > >> Result thread: > >> https://lists.apache.org/thread.html/54a3e681b25f084e0dc46e19764cd1 > >> 9507ff502b927516093a3bd667@%3Cdev.daffodil.apache.org > <http://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/2.1.0-rc3/ > >> > >> Staging artifacts can be found at: > >> > >> > https://repository.apache.org/content/repositories/orgapachedaffodil-1002/ > >> > >> This release has been signed with PGP key 033AE661, corresponding to > >> slawre...@apache.org <mailto:slawre...@apache.org>, which is included > in > the repository's KEYS file. > >> This key can be found on keyservers, such as: > >> > >> http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 > >> > >> It is also listed here: > >> > >> https://people.apache.org/keys/committer/slawrence.asc > >> > >> The release candidate has been tagged in git with v2.1.0-rc3. > >> > >> For reference, here is a list of all closed JIRAs tagged with 2.1.0: > >> > >> https://issues.apache.org/jira/browse/DAFFODIL-1897?jql= > >> project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202. > >> 1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > >> > >&g
Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3
The KEYS file was in dist/dev. I've moved it to dist/release, now available here: https://www.apache.org/dist/incubator/daffodil/KEYS Regarding the BSD-licenses, I don't believe the RAT CLI can detect BSD licenses, or at least I haven't figured out how to get it to work if it can. I'd love to hear if anyone knows. Thanks! - Steve On 04/11/2018 01:32 PM, Matt Sicker wrote: > * Signatures ok > * License, disclaimer, notice ok > * Rat check ok (using sbt-rat locally, though it doesn't seem to detect > some BSD-licensed source files as such) > * Builds/tests ok > * But there's no KEYS file! This should be at > https://www.apache.org/dist/incubator/daffodil/KEYS > > Please add the KEYS file to dist.a.o. > > On 9 April 2018 at 18:24, Steve Lawrence <slawre...@apache.org> wrote: > >> The Apache Daffodil community has voted and approved the proposed >> release of Apache Daffodil (incubating) 2.1.0-rc3. >> >> 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/10811e8f520bf100a9250a3ae06106 >> 33e9018e0ae8fc422e2c0f097a@%3Cdev.daffodil.apache.org%3E >> >> Result thread: >> https://lists.apache.org/thread.html/54a3e681b25f084e0dc46e19764cd1 >> 9507ff502b927516093a3bd667@%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/2.1.0-rc3/ >> >> Staging artifacts can be found at: >> >> https://repository.apache.org/content/repositories/orgapachedaffodil-1002/ >> >> This release has been signed with PGP key 033AE661, corresponding to >> slawre...@apache.org, which is included in the repository's KEYS file. >> This key can be found on keyservers, such as: >> >> http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 >> >> It is also listed here: >> >> https://people.apache.org/keys/committer/slawrence.asc >> >> The release candidate has been tagged in git with v2.1.0-rc3. >> >> For reference, here is a list of all closed JIRAs tagged with 2.1.0: >> >> https://issues.apache.org/jira/browse/DAFFODIL-1897?jql= >> project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202. >> 1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC >> >> For a summary of the changes in this release, see: >> >> https://daffodil.apache.org/releases/2.1.0/ >> >> Please review and vote. The vote will be open for at least 72 hours. >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Thanks, >> - Steve >> >> - >> 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
[VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3
The Apache Daffodil community has voted and approved the proposed release of Apache Daffodil (incubating) 2.1.0-rc3. 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/10811e8f520bf100a9250a3ae0610633e9018e0ae8fc422e2c0f097a@%3Cdev.daffodil.apache.org%3E Result thread: https://lists.apache.org/thread.html/54a3e681b25f084e0dc46e19764cd19507ff502b927516093a3bd667@%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/2.1.0-rc3/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachedaffodil-1002/ This release has been signed with PGP key 033AE661, corresponding to slawre...@apache.org, which is included in the repository's KEYS file. This key can be found on keyservers, such as: http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 It is also listed here: https://people.apache.org/keys/committer/slawrence.asc The release candidate has been tagged in git with v2.1.0-rc3. For reference, here is a list of all closed JIRAs tagged with 2.1.0: https://issues.apache.org/jira/browse/DAFFODIL-1897?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC For a summary of the changes in this release, see: https://daffodil.apache.org/releases/2.1.0/ Please review and vote. The vote will be open for at least 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc2
The Apache Daffodil (Incubating) 2.1.0-rc2 vote failed with one +1 binding vote and one -1 binding vote. +1 (binding): John D. Ament (carried over the from Daffodil dev vote) -1 (binding) and reasons: Justin Mclean - LICENSE is missing full text of the licenses, NOTICE contains unneeded information Vote thread: https://lists.apache.org/thread.html/1bc33636ec76ae80d390a0ac988d8e96f37190a3d1bc02f9668f78c1@%3Cgeneral.incubator.apache.org%3E We will prepare another release candidate to resolve the issues raised during this vote. Thanks, - Steve On 03/02/2018 02:50 PM, Steve Lawrence wrote: > The Apache Daffodil community has voted and approved the proposed > release of Apache Daffodil (Incubating) 2.1.0-rc2. > > 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/4b71db31a6a420098a18139a046c5493d5685137251b4727736a9f18@%3Cdev.daffodil.apache.org%3E > > Specific issues found during the rc2 VOTE that are planned to be > resolved in the next release include: > > DAFFODIL-1906: Updates to LICENSE/NOTICE files > https://issues.apache.org/jira/browse/DAFFODIL-1906 > > LEGAL-369: Guidance on Open Grid Forum (OGF) document inclusion > https://issues.apache.org/jira/browse/LEGAL-369 > > Result thread: > https://lists.apache.org/thread.html/f883421a96deffee80e59bd2fbbf07062dfe0ee26e4c4c4cfa194ba5@%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/2.1.0-rc2/ > > Staging artifacts can be found at: > > https://repository.apache.org/content/repositories/orgapachedaffodil-1001/ > > This release has been signed with PGP key 033AE661, corresponding to > slawre...@apache.org, which is included in the repository's KEYS file. > This key can be found on keyservers, such as: > > http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 > > It is also listed here: > > https://people.apache.org/keys/committer/slawrence.asc > > The release candidate has been tagged in git with v2.1.0-rc2. > > For reference, here is a list of all closed JIRAs tagged with 2.1.0: > > https://issues.apache.org/jira/browse/DAFFODIL-1897?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > For a summary of the changes in this release, see: > > https://daffodil.apache.org/releases/2.1.0/ > > Please review and vote. The vote will be open for at least 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks, > - Steve > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc2
The Apache Daffodil community has voted and approved the proposed release of Apache Daffodil (Incubating) 2.1.0-rc2. 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/4b71db31a6a420098a18139a046c5493d5685137251b4727736a9f18@%3Cdev.daffodil.apache.org%3E Specific issues found during the rc2 VOTE that are planned to be resolved in the next release include: DAFFODIL-1906: Updates to LICENSE/NOTICE files https://issues.apache.org/jira/browse/DAFFODIL-1906 LEGAL-369: Guidance on Open Grid Forum (OGF) document inclusion https://issues.apache.org/jira/browse/LEGAL-369 Result thread: https://lists.apache.org/thread.html/f883421a96deffee80e59bd2fbbf07062dfe0ee26e4c4c4cfa194ba5@%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/2.1.0-rc2/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachedaffodil-1001/ This release has been signed with PGP key 033AE661, corresponding to slawre...@apache.org, which is included in the repository's KEYS file. This key can be found on keyservers, such as: http://pgp.mit.edu/pks/lookup?op=get=0x033AE661 It is also listed here: https://people.apache.org/keys/committer/slawrence.asc The release candidate has been tagged in git with v2.1.0-rc2. For reference, here is a list of all closed JIRAs tagged with 2.1.0: https://issues.apache.org/jira/browse/DAFFODIL-1897?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC For a summary of the changes in this release, see: https://daffodil.apache.org/releases/2.1.0/ Please review and vote. The vote will be open for at least 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Daffodil into the Apache Incubator
Thank you for all that participated in the VOTE. The vote for entering Daffodil into the Apache Incubator is now closed. The vote has passed with: - three binding "+1" votes, and one non-binding "+1" votes - no "0" votes - no "-1" votes The votes were: +1, John D. Ament (binding) +1, Bertrand Delacretaz (binding) +1, Dave Fisher (binding) +1, Pierre Smits (non-binding) Vote thread: https://lists.apache.org/thread.html/694cdba8659ca588767fa6dda46fec709ac228c9d964c8ae2a3c73ba@%3Cgeneral.incubator.apache.org%3E I will work with the Daffodil mentors to start the podling creation process. Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Daffodil into the Apache Incubator
group of additional committers from a wide array of industries. === Reliance on Salaried Developers === The proposed initial committers are paid by their employer to contribute to the Daffodil project. We expect that Daffodil development will continue with salaried developers, and are committed to growing the community to include non-salaried developers as well. === Relationship with other Apache Projects === As mentioned in the Alignment section, Daffodil fills a clear gap in numerous other ASF projects that consume and manage large amounts of data. As a specific example, Daffodil developers have created a Daffodil Apache NiFi Processor, currently in use in data transfer solutions, which allows one to ingest non-native data into an Apache NiFi pipeline as XML or JSON. This processor was well received by the Apache NiFi developers, with positive comments about the concise API and how it could handle non-native data. Daffodil developers have also successfully prototyped integration with Apache Spark. We believe Daffodil could provide a strong benefit to many other ASF projects that handle fixed format data. We anticipate working closely with such ASF projects to include Daffodil where applicable to increase their ability to support new data formats with minimal effort. Daffodil also depends on existing ASF projects, including Apache Commons and Apache Xerces. === An Excessive Fascination with the Apache Brand === Although the Apache brand may certainly help to attract more contributors, publicity is not the reason for this proposal. We believe Daffodil could provide a great benefit to the ASF and the numerous data focused projects that comprise it, as described in the Rationale and Alignment sections. We hope to build a strong and vibrant community built around The Apache Way, and not dependent on a single company. === Documentation === Daffodil documentation can be found at: * https://opensource.ncsa.illinois.edu/confluence/display/DFDL/Daffodil%3A+Open+Source+DFDL Information about DFDL can be found at: * https://www.ogf.org/ogf/doku.php/standards/dfdl/dfdl * https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/df20060_.htm Public examples of DFDL Schemas can be found at: * https://github.com/DFDLSchemas == Initial Source == The Daffodil git repo goes back to mid-2011 with approximately 20 different contributors and feedback from many users and developers. The core codebase is written in Scala and includes both a Scala and Java API, along with Javadocs and Scaladocs for API usage. The initial code will come from the git repository currently hosted by NCSA at the University of Illinois : https://opensource.ncsa.illinois.edu/bitbucket/projects/DFDL/repos/daffodil/ == Source and Intellectual Property Submission == The complete Daffodil code is licensed under the University of Illinois/NCSA Open Source License. Much of the current codebase has been developed by Tresys Technology, who is open to relicensing the code to the Apache License version 2.0 and donate the source to the ASF. Contacts at NCSA are also open to relicensing their contributions to Apache v2. We plan to contact the other contributors and ask for permission to relicense and donate their contributed code. For those that decline or we cannot contact, their code will be removed or replaced. We will work closely with Apache Legal to ensure all issues related to relicensing are acceptable. == External Dependencies == We believe all current dependencies are compatible with the ASF guidelines. Our dependency licenses come from the following license styles: Apache v2, BSD, MIT, and ICU. The list of current Daffodil dependencies and their licenses are documented here: https://opensource.ncsa.illinois.edu/confluence/display/DFDL/Dependencies+and+Licenses == Cryptography == None == Required Resources == === Mailing Lists === * comm...@daffodil.incubator.apache.org * d...@daffodil.incubator.apache.org * priv...@daffodil.incubator.apache.org * u...@daffodil.incubator.apache.org === Source Control === git://git.apache.org/incubator-daffodil.git === Issue Tracking === JIRA Daffodil (DFDL) === Initial Committers === * Beth Finnegan * Dave Thompson * Josh Adams * Mike Beckerle * Steve Lawrence * Taylor Wise === Affiliations === * Beth Finnegan (Tresys Technology) * Dave Thompson (Tresys Technology) * Josh Adams (Tresys Technology) * Mike Beckerle (Tresys Technology) * Steve Lawrence (Tresys Technology) * Taylor Wise (Tresys Technology) == Sponsors == === Champion === * John D. Ament === Nominated Mentors === * Dave Fisher * John D. Ament * === Sponsoring Entity === We request the Apache Incubator to sponsor this project. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Daffodil Incubation Proposal
Sounds good to me. Can I start a vote, or is something a champion/mentor would normally start? The project also does not have a champion--is that necessary/would either of you be interested in being the champion? Thanks, - Steve On 08/08/2017 10:59 PM, Dave Fisher wrote: > Hi - > > I agree. I'm willing to proceed with John and I as Mentors. > > Regards, > Dave > > Sent from my iPhone > >> On Aug 8, 2017, at 7:10 PM, John D. Ament <johndam...@apache.org> wrote: >> >> Steve, >> >> At this point, I'd recommend we wrap the discussion and call for a vote. >> While ideally we want 3 mentors, we can get started with 2 and see how >> things progress. >> >> John >> >>> On Wed, Aug 2, 2017 at 3:55 PM Steve Lawrence >>> <stephen.d.lawre...@gmail.com> wrote: >>> Thanks John! >>> >>> On 08/02/2017 03:23 PM, John D. Ament wrote: >>>> You can also count me in as a mentor. >>>> >>>> John >>>> >>>> On Wed, Aug 2, 2017 at 3:14 PM Steve Lawrence >>>> <stephen.d.lawre...@gmail.com> >>>> wrote: >>>> >>>>> Understood. Thanks for the interest! >>>>> >>>>> - Steve >>>>> >>>>> On 08/02/2017 02:57 PM, Dave Fisher wrote: >>>>>> Hi Steve, >>>>>> >>>>>> It was not so much the lack of committers as it was the current >>>>> diversity. That is not a blocker for entry to Incubation. >>>>>> >>>>>> I am willing to be one of the Mentors. Once there are at least two more >>>>> we can push forward. >>>>>> >>>>>> Regards, >>>>>> Dave >>>>>> >>>>>>> On Aug 1, 2017, at 5:09 AM, Steve Lawrence < >>>>> stephen.d.lawre...@gmail.com> wrote: >>>>>>> >>>>>>> Discussions have died down, and I think the consensus from the responses >>>>>>> is that the issues are 1) the lack of committers and 2) the lack of a >>>>>>> champion and mentors. We hope to address #1 and grow the community as >>>>>>> part of incubation. Is anyone interested in being a champion or mentor >>>>>>> and help us with #2? >>>>>>> >>>>>>> Thanks, >>>>>>> - Steve >>>>>>> >>>>>>> On 07/26/2017 04:06 PM, Chris Mattmann wrote: >>>>>>>> This sounds like a very interesting project. >>>>>>>> >>>>>>>> I don’t have the time to mentor at the moment but I will keep a close >>>>> eye on it. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Chris Mattmann >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 7/25/17, 11:53 AM, "McHenry, Kenton Guadron" <mche...@illinois.edu> >>>>> wrote: >>>>>>>> >>>>>>>>Hi Dave, >>>>>>>> >>>>>>>>The developers that were at NCSA have moved on to other >>>>> organizations. While we still leverage Daffodil and are very much >>>>> interested in seeing it move forward, development is currently done by the >>>>> Tresys team. Agreed on the synergy with Tika. >>>>>>>> >>>>>>>>Kenton McHenry, Ph.D. >>>>>>>>Principal Research Scientist, Adjunct Assistant Professor of >>>>> Computer Science >>>>>>>>Deputy Director of the Scientific Software & Applications Division >>>>>>>>National Center for Supercomputing Applications, University of >>>>> Illinois at Urbana-Champaign >>>>>>>> >>>>>>>>On Jul 24, 2017, at 1:55 PM, Dave Fisher <dave2w...@comcast.net >>>>> <mailto:dave2w...@comcast.net>> wrote: >>>>>>>> >>>>>>>>Hi Kenton, >>>>>>>> >>>>>>>>Is there any reason that you and others from the NCSA are not >>>>> Initial Committers? That would make this proposal stronger. >>>>>>>> >>>>>>>>Regarding Apache Tika - it relies on other projects including >>&g
Re: [DISCUSS] Daffodil Incubation Proposal
Thanks John! On 08/02/2017 03:23 PM, John D. Ament wrote: > You can also count me in as a mentor. > > John > > On Wed, Aug 2, 2017 at 3:14 PM Steve Lawrence <stephen.d.lawre...@gmail.com> > wrote: > >> Understood. Thanks for the interest! >> >> - Steve >> >> On 08/02/2017 02:57 PM, Dave Fisher wrote: >>> Hi Steve, >>> >>> It was not so much the lack of committers as it was the current >> diversity. That is not a blocker for entry to Incubation. >>> >>> I am willing to be one of the Mentors. Once there are at least two more >> we can push forward. >>> >>> Regards, >>> Dave >>> >>>> On Aug 1, 2017, at 5:09 AM, Steve Lawrence < >> stephen.d.lawre...@gmail.com> wrote: >>>> >>>> Discussions have died down, and I think the consensus from the responses >>>> is that the issues are 1) the lack of committers and 2) the lack of a >>>> champion and mentors. We hope to address #1 and grow the community as >>>> part of incubation. Is anyone interested in being a champion or mentor >>>> and help us with #2? >>>> >>>> Thanks, >>>> - Steve >>>> >>>> On 07/26/2017 04:06 PM, Chris Mattmann wrote: >>>>> This sounds like a very interesting project. >>>>> >>>>> I don’t have the time to mentor at the moment but I will keep a close >> eye on it. >>>>> >>>>> Cheers, >>>>> Chris Mattmann >>>>> >>>>> >>>>> >>>>> >>>>> On 7/25/17, 11:53 AM, "McHenry, Kenton Guadron" <mche...@illinois.edu> >> wrote: >>>>> >>>>>Hi Dave, >>>>> >>>>>The developers that were at NCSA have moved on to other >> organizations. While we still leverage Daffodil and are very much >> interested in seeing it move forward, development is currently done by the >> Tresys team. Agreed on the synergy with Tika. >>>>> >>>>>Kenton McHenry, Ph.D. >>>>>Principal Research Scientist, Adjunct Assistant Professor of >> Computer Science >>>>>Deputy Director of the Scientific Software & Applications Division >>>>>National Center for Supercomputing Applications, University of >> Illinois at Urbana-Champaign >>>>> >>>>>On Jul 24, 2017, at 1:55 PM, Dave Fisher <dave2w...@comcast.net >> <mailto:dave2w...@comcast.net>> wrote: >>>>> >>>>>Hi Kenton, >>>>> >>>>>Is there any reason that you and others from the NCSA are not >> Initial Committers? That would make this proposal stronger. >>>>> >>>>>Regarding Apache Tika - it relies on other projects including >> Apache POI and Apache PDFBox. They are pragmatic about what is used. If >> Daffodil works to expand then I think that there would be good synergy >> between the projects. I know as a POI PMC member that the POI community has >> significantly benefited from the Tika community some of whom are from Mitre. >>>>> >>>>>To date Tika has not emphasized structured data, although they do >> extract content from Excel and OpenOffice. >>>>> >>>>>I am intrigued. >>>>> >>>>>Regards, >>>>>Dave >>>>> >>>>>On Jul 24, 2017, at 10:55 AM, McHenry, Kenton Guadron < >> mche...@illinois.edu<mailto:mche...@illinois.edu>> wrote: >>>>> >>>>>Yes, DFDL and its open source implementation Daffodil are more >> about file formats and getting access to the entirety of a file's contents >> in a consistent way through machine readable specifications. The work has >> implications in the area of digital preservation allowing one to preserve >> these machine readable specifications rather than all the tools needed to >> open/save a file in order to work with it. Imagine someone developing >> graphics software to work with 3D models and not having to worry about the >> hundreds of formats out there for 3D meshes (whether there are tools for >> opening the files and whether they can get access to those tools, whether >> the spec is available and worrying about how complex that spec is to >> implement, etc.), and simply building their code around the contents (e.g. >> vertices, faces, etc.). One could come up with similar
Re: [DISCUSS] Daffodil Incubation Proposal
Understood. Thanks for the interest! - Steve On 08/02/2017 02:57 PM, Dave Fisher wrote: > Hi Steve, > > It was not so much the lack of committers as it was the current diversity. > That is not a blocker for entry to Incubation. > > I am willing to be one of the Mentors. Once there are at least two more we > can push forward. > > Regards, > Dave > >> On Aug 1, 2017, at 5:09 AM, Steve Lawrence <stephen.d.lawre...@gmail.com> >> wrote: >> >> Discussions have died down, and I think the consensus from the responses >> is that the issues are 1) the lack of committers and 2) the lack of a >> champion and mentors. We hope to address #1 and grow the community as >> part of incubation. Is anyone interested in being a champion or mentor >> and help us with #2? >> >> Thanks, >> - Steve >> >> On 07/26/2017 04:06 PM, Chris Mattmann wrote: >>> This sounds like a very interesting project. >>> >>> I don’t have the time to mentor at the moment but I will keep a close eye >>> on it. >>> >>> Cheers, >>> Chris Mattmann >>> >>> >>> >>> >>> On 7/25/17, 11:53 AM, "McHenry, Kenton Guadron" <mche...@illinois.edu> >>> wrote: >>> >>>Hi Dave, >>> >>>The developers that were at NCSA have moved on to other organizations. >>> While we still leverage Daffodil and are very much interested in seeing it >>> move forward, development is currently done by the Tresys team. Agreed on >>> the synergy with Tika. >>> >>>Kenton McHenry, Ph.D. >>>Principal Research Scientist, Adjunct Assistant Professor of Computer >>> Science >>>Deputy Director of the Scientific Software & Applications Division >>>National Center for Supercomputing Applications, University of Illinois >>> at Urbana-Champaign >>> >>>On Jul 24, 2017, at 1:55 PM, Dave Fisher >>> <dave2w...@comcast.net<mailto:dave2w...@comcast.net>> wrote: >>> >>>Hi Kenton, >>> >>>Is there any reason that you and others from the NCSA are not Initial >>> Committers? That would make this proposal stronger. >>> >>>Regarding Apache Tika - it relies on other projects including Apache POI >>> and Apache PDFBox. They are pragmatic about what is used. If Daffodil works >>> to expand then I think that there would be good synergy between the >>> projects. I know as a POI PMC member that the POI community has >>> significantly benefited from the Tika community some of whom are from Mitre. >>> >>>To date Tika has not emphasized structured data, although they do >>> extract content from Excel and OpenOffice. >>> >>>I am intrigued. >>> >>>Regards, >>>Dave >>> >>>On Jul 24, 2017, at 10:55 AM, McHenry, Kenton Guadron >>> <mche...@illinois.edu<mailto:mche...@illinois.edu>> wrote: >>> >>>Yes, DFDL and its open source implementation Daffodil are more about >>> file formats and getting access to the entirety of a file's contents in a >>> consistent way through machine readable specifications. The work has >>> implications in the area of digital preservation allowing one to preserve >>> these machine readable specifications rather than all the tools needed to >>> open/save a file in order to work with it. Imagine someone developing >>> graphics software to work with 3D models and not having to worry about the >>> hundreds of formats out there for 3D meshes (whether there are tools for >>> opening the files and whether they can get access to those tools, whether >>> the spec is available and worrying about how complex that spec is to >>> implement, etc.), and simply building their code around the contents (e.g. >>> vertices, faces, etc.). One could come up with similar scenarios for other >>> data types (documents, images, videos, audio, depth data, numeric data). >>> Ideally tools built supporting DFDL, could someday, support any format for >>> that type without the developer having to worry about the details of how >>> that data is represented within a file. >>> >>>Kenton McHenry, Ph.D. >>>Principal Research Scientist, Adjunct Assistant Professor of Computer >>> Science >>>Deputy Director of the Scientific Software & Applications Division >>>National Center for Su
Re: [DISCUSS] Daffodil Incubation Proposal
Discussions have died down, and I think the consensus from the responses is that the issues are 1) the lack of committers and 2) the lack of a champion and mentors. We hope to address #1 and grow the community as part of incubation. Is anyone interested in being a champion or mentor and help us with #2? Thanks, - Steve On 07/26/2017 04:06 PM, Chris Mattmann wrote: > This sounds like a very interesting project. > > I don’t have the time to mentor at the moment but I will keep a close eye on > it. > > Cheers, > Chris Mattmann > > > > > On 7/25/17, 11:53 AM, "McHenry, Kenton Guadron" <mche...@illinois.edu> wrote: > > Hi Dave, > > The developers that were at NCSA have moved on to other organizations. > While we still leverage Daffodil and are very much interested in seeing it > move forward, development is currently done by the Tresys team. Agreed on > the synergy with Tika. > > Kenton McHenry, Ph.D. > Principal Research Scientist, Adjunct Assistant Professor of Computer > Science > Deputy Director of the Scientific Software & Applications Division > National Center for Supercomputing Applications, University of Illinois > at Urbana-Champaign > > On Jul 24, 2017, at 1:55 PM, Dave Fisher > <dave2w...@comcast.net<mailto:dave2w...@comcast.net>> wrote: > > Hi Kenton, > > Is there any reason that you and others from the NCSA are not Initial > Committers? That would make this proposal stronger. > > Regarding Apache Tika - it relies on other projects including Apache POI > and Apache PDFBox. They are pragmatic about what is used. If Daffodil works > to expand then I think that there would be good synergy between the projects. > I know as a POI PMC member that the POI community has significantly benefited > from the Tika community some of whom are from Mitre. > > To date Tika has not emphasized structured data, although they do extract > content from Excel and OpenOffice. > > I am intrigued. > > Regards, > Dave > > On Jul 24, 2017, at 10:55 AM, McHenry, Kenton Guadron > <mche...@illinois.edu<mailto:mche...@illinois.edu>> wrote: > > Yes, DFDL and its open source implementation Daffodil are more about file > formats and getting access to the entirety of a file's contents in a > consistent way through machine readable specifications. The work has > implications in the area of digital preservation allowing one to preserve > these machine readable specifications rather than all the tools needed to > open/save a file in order to work with it. Imagine someone developing > graphics software to work with 3D models and not having to worry about the > hundreds of formats out there for 3D meshes (whether there are tools for > opening the files and whether they can get access to those tools, whether the > spec is available and worrying about how complex that spec is to implement, > etc.), and simply building their code around the contents (e.g. vertices, > faces, etc.). One could come up with similar scenarios for other data types > (documents, images, videos, audio, depth data, numeric data). Ideally tools > built supporting DFDL, could someday, support any format for that type > without the developer having to worry about the details of how that data is > represented within a file. > > Kenton McHenry, Ph.D. > Principal Research Scientist, Adjunct Assistant Professor of Computer > Science > Deputy Director of the Scientific Software & Applications Division > National Center for Supercomputing Applications, University of Illinois > at Urbana-Champaign > > On Jul 24, 2017, at 10:30 AM, Steve Lawrence > <stephen.d.lawre...@gmail.com<mailto:stephen.d.lawre...@gmail.com><mailto:stephen.d.lawre...@gmail.com>> > wrote: > > I'll preface this saying that I don't have a ton of experience with > Apache Tika. But based on my understanding, Tika and Daffodil do have > somewhat similar goals, but reach them in different ways. For example, > Tika requires that one writes /code/ to perform data extraction, usually > relying on existing Java libraries to extract the desired metadata. The > downside to this is that code can be buggy, and libraries might not even > exist for formats of interest (especially common with legacy and > military data). > > Daffodil, on the other hand, does not require one to write any code. > Instead, one writes a DFDL Schema (similar to XML Schema, with DFDL > annotations) that fully describes the data, which Daffodil then uses to
Re: [DISCUSS] Daffodil Incubation Proposal
I've emailed two Apache NiFi committers, but I did not realize that they were not ASF members, so couldn't be a champion. One of them reached out to an IPMC member who said that it was fine to write a proposal and send it to the gen@incubator without having a champion, and this could be a good way to find a champion/mentors. The code is actually licensed under the University of Illinois/NCSA license [1], which is a combination of the MIT and 3-clause BSD licenses. But we do plan on relicensing to Apache v2 upon entering incubation. Tresys and NCSA (who contributed the bulk of the code) are both open to relicensing to Apache v2. We have not yet reached out to the other contributors, but we do not expect issues with this. Either we think they will have no objections, or their contributions (which are relatively small) can be removed and/or replaced. And we're absolutely open to granting committership to others. We have granted committership to others in the past, but over time, they have moved on to other projects/companies and did not continue contributions. One of our main goals in joining incubation is to grow the developer community beyond just Tresys. - Steve [1] https://opensource.org/licenses/NCSA On 07/24/2017 01:06 PM, John D. Ament wrote: > Hi, > > This looks like a very interesting proposal. It's a bit worrisome though > that you have no champion or mentor. Have you been in contact with anyone > at the ASF on this? > > I see that the existing code appears to have 3 different copyright holders, > and all code is derived from the BSD-3-clause license. It appears that all > of the initial developers are from a single holder, Tresys. Is there any > interest in granting committership to the other contributors? > > John > > On Mon, Jul 24, 2017 at 11:30 AM Steve Lawrence < > stephen.d.lawre...@gmail.com> wrote: > >> I'll preface this saying that I don't have a ton of experience with >> Apache Tika. But based on my understanding, Tika and Daffodil do have >> somewhat similar goals, but reach them in different ways. For example, >> Tika requires that one writes /code/ to perform data extraction, usually >> relying on existing Java libraries to extract the desired metadata. The >> downside to this is that code can be buggy, and libraries might not even >> exist for formats of interest (especially common with legacy and >> military data). >> >> Daffodil, on the other hand, does not require one to write any code. >> Instead, one writes a DFDL Schema (similar to XML Schema, with DFDL >> annotations) that fully describes the data, which Daffodil then uses to >> convert the data to XML/JSON for extraction. So adding support for a new >> format means writing a new schema rather than new code. And less code >> generally means less bugs. Also, for secure systems that require >> certification, generally speaking, it is easier to certify a schema as >> compared to code. >> >> We certainly don't believe that Daffodil could replace Tika, but it does >> have the potential to add new functionality to Tika for formats that do >> not have existing libraries. One of our goals is to look into >> integrating Daffodil support into tools like Tika. We'd love to hear >> from Tika devs if this is something they'd be interested in. >> >> I'll also add that whereas Tika tends to focus primarily on metadata, >> DFDL schemas usually describe an entire file format down to the byte, so >> one can extract more than just meta data, including text and binary >> data. Further differentiating, Daffodil has support for serializing data >> (called unparse) from the XML/JSON representation, allowing one to >> transform or filter data as well. We don't believe this feature is all >> that applicable to Tika, but may be useful to other technologies such as >> filtering or data fuzzing technologies. >> >> - Steve >> >> >> On 07/24/2017 10:59 AM, Mike Drob wrote: >>> What is the relationship between Daffodil and something like Apache >> Tika's >>> extraction engine? >>> >>> On Mon, Jul 24, 2017 at 9:53 AM, Steve Lawrence < >>> stephen.d.lawre...@gmail.com> wrote: >>> >>>> Dear Apache Incubator Community, >>>> >>>> We would like to start a discussion around a proposal to bring Daffodil >>>> into the Apache Incubator. Daffodil is a implementation of the DFDL >>>> specification used to convert between fixed format data and XML/JSON. >>>> >>>> The draft proposal can be found in the wiki at the following URL: >>>> >>>> https://wiki.apache.org/incubator/DaffodilProposal >>>> >
Re: [DISCUSS] Daffodil Incubation Proposal
I'll preface this saying that I don't have a ton of experience with Apache Tika. But based on my understanding, Tika and Daffodil do have somewhat similar goals, but reach them in different ways. For example, Tika requires that one writes /code/ to perform data extraction, usually relying on existing Java libraries to extract the desired metadata. The downside to this is that code can be buggy, and libraries might not even exist for formats of interest (especially common with legacy and military data). Daffodil, on the other hand, does not require one to write any code. Instead, one writes a DFDL Schema (similar to XML Schema, with DFDL annotations) that fully describes the data, which Daffodil then uses to convert the data to XML/JSON for extraction. So adding support for a new format means writing a new schema rather than new code. And less code generally means less bugs. Also, for secure systems that require certification, generally speaking, it is easier to certify a schema as compared to code. We certainly don't believe that Daffodil could replace Tika, but it does have the potential to add new functionality to Tika for formats that do not have existing libraries. One of our goals is to look into integrating Daffodil support into tools like Tika. We'd love to hear from Tika devs if this is something they'd be interested in. I'll also add that whereas Tika tends to focus primarily on metadata, DFDL schemas usually describe an entire file format down to the byte, so one can extract more than just meta data, including text and binary data. Further differentiating, Daffodil has support for serializing data (called unparse) from the XML/JSON representation, allowing one to transform or filter data as well. We don't believe this feature is all that applicable to Tika, but may be useful to other technologies such as filtering or data fuzzing technologies. - Steve On 07/24/2017 10:59 AM, Mike Drob wrote: > What is the relationship between Daffodil and something like Apache Tika's > extraction engine? > > On Mon, Jul 24, 2017 at 9:53 AM, Steve Lawrence < > stephen.d.lawre...@gmail.com> wrote: > >> Dear Apache Incubator Community, >> >> We would like to start a discussion around a proposal to bring Daffodil >> into the Apache Incubator. Daffodil is a implementation of the DFDL >> specification used to convert between fixed format data and XML/JSON. >> >> The draft proposal can be found in the wiki at the following URL: >> >> https://wiki.apache.org/incubator/DaffodilProposal >> >> We do not yet have a champion or mentors, but it was recommended that we >> create a proposal and send it to this list to potentially find those >> that might be interested. The text for the draft proposal is found >> below. We look forward to your input. >> >> Thanks, >> -Steve >> >> >> = Daffodil Proposal = >> >> == Abstract == >> >> Daffodil is an implementation of the Data Format Description Language >> (DFDL) used to convert between fixed format data and XML/JSON. >> >> == Proposal == >> >> The Data Format Description Language (DFDL) is a specification, >> developed by the Open Grid Forum, capable of describing many data >> formats, including both textual and binary, scientific and numeric, >> legacy and modern, commercial record-oriented, and many industry and >> military standards. It defines a language that is a subset of W3C XML >> schema to describe the logical format of the data, and annotations >> within the schema to describe the physical representation. >> >> Daffodil is an open source implementation of the DFDL specification that >> uses these 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. >> >> == Background == >> >> Many different software solutions need to consume and manage data, >> including data directed routing, databases, data analysis, data >> cleansing, data visualizing, and more. A key aspect of such solutions is >> the need to transform the data into an easily consumable format. >> Usually, this means that for each unique data format, one develops a >> tool that can read and extract the necessary information, often leading >> to ad-hoc and data-format-specific description systems. Such systems are >> often proprietary, not well tested, and incompatible, leading to vendor >> lo
[DISCUSS] Daffodil Incubation Proposal
pect that Daffodil development will continue with salaried developers, and are committed to growing the community to include non-salaried developers as well. === Relationship with other Apache Projects === As mentioned in the Alignment section, Daffodil fills a clear gap in numerous other ASF projects that consume and manage large amounts of data. As a specific example, Daffodil developers have created a Daffodil Apache !NiFi Processor, currently in use in data transfer solutions, which allows one to ingest non-native data into an Apache !NiFi pipeline as XML or JSON. This processor was well received by the Apache !NiFi developers, with positive comments about the concise API and how it could handle non-native data. Daffodil developers have also successfully prototyped integration with Apache Spark. We believe Daffodil could provide a strong benefit to many other ASF projects that handle fixed format data. We anticipate working closely with such ASF projects to include Daffodil where applicable to increase their ability to support new data formats with minimal effort. Daffodil also depends on existing ASF projects, including Apache Commons and Apache Xerces. === An Excessive Fascination with the Apache Brand === Although the Apache brand may certainly help to attract more contributors, publicity is not the reason for this proposal. We believe Daffodil could provide a great benefit to the ASF and the numerous data focused projects that comprise it, as described in the Rationale and Alignment sections. We hope to build a strong and vibrant community built around The Apache Way, and not dependent on a single company. === Documentation === Daffodil documentation can be found at: * https://opensource.ncsa.illinois.edu/confluence/display/DFDL/Daffodil%3A+Open+Source+DFDL Information about DFDL can be found at: * https://www.ogf.org/ogf/doku.php/standards/dfdl/dfdl * https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/df20060_.htm Public examples of DFDL Schemas can be found at: * https://github.com/DFDLSchemas == Initial Source == The Daffodil git repo goes back to mid-2011 with approximately 20 different contributors and feedback from many users and developers. The core codebase is written in Scala and includes both a Scala and Java API, along with Javadocs and Scaladocs for API usage. The initial code will come from the git repository currently hosted by NCSA at the University of Illinois : https://opensource.ncsa.illinois.edu/bitbucket/projects/DFDL/repos/daffodil/ == Source and Intellectual Property Submission == The complete Daffodil code is licensed under the University of Illinois/NCSA Open Source License. Much of the current codebase has been developed by Tresys Technology, who is open to relicensing the code to the Apache License version 2.0 and donate the source to the ASF. Contacts at NCSA are also open to relicensing their contributions to Apache v2. We plan to contact the other contributors and ask for permission to relicense and donate their contributed code. For those that decline or we cannot contact, their code will be removed or replaced. We will work closely with Apache Legal to ensure all issues related to relicensing are acceptable. == External Dependencies == We believe all current dependencies are compatible with the ASF guidelines. Our dependency licenses come from the following license styles: Apache v2, BSD, MIT, and ICU. The list of current Daffodil dependencies and their licenses are documented here: https://opensource.ncsa.illinois.edu/confluence/display/DFDL/Dependencies+and+Licenses == Cryptography == None == Required Resources == === Mailing Lists === * comm...@daffodil.incubator.apache.org * d...@daffodil.incubator.apache.org * priv...@daffodil.incubator.apache.org * u...@daffodil.incubator.apache.org === Source Control === git://git.apache.org/incubator-daffodil.git === Issue Tracking === JIRA Daffodil (DFDL) === Initial Committers === * Beth Finnegan * Dave Thompson * Josh Adams * Mike Beckerle * Steve Lawrence * Taylor Wise === Affiliations === * Beth Finnegan (Tresys Technology) * Dave Thompson (Tresys Technology) * Josh Adams (Tresys Technology) * Mike Beckerle (Tresys Technology) * Steve Lawrence (Tresys Technology) * Taylor Wise (Tresys Technology) == Sponsors == === Champion === * TBD === Nominated Mentors === * TBD === Sponsoring Entity === We request the Apache Incubator to sponsor this project. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Edit access to wiki for proposal
I would like to request edit access to the incubator wiki so that I can create a new proposal. My wiki username is: SteveLawrence Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
