Merge branch '17.0' of https://github.com/OpenSPP/openspp-modules into 369-add-events-data-models-and-ui-for-laos-farmer-registry-module

Author: reichie020212

.github/workflows/pre-commit.yml

@@ -6,13 +6,13 @@ jobs:
   pre-commit:
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
         with:
           python-version: "3.11"
       - name: Get python version
         run: echo "PY=$(python -VV | sha256sum | cut -d' ' -f1)" >> $GITHUB_ENV
-      - uses: actions/cache@v1
+      - uses: actions/cache@v4
         with:
           path: ~/.cache/pre-commit
           key: pre-commit|${{ env.PY }}|${{ hashFiles('.pre-commit-config.yaml') }}

.github/workflows/test.yml

@@ -17,7 +17,7 @@ jobs:
     runs-on: ubuntu-latest
     name: Detect unreleased dependencies
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - run: |
           for reqfile in requirements.txt test-requirements.txt ; do
               if [ -f ${reqfile} ] ; then
@@ -54,7 +54,7 @@ jobs:
         ports:
           - 5432:5432
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 #        with:
 #          persist-credentials: false
 

README.md

@@ -1,8 +1,8 @@
 
 <!-- /!\ Non OCA Context : Set here the badge of your runbot / runboat instance. -->
-[![Pre-commit Status](https://github.com/openspp/openspp-registry/actions/workflows/pre-commit.yml/badge.svg?branch=15.0)](https://github.com/openspp/openspp-registry/actions/workflows/pre-commit.yml?query=branch%3A15.0)
-[![Build Status](https://github.com/openspp/openspp-registry/actions/workflows/test.yml/badge.svg?branch=15.0)](https://github.com/openspp/openspp-registry/actions/workflows/test.yml?query=branch%3A15.0)
-[![codecov](https://codecov.io/gh/openspp/openspp-registry/branch/15.0/graph/badge.svg)](https://codecov.io/gh/openspp/openspp-registry)
+[![Pre-commit Status](https://github.com/openspp/openspp-modules/actions/workflows/pre-commit.yml/badge.svg?branch=17.0)](https://github.com/openspp/openspp-modules/actions/workflows/pre-commit.yml?query=branch%3A17.0)
+[![Build Status](https://github.com/openspp/openspp-modules/actions/workflows/test.yml/badge.svg?branch=17.0)](https://github.com/openspp/openspp-modules/actions/workflows/test.yml?query=branch%3A17.0)
+[![codecov](https://codecov.io/gh/openspp/openspp-modules/branch/17.0/graph/badge.svg)](https://codecov.io/gh/openspp/openspp-modules)
 <!-- /!\ Non OCA Context : Set here the badge of your translation instance. -->
 [![Translation Status](https://translate.openspp.org/widgets/openspp/-/svg-badge.svg)](https://translate.openspp.org/engage/openspp/?utm_source=widget)
 

SECURITY.md

@@ -0,0 +1,76 @@
+# OpenSPP Vulnerability Disclosure Policy
+
+## Introduction
+
+OpenSPP welcomes feedback from security researchers and the general public to help improve our security. If
+you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any
+of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what
+we expect, what you can expect from us.
+
+## Systems in Scope
+
+This policy applies to any digital assets owned, operated, or maintained by OpenSPP.
+
+## Out of Scope
+
+- Assets or other equipment not owned by parties participating in this policy.
+
+Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor
+or applicable authority.
+
+## Our Commitments
+
+When working with us, according to this policy, you can expect us to:
+
+- Respond to your report promptly, and work with you to understand and validate your report;
+- Strive to keep you informed about the progress of a vulnerability as it is processed;
+- Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
+- Extend Safe Harbor for your vulnerability research that is related to this policy.
+
+## Our Expectations
+
+In participating in our vulnerability disclosure program in good faith, we ask that you:
+
+- Play by the rules, including following this policy and any other relevant agreements. If there is any
+  inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
+- Report any vulnerability you’ve discovered promptly;
+- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user
+  experience;
+- Use only the Official Channels to discuss vulnerability information with us;
+- Provide us a reasonable amount of time (at least 120 days from the initial report) to resolve the issue
+  before you disclose it publicly;
+- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
+- If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum
+  required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately
+  if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal
+  Healthcare Information (PHI), credit card data, or proprietary information;
+- You should only interact with test accounts you own or with explicit permission from the account holder; and
+- Do not engage in extortion.
+
+## Official Channels
+
+Please report security issues via email: [email protected], providing all relevant information. The more
+details you provide, the easier it will be for us to triage and fix the issue.
+
+## Safe Harbor
+
+When conducting vulnerability research, according to this policy, we consider this research conducted under
+this policy to be:
+
+- Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action
+  against you for accidental, good-faith violations of this policy;
+- Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for
+  circumvention of technology controls;
+- Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) that would
+  interfere with conducting security research, and we waive those restrictions on a limited basis; and
+- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
+
+You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party
+against you and you have complied with this policy, we will take steps to make it known that your actions were
+conducted in compliance with this policy.
+
+If at any time you have concerns or are uncertain whether your security research is consistent with this
+policy, please submit a report through one of our Official Channels before going any further.
+
+> Note that the Safe Harbor applies only to legal claims under the control of the organization participating
+> in this policy, and that the policy does not bind independent third parties.

code_of_conduct.md

@@ -0,0 +1,110 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free
+experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex
+characteristics, gender identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy
+community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit
+  permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will
+take appropriate and fair corrective action in response to any behavior that they deem inappropriate,
+threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki
+edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate
+reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially
+representing the community in public spaces. Examples of representing our community include using an official
+e-mail address, posting via an official social media account, or acting as an appointed representative at an
+online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders
+responsible for enforcement. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action
+they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in
+the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the
+violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved,
+including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time.
+This includes avoiding interactions in community spaces as well as external channels like social media.
+Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a
+specified period of time. No public or private interaction with the people involved, including unsolicited
+interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may
+lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained
+inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of
+individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][mozilla coc].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla coc]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

spp_registry_group_hierarchy/README.rst

@@ -0,0 +1 @@
+from . import models

spp_registry_group_hierarchy/__init__.py

@@ -0,0 +1,32 @@
+# Part of OpenSPP. See LICENSE file for full copyright and licensing details.
+
+{
+    "name": "SPP Registry Group Hierarchy",
+    "category": "OpenSPP",
+    "version": "17.0.1.0.0",
+    "sequence": 1,
+    "author": "OpenSPP.org",
+    "website": "https://github.com/OpenSPP/openspp-modules",
+    "license": "LGPL-3",
+    "development_status": "Production/Stable",
+    "maintainers": ["jeremi", "gonzalesedwin1123"],
+    "depends": [
+        "base",
+        "g2p_registry_base",
+        "g2p_registry_individual",
+        "g2p_registry_group",
+        "g2p_registry_membership",
+    ],
+    "external_dependencies": {},
+    "data": [
+        "views/group_kind_views.xml",
+        "views/group_membership_views.xml",
+        "views/group_views.xml",
+    ],
+    "assets": {},
+    "demo": [],
+    "images": [],
+    "application": True,
+    "installable": True,
+    "auto_install": False,
+}

spp_registry_group_hierarchy/__manifest__.py

@@ -0,0 +1,2 @@
+from . import group_kind
+from . import group_membership

spp_registry_group_hierarchy/models/__init__.py

@@ -0,0 +1,7 @@
+from odoo import fields, models
+
+
+class SPPGroupKind(models.Model):
+    _inherit = "g2p.group.kind"
+
+    allow_all_member_type = fields.Boolean("Allow group and individual members", default=False)