Difference between revisions of "Internal communication"
From GLMWiki
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Would suggest return to weekly Engineering meetings | + | *Would suggest return to weekly Engineering meetings |
| − | Chart out intended prorities for the week | + | *Chart out intended prorities for the week |
| − | Discuss (briefly) what has been completed, and if it has been documented properly | + | *Discuss (briefly) what has been completed, and if it has been documented properly |
| − | Identify timeframes of potential network related issues (intended reboots, of services, routers, etc) so that employees, at least, are notified. | + | *Identify timeframes of potential network related issues (intended reboots, of services, routers, etc) so that employees, at least, are notified. |
| − | Be pro-active in notifying customers of scheduled maintainance, that will impact their services. | + | *Be pro-active in notifying customers of scheduled maintainance, that will impact their services. |
| − | We will probably need to come up with some sort of guidelines as to at what level of 'potential' impact, should we notify customers. | + | *We will probably need to come up with some sort of guidelines as to at what level of 'potential' impact, should we notify customers. |
| − | Create, and keep a 'Network Status', or something to that effect ... area in a prominent area available off our main web page | + | *Create, and keep a 'Network Status', or something to that effect ... area in a prominent area available off our main web page |
| − | Network engineers should be alerted when something is happening on the network that may result in system issues ... We may not be able to work as one person, but would be good to know generally what each of us is doing. | + | *Network engineers should be alerted when something is happening on the network that may result in system issues ... We may not be able to work as one person, but would be good to know generally what each of us is doing. |
--[[User:Dhosh|dhosh]] 03:39, 23 May 2009 (UTC) | --[[User:Dhosh|dhosh]] 03:39, 23 May 2009 (UTC) | ||
Latest revision as of 00:11, 23 May 2009
- Would suggest return to weekly Engineering meetings
- Chart out intended prorities for the week
- Discuss (briefly) what has been completed, and if it has been documented properly
- Identify timeframes of potential network related issues (intended reboots, of services, routers, etc) so that employees, at least, are notified.
- Be pro-active in notifying customers of scheduled maintainance, that will impact their services.
- We will probably need to come up with some sort of guidelines as to at what level of 'potential' impact, should we notify customers.
- Create, and keep a 'Network Status', or something to that effect ... area in a prominent area available off our main web page
- Network engineers should be alerted when something is happening on the network that may result in system issues ... We may not be able to work as one person, but would be good to know generally what each of us is doing.
--dhosh 03:39, 23 May 2009 (UTC)
