EXCELLENT WORK! A few quick comments: - Is ":rfc:5322" a macro that should do anything? It looks a bit weird in the generated HTML. - In "fixing a bug" can we link to how "branching the code" and "proposing a merge" works?
I most confess I'm a bit unsure about the structure of the guide and where we're going with it. The way I understood our discussions at UDS we essentially wanted to be task-based and provide articles that help folks to solve a specific problem (fix a bug, update a package to new upstream version, etc.) It's clear that by moving from the Wiki docs to the packaging guide you mostly followed the old structure. One way I can imagine this working out is by writing articles that explain how to attack a task "in general" and add a link to some other article if it doesn't pan out because it's one of those >10% weird cases. (Quick howto that links to in-depth articles if you really need to understand all of it.) Or maybe split the whole guide up into "knowledge base articles" vs. "howto guides"? Can you share your thoughts on it? This is an excellent start, even if we should decide to juggle the sections around a little bit. -- https://code.launchpad.net/~barry/ubuntu-packaging-guide/udd/+merge/48685 Your team Ubuntu Packaging Guide Team is requested to review the proposed merge of lp:~barry/ubuntu-packaging-guide/udd into lp:ubuntu-packaging-guide. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-packaging-guide-team Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-packaging-guide-team More help : https://help.launchpad.net/ListHelp
