Skip to content

Add repository standards: CODE_OF_CONDUCT, SECURITY policy, and interactive issues#501

Closed
shiva24082 wants to merge 5 commits into
altic-dev:mainfrom
shiva24082:improve/repository-standards
Closed

Add repository standards: CODE_OF_CONDUCT, SECURITY policy, and interactive issues#501
shiva24082 wants to merge 5 commits into
altic-dev:mainfrom
shiva24082:improve/repository-standards

Conversation

@shiva24082

Copy link
Copy Markdown

This Pull Request introduces standard formatting, local privacy guidelines, code of conduct, and interactive issue templates:

  1. Code of Conduct (CODE_OF_CONDUCT.md): Configures standard Contributor Covenant (v2.1) community guidelines.
  2. Security Policy (SECURITY.md): Configures on-device local transcription privacy disclosures and private vulnerability reporting details.
  3. Formatting Settings (.editorconfig): Enforces standard spaces and line-endings across Swift code, make/shell files, and markdown documentation.
  4. Modern Issue Templates: Adds interactive forms for bug reporting and feature requests under .github/ISSUE_TEMPLATE/.

Created using the Antigravity GitHub repository analyzer.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9d5019aeed

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread SECURITY.md

## On-Device Privacy Commitment

FluidVoice operates entirely locally. Your audio recordings, transcripts, and model configurations never leave your machine.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Qualify the local-only privacy promise

This blanket statement is inaccurate when users enable the supported cloud AI enhancement path: README.md advertises OpenAI/Groq/custom providers, and the dictation flow folds the transcript into userMessageContent before building an LLMClient.Config with the provider baseURL and sending it as a POST body via URLSession (Sources/Fluid/ContentView.swift lines 1866-1871 and 2007-2020; Sources/Fluid/Services/LLMClient.swift lines 240-264). As written, the security policy tells privacy-sensitive users that transcripts never leave the machine even in a documented opt-in cloud-provider configuration, so it should mirror the README's "unless you opt in" caveat.

Useful? React with 👍 / 👎.

@grohith327 grohith327 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @shiva24082 we already have bug report and feature request issue templates. If you feel they are deficient, please open a issue to discuss and open a PR

@grohith327 grohith327 closed this Jul 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants