add a "what do we host and how" document #1
Conversation
|
Should we have a style requirement (CSS) somewhere to make all the sites look similar? |
That's for the marketing team to figure out, not the IWG. Our goal is simply to keep track of what things we have and to keep them running. |
genehack
left a comment
genehack
left a comment
There was a problem hiding this comment.
Modulo feedback, none of which I feel super strongly about.
| and such service has crashed and needs a reboot." | ||
|
|
||
| The larger question is what happens when a service's custom code is broken by | ||
| changes to the standard deployment environment. If the IWG is unable to make |
There was a problem hiding this comment.
Don't we have a responsibility to test any such change to make sure it doesn't break stuff? And if it does, give a window for remediation?
There was a problem hiding this comment.
Yes, but consider:
- imagine we say "services must run on Debian, and we have some minimum version"
- hosted service relies on a feature of Debian-packaged service no longer found in new version
- if it's trivial to tweak the software, we will
- …but what if it's not?
We discussed this on Zoom, basically saying that in a case like this, we would make at least a bare minimum attempt to see if the problem was trivially addressable, and failing that, we would make a notice that the service would go offline at some future point if nobody provided a fix. We'd say "send your fix to this github repo" or the like.
This document was discussed at the 2020-09-17 meeting, and notes taken. I expect this will change over time, but this is the first pass.