Welcome to Etherpad!

This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!

To prevent your pad from appearing in the archive, put the word __NOPUBLISH__ (including the surrounding double underscores) anywhere in this pad. Changes will be reflected after the next archive update.

Warning: DirtyDB is used. This is fine for testing but not recommended for production. -- To suppress these warning messages change suppressErrorsInPadText to true in your settings.json Meetings tonight:
    19h Guifi.net meeting  - Community owned mesh network : https://archive.org/details/Guifi (intro to guifi)
    19h Esta es una plaza: http://estaesunaplaza.blogspot.com.es/

Meeting tomorrow:
    10-13h: 
        * presentation of projects
        * small group to turn Library Box TP-Link 2030 into Piratebox
        * 11h: documentation zipped to copy
    
November 2016
Constant would like to organise a travelling ' exhibition ' (maybe not the best word for it) throughout ( flab ) labs in Belgium , Brussels & other places
The goal is to make knowledge exchange , documentation tangible in an environment (lab) from which this is often lacking and that is not the most suitabale for it. 
The wider scope: make discussion between labs happen. This can be a talking object, a step in the process.
The display, show, exposé, collection ..., can contain amongst other series of derivative works (think about the example of the bookfurniture Bouctje, that is flexible in scale and material) 
See it as a 'thinking object' that serves to think together about the function and place of documentation and exhange in different forms and sizes depending on different fablabs .
It can contain documentation of digital to physical transformation for each object, present physically (tangible seems to be a good word for it)
Libre Objet (Mathieu) will create an exhibition object that will be made collectively in different shapes/materials in 3 fablabs (Timelab, Fablab Brussels, KIKK Festival)
-> What about Fablab Leuven/Genk/Molenbeek? would they be interested in joining ? That would be nice !
-> D ocumentation is existential part of fablab & how to display this
-> why fablabs and not other structures as well ?
-> take different contexts into account, (university / community center / artists space .. ) different publics (makers, elderly, specialists, children .....)


Software Tips & Tricks
Digital to physical

- main design software  - free of possible
you need expertise on translation part, can be difficult
f.ex. svg -> dxf
f.ex. Make Human: you have large series of parameters in software, but lot of glitches in export to 3D
protocol people follow to prepare the file & translation
boolean process in Blender needs sometimes adjustments and technical knowledge to perform connectly.
New boolean software workinq only with triangular mesh is in preperation (works from commandline)

-> if you design with groups, also depends on background of people
    - use autodesk... F/LOSS? ingeneers prefer this
    - use Grasshopper
    - Openscad -> methematicians love it

3d software choice : http://wiki.imal.org/howto/3d-modeler-cad-softwares and https://www.gliffy.com/go/publish/5271448 (thanks microfactory)
2d soft w are choice : http://wiki.imal.org/howto/2d-drawing-software-tools-use-laser-cuter-and-cnc
Imal code, art & craft session: human interaction for specific projects
timelab: has a list of FLOSS solutions for beginners

classic: people come with digital file & think printing will be instant
3D printing adds layers, some parts need physical support
CNC takes away layers. but with physical limits (ex round objects)
Daniel tweaking machines, f.ex. lasercutter: sends file to machine, becaus ehe knows the machines, he changes the height of calibration for depeer cuts -> nice to see that operators know their machines & costumize
'was not using the machines correctly' or 'was using the machine correctly!'
-> are using device for other things than what they're meant for
-> Veerle: keeps log of maintenance of machines // problems & solutions

imal: users are obliged to follow introduction
TRAKK : Users receives machine introduction when they need it. 
MicroF : old members teach to the new members 

Fablab Leuven: people coming 1x, they help / others: explain quickly
linked to university

imal: people cannot come only once, community building is very important, they don't want to be a service
-> art organisation
informal exchange around machines, important on design of the space
collaborating with other people in the building
2,5 fulltime jobs

Fablab Genk: allows people to come once, they might come back
linked to art school
open days on Thu/Fri, no limitation, first come first served
waiting lines for CNC
2000 users/year

Microfactory (20 à 24 people) in Micromarché (housing different organisations, bar)
sprl (small company)
people sometimes decide to buy machines together (internal crowdfunding)
small scale, 1 table, 1 clean + 1 dirty work space
only memberships, from 50€ till 150€/month

TRAKK in same building as offices
-> non profit organisation
employees have entrance to fablab
creativity, brainstorm, technical workshops

Fablab Dakar
linked to art center Ker Thiossane (ngo)

Fabrication Ateneus, Barcelona
http://ateneusdefabricacio.barcelona.cat/es/
'ateneu': place where people meet, stay, relate...
network of townhall with fablabs, makespaces...
trying to put one of these labs in each districts
free to use all machines
return your work to community
ex embroidery machine -> Mireia was proposed to learn the machine and to explain to others (this is her payback)
goal: to create a community around it
not like fablabs: they ask for money
'fablabcity' did not work, machines were there -> invented this ocncept


Digital versioning
wiki's with related pages
el recetario: projects can be related

git - keep track of first version & all changes
software vs platform (github, gitlab, bitbucket)
-> you don't need a server, you can use it alone on your own machine 
f.ex. if you write a text/make image, you usually have many numbered versions -> when you come back 6 months later, you don't remember what was the last version
git = watch this file for the changes, record the changes, you can describe your changes

• = more efficient with text based format (shows exactly which text has changed + where)

github popularized git, made it fun to use
but it created confusion between git/platform (cfr gmail/mail, internet/FB)
alternatives: subversion (needs server), mercury, wiki software (indirect, difficult to fork)

* Cecilia creates enhanced folder (includes .git)

• go inside folder
• git init 

* Cecilia push it onto a server

• git push 'address_of_repository'

* FRFR else wants to work on it

• git clone 'address_of_repository'

* FRFR makes changes
creates new file 
says to git 'watch this file': 

• git add new_file

stores file into the history:

• git commit new_file

sends file back to Cecilia's server:
    git push

Schematic : https://en.wikipedia.org/wiki/Git_%28software%29#/media/File:Git_operations.svg
This one is nice: http://www.tsbakker.nl/images/gitstages.jpg

when Cecilia is working on same file & pulls changed file from FRFR:
    there will be 'conflict' if they both worked on introduction
    needs to be solved manually
    if they worked on different parts, she can 'merge' the files
-> in collective projects: you need decision process outside of git (agreement or fork)

Master-Branch structure
each folder has 1 default branch: master (you can change the name)
using git alone:
    pink -> blue -> green -> pink (3 months later)
    instead of going in file and make pink, you make a branch:
        git branch blue
    it does not copy all the files, from that point on it creates a branch in the history with exactly the same content
    go into that branch

•    git checkout blue

-> no one ever works on master branch, is like history tree
everyone works on her own branch
when you're happy with result, you merge it back to 'main trunk' and make it next version
if there is a bug you have to fix, you repair on the master & continue developing in branch
Branch schematic : http://i.stack.imgur.com/n3gDy.png
you make as many as you want, you can delete them
-> you can share your branches with people (instead of messing up master)

git diff
git visualizers (f;ex. see birth of Linux :-))