Hi
user
Admin Login:
Username:
Password:
Name:
How to build a BOM: Sourcing and open source
--client
croud_supply
--show
teardown_portland_2018
--room 510 13809 --force
Next: 1 More Than Music with MIDI, Tiny Computers & JavaScript
show more...
Marks
Author(s):
Nadya Peek
Location
510
Date
may Sun 13
Days Raw Files
Start
10:30
First Raw Start
error-in-template
Duration
0:30:00
Offset
None
End
11:00
Last Raw End
Chapters
Total cuts_time
None min.
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
How_to_build_a_BOM_Sourcing_and_open_source.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
The accessibility of open source hardware is predicated on reliable low-volume component sourcing. How can you best design a Bill of Materials (BOM) for a toolkit or infrastructural hardware contribution? Reproducibility of parts and assemblies is key! How do you make it easy for others to build on your designs? Drawing from experiences in designing open source hardware machine building kits, I give recommendations for reproducible design BOMs.
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review