I think a lot of the problem here is conflicting ideas (or just confusion) about what the Ubuntu documentation should 'be'. What purpose should it fulfil?
If we look at the extreme of having 'no overlap', the Ubuntu documentation would just be a front page with links to everyone else's documentation. Every app on the desktop has its own documentation - do we just glue that together? If so, what is the Doc Team for? I think that if people come to our docs to look for answers, we should provide answers or tell them where to get them. In some circumstances, it is better to provide the answers ourselves, because upstream don't provide satisfactory answers, because it's faster/easier to do that than make the user click a link and look through a manual, or because we can't link to those answers anyway. Also, Yelp is incompatible with many upstreams. If we convert the OpenOffice docs to DocBook for Yelp, then the OO.org project has to change how it develops its documentation, and takes a hit in terms of having to maintain the new docs. I think that projects will resist change, especially when they don't see any benefit to themselves from our proposed changes. Re:[1] - Pidgin doesn't have to be connected to the Internet to be useful. See the use cases in my comment above. Re:[2] - I don't know about that. If there were tools in existence already to do that job then it would be less time consuming. Otherwise, we'd have to develop those tools... -- Instant messaging documentation doesn't cover useful topics https://bugs.launchpad.net/bugs/128384 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
