Merge branch 'devel' into patch-27

Author: LeStarch

.github/workflows/fpp-tests.yml

@@ -21,7 +21,7 @@ jobs:
     name: Run FppTest
     runs-on: ubuntu-22.04
     steps:
-      - name: "Checkout F´ Repository"
+      - name: "Checkout F´ Repository"
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
@@ -52,3 +52,39 @@ jobs:
           name: FppTest-Logs
           path: ./FppTestProject/build-fprime-automatic-native-ut/Testing/Temporary/*.log
           retention-days: 5
+
+  fpptest-direct-port-calls:
+    name: Run FppTest (Direct Port Calls)
+    runs-on: ubuntu-22.04
+    steps:
+      - name: "Checkout F´ Repository"
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          submodules: true
+      - name: "Install requirements.txt"
+        run: |
+          pip3 install -r ./requirements.txt
+        shell: bash
+      - name: "Generate UT build cache"
+        working-directory: ./FppTestProject
+        run: |
+          fprime-util generate --ut -DFPRIME_ENABLE_DIRECT_PORT_CALLS=ON -DFPRIME_ENABLE_JSON_MODEL_GENERATION=ON
+        shell: bash
+      - name: "Build UTs"
+        working-directory: ./FppTestProject/FppTest
+        run: |
+          fprime-util build --ut
+        shell: bash
+      - name: "Run UTs"
+        working-directory: ./FppTestProject/FppTest
+        run: |
+          fprime-util check --pass-through --output-on-failure
+        shell: bash
+      - name: "Archive Logs"
+        uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: FppTest-DirectPortCalls-Logs
+          path: ./FppTestProject/build-fprime-automatic-native-ut/Testing/Temporary/*.log
+          retention-days: 5

.github/workflows/pip-check.yml

@@ -20,7 +20,7 @@ jobs:
     runs-on: ${{ matrix.runner }}
     strategy:
       matrix:
-        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13", "3.14"]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
         # Purposefully test on both ARM and Intel macOS (macos-latest is ARM)
         runner: [macos-15-intel, macos-latest, ubuntu-22.04, ubuntu-latest]
     steps:

AI_POLICY.md

@@ -2,25 +2,18 @@
 
 We're excited about the potential of generative AI to help make [F´](https://github.com/nasa/fprime) development more productive, enjoyable, and accessible! Whether you're using AI to write code, improve documentation, or learn about complex systems, we welcome the thoughtful use of these powerful tools in your F´ contributions.
 
-This guide shares our community's approach to using generative AI effectively and responsibly. You'll find practical tips, best practices, and simple guidelines to help you get the most out of AI tools while maintaining the quality standards that make F´ great.
+This guide shares our community's approach to using generative AI effectively and responsibly.
 
 ## Our Position on Generative AI
 
-F´ embraces technological advancement and innovation. Generative AI tools can assist with:
-
-- Code generation and refactoring
-- Documentation creation and improvement  
-- Test case development
-- Debugging assistance
-- Design pattern suggestions
-- Learning and understanding our codebases
-
+F´ embraces technological advancement and innovation, including the use of Generative AI tools.
 However, the use of generative AI must align with our commitment to high technical standards, quality, and the collaborative nature of open source development.
 
 ## Disclosure
 
-To maintain transparency and enable effective code review, contributors **must disclose all generative AI usage**.   
-This includes contributions in the forms of **Pull Requests**, **Issues** or **Discussions**. 
+To maintain transparency and enable effective code review, contributors **must disclose all generative AI usage**.
+This is not meant to discourage AI use, but to ensure that maintainers and reviewers have the necessary context to evaluate contributions effectively.
+This includes contributions in the forms of **Pull Requests**, **Issues**, **Security Advisories**, **Discussions**, or any other communication channels.
 
 ### Pull Request Submissions for Contributors
 
@@ -36,15 +29,6 @@ Include information about:
 - **Tool(s) used**: Name of the AI system(s) employed (e.g., GitHub Copilot, ChatGPT, etc.)
 - **Level of modification**: Whether AI-generated content was used as-is, modified, or used as inspiration
 
-
-### What AI Cannot Replace
-
-- **Domain expertise** in flight software and embedded systems
-- **Understanding of F Prime architecture** and design patterns
-- **Critical thinking** about system requirements and constraints
-- **Human judgment** on safety-critical decisions
-- **Community collaboration** and peer review processes
-
 ## Best Practices
 
 ### Providing Guidelines to AI Tools

CONTRIBUTING.md

@@ -16,7 +16,7 @@ Specific Ways to Contribute:
 - [Ask a Question or Suggest Improvements](https://github.com/nasa/fprime/discussions/new)
 - [Report a Bug or Mistake](https://github.com/nasa/fprime/issues/new/choose)
 - [Review Contributions](https://github.com/nasa/fprime/pulls)
-- Submit a Pull Request see: [Code Contribution Process](#cod-ontribution-process)
+- Submit a Pull Request see: [Code Contribution Process](#code-contribution-process)
 - Contribute to Ongoing Discussions and Reviews
 
 Feel free to contribute any way that suits your skills and enjoy.
@@ -37,9 +37,28 @@ development process, and helpful tips sections below.
 
 ## Code Contribution Process
 
-All code contributions to F´ begin with an issue. Whether you're fixing a bug, adding a feature, or improving documentation, please start by opening an issue describing your proposal. The Change Control Board (CCB) reviews and approves issues before work begins to ensure alignment with project goals and standards. Once approved, you can proceed with implementation and submit a pull request (PR).
+All code contributions to F´ begin with an issue. Whether you're fixing a bug, adding a feature, or improving documentation, start by opening an issue describing your proposal. The Change Control Board (CCB) reviews and approves issues before work begins to ensure alignment with project goals, roadmap priorities, and review capacity. Once approved, you can proceed with implementation and submit a pull request (PR).
 
-If a PR is opened for work that does not correspond to an approved issue, the PR will be routed through the CCB process first—reviewed on a best-effort basis—and may be delayed or declined depending on CCB decisions.You can read more about how this process works in the [F´ Governance document](https://github.com/nasa/fprime/blob/devel/GOVERNANCE.md).
+For non-trivial changes, opening an issue is not just a notification step. It is an approval gate. Please do not invest significant implementation effort until maintainers confirm that the work is in scope for F´ and appropriate for this repository.
+
+### What We Prioritize
+
+Maintainer review time is limited. We prioritize work that is approved by our [Change Control Board (CCB)](./GOVERNANCE.md) and aligned with project and community needs.
+
+If a PR is opened for work that does not correspond to an approved issue, the PR will be routed through the CCB process first, reviewed on a best-effort basis, and may be delayed or declined. You can read more about how this process works in the [F´ Governance document](./GOVERNANCE.md).
+
+### When Maintainers May Close a PR
+
+To keep review bandwidth focused on the work that benefits the community the most, maintainers may close a pull request without
+extended review when any of the following apply:
+
+- The PR does not correspond to an approved issue per our [CCB process](./GOVERNANCE.md)
+- The PR is too large, too cross-cutting, or combines multiple independent changes
+- The contribution appears to be generated by AI without clear author understanding
+- The PR lacks a clear rationale or explanation of the changes
+- The contributor has not responded to review comments after a reasonable amount of time
+
+Closing a PR in these cases is a scope and capacity decision, not a judgment on the contributor. We encourage follow-up through Discussions, smaller issue-backed changes, or work on areas maintainers have identified as needed.
 
 ### Development Process
 

Drv/Ports/DataTypes/DataBuffer.hpp

@@ -11,7 +11,7 @@ class DataBuffer : public Fw::LinearBufferBase {
     enum {
         DATA_BUFFER_SIZE = 256,
         SERIALIZED_TYPE_ID = 1010,
-        SERIALIZED_SIZE = DATA_BUFFER_SIZE + sizeof(FwBuffSizeType)
+        SERIALIZED_SIZE = STATIC_SERIALIZED_SIZE(DATA_BUFFER_SIZE)
     };
 
     DataBuffer(const U8* args, FwSizeType size);

Fw/Cmd/CmdArgBuffer.hpp

@@ -21,8 +21,9 @@ namespace Fw {
 class CmdArgBuffer final : public LinearBufferBase {
   public:
     enum {
-        SERIALIZED_TYPE_ID = FW_TYPEID_CMD_BUFF,                    //!< type id for CmdArgBuffer
-        SERIALIZED_SIZE = FW_CMD_ARG_BUFFER_MAX_SIZE + sizeof(I32)  //!< size when serialized. Buffer + size of buffer
+        SERIALIZED_TYPE_ID = FW_TYPEID_CMD_BUFF,  //!< type id for CmdArgBuffer
+        SERIALIZED_SIZE =
+            STATIC_SERIALIZED_SIZE(FW_CMD_ARG_BUFFER_MAX_SIZE)  //!< size when serialized. Buffer + size of buffer
     };
 
     CmdArgBuffer(const U8* args, FwSizeType size);       //!< buffer source constructor

Fw/Com/ComBuffer.hpp

@@ -21,7 +21,7 @@ class ComBuffer final : public LinearBufferBase {
   public:
     enum {
         SERIALIZED_TYPE_ID = 1010,
-        SERIALIZED_SIZE = FW_COM_BUFFER_MAX_SIZE + sizeof(FwBuffSizeType)  // size of buffer + storage of size word
+        SERIALIZED_SIZE = STATIC_SERIALIZED_SIZE(FW_COM_BUFFER_MAX_SIZE)  // size of buffer + storage of size word
     };
 
     ComBuffer(const U8* args, FwSizeType size);

Fw/Fpy/StatementArgBuffer.hpp

@@ -11,7 +11,7 @@ class StatementArgBuffer : public LinearBufferBase {
   public:
     enum {
         SERIALIZED_TYPE_ID = FW_TYPEID_TLM_BUFF,
-        SERIALIZED_SIZE = FW_STATEMENT_ARG_BUFFER_MAX_SIZE + sizeof(FwBuffSizeType)
+        SERIALIZED_SIZE = STATIC_SERIALIZED_SIZE(FW_STATEMENT_ARG_BUFFER_MAX_SIZE)
     };
 
     StatementArgBuffer(const U8* args, FwSizeType size);

Fw/Log/LogBuffer.hpp

@@ -20,7 +20,7 @@ namespace Fw {
 
 class LogBuffer final : public LinearBufferBase {
   public:
-    enum { SERIALIZED_TYPE_ID = FW_TYPEID_LOG_BUFF, SERIALIZED_SIZE = FW_LOG_BUFFER_MAX_SIZE + sizeof(FwBuffSizeType) };
+    enum { SERIALIZED_TYPE_ID = FW_TYPEID_LOG_BUFF, SERIALIZED_SIZE = STATIC_SERIALIZED_SIZE(FW_LOG_BUFFER_MAX_SIZE) };
 
     LogBuffer(const U8* args, FwSizeType size);
     LogBuffer();

Fw/Prm/PrmBuffer.hpp

@@ -27,7 +27,7 @@ class ParamBuffer final : public LinearBufferBase {
   public:
     enum {
         SERIALIZED_TYPE_ID = FW_TYPEID_PRM_BUFF,
-        SERIALIZED_SIZE = FW_PARAM_BUFFER_MAX_SIZE + sizeof(FwBuffSizeType)
+        SERIALIZED_SIZE = STATIC_SERIALIZED_SIZE(FW_PARAM_BUFFER_MAX_SIZE)
     };
 
     ParamBuffer(const U8* args, FwSizeType size);