I've updated the report on the wiki, with an additional mention of the runtime 2 interest.
https://cwiki.apache.org/confluence/display/INCUBATOR/March2020#Daffodil We still have have a few more days to make updates if there is anything else of interest to add. Just wanted to get this up before the weekend so I don't forget. On 2/28/20 11:25 AM, Beckerle, Mike wrote: > Julian has not been actively contributing, but just this week we got interest > from another developer who has not previously contributed, but who wants to > work on Runtime 2. > > That's why I actually have been rebasing that branch forward this week. > > > ________________________________ > From: Sloane, Brandon <bslo...@tresys.com> > Sent: Friday, February 28, 2020 10:52 AM > To: dev@daffodil.apache.org <dev@daffodil.apache.org> > Subject: Re: [DRAFT] Daffodil Podling Report - March 2020 > > What's the status with Runtime2? Is Julian still contributing to that effort? > ________________________________ > From: Steve Lawrence <slawre...@apache.org> > Sent: Friday, February 28, 2020 10:20 AM > To: dev@daffodil.apache.org <dev@daffodil.apache.org> > Subject: [DRAFT] Daffodil Podling Report - March 2020 > > Apache Daffodil is an implementation of the Data Format Description > Language (DFDL) used to convert between fixed format data and XML/JSON. > > Daffodil has been incubating since 2017-08-27. > > ### Three most important unfinished issues to address before graduating: > > 1. Increase community growth and participation beyond Tresys > (main priority) > 2. Work with other Apache projects where Daffodil could provide extra > functionality (NiFI and Drill are highest priority goals) > 3. Continue frequent release schedule > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > - None > > ### How has the community developed since the last report? > > - Continued mailing lists discussions, with a handful of new faces > asking questions on the users@ mailing list, hopefully some of these > can be converted to developers > - Struggling to get active involvement outside of Tresys. We are > actively working with known users of Daffodil to encourage > contributions, including virtual meetings and making time to help > spin up with the codebase > > ### How has the project developed since the last report? > > - Release Daffodil 2.5.0 > - 29 commits merged from 5 different contributors > - 44 issues created, 29 issues resolved, focus was primarily on large > features rather than bug burn down. > - Significant improvement to DFDL schema compilation time > - Incorporated SonarCloud static analysis to help verify code quality > - Lots of refactoring to improve code quality and type safety > - Created a container to streamline a repeatable release process > - Looking like next release will be sometime in March > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [X] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > 2020-01-12 > > ### When were the last committers or PPMC members elected? > > - 2019-11-26 - Olabusayo Kilo (Committer) > - 2019-06-20 - Brandon Sloane (PPMC) > > ### Have your mentors been helpful and responsive? > > - Yes > > ### Is the PPMC managing the podling's brand / trademarks? > > - No known cases of a 3rd party incorrectly using the Daffodil > name/brand. > - Podling name search has been completed and approved by Brand > Management Committee: > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-147 > >
