Timeline for Documentation degrading - how to deal with it?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25, 2012 at 17:16 | comment | added | Andrzej Bobak | That's right, and one thing is for sure - his life among the team won't be easy | |
| Jul 25, 2012 at 14:51 | comment | added | Michael | The underlying point here is important -- you need a documentation champion who is going to hold the team to some kind of standard. | |
| Jul 23, 2012 at 18:52 | comment | added | Andrzej Bobak | then roll-back his solution pointing out which sections of the wiki need to be updated in order to finish the task | |
| Jul 23, 2012 at 18:51 | comment | added | k.m | Initial write-up is not a problem. When that doc is already present, and somebody else changes original module code he often "forgets" update external docs/wiki (or sometimes isn't even aware that such thing exists). | |
| Jul 23, 2012 at 18:34 | history | edited | Andrzej Bobak | CC BY-SA 3.0 |
edited body
|
| Jul 23, 2012 at 18:26 | history | answered | Andrzej Bobak | CC BY-SA 3.0 |