Define the scope of the project at CoreOS #2
Labels
No labels
Doing
To Do
basic
bug
duplicate
enhancement
evaluation
help wanted
invalid
priority/High
priority/Normal
research
topic/ideal-distributed-infrastructure
topic/package-centric-containers
type/Backlog
type/Planned
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: steveej/msc-thesis#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It was discussed that the full scope of this project does not align with what CoreOS is expecting.
This should not stop the project at CoreOS, but rather limit the scope of what is actually concerned by CoreOS. Effectively this divides the thesis to subjects that counts as work for CoreOS and others that don't. Subjects that belong to work for CoreOS should not depend on non CoreOS subjects because the former will have the higher priority.
/cc @philips @jonboulle
Doesn't happen as described.