Rob Hirschfeld ([email protected]) wrote: > All, > > HELP REQUEST: We need your help to create a catalog of doc issues on > http://bit.ly/crowbar-maladocs > > We had a discussion today about the high community cost for errors and > omissions in our documentation, wiki and other information. > > First - I apologize for the impact of this. As one of the longest active > maintainers, I know first-hand the expense and frustration for these gaps; > however, I also acknowledge that I am often a culprit in failing to leave > behind sufficient instructions. > > To remedy the problem, I believe that we first need to create a catalog of > issues to resolve. While we could create defects for these, our current > tracking process is not ready to handle these types of issues. Instead, I'd > like to offer a Trello board (http://bit.ly/crowbar-maladocs ) where you can > add new issues as you find them. Sometime in the next few weeks, I'm > recommending a "docs hack day" where we burn down the issues. > > Of course, you're welcome to grab doc issue cards right away. I just wanted > to set an expectation that we're not going to jump on each issue - our first > priority is to find them. > > Suggestions and corrections to this approach are appreciated!
Thanks for kicking off some fresh impetus on this much-needed area. We already have several documentation cards in the Community List of the 2.0 backlog board. Should those be moved to this new board? I'm slightly worried that having a dedicated board for doc issues will make it easier than ever for them to remain "out of sight, out of mind". However, I'd be delighted to be proven wrong ;-) +100 for a docs hack day ... _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
