|
|
= Network Health =
|
|
|
# Network Health
|
|
|
|
|
|
We will organize potential network health team work according priorities. This will involve
|
|
|
1. Getting some rough understanding what is in scope and where items overlap with other teams' work
|
... | ... | @@ -15,20 +15,20 @@ We'll start with arma's mail about the roadmap for a potential network health te |
|
|
|
|
|
**Duration:** 1 hour
|
|
|
|
|
|
== Prep ==
|
|
|
## Prep
|
|
|
|
|
|
You do not need any prep to make this session. (Re-)reading the mail linked to in the Material section above is recommended, though.
|
|
|
|
|
|
|
|
|
== Desired outcomes ==
|
|
|
## Desired outcomes
|
|
|
|
|
|
* Having a prioritized list of things a network health team/person would work on
|
|
|
* Having a clear understanding where the network health work overlaps with other areas and how do avoid duplication of work
|
|
|
|
|
|
|
|
|
== Notes ==
|
|
|
## Notes
|
|
|
|
|
|
{{{
|
|
|
```
|
|
|
1. Overview
|
|
|
- Standards for good relays (community team owns most of it)
|
|
|
- Documenting community standards about good relays [gus has done some work - community team ownership]
|
... | ... | @@ -74,4 +74,4 @@ You do not need any prep to make this session. (Re-)reading the mail linked to i |
|
|
|
|
|
3. Who owns what; who should own what?
|
|
|
- Documented above
|
|
|
}}} |
|
|
\ No newline at end of file |
|
|
``` |
|
|
\ No newline at end of file |