Adding MIT License to Debian Package

[guptagunjan]

Description:

The license field is set during package build.
During build electron-builder reads the license from package.json

Related Issue:

If this pull request is related to any existing issue, please mention the issue number here.

Changes Made:

Please list down the specific changes made in this pull request.

Testing Done:

Please describe the testing that has been done to ensure the changes made in this pull request are functioning as expected.

Screenshots:

If applicable, please provide screenshots or GIFs or videos to visually demonstrate the changes made.

Checklist:

• I have tested the changes locally.
• I have self-reviewed the code changes.
• I have updated the documentation, if necessary.

Summary by CodeRabbit

• Chores
  • Updated app/package metadata with official Intel branding and maintainer details.
  • Added license information to package metadata.
  • Included Linux package vendor and maintainer details in the build configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fd2eba95-5ca0-4b44-bf5e-d82899cfc409

📥 Commits

Reviewing files that changed from the base of the PR and between cc59d5d and 44fbace.

📒 Files selected for processing (2)

• WebUI/build/build-config.json
• WebUI/package.json

---

📝 Walkthrough

Walkthrough

This change adds Intel Corporation metadata to the WebUI build configuration and package manifest. Specifically, vendor and maintainer fields are added to build-config.json, and license/author fields are added or updated in package.json.

Changes

Package Metadata Update

Layer / File(s)	Summary
Build and package metadata WebUI/build/build-config.json, WebUI/package.json	Adds vendor and maintainer fields with Intel Corporation values to Linux build config, and adds a license field while replacing placeholder author info with Intel Corporation details in package.json.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Related Issues: None mentioned in the provided information.

Related PRs: None mentioned in the provided information.

Suggested labels: documentation, chore

Suggested reviewers: None available based on provided information.

Poem:
A rabbit hops through config files small,
Adding a name where "TODO" once did sprawl,
Vendor and license, now clear and true,
Intel's mark on every line anew,
Metadata tidy — a job well done for all! 🐰

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The template is present, but Changes Made, Testing Done, and Related Issue details are effectively missing.	Add the specific file changes, any related issue number, the tests you ran, and fill in or remove unused template sections.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the package licensing metadata updates, though it is broader than the actual config changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}