2013/7/19 Samuel Chase <samebchase@...400...>:
This is what has been done so far: http://staging.inkscape.org/en/develop/getting-started/
What sections to add/remove, etc?
1. Change the command for getting the source from "bzr branch" to "bzr checkout". New developers should default to the SVN style workflow, as it's easier to keep up to date with trunk and submit small patches in this fashion. Branches are better for developing larger features.
2. Do not split the text with many small headings, this looks ugly and is unreadable. For instance, all h3's under the "Fetching the source code" heading are unnecessary and could be rewritten as prose.
3. Detailed compilation instructions should not be included on this page. Instead, these should be links to the relevant pages on the wiki, or there should be separate pages on developer workflow on each platform. "Getting Started" should only contain basic information, e.g. that you need to type "btool" or "./autogen.sh; ./configure; make".
4. When it comes to Bazaar usage information, Getting Started should only include instructions on how to generate a patch. For any further info the reader should be directed to our very good "Working with Bazaar" wiki page.
5. Programming style has its own page, which is fairly complete: http://staging.inkscape.org/en/develop/coding-style/ - there should be only a link.
6. The "Collaboration" section belongs under "Community", and Getting Started should only mention how developers communicate and link the the relevant pages. Remember, this is supposed to be a brief walkthrough with pointers to more information, not a giant wall of text.
Regards, Krzysztof