plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject WG: PLC4X Board Report due by Wed Mar 10th - Initial Reminder
Date Fri, 05 Mar 2021 08:47:26 GMT
Forwarding this to dev@ ... 

-----Ursprüngliche Nachricht-----
Von: Christofer Dutz <christofer.dutz@c-ware.de> 
Gesendet: Freitag, 5. März 2021 09:47
An: private@plc4x.apache.org
Betreff: AW: PLC4X Board Report due by Wed Mar 10th - Initial Reminder

Hi all,

So I just went through our emails and numbers and whipped up this report.
Feel free to comment:

----------------------------------------------------------------------

## 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:
There are currently no issues needing board attention.

## Membership Data:
Apache PLC4X was founded 2019-04-17 (2 years ago) There are currently 18 committers and 12
PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Ben Hutcheson on 2020-11-08.
- No new committers. Last addition was Ben Hutcheson on 2020-09-26.

## Project Activity:
In January we finally managed to bring all ongoing work to a state in which we could finally
do a release again. We are planning on releasing way more often after these intense refactoring
has been completed.

We have seen an increase of incoming questions and support-requests on the mailing list from
new sources, which seems to imply a growing usage in public.

The main areas the community has been working on are:
- Rebuilding the Kafka Connect adapter, having that validated and made
  available in the Confluent Hub for easy installation
- Implementing an MSPEC based OPC-UA driver for PLC4X, which will allow us to
  support OPC-UA in other languages (We were currently relying on Eclipse Milo
  for that)
- Creating an API for Discovery and Browsing (Testing this in PLC4Go)
- Implementing Auto-Discovery and Browsing for the KNX protocol

PLC4X has reported to be mentioned in more and more Industrial IoT related podcasts and videos.

Conference-wise this quarter has been very quiet. 

## Community Health:
I think the community is generally in a good shape and continuously growing.

We have continued our monthly community zoom call on every first Wednesday of the month, which
we stated last year, but this is mainly used for community building and sometimes for answering
questions, not for discussing important project matters.

- dev@plc4x.apache.org had a 13% decrease in traffic in the past quarter (363
  emails compared to 417)
- issues@plc4x.apache.org had a 198% increase in traffic in the past quarter
  (260 emails compared to 87)
- 24 issues opened in JIRA, past quarter (84% increase)
- 40 issues closed in JIRA, past quarter (344% increase)
- 377 commits in the past quarter (-23% decrease)
- 12 code contributors in the past quarter (9% increase)
- 17 PRs opened on GitHub, past quarter (-29% decrease)
- 20 PRs closed on GitHub, past quarter (-23% decrease)
- 305 Stars on GitHub (up by 45)
- 134 Forks on GitHub (up by 12)
- 421 Twitter Followers (up by 28)


-----Ursprüngliche Nachricht-----
Von: Roy T. Fielding <fielding@apache.org>
Gesendet: Freitag, 5. März 2021 02:51
An: Christofer Dutz <cdutz@apache.org>
Cc: private@plc4x.apache.org
Betreff: PLC4X Board Report due by Wed Mar 10th - Initial Reminder

Hello,

According to our records, you are listed as the chair of PLC4X, a committee that is due to
submit a report by Wed Mar 10th for the next ASF board meeting. This is an initial reminder
to prepare a report for PLC4X and submit it as described below.

In the Apache governance model, the ASF board delegates responsibility for managing projects
to PMCs. This allows projects to govern themselves, in terms of their own development goals,
guidelines, and volunteer spirit, within the scope of our purpose as an open source foundation.
The state allows us to provide an umbrella of corporate protection to our projects and volunteers,
but only to the extent that we retain active and effective oversight of each project's operation
on behalf of the public's interest.

To enable the board to provide oversight across the foundation, each PMC is tasked with providing
the board a quarterly report on the health of their project. This allows us to hear your heartbeat,
to see the project through your eyes, and to inform the public through our meeting minutes.

Thank you for being a responsible project chair and helping us maintain oversight over the
Apache Software Foundation. If, for whatever reason, a full report is not possible by the
deadline, please report just that.
It's okay to postpone a report by a month.

Please note that we will be reviewing and approving these reports, asynchronously, during
the week prior to our scheduled board meeting.
Reports received after Wed Mar 10th will be postponed to the next regular meeting. Please
try to submit your report early.


Submitting your report
----------------------

Full details about reporting to the board are at

  https://www.apache.org/foundation/board/reporting

Please be aware that the board is looking for your personal observations, assessment, and
ideas, not just raw statistics.

Chairs may use one of several mechanisms to submit or edit their report:

 a) the Apache Reporter Service
    https://reporter.apache.org/

 b) the Whimsy online agenda tool
    https://whimsy.apache.org/board/agenda/2021-03-17/PLC4X

 c) carefully editing and committing changes to the dated agenda in
    https://svn.apache.org/repos/private/foundation/board

 d) or, if none of the above work, send an email to board@apache.org with
    Subject: [REPORT] PLC4X

If you believe it won't be possible to prepare a report before the deadline, or if the PMC
is aware that the Chair is unavailable, please report that and we can reschedule or have someone
else report on your behalf.


Attending the Board Meeting
---------------------------

The formal board meeting (usually an online videoconference) will be held at

  Wed, 17 Mar 2021 at 20:00 UTC
  
which in other time zones is

  https://timeanddate.com/s/42ac

As always, chairs and ASF members are welcome to attend the board meeting.
However, in most cases, we will not be using meeting time to discuss reports unless you specifically
request time to speak in person.

During the week prior to the meeting, the directors will read the received reports, make comments
(if any) within the agenda tool, discuss those comments on the board and/or private committee
lists, and vote to approve.

If we have comments on a report, we will forward them during the review and attempt to complete
any associated action items as well.
This will allow us to be more responsive to project needs and give you an opportunity to expand
on your report if additional details are requested prior to the meeting.

Regular board meetings are held monthly, as scheduled at

  https://svn.apache.org/repos/private/committers/board/calendar.txt


Requesting a Board Action
-------------------------

If you want the board to make a decision related to your report, such as changing the chair,
establishing a new committee, or allocating a budget for something related to PLC4X, you should
author a resolution for that purpose or ask a director to do so for you.

To make this easier, there are several templates we use for common board resolutions. They
can be found in

  https://svn.apache.org/repos/private/committers/board/templates

or accessible within the Whimsy online agenda tool

  https://whimsy.apache.org/board/agenda/2021-03-17/PLC4X

If you do place a resolution before the board and that resolution has not been preapproved
before the board meeting, you are encouraged to attend the meeting in person to address any
last-minute questions or concerns that might arise.

Thanks,
The ASF Board
Mime
View raw message