These are chat archives for ethereum/homestead-guide
@frozeman: I agree the homestead docs should not be an all encompassing entity. Ethereum has many, many areas, and stuff like the intimate details of the APIs may be better placed on the wiki or in the repos that develop those APIs.
@tgerring : My opinion is this guide should be for people who have never heard of Ethereum, heard about the homestead update, and want to do 2 things: Use Ethereum and/or develop on Ethereum. What that means is we need to have a section for "using Ethereum", which is a combination of basic information with examples (like dealing with accounts, sending ether, and interacting with a DApp) and a "developing using Ethereum" with details on creating, compiling, and deploying a contract. There will be more detailed short tutorials/examples in the development section of the guide, and anything beyond the basics can be directed to the new Solidity documentation or areas of the Web3 JS wiki.
This guide should serve to be an entry level for Ethereum users and developers who have to scramble around multiple resources for the most up to date information. I think of it as a checkpoint of updates and better examples/context compared to the previous checkpoint, the Frontier Guide.
So the homestead document's purpose would be to be an entry point for all ethereum users and developers and not overly specific or overly technical details. Anything that is specific (for example: certain aspects or details of web3 that devs will likely not even need to use in their general DApp programming or the technical details of ET Hash/how tries are implimented) would stay on the wiki with the possibility of linking to them from the homestead guide. Additionally, things that are not ready for homestead yet, like Whisper and much of the serenity details, will stay on a wiki or independent format. If the document's prove to be successful in this format and we agree to expand it, we can then make a decision to move or not to move the specific data to the guide.
To address the duplication concern: duplicate information should be kept at a minimum and we can do that for most of the information by either adding a "LEGACY" notice to the non-maintained pages with a link to the homestead guide or editing the wikis to remove the material that is a direct copy/paste of homestead guide.