Skip to content

Commit

Permalink
Gathered feedback helium#1 and my feedback on the HIP
Browse files Browse the repository at this point in the history
Added myself as an author, let me know if this is appropriate or not - I'm just here to help, I’m happy to conference call to talk through the changes.
-Fixed a bunch of spelling and typo errors - might have added some more, hope not!
-Changed several sentences to be concise, you may want to check the spelling again, I've been at this a while.
-Added roles and subgroups to improvements under summary it is mentioned further through but not up there where it should have been
-Updated motivation wording to include statements from Tony Smith from 3rd March 2022 community zoom meeting with Helium reprehensive, also to recognise existing work
-Updated Stakeholders removed a title to keep with formatting of HIP
-Added how improvement will be achieved to first line of the detailed explanation, note this will mean the proposal is the create the Terms of Reference using the details as the minizine baseline rather then make the proposal the TOR.
-Updated recommendation to include makers and consumers rather than just operators (following Tony Smith's words as for mentioned).
-Removed part about contracts, not sure what you mean but I’m not legal so if it’s something on that…
-We may want to discuss the definition of an independent chair!
-Removed "and remaining committee members" from decision on conflict of interest, the TOR will have to describe what occurs if the chair has a conflict of interest.
-Added quorum statement, feel free to change and look at proxy use.
-Updated titles to use the role words instead of expected to be more consistent with a TOR and the improvements mentioned in summary.
-Added to chair and member roles some nominal common TOR ones
-Updated Drawbacks statement, no I didn’t add one about my conversation with our friendly discord community 😉
-Added to Rationale on reduced confidence statement as per a few comments from Helium discord.
-Added to the todo for out of scope and an unresolved question. Let me know if you can answer the unresolved question as IoT has a lot of inherent security issues.
  • Loading branch information
jamesmeikle authored Mar 18, 2022
1 parent 40b9a2f commit 6d94a22
Showing 1 changed file with 47 additions and 42 deletions.
89 changes: 47 additions & 42 deletions 00XX-lorawan-committee.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# LoRaWAN Committee

- Author(s): [@leogaggl](https://github.com/leogaggl), [@tonysmith55](https://github.com/tonysmith55), [@buzzware](https://github.com/buzzware)
- Author(s): [@leogaggl](https://github.com/leogaggl), [@tonysmith55](https://github.com/tonysmith55), [@buzzware](https://github.com/buzzware), [@jamesmeikle](https://github.com/jamesmeikle)
- Start Date: 2022-03-09
- Category: governance
- Original HIP PR: <!-- leave this empty; maintainer will fill in ID of this pull request -->
Expand All @@ -9,21 +9,25 @@
# Summary
[summary]: #summary

The proposed change of frequency plan for Australia has highlighted some major deficiencies on how the DEWI LoRaWAN committee is currently selected and how the process can be improved for all concerned and affected.
The proposed change of frequency plan for Australia highlighted some major deficiencies on how the DEWI LoRaWAN committee is currently selected, operated and how the process can be improved for all impacted by the committee decisions.

This HIP suggests a number of improvements in the following areas
1. Selection of members
This HIP suggests improvements in the following areas:
1. Selection of members and defining their roles
2. Declaration of conflict of interest
3. Governance procedures
4. Ethics guidelines
5. Process of including the affected regions in the decision-making process
6. Failures and consequences.
3. Governance procedures, such as reporting
4. Creation of sub groups to perform specific tasks or assignments to assist the committee decisions
5. Ethics guidelines
6. Process of including the affected regions in the decision-making process
7. Failures and consequences.

# Motivation
[motivation]: #motivation

Currently there are no publicly available terms of reference for the DEWI LoRaWAN committee.
Given that as a community of network builders , we are asked to contribute, directly or indirectly, financially and with effort and consideration. Now is the time to enact a governance framework that values those contributions.
Currently there are no publicly available Terms of Reference (TOR) for the DEWI LoRaWAN committee. This can place burden on the committee and the community creating an absence of clarity for both that has led to undesirable results.

Given the accelerated growth of the community, the number of diverse groups (such as makers, operators, and consumers) the number of diverse cultures (worldwide) that are asked to contribute time, financials (blood, sweat and tears) either directly or indirectly we believe it is now time to enact a governance framework that values all contributors to the community and continues to strengthen the resilience of it as it grows.

This proposed change should be seen as a positive for the existing committee, as due to their effort thus far the community has grown to the size and complexity that requires more formal governance.

# Stakeholders
[stakeholders]: #stakeholders
Expand All @@ -32,38 +36,35 @@ There are two (2) stakeholder groups with this HIP:
- DEWI LoRaWAN Committee
- A clear governance structure will support the DEWI LoRaWAN committee to ensure strong, objective, sustainable and inclusive growth, without bias and conflict.
- Wider Helium Ecosystem
- Without a clear articulated governance structure decisions made will inadvertedly create unintended consequeces. Such decisions without adequate consultation have the potential to create critical user issues and harm growth, which is the reason why selection and governance of this committee are so crucial.

- Without a clear articulated governance structure decisions made will inadvertedly create unintended consequences. Such decisions, without adequate consultation, have the potential to create critical user issues and harm growth, which is the reason why selection and governance of this committee are so crucial.

## Community and stakeholder engagement
We are reaching out to members
We have started reaching out to people
- Github repository feedback
- Helium Community HIP Discord channel
- Other relevant Helium Community Discord channels.

# Detailed Explanation
[detailed-explanation]: #detailed-explanation

The improvements are to be achieved by the development of a publically accessible Terms of Reference (TOR) that establishes the governance of the comittee, the following details provide a minimine guidence for what must be part of the TOR.

## Guiding principles of the committee
The committee has a responsiblity too:
The committee has a responsibility to:
- operate in a transparent, timely and accountable manner at all times
- communicate clearly and regularly with stakeholders and the DEWI as appropriate
- adopt existing LoRa Alliance standards where applicable
- act in conformance with the relevant regulatory bodies in each regionReport to wider Helium Community via meeting minutes and / or communiques on meeting outcomesReport to wider Helium Community via meeting minutes and / or communiques on meeting outcomesReport to wider Helium Community via meeting minutes and / or communiques on meeting outcomesReport to wider Helium Community via meeting minutes and / or communiques on meeting outcomes
- act in conformance with the relevant regulatory bodies in each region
- report to wider Helium Community via publicly accessible meeting minutes and / or communiques on meeting outcomes
- endeavour to reach consensus within the committee, taking into account the views of all members.


The committee’s recommendations must:
- not be inconsistent with LoRa Alliance standards and directives by regional regulators
- be based on the best available scientific information, evidence based policy and encourage best practice in the Helium ecosystem
- balance the technical implications and impacts of changes with the practicalities of operators in the wider Helium ecosystem
- balance the technical implications and impacts of changes with the practicalities of operators, makers and consumers in the wider Helium ecosystem
- be clear, logical and verifiable
- demonstrate that the views of affected stakeholder groups have been considered
- aim to reduce unnecessary, ineffective or duplicative regulation.



## Membership
Committee membership is critical to the transparency and capability of the committee for effective and independent in decision making.

Expand All @@ -73,46 +74,46 @@ The committee must consist of at least:
- one person with a practical understanding of the operational, technical and logistical facets
- one standards development/regulation specialist.

The committee should engage other external experts and participants invited by the chair as required and determined by the agenda.
The committee has the opportunity to establish working groups (may be topic or region specific) to provide advice the committee.

A quorum must be established to proceed with the committee meeting.

The committee should engage other external experts and participants invited by the chair as required and determined by the agenda.
The committee has the opportunity to establish sub groups (may be topic or region specific) to provide advice the committee.

## Eligibility requirements and declarations of personal interests (conflicts of interest)
Each member is required to make a declaration confirming they met the eligibility requirements upon their appointment to the committee. As part of each contract, members must continue to comply with eligibility requirements.
Each member is required to make a declaration confirming they met the eligibility requirements upon their appointment to the committee. Members must continue to comply with eligibility requirements.

During the operation of the committee, members are to declare to the chair all known actual or potential conflicts of interest as soon as they become aware of the conflict. Each meeting should contain a standard agenda item to allow for actual and percieved acknowledgement.
During the operation of the committee, members are to declare to the chair all known actual or potential conflicts of interest as soon as they become aware of the conflict. Each meeting should contain a standard agenda item to allow for actual and perceived acknowledgement.

The initial declaration of eligibility made to the DEWI prior to joining the committee and subsequent statements of personal interest will be deemed to be a ‘standing statement’ for all meetings of the committee.

At each meeting, members are to advise of any new actual or potential conflicts of interest arising in respect of issues on the meeting agenda. These should be recorded in the minutes of the meeting,
along with the course of action taken in relation to managing the conflict of interest.
Where a conflict of interest is declared by a member on a particular agenda item, the chair and remaining committee members are to consider the nature and extent of the conflict and adopt one of
At each meeting, members are to advise of any new actual or potential conflicts of interest arising in respect of issues on the meeting agenda. These should be recorded in the minutes of the meeting, along with the course of action taken in relation to managing the conflict of interest. Where a conflict of interest is declared by a member on a particular agenda item, the chair is to consider the nature and extent of the conflict and adopt one of
the following courses of action:
- allow the member to participate in discussion and in decision-making on the matter
- allow the member to be involved in discussions on the matter but not be involved in making a decision in relation to the matter
- exclude the member from participation in any discussion or decision-making on the matter
- direct the member to leave the meeting during deliberation on the matter.


The use of external experts is also subject to conflict of interest considerations. Each potential external expert must declare any potential conflict of interest or any possible perception of bias that could prevent him or her from participating in the review of a particular issue/standard. If this declaration raises concerns about whether the external expert should participate in the review, the chair may nominate an alternative expert.

## Technical Advisory Committee Operational Guidelines
### Committee roles and responsibilities
The committee structure has been designed to balance the skills, interests and expertise of its members so that the group may offer sound advice to DEWI.

All members are responsible for:
Role of individual members:
- participate in meetings, engage in quality debate to give professional, independent and advice to the Chair
- Represent the consensus view of the community
- Understand the strategic impacts and outcomes of initiatives being considered
- remaining fundamentally committed to the improvement of the Helium ecosystem
- operating in a transparent, timely and accountable manner
- ensuring all technical issues, new research and scientific knowledge submitted by stakeholders relating to technical matters have been properly considered by the committee and independent expert
advice sought as necessary
- ensuring all technical issues, new research and scientific knowledge submitted by stakeholders relating to technical matters have been properly considered by the committee and independent expert advice sought as necessary
- contributing to the development of clear timelines and work plans for the committee
- ensuring all interested stakeholders have the opportunity to provide review input
- clearly analysing the benefits and costs of the proposed options for affected stakeholders in a balanced and objective manner.

The independent chair is expected to:
Role of the independent chair:
- chair meetings, including:
- advising the committee about meeting protocols
- Ensure actions from each meeting are discussed and managed to their conclusion
- reminding committee members that they are bound by confidentiality provisions
- managing declarations of conflict of interest
- facilitate constructive processes that allow for continuous improvement DEWI and the Helium ecosystem overall
Expand All @@ -135,7 +136,7 @@ will also be published on these pages.

None.

The Helium ecosystem can not afford the fact that there are no publicly available terms of reference or a governance framework in existence for this important committee.
The Helium ecosystem needs a governance framework to meet the fast growth that has occurred and allow continued positive growth for the community.

# Rationale and Alternatives
[alternatives]: #rationale-and-alternatives
Expand All @@ -144,41 +145,45 @@ The Helium ecosystem can not afford the fact that there are no publicly availabl

No other proposals are currently available. Widest possible community feedback will be sought to consider in this proposal.

Best practice governance provides strong platform for growth and sustainablity
Best practice governance provides strong platform for growth, sustainability and resilience.

- What is the impact of not doing this?

Poor decision making and unneccesary disruption of the ecosystem due to such decisions. Regional disruptions and potential disconnect
Poor decision making and unnecessary disruption of the ecosystem due to such decisions. Regional disruptions and potential disconnect. Reduction of confidence in the Helium network.

# Unresolved Questions
[unresolved]: #unresolved-questions

- How does this governance proposal for the LoRaWAN committee fit in with an overall DEWI governance structure?

- Do any decisions made by the LoRaWAN committee prior to the approval of this HIP need to be reviewed? Details of existing documentation has been sought.
- Do any decisions made by the LoRaWAN committee prior to the approval of this HIP need to be reviewed? Details of existing documentation has been sought?

- Does cyber security have enough representation within the committees?

What related issues do you consider out of scope for this HIP that could be addressed in the future independently of the solution that comes out of this HIP?

-[TODO]
-Issue escalation procedure with Alliance
-Positive mental health of members (including reduction of burnout)
-Risk management.

-[TODO] add some more.

# Deployment Impact
[deployment-impact]: #deployment-impact

There is no deployment impact. This HIP purely describes poper governance and procedures in the decision making process
There is no deployment impact. This HIP purely describes proper governance and procedures in the decision making process.

It will create a proper governance structure ensuring that decisions are made with proper consideration of all stakeholders and ensures that conflicts of interest have to be declared.

Documentation on this process should be made available via Helium Docs
Documentation on this process should be made available via Helium Docs.

There are no backwards compatibility issues. The only potential issue is how to deal with decisions made prior to this change in governance.


# Success Metrics
[success-metrics]: #success-metrics

What metrics can be used to measure the success of this design?

- Faith of current Helium investors in regions
- Engagement by community in future decisions
- Alignment to best practice and possibility to lead by example
- Alignment to best practice and possibility to lead by example

0 comments on commit 6d94a22

Please sign in to comment.