~Meeting Notes - Monthly Planning~

[jonnyarndt]

PepperDash Essentials Planning (Monthly Notes)

1. PepperDash team meets once a month to discuss PepperDash Essentials and Essentials Plug-Ins (EPIs).
2. Discussion items surround topics include development priorities and strategies.
3. Check this board often for features and improvements being discussed.
4. Feel free to comment and provide feedback of posted notes.
5. Keep in mind that PepperDash Essentials is open-source and supported by a community of Crestron developers.

[jonnyarndt]

Thursday, April 27, 2023

Priorities for Essentials (not in priority order)

1. 4-series (getting outside of the sandbox, compile Essentials for 4-series, currently it builds for 3)
2. Logging
3. Automated documentation mechanism (interfaces)
4. Rooms logic as an Essentials Plug-in (EPI)
5. Updating stuff for 4-series

Discussion Notes

1. PepperDash/Projects/Essentials Maintenance [https://github.com/orgs/PepperDash/projects/4]
2. Essentials release pushed v1.13.4.
3. Co-Pilot X (different things you can throw Co-Pilot in).
   1. Should we consider adding this to Essentials?
   2. Summarizes poll request.
   3. Runs a robot on the repo to summarize things.
   4. Robots won’t figure out WHY we are making this change.
4. GitHub Workflow Templates.
   1. Betas, release, actions.
   2. Existing EPI’s won’t utilize latest GitHub workflow.
5. Symantec release notes based on the commit messages.
   1. Need to add a configuration file to the repos to utilize latest GitHub workflow.
   2. When making a commit message, make it match ‘convenctionalcommits.org’
      1. Set scope to: force-patch which trigger a release based on Workflow configuration file mentioned below.
      2. Example configuration file: EPI-Switcher-Extron-Quantum (feature/initial-feature) has ‘.releasesrc.json’ configuration file that analyses commit notes to determine.
   3. Plugin template will need a 4-series template.
6. How are we authoring and creating modern day user interfaces with Essentials?
   1. PepperDash Mobile Control.
   2. Authoring/customizing user interfaces with online tool called, Figma [https://www.figma.com/].
   3. Modern day user interface concepts/constructs:
      1. Context sensitive feedback: Communication and user-session logic, navigating between views.
      2. Modern user interface development in the modern day data model.
         1. Front end: Paginated controls, typical technician controls (typical Crestron SIMPL touch panel control and folder logic moving to React).
         2. Back end: Source-of-truth for front-end, user logic for shared user navigation.

[jonnyarndt]

Thursday, September 7, 2023

Priorities for Essentials (not in priority order)

1. 4-series Essentials & EPIs (getting outside of the sandbox, compile Essentials for 4-series, currently it builds for 3)
2. Logging & debugging
3. Automated documentation mechanism (interfaces)
4. Rooms logic as an Essentials Plug-in (EPI)

Discussion Notes

1. New item! Public Essentials GitHub repo documenting every EPI and interfaces used.
   a. https://github.com/PepperDash/Essentials-Plugin-Library
   b. Pinned to the PepperDash Public org.
2. Feature: Admin Web UI
3. 4-series only Essentials branch in the works (development/2.0.0).
   a. Branch: development/2.0.0, https://github.com/PepperDash/Essentials/tree/development-2.0.0
   b. New release for 4-series, functional improvement road-map, breaking changes (debugging) vs additive to 2.1.0 items.
   c. 4-series contains standardized logging mechanisms.
   d. GitHub ticket (Features or bugs) all end up in the Essentials Maintenance board: https://github.com/orgs/PepperDash/projects/4.
   e. Releases of Essentials 2.x.x to the public.
   e. 1. EPI branches that support 2.x.x (EPI is 2.x.x compatible?).
   e. 2. Different compile versions (3.5 and 4.7) may need to reference different class libraries (reference different namespaces).
   e. 3. Changing namespaces to account for the interfaces used within plug-ins.
4. Future endeavors and current priorities.