Skip to content

chore: prepare repository for open source release#20

Merged
frankieyan merged 5 commits into
mainfrom
frankieyan/open-source-prep
Jan 16, 2026
Merged

chore: prepare repository for open source release#20
frankieyan merged 5 commits into
mainfrom
frankieyan/open-source-prep

Conversation

@frankieyan
Copy link
Copy Markdown
Member

@frankieyan frankieyan commented Jan 16, 2026

This PR takes care of a couple of documentation/configuration loose ends:

  • Fix SECURITY.md placeholders
  • Update CODEOWNERS with @doist/frontend-product
  • Remove unused dependabot.yml
  • Add CONTRIBUTING.md with development workflow and commit guidelines
  • Add CODE_OF_CONDUCT.md using Contributor Covenant v2.1

Replace {repository-url} placeholder with actual GitHub repository URL.
This repository uses Renovate for dependency updates instead of Dependabot.
Add contribution guidelines including:
- Code of Conduct reference
- Open development policy
- Semantic versioning explanation
- Branch organization
- How to propose changes
- Project setup instructions
- Development workflow and available commands
- Pull request guidelines
- Commit message guidelines (Conventional Commits)
Add Contributor Covenant v2.1 code of conduct with Doist contact
email (frontend+opensource@doist.com) for enforcement.
Copy link
Copy Markdown

@doistbot-app doistbot-app Bot left a comment

Choose a reason for hiding this comment

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

The PR successfully prepares the repository for open source with clear guidelines and standard files. I have flagged one security concern regarding the vulnerability reporting process.

Comment thread SECURITY.md
## Reporting a vulnerability

Please report any vulnerabilities by [opening an issue]({repository-url}/issues/new) and including as many details as you can. We will prioritize security reports over other issues.
Please report any vulnerabilities by [opening an issue](https://github.com/Doist/react-compiler-tracker/issues/new) and including as many details as you can. We will prioritize security reports over other issues.
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] Insecure vulnerability reporting mechanism. Directing users to report security vulnerabilities via public GitHub issues forces public disclosure of exploits before a fix can be prepared. I recommend directing these reports to a private channel (such as security@doist.com or the team email frontend+opensource@doist.com) or instructing users to use GitHub's private vulnerability reporting feature.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I believe the private reporting feature is only available once the repo is public. We can follow up once that's done.

@frankieyan frankieyan force-pushed the frankieyan/open-source-prep branch from 334134b to 2651f65 Compare January 16, 2026 19:43
@frankieyan frankieyan added the 👀 Show PR PR must be reviewed before or after merging label Jan 16, 2026
@frankieyan frankieyan requested review from a team and craigcarlyle and removed request for a team January 16, 2026 19:45
@frankieyan frankieyan merged commit 8013795 into main Jan 16, 2026
6 checks passed
@frankieyan frankieyan deleted the frankieyan/open-source-prep branch January 16, 2026 23:12
Copy link
Copy Markdown
Member

@rfgamaral rfgamaral left a comment

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

👀 Show PR PR must be reviewed before or after merging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants