diff --git a/spp_hazard_programs/README.rst b/spp_hazard_programs/README.rst index 9f4a3d92..c963bb82 100644 --- a/spp_hazard_programs/README.rst +++ b/spp_hazard_programs/README.rst @@ -24,22 +24,28 @@ OpenSPP Hazard Programs Integration Links hazard incidents to emergency response programs. Enables programs to target affected populations using verified impact data, filter -registrants by damage severity, and automatically enable emergency mode -when responding to active incidents. +registrants by damage severity, and flag programs as emergency when +responding to active incidents. Auto-installs when both ``spp_hazard`` +and ``spp_programs`` are present. Key Capabilities ~~~~~~~~~~~~~~~~ - Link programs to one or more hazard incidents via many-to-many relation -- Automatically flag programs as emergency when linked to incidents in - alert/active/recovery status -- Filter eligible registrants by damage level threshold (any, moderate+, - severe+, critical only) -- Count affected registrants based on verified impacts matching damage - criteria -- Track which programs are responding to each incident (bidirectional - navigation) +- Compute ``is_emergency_program`` flag when any linked incident has + status alert, active, or recovery +- Filter eligible registrants by damage level threshold: any, moderate+, + severe+, or critical/totally damaged only +- Count affected registrants from verified ``spp.hazard.impact`` records + matching the damage criteria +- Toggle ``is_emergency_mode`` to apply relaxed compliance rules during + active response +- Navigate from programs to target incidents and affected registrants + via stat buttons +- Navigate from incidents to response programs via stat button +- Show "Emergency Response" ribbon on program forms when + ``is_emergency_program`` is true Key Models ~~~~~~~~~~ @@ -47,28 +53,33 @@ Key Models +----------------------------------+-----------------------------------+ | Model | Description | +==================================+===================================+ -| ``spp.program`` (extend) | Adds target incidents, emergency | -| | mode, damage filter | +| ``spp.program`` (extend) | Adds ``target_incident_ids``, | +| | ``is_emergency_program``, | +| | ``is_emergency_mode``, | +| | ``qualifying_damage_levels`` | +----------------------------------+-----------------------------------+ -| ``spp.hazard.incident`` (extend) | Adds reverse relation to response | -| | programs | +| ``spp.hazard.incident`` (extend) | Adds ``program_ids`` reverse | +| | relation and ``program_count`` | +----------------------------------+-----------------------------------+ UI Location ~~~~~~~~~~~ -- **Programs**: Programs > Programs > "Emergency Response" tab -- **Incidents**: Hazard & Emergency > Incidents > All Incidents > - "Response Programs" tab -- **Stat buttons**: Programs show incident count and affected registrant - count; incidents show response program count -- **Filters**: "Emergency Programs" and "Has Target Incidents" filters - in program search view +- **Programs form**: Programs > Programs > "Emergency Response" tab +- **Incidents form**: Hazard and Emergency > Incidents > All Incidents > + "Response Programs" tab (visible when programs linked) +- **Stat buttons**: Program form shows incident count and affected + registrant count; incident form shows response program count +- **List views**: Program list adds "Emergency" column; incident list + adds "Programs" column +- **Filters**: "Emergency Programs" and "Has Target Incidents" in + program search view Security ~~~~~~~~ -No new ACL entries. Access inherited from base models: +No new models or ACL entries. Fields added to existing models inherit +access from: - ``spp.program``: Controlled by ``spp_programs`` security groups - ``spp.hazard.incident``: Controlled by ``spp_hazard`` security groups @@ -94,6 +105,222 @@ Dependencies .. contents:: :local: +Usage +===== + +Prerequisites +~~~~~~~~~~~~~ + +Before testing, ensure the following modules are installed: + +- ``spp_hazard`` (provides incidents, impacts, categories) +- ``spp_programs`` (provides programs) +- ``spp_hazard_programs`` (auto-installs when both above are present) + +You will also need: + +- At least one hazard category (e.g., "Typhoon") created at **Hazard and + Emergency > Configuration > Hazard Categories** +- At least one impact type (e.g., "Property Damage") created at **Hazard + and Emergency > Configuration > Impact Types** +- At least two registrants with ``is_registrant = True`` +- At least one incident with impact records linked to those registrants + +Test Scenario 1: Link a Program to Incidents +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Navigate to **Programs > Programs** +2. Open an existing program or create a new one +3. Click the **"Emergency Response"** tab in the form notebook +4. In the "Target Incidents" section, confirm the **Is Emergency + Program** field is read-only and shows ``False`` +5. In the "Emergency Settings" section, confirm: + + - **Qualifying Damage Levels** defaults to "Any Damage Level" + - **Emergency Mode** checkbox defaults to unchecked + +6. In the inline list below, click "Add a line" to add an incident +7. Select an incident with status **Active** +8. Save the program + +**Expected results:** + +- The **Is Emergency Program** field changes to ``True`` +- A yellow **"Emergency Response"** ribbon appears at the top of the + form +- An **"Incidents"** stat button (bolt icon) appears in the button box + showing "1" +- An **"Affected"** stat button (users icon) appears showing the count + of registrants with verified impacts from that incident + +Test Scenario 2: Verify Emergency Flag by Incident Status +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Link a program to an incident with status **Alert** +2. Save and confirm **Is Emergency Program** is ``True`` +3. Change the incident status to **Active** -- confirm still ``True`` +4. Change the incident status to **Recovery** -- confirm still ``True`` +5. Change the incident status to **Closed** -- confirm **Is Emergency + Program** becomes ``False`` (assuming no other linked incidents have + alert/active/recovery status) + +**Expected results:** + +- The emergency flag is ``True`` for alert, active, and recovery + statuses +- The emergency flag is ``False`` for closed status (when no other + active incidents are linked) +- The yellow ribbon appears/disappears accordingly + +Test Scenario 3: Damage Level Filtering +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Setup:** Ensure the linked incident has verified impact records with +different damage levels (e.g., one "critical", one "moderate", one +unverified "severe"). + +**Steps:** + +1. Open a program linked to the incident +2. Go to the **"Emergency Response"** tab +3. Set **Qualifying Damage Levels** to each option and save after each + change: + ++---------------------------------+------------------------------------+ +| Setting | Expected "Affected" count | ++=================================+====================================+ +| "Any Damage Level" | All registrants with verified | +| | impacts (unverified excluded) | ++---------------------------------+------------------------------------+ +| "Moderate and Above" | Registrants with moderate, severe, | +| | critical, partially damaged, or | +| | totally damaged verified impacts | ++---------------------------------+------------------------------------+ +| "Severe and Above" | Registrants with severe, critical, | +| | or totally damaged verified | +| | impacts | ++---------------------------------+------------------------------------+ +| "Critical/Totally Damaged Only" | Registrants with critical or | +| | totally damaged verified impacts | ++---------------------------------+------------------------------------+ + +**Expected results:** + +- The **"Affected"** stat button count updates after each save +- Unverified impact records are always excluded regardless of damage + level + +Test Scenario 4: Stat Button Navigation +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Open a program with at least one linked incident and affected + registrants +2. Click the **"Incidents"** stat button (bolt icon) +3. Confirm it opens a list view of ``spp.hazard.incident`` records + filtered to only the program's target incidents +4. Navigate back to the program +5. Click the **"Affected"** stat button (users icon) +6. Confirm it opens a list view of ``res.partner`` records filtered to + only registrants with qualifying verified impacts + +**Expected results:** + +- Each stat button opens the correct model with the correct filtered + records +- The number of records in the opened list matches the stat button count + +Test Scenario 5: Incident Side -- Response Programs +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Navigate to **Hazard and Emergency > Incidents > All Incidents** +2. Open an incident that has NO programs linked to it +3. Confirm: + + - No **"Programs"** stat button is visible in the button box + - No **"Response Programs"** tab is visible in the notebook + +4. Now link a program to this incident (from the program side, add this + incident to a program's target incidents) +5. Reload the incident form + +**Expected results:** + +- A **"Programs"** stat button (list icon) appears showing "1" +- A **"Response Programs"** tab appears in the notebook +- The tab contains a read-only list showing the linked program's name, + state (badge), qualifying damage levels, and emergency mode +- Clicking the stat button opens a list view of ``spp.program`` records + filtered to the responding programs + +Test Scenario 6: Bidirectional Relationship +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Open a program and add Incident A to its target incidents via the + "Emergency Response" tab +2. Save the program +3. Open Incident A and check the "Response Programs" tab + +**Expected results:** + +- Incident A's "Response Programs" tab shows the program +- Removing the incident from the program also removes the program from + the incident's response programs (and vice versa) + +Test Scenario 7: Program List View Columns +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Navigate to **Programs > Programs** (list view) +2. Check the column headers + +**Expected results:** + +- An **"Emergency"** column is visible by default (shows True/False) +- An **"Incidents"** column is available via the optional columns toggle + (hidden by default) + +Test Scenario 8: Search Filters +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Navigate to **Programs > Programs** (list view) +2. Open the search bar's **Filters** dropdown +3. Activate the **"Emergency Programs"** filter +4. Confirm only programs with ``is_emergency_program = True`` are shown +5. Deactivate that filter and activate **"Has Target Incidents"** +6. Confirm only programs with at least one target incident are shown + +**Expected results:** + +- Both filters appear in the search dropdown +- Each filter correctly narrows the program list + +Test Scenario 9: Incident List View Column +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +**Steps:** + +1. Navigate to **Hazard and Emergency > Incidents > All Incidents** + (list view) +2. Check the column headers + +**Expected results:** + +- A **"Programs"** column is visible by default showing the count of + response programs for each incident + Bug Tracker =========== diff --git a/spp_hazard_programs/readme/DESCRIPTION.md b/spp_hazard_programs/readme/DESCRIPTION.md index 60c4c967..29f7ab3b 100644 --- a/spp_hazard_programs/readme/DESCRIPTION.md +++ b/spp_hazard_programs/readme/DESCRIPTION.md @@ -1,30 +1,38 @@ -Links hazard incidents to emergency response programs. Enables programs to target affected populations using verified impact data, filter registrants by damage severity, and automatically enable emergency mode when responding to active incidents. +Links hazard incidents to emergency response programs. Enables programs to +target affected populations using verified impact data, filter registrants +by damage severity, and flag programs as emergency when responding to +active incidents. Auto-installs when both `spp_hazard` and `spp_programs` +are present. ### Key Capabilities - Link programs to one or more hazard incidents via many-to-many relation -- Automatically flag programs as emergency when linked to incidents in alert/active/recovery status -- Filter eligible registrants by damage level threshold (any, moderate+, severe+, critical only) -- Count affected registrants based on verified impacts matching damage criteria -- Track which programs are responding to each incident (bidirectional navigation) +- Compute `is_emergency_program` flag when any linked incident has status alert, active, or recovery +- Filter eligible registrants by damage level threshold: any, moderate+, severe+, or critical/totally damaged only +- Count affected registrants from verified `spp.hazard.impact` records matching the damage criteria +- Toggle `is_emergency_mode` to apply relaxed compliance rules during active response +- Navigate from programs to target incidents and affected registrants via stat buttons +- Navigate from incidents to response programs via stat button +- Show "Emergency Response" ribbon on program forms when `is_emergency_program` is true ### Key Models -| Model | Description | -| --------------------------- | ---------------------------------------------------- | -| `spp.program` (extend) | Adds target incidents, emergency mode, damage filter | -| `spp.hazard.incident` (extend) | Adds reverse relation to response programs | +| Model | Description | +| -------------------------------- | ------------------------------------------------------------------ | +| `spp.program` (extend) | Adds `target_incident_ids`, `is_emergency_program`, `is_emergency_mode`, `qualifying_damage_levels` | +| `spp.hazard.incident` (extend) | Adds `program_ids` reverse relation and `program_count` | ### UI Location -- **Programs**: Programs > Programs > "Emergency Response" tab -- **Incidents**: Hazard & Emergency > Incidents > All Incidents > "Response Programs" tab -- **Stat buttons**: Programs show incident count and affected registrant count; incidents show response program count -- **Filters**: "Emergency Programs" and "Has Target Incidents" filters in program search view +- **Programs form**: Programs > Programs > "Emergency Response" tab +- **Incidents form**: Hazard and Emergency > Incidents > All Incidents > "Response Programs" tab (visible when programs linked) +- **Stat buttons**: Program form shows incident count and affected registrant count; incident form shows response program count +- **List views**: Program list adds "Emergency" column; incident list adds "Programs" column +- **Filters**: "Emergency Programs" and "Has Target Incidents" in program search view ### Security -No new ACL entries. Access inherited from base models: +No new models or ACL entries. Fields added to existing models inherit access from: - `spp.program`: Controlled by `spp_programs` security groups - `spp.hazard.incident`: Controlled by `spp_hazard` security groups diff --git a/spp_hazard_programs/readme/USAGE.md b/spp_hazard_programs/readme/USAGE.md new file mode 100644 index 00000000..866ae7ff --- /dev/null +++ b/spp_hazard_programs/readme/USAGE.md @@ -0,0 +1,178 @@ +### Prerequisites + +Before testing, ensure the following modules are installed: + +- `spp_hazard` (provides incidents, impacts, categories) +- `spp_programs` (provides programs) +- `spp_hazard_programs` (auto-installs when both above are present) + +You will also need: + +- At least one hazard category (e.g., "Typhoon") created at + **Hazard and Emergency > Configuration > Hazard Categories** +- At least one impact type (e.g., "Property Damage") created at + **Hazard and Emergency > Configuration > Impact Types** +- At least two registrants with `is_registrant = True` +- At least one incident with impact records linked to those registrants + +### Test Scenario 1: Link a Program to Incidents + +**Steps:** + +1. Navigate to **Programs > Programs** +2. Open an existing program or create a new one +3. Click the **"Emergency Response"** tab in the form notebook +4. In the "Target Incidents" section, confirm the **Is Emergency Program** field + is read-only and shows `False` +5. In the "Emergency Settings" section, confirm: + - **Qualifying Damage Levels** defaults to "Any Damage Level" + - **Emergency Mode** checkbox defaults to unchecked +6. In the inline list below, click "Add a line" to add an incident +7. Select an incident with status **Active** +8. Save the program + +**Expected results:** + +- The **Is Emergency Program** field changes to `True` +- A yellow **"Emergency Response"** ribbon appears at the top of the form +- An **"Incidents"** stat button (bolt icon) appears in the button box showing "1" +- An **"Affected"** stat button (users icon) appears showing the count of + registrants with verified impacts from that incident + +### Test Scenario 2: Verify Emergency Flag by Incident Status + +**Steps:** + +1. Link a program to an incident with status **Alert** +2. Save and confirm **Is Emergency Program** is `True` +3. Change the incident status to **Active** -- confirm still `True` +4. Change the incident status to **Recovery** -- confirm still `True` +5. Change the incident status to **Closed** -- confirm **Is Emergency Program** + becomes `False` (assuming no other linked incidents have alert/active/recovery + status) + +**Expected results:** + +- The emergency flag is `True` for alert, active, and recovery statuses +- The emergency flag is `False` for closed status (when no other active incidents + are linked) +- The yellow ribbon appears/disappears accordingly + +### Test Scenario 3: Damage Level Filtering + +**Setup:** Ensure the linked incident has verified impact records with different +damage levels (e.g., one "critical", one "moderate", one unverified "severe"). + +**Steps:** + +1. Open a program linked to the incident +2. Go to the **"Emergency Response"** tab +3. Set **Qualifying Damage Levels** to each option and save after each change: + +| Setting | Expected "Affected" count | +| --- | --- | +| "Any Damage Level" | All registrants with verified impacts (unverified excluded) | +| "Moderate and Above" | Registrants with moderate, severe, critical, partially damaged, or totally damaged verified impacts | +| "Severe and Above" | Registrants with severe, critical, or totally damaged verified impacts | +| "Critical/Totally Damaged Only" | Registrants with critical or totally damaged verified impacts | + +**Expected results:** + +- The **"Affected"** stat button count updates after each save +- Unverified impact records are always excluded regardless of damage level + +### Test Scenario 4: Stat Button Navigation + +**Steps:** + +1. Open a program with at least one linked incident and affected registrants +2. Click the **"Incidents"** stat button (bolt icon) +3. Confirm it opens a list view of `spp.hazard.incident` records filtered to + only the program's target incidents +4. Navigate back to the program +5. Click the **"Affected"** stat button (users icon) +6. Confirm it opens a list view of `res.partner` records filtered to only + registrants with qualifying verified impacts + +**Expected results:** + +- Each stat button opens the correct model with the correct filtered records +- The number of records in the opened list matches the stat button count + +### Test Scenario 5: Incident Side -- Response Programs + +**Steps:** + +1. Navigate to **Hazard and Emergency > Incidents > All Incidents** +2. Open an incident that has NO programs linked to it +3. Confirm: + - No **"Programs"** stat button is visible in the button box + - No **"Response Programs"** tab is visible in the notebook +4. Now link a program to this incident (from the program side, add this incident + to a program's target incidents) +5. Reload the incident form + +**Expected results:** + +- A **"Programs"** stat button (list icon) appears showing "1" +- A **"Response Programs"** tab appears in the notebook +- The tab contains a read-only list showing the linked program's name, state + (badge), qualifying damage levels, and emergency mode +- Clicking the stat button opens a list view of `spp.program` records filtered + to the responding programs + +### Test Scenario 6: Bidirectional Relationship + +**Steps:** + +1. Open a program and add Incident A to its target incidents via the + "Emergency Response" tab +2. Save the program +3. Open Incident A and check the "Response Programs" tab + +**Expected results:** + +- Incident A's "Response Programs" tab shows the program +- Removing the incident from the program also removes the program from the + incident's response programs (and vice versa) + +### Test Scenario 7: Program List View Columns + +**Steps:** + +1. Navigate to **Programs > Programs** (list view) +2. Check the column headers + +**Expected results:** + +- An **"Emergency"** column is visible by default (shows True/False) +- An **"Incidents"** column is available via the optional columns toggle + (hidden by default) + +### Test Scenario 8: Search Filters + +**Steps:** + +1. Navigate to **Programs > Programs** (list view) +2. Open the search bar's **Filters** dropdown +3. Activate the **"Emergency Programs"** filter +4. Confirm only programs with `is_emergency_program = True` are shown +5. Deactivate that filter and activate **"Has Target Incidents"** +6. Confirm only programs with at least one target incident are shown + +**Expected results:** + +- Both filters appear in the search dropdown +- Each filter correctly narrows the program list + +### Test Scenario 9: Incident List View Column + +**Steps:** + +1. Navigate to **Hazard and Emergency > Incidents > All Incidents** (list view) +2. Check the column headers + +**Expected results:** + +- A **"Programs"** column is visible by default showing the count of response + programs for each incident diff --git a/spp_hazard_programs/static/description/index.html b/spp_hazard_programs/static/description/index.html index 5bce9c0a..0c8c322a 100644 --- a/spp_hazard_programs/static/description/index.html +++ b/spp_hazard_programs/static/description/index.html @@ -372,21 +372,27 @@

OpenSPP Hazard Programs Integration

Beta License: LGPL-3 OpenSPP/OpenSPP2

Links hazard incidents to emergency response programs. Enables programs to target affected populations using verified impact data, filter -registrants by damage severity, and automatically enable emergency mode -when responding to active incidents.

+registrants by damage severity, and flag programs as emergency when +responding to active incidents. Auto-installs when both spp_hazard +and spp_programs are present.

Key Capabilities

@@ -403,12 +409,14 @@

Key Models

spp.program (extend) -Adds target incidents, emergency -mode, damage filter +Adds target_incident_ids, +is_emergency_program, +is_emergency_mode, +qualifying_damage_levels spp.hazard.incident (extend) -Adds reverse relation to response -programs +Adds program_ids reverse +relation and program_count @@ -416,18 +424,21 @@

Key Models

UI Location

Security

-

No new ACL entries. Access inherited from base models:

+

No new models or ACL entries. Fields added to existing models inherit +access from:

+
+

Prerequisites

+

Before testing, ensure the following modules are installed:

+ +

You will also need:

+ +
+ +
+

Test Scenario 2: Verify Emergency Flag by Incident Status

+

Steps:

+
    +
  1. Link a program to an incident with status Alert
    2. +
  2. Save and confirm Is Emergency Program is True
    3. +
  3. Change the incident status to Active – confirm still True
    4. +
  4. Change the incident status to Recovery – confirm still True
    5. +
  5. Change the incident status to Closed – confirm Is Emergency +Program becomes False (assuming no other linked incidents have +alert/active/recovery status)
    6. +
+

Expected results:

+ +
+
+

Test Scenario 3: Damage Level Filtering

+

Setup: Ensure the linked incident has verified impact records with +different damage levels (e.g., one “critical”, one “moderate”, one +unverified “severe”).

+

Steps:

+
    +
  1. Open a program linked to the incident
    2. +
  2. Go to the “Emergency Response” tab
    3. +
  3. Set Qualifying Damage Levels to each option and save after each +change:
    4. +
+ ++++ + + + + + + + + + + + + + + + + + + + +
SettingExpected “Affected” count
“Any Damage Level”All registrants with verified +impacts (unverified excluded)
“Moderate and Above”Registrants with moderate, severe, +critical, partially damaged, or +totally damaged verified impacts
“Severe and Above”Registrants with severe, critical, +or totally damaged verified +impacts
“Critical/Totally Damaged Only”Registrants with critical or +totally damaged verified impacts
+

Expected results:

+ +
+
+

Test Scenario 4: Stat Button Navigation

+

Steps:

+
    +
  1. Open a program with at least one linked incident and affected +registrants
    2. +
  2. Click the “Incidents” stat button (bolt icon)
    3. +
  3. Confirm it opens a list view of spp.hazard.incident records +filtered to only the program’s target incidents
    4. +
  4. Navigate back to the program
    5. +
  5. Click the “Affected” stat button (users icon)
    6. +
  6. Confirm it opens a list view of res.partner records filtered to +only registrants with qualifying verified impacts
    7. +
+

Expected results:

+ +
+
+

Test Scenario 5: Incident Side – Response Programs

+

Steps:

+
    +
  1. Navigate to Hazard and Emergency > Incidents > All Incidents
    2. +
  2. Open an incident that has NO programs linked to it
    3. +
  3. Confirm:
      +
    • No “Programs” stat button is visible in the button box
      • +
    • No “Response Programs” tab is visible in the notebook
    4. +
  4. Now link a program to this incident (from the program side, add this +incident to a program’s target incidents)
    5. +
  5. Reload the incident form
    6. +
+

Expected results:

+ +
+
+

Test Scenario 6: Bidirectional Relationship

+

Steps:

+
    +
  1. Open a program and add Incident A to its target incidents via the +“Emergency Response” tab
    2. +
  2. Save the program
    3. +
  3. Open Incident A and check the “Response Programs” tab
    4. +
+

Expected results:

+ +
+
+

Test Scenario 7: Program List View Columns

+

Steps:

+
    +
  1. Navigate to Programs > Programs (list view)
    2. +
  2. Check the column headers
    3. +
+

Expected results:

+ +
+
+

Test Scenario 8: Search Filters

+

Steps:

+
    +
  1. Navigate to Programs > Programs (list view)
    2. +
  2. Open the search bar’s Filters dropdown
    3. +
  3. Activate the “Emergency Programs” filter
    4. +
  4. Confirm only programs with is_emergency_program = True are shown
    5. +
  5. Deactivate that filter and activate “Has Target Incidents”
    6. +
  6. Confirm only programs with at least one target incident are shown
    7. +
+

Expected results:

+
+
+

Test Scenario 9: Incident List View Column

+

Steps:

+
    +
  1. Navigate to Hazard and Emergency > Incidents > All Incidents +(list view)
    2. +
  2. Check the column headers
    3. +
+

Expected results:

+
-

Bug Tracker

+

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed @@ -468,15 +702,15 @@

Bug Tracker

Do not contact contributors directly about support or help with technical issues.

-

Credits

+

Credits

-

Authors

+

Authors

  • OpenSPP.org
-

Maintainers

+

Maintainers

Current maintainers:

jeremi gonzalesedwin1123 reichie020212

This module is part of the OpenSPP/OpenSPP2 project on GitHub.