Will do. I'll include it when adding the report to the wiki.

On 5/28/20 10:58 AM, Beckerle, Mike wrote:
> +1  Looks right to me.
> 
> Under community - if you want, you can add that Nteligen has two student 
> summer interns starting Daffodil-related projects next week.
> 
> Or we can wait until the next report. Either way.
> 
> 
> 
> 
> ________________________________
> From: Steve Lawrence <slawre...@apache.org>
> Sent: Thursday, May 28, 2020 9:43 AM
> To: dev@daffodil.apache.org <dev@daffodil.apache.org>
> Subject: [DRAFT] Daffodil Podling Report - June 2020
> 
> ## Daffodil
> 
> 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 Owl (formerly
>      Tresys) (main priority)
>   2. Work with other Apache projects where Daffodil could provide extra
>      functionality
>   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?
> 
>   - Pull requests merged from three first-time non-Owl contributors
>   - Continued involvement in the mailing lists
>       - dev: 78 postings, 5 new subscribers
>       - users: 96 postings, 4 new subscribers
>   - Owl is actively encouraging other companies with known Daffodil
>     interests to make contributions and increase involvement.
>     Anticipating initial on-list activity to begin in the coming weeks
>   - Daffodil integrated into Smooks (https://www.smooks.org) by outside
>     developers
> 
> ### How has the project developed since the last report?
> 
>   - Released Daffodil 2.6.0
>   - 56 commits merged from 7 different contributors
>   - Changes include thread-safe API improvements, cleanups based on
>     SonarCloud scans, improved validation of of input XML,
>     newVariableInstance feature, and many important misc bug fixes
>   - 59 issues created, 61 issues resolved
>   - Initial discussions and planning/ramping up on the proposed
>     code-generation runtime.
>   - New proposals and plans in place to improve Daffodil streaming
>     capabilities and memory requirement reduction--main focus for the
>     next release
> 
> ### 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-04-24
> 
> ### 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
> 
> 

Reply via email to