Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create a security policy #129

Closed
2 tasks
Aveline-art opened this issue Jan 25, 2022 · 3 comments
Closed
2 tasks

Create a security policy #129

Aveline-art opened this issue Jan 25, 2022 · 3 comments
Labels
feature: GitHub Setup Pertains to GitHub settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: backend Pertains to backend tasks size: 2pt Can be done in 7-12 hours
Milestone
04 - Project Setup

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Jan 25, 2022 •
edited
Loading

Overview

As a developer, we need to patch vulnerabilities as they come up. For this issue, we will draft and create a security policy, so that we may collect feedback on potential holes in our security without making it public.

Action Items

  • Create a SECURITY.md file with our security policy.
  • Add a link to it to our README.md and CONTRIBUTING.md

Resources/Instructions

Resources
Adding a security policy to your repository
@Aveline-art Aveline-art added feature: GitHub Setup Pertains to GitHub settings size: 1pt Can be done in 4-6 hours role: missing labels Jan 25, 2022
@sdimran
Copy link
Member

sdimran commented Jan 27, 2022

@Aveline-art i think we can consider this a good first issue for the new developers to take on, let me know if you agree. if so -- once they have been added to the repo one of them can take this on

@Aveline-art
Copy link
Member Author

This might be a bit rough for a new developer since it involves security, and that might require a team discussion on how security flaw feedback is collected.

@sdimran sdimran added role: backend Pertains to backend tasks and removed role: missing labels Feb 6, 2022
@sdimran sdimran added this to the 04 - Project Setup milestone Feb 6, 2022
@Aveline-art Aveline-art moved this from 🆕 New to 📋 Backlog in P: CTJ: Project Board May 12, 2023
@kcoronel kcoronel added size: 2pt Can be done in 7-12 hours and removed size: 1pt Can be done in 4-6 hours labels Feb 14, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the PBV: dev all issues for engineering roles (devops, backend, frontend, db) label Jun 12, 2024
@nooriaali9
Copy link
Member

Closing this issue - since it is outdated/ not a priority anymore - based off of #552

@github-project-automation github-project-automation bot moved this from 📋 Prioritized Backlog to ✅ Done in P: CTJ: Project Board Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: GitHub Setup Pertains to GitHub settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: backend Pertains to backend tasks size: 2pt Can be done in 7-12 hours
Projects
P: CTJ: Project Board
Archived in project
Milestone
04 - Project Setup
Development

No branches or pull requests
5 participants
@sdimran @nooriaali9 @ExperimentsInHonesty @kcoronel @Aveline-art