Define the scope of the project at CoreOS #2

Closed
opened 2015-08-05 23:12:01 +00:00 by steveej · 1 comment
steveej commented 2015-08-05 23:12:01 +00:00 (Migrated from gitlab.com)

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

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
steveej commented 2016-02-08 11:06:48 +00:00 (Migrated from gitlab.com)

Doesn't happen as described.

Doesn't happen as described.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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: steveej/msc-thesis#2
No description provided.