You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by Keon Amini <ke...@merico.dev.INVALID> on 2023/01/31 17:22:51 UTC
DevLake's podling report (January 2023)
Hi all,
Below is our podling status report for January 2023. Thanks to all the people who gave their comments and our contributors of the project.
DevLake is a development data platform, providing the data infrastructure for developer teams to analyze and improve their engineering productivity.
DevLake has been incubating since 2022-04-29.
Three most important unfinished issues to address before graduating:
1. Grow the community, add committers and PPMC members
2. Grow the ecosystem, support more data sources and use cases
Are there any issues that the IPMC or ASF Board need to be aware of?
No issues at the moment.
How has the community developed since the last report?
1. 22 new contributors have joined the community (78 contibuters in total)
2. One new committer was elected
3. Hosted a total of 10 community meetups, including an end-of-year community celebration event.
How has the project developed since the last report?
1. Made one new major release (currently in voting process)
2. Support for projects in DevLake for custom aggregation of metrics”
3. Better support for parallelism in Blueprint executions
4. Github data collection now uses GraphQL queries by default where possible for much better performance
5. Support for skipping failed pipeline stages to allow partial data collection
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:
2023-01-18
When were the last committers or PPMC members elected?
2022-11-01
Have your mentors been helpful and responsive?
Yes, the mentors helped tremendously throughout version releases and community governance.
Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues.
Re: DevLake's podling report (January 2023)
Posted by Hezheng Yin <yi...@gmail.com>.
Hi community,
I've migrated the draft to confluence:
https://cwiki.apache.org/confluence/display/INCUBATOR/February2023
Our podling report for Feb 2023 is out. Thank you!
Best,
Hezheng
On Tue, Jan 31, 2023 at 7:00 PM Hezheng Yin <yi...@gmail.com>
wrote:
> Hi Keon,
>
> Thanks for taking the initiative. This report looks good to me!
>
> Best,
> Hezheng
>
> On Tue, Jan 31, 2023 at 9:23 AM Keon Amini <ke...@merico.dev.invalid>
> wrote:
>
>> Hi all,
>>
>> Below is our podling status report for January 2023. Thanks to all the
>> people who gave their comments and our contributors of the project.
>>
>>
>> DevLake is a development data platform, providing the data infrastructure
>> for developer teams to analyze and improve their engineering productivity.
>>
>> DevLake has been incubating since 2022-04-29.
>>
>> Three most important unfinished issues to address before graduating:
>>
>> 1. Grow the community, add committers and PPMC members
>> 2. Grow the ecosystem, support more data sources and use cases
>>
>> Are there any issues that the IPMC or ASF Board need to be aware of?
>>
>> No issues at the moment.
>>
>> How has the community developed since the last report?
>>
>> 1. 22 new contributors have joined the community (78 contibuters in
>> total)
>> 2. One new committer was elected
>> 3. Hosted a total of 10 community meetups, including an end-of-year
>> community celebration event.
>>
>> How has the project developed since the last report?
>>
>> 1. Made one new major release (currently in voting process)
>> 2. Support for projects in DevLake for custom aggregation of metrics”
>> 3. Better support for parallelism in Blueprint executions
>> 4. Github data collection now uses GraphQL queries by default where
>> possible for much better performance
>> 5. Support for skipping failed pipeline stages to allow partial data
>> collection
>>
>> 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:
>>
>> 2023-01-18
>>
>> When were the last committers or PPMC members elected?
>>
>> 2022-11-01
>>
>> Have your mentors been helpful and responsive?
>>
>> Yes, the mentors helped tremendously throughout version releases and
>> community governance.
>>
>> Is the PPMC managing the podling's brand / trademarks?
>>
>> There are no known brand and naming issues.
>>
>>
Re: DevLake's podling report (January 2023)
Posted by Hezheng Yin <yi...@gmail.com>.
Hi Keon,
Thanks for taking the initiative. This report looks good to me!
Best,
Hezheng
On Tue, Jan 31, 2023 at 9:23 AM Keon Amini <ke...@merico.dev.invalid>
wrote:
> Hi all,
>
> Below is our podling status report for January 2023. Thanks to all the
> people who gave their comments and our contributors of the project.
>
>
> DevLake is a development data platform, providing the data infrastructure
> for developer teams to analyze and improve their engineering productivity.
>
> DevLake has been incubating since 2022-04-29.
>
> Three most important unfinished issues to address before graduating:
>
> 1. Grow the community, add committers and PPMC members
> 2. Grow the ecosystem, support more data sources and use cases
>
> Are there any issues that the IPMC or ASF Board need to be aware of?
>
> No issues at the moment.
>
> How has the community developed since the last report?
>
> 1. 22 new contributors have joined the community (78 contibuters in
> total)
> 2. One new committer was elected
> 3. Hosted a total of 10 community meetups, including an end-of-year
> community celebration event.
>
> How has the project developed since the last report?
>
> 1. Made one new major release (currently in voting process)
> 2. Support for projects in DevLake for custom aggregation of metrics”
> 3. Better support for parallelism in Blueprint executions
> 4. Github data collection now uses GraphQL queries by default where
> possible for much better performance
> 5. Support for skipping failed pipeline stages to allow partial data
> collection
>
> 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:
>
> 2023-01-18
>
> When were the last committers or PPMC members elected?
>
> 2022-11-01
>
> Have your mentors been helpful and responsive?
>
> Yes, the mentors helped tremendously throughout version releases and
> community governance.
>
> Is the PPMC managing the podling's brand / trademarks?
>
> There are no known brand and naming issues.
>
>