+1 Great to see those numbers

Just one small finding from me. "er" looks like a typo here

> At the same time er lowered the bar
for committership a little and redefined how we interpret the term

Am 5. März 2020, 09:43, um 09:43, Christofer Dutz <[email protected]> 
schrieb:
>## Description:
>The mission of the Apache PLC4X project is creating a set of libraries
>for
>communicating with industrial programmable logic controllers (PLCs)
>using a
>variety of protocols but with a shared API.
>
>## Issues:
>None
>
>## Membership Data:
>Apache PLC4X was founded 2019-04-17 (a year ago)
>There are currently 14 committers and 9 PMC members in this project.
>The Committer-to-PMC ratio is roughly 7:5.
>
>Community changes, past quarter:
>- No new PMC members. Last addition was Łukasz Dywicki on 2019-07-28.
>- Alvaro del Castillo was added as committer on 2020-01-29
>- César García was added as committer on 2020-02-03
>- Niklas Merz was added as committer on 2020-01-29
>- Lukas Ott was added as committer on 2020-01-03
>- Dominik Riemer was added as committer on 2020-02-04
>
>## Project Activity:
>- 0.6.0 was released on 2020-03-01
>
>In December we had a 3 day code retreat, where a large portion of the
>core-team meet and worked on addressing some of the most important
>architectural challenges in preparation to porting all of our drivers
>to the
>new generated codebase.
>
>In general have we started to maintain and fix a lot of reported issues
>in the
>0.6 branch which we now consider a LTS release branch. The version
>0.7.0 is a
>huge refactoring as we completely rewrote the core of PLC4X and are
>currently
>deleting all existing drivers, replacing them with new version which we
>generate from our new code-generation tool. Still 1-2 drivers to port,
>but
>most of the others are already finished.
>
>We completely relaunched our website, giving it a way more appealing
>look and
>feel as we think the old website was preventing people from giving
>PLC4X a
>chance.
>
>We are currently in the process of preparing the ASF to become member
>of a
>list of 4-5 industry foundation in order to allow us to legally be able
>to
>provide some drivers and or mention them on our website and other
>public
>information material.
>
>We have had Meetups/Conference-Talks/Workshops:
>- PLC4X full day workshop: Building IoT (02-03-2020)
>- Talks: Building IoT - Essen (03-03-2020, 04-03-2020)
>- Talk: Stuttgarter Innovationstage (03-03-2020)
>- Talk: OOP - Munich (05-02-2020)
>
>Perhaps worth mentioning:
>In December Christofer applied for European research funds via NLnet
>Foundation and was recently informed that his application was granted.
>So if
>this really will happen, then these funds will be used 100% for driving
>the
>C-type drivers for PLC4X as well as an Apache MyNewt integration.
>
>## Community Health:
>This year the number of contributors has grown quite a bit. Also the
>number of
>people showing up from different companies has increased significantly.
>
>Also starting this year we started to invite people as committer first
>and
>stopped instantly inviting them as PMC in one go, as we noticed some
>people
>became less active after becoming PMCs. At the same time er lowered the
>bar
>for committership a little and redefined how we interpret the term
>"committer". We treat committers as people who are committed to PLC4X
>and PMCs
>who have proven to be so for a prolonged period of time (not too long)
>
>- [email protected] had a 59% increase in traffic in the past
>quarter
>  (494 emails compared to 309)
>- [email protected] had a 444% increase in traffic in the past
>quarter
>  (305 emails compared to 56)
>- 23 issues opened in JIRA, past quarter (21% increase)
>- 20 issues closed in JIRA, past quarter (42% increase)
>- 490 commits in the past quarter (62% increase)
>- 17 code contributors in the past quarter (13% increase)
>- 28 PRs opened on GitHub, past quarter (21% increase)
>- 27 PRs closed on GitHub, past quarter (28% increase)
>- 172 Github Stars (up by 18 since last report) (up by 30)
>- 305 @ApachePLC4X Twitter account followers (up by 33)

Reply via email to