{"action":"created","issue":{"url":"https://api.github.com/repos/KiCad/kicad-doc/issues/394","repository_url":"https://api.github.com/repos/KiCad/kicad-doc","labels_url":"https://api.github.com/repos/KiCad/kicad-doc/issues/394/labels{/name}","comments_url":"https://api.github.com/repos/KiCad/kicad-doc/issues/394/comments","events_url":"https://api.github.com/repos/KiCad/kicad-doc/issues/394/events","html_url":"https://github.com/KiCad/kicad-doc/issues/394","id":161457602,"number":394,"title":"GSIK: Proposal for restructure","user":{"login":"evanshultz","id":1936989,"avatar_url":"https://avatars.githubusercontent.com/u/1936989?v=3","gravatar_id":"","url":"https://api.github.com/users/evanshultz","html_url":"https://github.com/evanshultz","followers_url":"https://api.github.com/users/evanshultz/followers","following_url":"https://api.github.com/users/evanshultz/following{/other_user}","gists_url":"https://api.github.com/users/evanshultz/gists{/gist_id}","starred_url":"https://api.github.com/users/evanshultz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evanshultz/subscriptions","organizations_url":"https://api.github.com/users/evanshultz/orgs","repos_url":"https://api.github.com/users/evanshultz/repos","events_url":"https://api.github.com/users/evanshultz/events{/privacy}","received_events_url":"https://api.github.com/users/evanshultz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-06-21T14:50:29Z","updated_at":"2016-07-07T13:44:29Z","closed_at":null,"body":"Currently there are a few sections at the top which are nice, IMO. But after that, it gets unclear to me:\r\n-There's a huge Eeschema section which covers project creation, exporting a netlist, assigning footprints, generating a BOM, etc. It's monolithic.\r\n-Next is the Pcbnew section, which just covers designing the PCB. Generating and checking Gebers is a separate section, as is auto routing and annotation.\r\n-Then is the creation of schematic parts by a number of means and then making footprints. And finally a small note (which is a somewhat of a repeat of the Support section at the top).\r\n-Finally there are some notes.\r\n\r\nThe flowchart isn't especially clear, because it doesn't show project creation, shows two different ways to assign footprints, etc. (There are instructions to update this, I know.)\r\n\r\nIt seems to me that a few more sections would be helpful in showing the process, mostly on the schematic side. Here's my suggestion for re-arranging this doc starting at the \"Draw electronic schematics\" section (section titles not finalized, just the workflow):\r\n-Create project (KiCad manager)\r\n-Eeschema\r\n--Draw schematic\r\n--Bus connections\r\n--Annotate schematic\r\n--ERC\r\n--Assign footprints\r\n--Generate netlist\r\n--BOM\r\n-Pcbnew\r\n--Set up board (DRC, layers, etc.)\r\n--Import netlist\r\n--Place components\r\n--Lay out copper\r\n-FreeRouter (see below)\r\n-Design changes (Backward Annotation also included here)\r\n-3D viewer\r\n-Generate fab files (back to Pcbnew)\r\n-View fab files\r\n-Making components (few sections)\r\n-Making footprints\r\n-Send off\r\n\r\nWhat to do with FreeRouter? Considering that project's current status, does this section get removed? Keep it as is, with polish as needed? Add note about Java version/dependencies?\r\n\r\nI also find that titles using a present participle (-ing words) are more friendly, so I suggest changing \"Generate Geber files\" to \"Generating Geber files\". And also eliminating first person (\"we, \"let's\") in favor of strictly second person (\"you\", \"your\") perspective.\r\n\r\nIs there something wrong with this? It seems to me that breaking things down a bit more is better to show the process. Comments? Criticism?"},"comment":{"url":"https://api.github.com/repos/KiCad/kicad-doc/issues/comments/231081416","html_url":"https://github.com/KiCad/kicad-doc/issues/394#issuecomment-231081416","issue_url":"https://api.github.com/repos/KiCad/kicad-doc/issues/394","id":231081416,"user":{"login":"ciampix","id":372887,"avatar_url":"https://avatars.githubusercontent.com/u/372887?v=3","gravatar_id":"","url":"https://api.github.com/users/ciampix","html_url":"https://github.com/ciampix","followers_url":"https://api.github.com/users/ciampix/followers","following_url":"https://api.github.com/users/ciampix/following{/other_user}","gists_url":"https://api.github.com/users/ciampix/gists{/gist_id}","starred_url":"https://api.github.com/users/ciampix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ciampix/subscriptions","organizations_url":"https://api.github.com/users/ciampix/orgs","repos_url":"https://api.github.com/users/ciampix/repos","events_url":"https://api.github.com/users/ciampix/events{/privacy}","received_events_url":"https://api.github.com/users/ciampix/received_events","type":"User","site_admin":false},"created_at":"2016-07-07T13:44:28Z","updated_at":"2016-07-07T13:44:28Z","body":"I would like to make arrangements to create automatic builds also for the dev branch, just to be able to check the results in real-time for errors..."}}
{"actor":{"display_login":"ciampix"}}