-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why no .pdf's included? #5
Comments
The "no PDF" rule is meant for original scanned PDFs. In terms of project scope, I had in mind designs that predate eCAD generated PDFs. My decision was that we link to system-specific repositories that contain the original source material/schematics. Regarding KiCad generated PDF, I'm open to that. |
Ah, that's good to hear. Might I suggest updating the "rules" readme since it seems to pretty explicit say only KiCad source files?
|
Kicad can generate PDF files if/when needed, which would obviously be of better quality than old scans of original documents. Being composed primary of human readable text, the KiCad file would be much more searchable (both manually and machine) than PDF. Again, not saying PDFs would be useful or practical. Only that making it a rule seems unnecessary to me. Consider if the rule was "must include JPG so that we can embed in web pages, or must be viewable directly in github.? Seems to me that more important things to work out include version numbering and contributor tracking. Did you copy the schematic layout page for page or did you optimize? How does one validate the accuracy and completeness of the schematic capture? Are board dimensions required? Etc |
PDFs and images will inevitably drift away from the KiCAD source of truth as changes are made either for more accuracy, better readability, or to correct errors. It would be nice if there were an online generator of schematic -> image, but absent that, this repository should not be the place to solve that problem. |
Howdy,
Submitting here because I'm sure others have the same question.
Since it github's bandwidth anyway, I'm curious what the reason is for not including .pdf's along with the KiCad design?
I can somewhat understand not wanting pdf-only submissions (although I'd personally like to see searchable pdf's included too), but by not including them even on KiCad designs, the utility of this repository is really limited to those that can successfully install KiCad. There are a whole host of reasons that might not be the case:
I hope you'll reconsider - I think the goal here is noble and I'd like to see it have the greatest chance of success.
The text was updated successfully, but these errors were encountered: