epel/docs
7
0
Fork 6
Code Pull requests 4 Projects Activity

Vulnerability Management policy #167

Open
salimma wants to merge 1 commit from security into main
pull from: security
merge into: epel:main
Conversation 6 Commits 1 Files changed 3 +56
salimma commented 2022-03-30 19:15:13 +00:00
Contributor
Copy link

Vulnerability Management policy, as part of the discussions around https://pagure.io/epel/issue/159

Signed-off-by: Michel Alexandre Salim salimma@fedoraproject.org

Vulnerability Management policy, as part of the discussions around https://pagure.io/epel/issue/159 Signed-off-by: Michel Alexandre Salim <salimma@fedoraproject.org>
tdawson commented 2022-03-30 19:18:04 +00:00
Owner
Copy link

What does this mean "should not be in EPEL"?
If a package shouldn't be in EPEL, that has nothing to do with CVE checking.

What does this mean "should not be in EPEL"? If a package shouldn't be in EPEL, that has nothing to do with CVE checking.
salimma commented 2022-03-30 20:59:55 +00:00
Author
Contributor
Copy link

What does this mean "should not be in EPEL"?
If a package shouldn't be in EPEL, that has nothing to do with CVE checking.

true, but this actually happened - libvncserver had lots of CVEs, and we only found out and retire it as part of looking at CVEs

> What does this mean "should not be in EPEL"? > If a package shouldn't be in EPEL, that has nothing to do with CVE checking. true, but this actually happened - libvncserver had lots of CVEs, and we only found out and retire it as part of looking at CVEs
sobek commented 2022-04-26 21:22:24 +00:00
Contributor
Copy link

I would change (I am not a native English speaker, hence might be wrong):

  • "critical bug not" to "critical, but not" (or "critical and not")
  • "above but retire" to "above, but retire" (or "above and retire")
I would change (I am not a native English speaker, hence might be wrong): - "critical bug not" to "critical, but not" (or "critical and not") - "above but retire" to "above, but retire" (or "above and retire")
carlwgeorge commented 2022-04-28 01:38:42 +00:00
Owner
Copy link

s/Confligting/Conflicting/

s/Confligting/Conflicting/
carlwgeorge commented 2022-04-28 01:40:23 +00:00
Owner
Copy link

These bullet points seem to be using a mix of sentence fragments and complete sentences. We should stick with doing it one way or the other, with the appropriate capitalization and punctuation.

These bullet points seem to be using a mix of sentence fragments and complete sentences. We should stick with doing it one way or the other, with the appropriate capitalization and punctuation.
dherrera commented 2025-03-11 06:34:40 +00:00
Owner
Copy link

After the big restructuring, this PR got into a state that can't be fixed by just rebasing. The change is small, since it only involves the nav file, but if you want to continue working on this, I rebased it on this branch.

https://pagure.io/fork/dherrera/epel/tree/pr-307-rebase

After the big restructuring, this PR got into a state that can't be fixed by just rebasing. The change is small, since it only involves the nav file, but if you want to continue working on this, I rebased it on this branch. https://pagure.io/fork/dherrera/epel/tree/pr-307-rebase
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin security:security
git switch security

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff security
git switch security
git rebase main
git switch main
git merge --ff-only security
git switch security
git rebase main
git switch main
git merge --no-ff security
git switch main
git merge --squash security
git switch main
git merge --ff-only security
git switch main
git merge security
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
meeting
  
backlog status
needs review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

Archived

  
backlog status
ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

Archived

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

Archived

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

Archived

  
planned
A task that was added to a sprint from the beggining of it.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

Archived

  
priority
high
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
priority
low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
priority
medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
sprint status
blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

Archived

  
sprint status
done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

Archived

  
sprint status
in progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

Archived

  
sprint status
review
 Work items that are complete but need review, testing, or approval before being marked as done.

Archived

  
sprint status
to do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

Archived

  
technical debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

Archived

  
work item
bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

Archived

  
work item
epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
work item
spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

Archived

  
work item
task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

Archived

  
work item
user story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

Archived

No labels
meeting
backlog status
needs review
backlog status
ready
chore
documentation
planned
points
01
points
02
points
03
points
05
points
08
points
13
priority
high
priority
low
priority
medium
sprint status
blocked
sprint status
done
sprint status
in progress
sprint status
review
sprint status
to do
technical debt
work item
bug
work item
epic
work item
spike
work item
task
work item
user story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
epel/docs!167
No description provided.