Add a summary of our general Tech Infrastructure #93
Conversation
It's more than just {hard,soft}ware development.
|
Infrastructure is not in the competition remit. Please consider submitting this documentation to the appropriate location, or limiting the scope to competition team infrastructure only. This is especially relevant as Kit specific infrastructure is likely to be deployed in the near-future. There was an Infrastructure Team proposal flying around a while ago, might be best to wait until that is settled. I'd request that this PR is not merged until this is settled. Content looks good from a brief glance. Related: #92 |
docs/infrastructure/README.md
Outdated
| @@ -0,0 +1,62 @@ | |||
| # Overview | |||
|
|
|||
| Student Robotics has a variety of infrastrcture in order to support its mission. | |||
There was a problem hiding this comment.
| Student Robotics has a variety of infrastrcture in order to support its mission. | |
| Student Robotics has a variety of infrastructure in order to support its goals. |
There was a problem hiding this comment.
Typo fixed in 24fe613. Is there a reason to change mission to goals?
This is true but irrelevant. The runbook is not and never has been exclusive to the Competition Team. I am not interested in having a discussion of remit on this PR. |
Co-authored-by: Dan Trickey <[email protected]>
Co-authored-by: Dan Trickey <[email protected]>
Co-authored-by: Dan Trickey <[email protected]>
There was a problem hiding this comment.
Infrastructure is not in the competition remit.
This is true but irrelevant. The runbook is not and never has been exclusive to the Competition Team. I am not interested in having a discussion of remit on this PR.
It is a shame that we could not discuss this.
Requesting changes on the grounds that information not under remit of the competition team should not be committed to this documentation.
To be clear: I am stating that we should not discuss this on this PR.
Unfortunately I'm not going to be able to help with your request here, because it is based on an incorrect premise. As noted, I am not interested in having a discussion of the remit of the runbook on this PR. If you would like to have a general a discussion of the remit of the runbook, I suggest opening an issue instead. However I would caution against expecting radical change quickly -- it was quite a surprise to many that the Kit Team believed that the runbook was a purely Competition Team edifice, especially when the runbook self-documents otherwise. |
Co-authored-by: Dan Trickey <[email protected]>
This will need review as part of srobo#71, though is hopefully useful enough for now.
At some point we'll need to work out how & where to outline exactly who is responsible for what, but I'm opting not to do that for now.
This is deliberately fairly high level and I expect that it will probably remain relatively high level in favour of having detailed instructions closer to the code which actually controls the relevant setups.