I quite like the CoC of the EMF camp as it seems to the point, un-ambigious and written in language I understand. I may try and adapt it for online interaction. What do others think?
3,337 karma · joined May 8, 2011
https://kaspar.systems
github.com/kasbah
hn@kaspar.systems ---
I quite like the CoC of the EMF camp as it seems to the point, un-ambigious and written in language I understand. I may try and adapt it for online interaction. What do others think?
This one is really well done and gives me some ideas. Would be cool if it took advantage of bigger screens.
For 2. it might be worth integrating with some of the part managements systems. https://github.com/monostable/awesome-electronics#inventory-...
https://github.com/mossmann/hackrf
P.S. I should really have a go at this power supply too: https://github.com/eez-open/psu-hw
The cost for a one-off order is always more than something that is made multiple times so I it's not a question of competing on price. Kitspace currently optimizes for one-off orders (batching orders of a single design for multiple people would be interesting too though).
I am curious, how do you think it lowers the support burden? Do you mean they can just say: "you soldered it, I don't know, works for me" or is it something more? :D
I think the stencils are best left to the batching services and Aisler and PCBway, which are linked from Kitspace, offer them too (and they should pick out the relevant solder-paste Gerber files).
EDIT: Oh, and regarding planned features check: https://github.com/monostable/kitspace#planned and the work-in-progess (WIP) pull-requests: https://github.com/monostable/kitspace/pulls
It would indeed be great to have more types of designs. We've had an influx of animal shaped PCBs recently (partly my own fault [1]) so I am on the search for some rectangular green, serious ones to offset that. I feel like it's slowly getting to a point where it's worthwhile adding categories.
[1]: https://blog.monostable.co.uk/posts/etching-oscillators-in-z...
Best practices, it's a good idea, but it is hard enough to get people to do the minimal thing that I came up with for Kitspace and I think only certain kinds of people will read a best practices guide. At the Global Open Science Hardware Gathering [4] we are trying to come up with more general best practices for open source hardware though and doing a more focused one for electronics would be worthwhile anyway.
About attending OHS, not unless I can get some travel funding :(
[1]: https://www.evilmadscientist.com/2011/improving-open-source-... [2]: http://www.xess.com/blog/schematics-really/ [3]: https://fosdem.org/2018/schedule/event/cad_pcb_code/ [4]: http://openhardware.science/gosh-manifesto/
Yes, I totally can't wait to take more advantage of the Git back-end! I like the idea of visual diffs though they can have problems (if you move the entire design by 1mm say). Just having tagged versions will be the first step and we can experiment after that.
I have been pushing people to better document the projects and helping with getting the required files into place (and sometime helping them use Git/GitHub). I have been doing what I call guerrilla BOM building (never shout this at an airport!) where I sort out an OSHW project's bill of materials and send a PR. I was doing some of this today: [1][2]. I will be applying for grants to do more of this and maybe get some help with it.
[1]: https://github.com/prometheus-science/Flypi/pull/2 [2]: https://github.com/rwb27/openflexure_nano_motor_controller/p...
If you click on the "repo" link for most (not all) projects you will be able to download schematics (the majority are done in KiCad).
I forked the ergodox project and will have a go at helping the creator put it up when I get a chance.
[1]: https://kitspace.org/boards/github.com/im-tomu/tomu-hardware...
Source code for Kitspace is on GitHub as well: https://github.com/monostable/kitspace
Tindie is a really cool platform for selling kits and assembled projects and I need to figure out how to best reach people there. Kitspace is kind of trying to serve the niche of creators that don't want to put in the effort to put together and sell assembled projects or kits. There is probably still some overlap though and some people do have projects on both sites already I believe.
Kitspace is built with React and Semantic-UI (and pcb-stackup! [2]) and is compiled into a static site hosted on Netlify. I chose to implement my own build system using Ninja because I didn't get on with the frontend build tools at the time and it needs to process a lot of assets (and I do embedded systems programming by day, so I actually like Make and Make-like build tools). This was before Webpack and I had a go at understanding Webpack a few times in the mean time but never got my head around the config language.
I am currently working on moving away from a static site and using an instance of GitLab as a back-end. I am eyeing up Parcel and Next.js as possible routes for building the new front-end.
[1]: https://github.com/kitspace-forks [2]: https://github.com/tracespace/pcb-stackup/
I have been working on this for a number of years already (started with the browser extension) and have a few things in the pipeline such as integrating a GitLab back-end for easier file-uploads and adding a bill of materials editor.
The source code is available at https://github.com/monostable/kitspace (give it a star if you like it - it really helps a lot with grant applications). There is an alpha version of a BOM builder tool at: https://bom-builder.kitspace.org. Feel free to ask for more details of course :)
The extension source code is available at: https://github.com/monostable/1clickBOM and it's been extensively reviewed by Mozilla for getting it up on addons.mozilla.org.
(Source code for Kitspace is on https://github.com/monostable/kitspace by the way.)
https://fosdem.org/2018/schedule/track/cad_and_open_hardware...
- Use version control!
- Hire a professional software developer
- Good architecture and abstraction comes mostly from practice but if you really want to do some reading on software architecture check out "The Architecture of Open Source Applications" (vol 1 & vol 2)
[1]: https://homes.cs.washington.edu/~bodik/ucb/cs294fa12.html