Hackerspace Nijmegen Wiki - Gebruikersbijdragen [nl]

Netwerk

2026-04-02T21:56:49Z

SA007: lastdrager aangesloten en extra ap

Deze pagina omschrijft de netwerkinfrastructuur aan de Winkelsteegseweg.

=Overview=

[[Bestand:Netwerkinfra.png|x137px]]

Dit plaatje is verouderd (dit was de setup aan de Villanovastraat). Tegenwoordig is het:
<---Odido (5G)---| Odido router |<---eth--->| pfsense |<---eth--->| Netgear GS728TP |<---eth--->| Aruba APs... |

=TODO=

*Backup configs
*Note passwords somewhere outside of this wiki
*Spacenet

=VLANs=

*1 (of untagged) - management
**dhcp-server op pfsense
**10.138.1.0/24
***10.138.1.1 pfsense
***10.138.1.2 switch (dhcp, static assignment)
***10.138.1.3 lastdrager (ESXi host)
*1336 - Park Winkelsteeg
**dhcp-server op pfsense
**10.138.65.0/24
***10.138.65.1 pfsense
*1337 - hsn
**dhcp-server op pfsense
**10.138.66.0/24
***10.138.66.1 pfsense
***10.138.66.2 domestobot (vm)
***10.138.66.3 homeassistant (vm)
*1338 - bambu
**dhcp-server op pfsense
**10.138.67.0/24
***10.138.67.1 pfsense

=Netgear GS728TP=

*DHCP op untagged - krijgt static assignment 192.168.1.2 van pfsense
*No IP on all other VLANs

==Ports==

*1 --> accesspoint bij groepenkast
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*2 -> Wired naar groepenkast, niet aangesloten
*3 --> accesspoint Diana 1
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*4 --> accesspoint Diana 2
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*5 --> accesspoint serverhok
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*21 -> lastdrager host
*22 -> lastdrager vmnic voor de vm's
*23 -> pfsense

=pfsense=
In het serverhok staat een HP Z220 met daarop VMware ESXi, hostname "lastdrager". Op ESXi draait een VM genaamd "pfsense".

Let op: als deze server bij booten niet doorstart en 6 piepjes geeft, dan komt dat doordat er een beeldscherm aangesloten moet zijn. DVI -> HDMI werkte daarvoor niet, DVI -> VGA wel.

In de server zit een PCI-netwerkkaart die wordt gepassthrought naar de pfsense VM.
*dhcp servers:
**let erop dat je de pool start/end moet invullen, anders is de pool size 0 en krijg je geen leases
**mgmt 10.138.1.0/24 (vanaf .10)
**winkelsteeg 10.138.65.0/24 (vanaf .10)
**hsn 10.138.66.0/24 (vanaf .10)

==Ports==

*eth0 wan --> Odido-router
**dhcp client
*eth1 lan --> netgear port 1 trunkport
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)
*eth2
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)
*eth3
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)
*eth4
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)

=Aruba Accesspoints=

==Setup==

*kies een poortje, zet in de tabel hierboven, hang AP eraan
*default AP config is untagged management, dus AP krijgt automatisch een lease in het management subnet
*AP vindt automatisch de huidige instant controller en trekt config daaruit

Netwerk

2026-03-31T19:56:01Z

SA007: /* VLANs */

Deze pagina omschrijft de netwerkinfrastructuur aan de Winkelsteegseweg.

=Overview=

[[Bestand:Netwerkinfra.png|x137px]]

Dit plaatje is verouderd (dit was de setup aan de Villanovastraat). Tegenwoordig is het:
<---Odido (5G)---| Odido router |<---eth--->| pfsense |<---eth--->| Netgear GS728TP |<---eth--->| Aruba APs... |

=TODO=

*Backup configs
*Note passwords somewhere outside of this wiki
*Spacenet

=VLANs=

*1 (of untagged) - management
**dhcp-server op pfsense
**10.138.1.0/24
***10.138.1.1 pfsense
***10.138.1.2 switch (dhcp, static assignment)
*1336 - Park Winkelsteeg
**dhcp-server op pfsense
**10.138.65.0/24
***10.138.65.1 pfsense
*1337 - hsn
**dhcp-server op pfsense
**10.138.66.0/24
***10.138.66.1 pfsense
*1338 - bambu
**dhcp-server op pfsense
**10.138.67.0/24
***10.138.67.1 pfsense

=Netgear GS728TP=

*DHCP op untagged - krijgt static assignment 192.168.1.2 van pfsense
*No IP on all other VLANs

==Ports==

*1 --> pfsense
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*2 --> accesspoint in de ruimte met de wc
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*3 --> accesspoint in de ruimte met de keuken
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*4 --> accesspoint Diana 1
**vlan 1 (untagged)
**vlan 1336
**vlan 1337
*5 --> accesspoint Diana 2
**vlan 1 (untagged)
**vlan 1336
**vlan 1337

=pfsense=
In het serverhok staat een HP Z220 met daarop VMware ESXi, hostname "lastdrager". Op ESXi draait een VM genaamd "pfsense".

Let op: als deze server bij booten niet doorstart en 6 piepjes geeft, dan komt dat doordat er een beeldscherm aangesloten moet zijn. DVI -> HDMI werkte daarvoor niet, DVI -> VGA wel.

In de server zit een PCI-netwerkkaart die wordt gepassthrought naar de pfsense VM.
*dhcp servers:
**let erop dat je de pool start/end moet invullen, anders is de pool size 0 en krijg je geen leases
**mgmt 10.138.1.0/24 (vanaf .10)
**winkelsteeg 10.138.65.0/24 (vanaf .10)
**hsn 10.138.66.0/24 (vanaf .10)

==Ports==

*eth0 wan --> Odido-router
**dhcp client
*eth1 lan --> netgear port 1 trunkport
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)
*eth2
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)
*eth3
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)
*eth4
**vlan 1 (untagged, management, dhcp-server)
**vlan 1336 (dhcp-server)
**vlan 1337 (dhcp-server)

=Aruba Accesspoints=

==Setup==

*kies een poortje, zet in de tabel hierboven, hang AP eraan
*default AP config is untagged management, dus AP krijgt automatisch een lease in het management subnet
*AP vindt automatisch de huidige instant controller en trekt config daaruit

Overleg gebruiker:Pypytje

2026-03-21T22:36:34Z

SA007: Welkom!

'''Welcome to ''Hackerspace Nijmegen Wiki''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[Gebruiker:SA007|SA007]] ([[Overleg gebruiker:SA007|overleg]]) 21 mrt 2026 22:36 (UTC)

MetaMeet24x09x10

2024-09-10T19:06:28Z

SA007: /* Notulen */

{{Event
|Name=Metameet
|DateStart=2024-09-10 20:00
|DateEnd=2024-09-10 21:00
|InfoLocation=Hackerspace_Nijmegen
}}
[[Category:Metameet]]

=Agenda=
# Wie notuleert
# Financiele update
## Huidige inkomsten en uitgaven
# Huisvesting
## Wat vinden we momenteel van de huidige locatie?
## Is verhuizen naar een permanente locatie mogelijk?
## Zijn er dingen die we willen verbeteren aan de space?
### Verwarming.
### Toegang tot pand.
#Mensen naar de space trekken, suggesties (met als doel nieuwe deelnemers vinden).
##Workshops?
##Eerste vrijdag vd maand weer organiseren?

# Status-updates, mededelingen, verzoeken om hulp en WVTTK

=Notulen=
Opening 20:15.

Financiele update helaas niet gelukt.

Schuift door volgende meet.

Wat vinden we van de huidige locatie:

* Goedkoop, goedkoper is moeilijk.
* Koud in de winter, kan <11 graden worden.
* Slak is onbetrouwbaar, kan zomaar einde contract zijn.
* Brandweer komt van de week kijken, gang moet leeg, komen niet binnen.
* Onafhankelijkheid in belangrijk
* Contract moet dat wel borgen.
* Sponsoring bij IT bedrijven?

Beginnen met zoeken

* Mensen met focus op delen?
* Voelt iemand zich geroepen?
* Idee is om dit wekelijks/2 wekelijks kort te doen met een klein groepje.

Toegang tot het pand

* Meeste spaces hebben elektronisch slot en we willen mensen toegang geven buiten de normale tijden.
* Toestemming nodig van het slak waarschijnlijk.
* Voordeel is dat sleutelhouders weg kunnen gaan als ze willen, peer pressure zorgt ervoor dat dat soms niet lukt.
* Voordeel is ook sleutels kan terugtrekken, dus kan je sleutels vrijer verdelen.
* Voordeurslot aanpassingen spelen via Harm/pandbeheer, misschien erop spelen dat het veiliger kan dan het nu is.
* Als het aanpassen mag en de kosten laag blijven < 200 euro blijft is het een goed idee.

Mensen naar de space trekken.

Coordinatie ligt in basis bij Martijn.

Iedereen is wel specialist op een gebied en kan zelf of wellicht iemand anders overtuigen om wat te organiseren.

Graag ideeen aandragen.

WVTTK

* 3d printer inkoopactie: nog 175 te gaan. 2e hands zijn we er.
* 2x in de maand is misschien wat vaak, 1x per maand een halfuur misschien? Eerst eens zo beginnen en kijken of het korter wordt.

Sluiting: 21:05.

Inkoopactie 3Dprinter

2024-09-03T18:09:16Z

SA007: /* Ik help mee! */

{{Project
|name=Inkoopactie 3Dprinter
|start=2024/07/30
|end=2024/09/01
|contact=Dutchmartin
|URL=https://eu.store.bambulab.com/nl-nl/collections/3d-printer/products/p1s
|Picture=BambuP1S.jpeg
|info=Tientjes inzamelen voor een betere 3D printer:)
|status=Ongoing
}}

Op dit moment hebben we bij Hackerspace Nijmegen een Ultimaker 2. Hier zijn van tijd tot tijd wat problemen mee, is beperkt qua featureset en ook niet bijzonder snel. Daarom is het idee ontstaan om een inkoopactie te starten voor een Bambulab P1S, op dit moment loopt er ook een kortingsactie bij Bambulab, dus dat is mooi meegenomen!

Specificaties kan je vinden bij de productpagina van de Bambulab P1S, maar long story short zijn de belangrijkste features:

* Works right out of the box, set up in 15 minutes
* Well-polished hardware and software
* Enclosed-body for high-temperature filament printing
* Up to 16-color printing (with AMS equipped)
* Up to 20000 mm/s² acceleration, prints a benchy in 18min
* Built-in camera for remote monitoring and timelapse
* Supported Filament (ideal): PLA, PETG, TPU, PVA, PET, ABS, ASA
* Also possible: PA, PC

We willen gaan kijken of het lukt om voor de Combo uitvoering te gaan. Deze is voorzien van de [https://eu.store.bambulab.com/products/ams-multicolor-printing Bambu Automatic Material System (AMS)], welke volautomatisch en in multi-color (4 kleuren per AMS) kan printen.

{| class="wikitable"
! Goals !! Prijs (ex shipping) !! With AMS
|-
| [https://eu.store.bambulab.com/products/p1s?variant=48666904625500 Bambulab P1S] || 609,70 euro || No
|-
| [https://eu.store.bambulab.com/products/p1s?variant=47966917886300 Bambulab P1S Combo] || 863,27 euro || Yes
|-
|
|}

== Ik help mee! ==

Voeg je naam hieronder toe, en het bedrag wat je graag bij wilt dragen.
Als je nog niet bekend bent bij de space, zorg dan dat we je kunnen bereiken om je donatie te verzamelen.

{| class="wikitable"
! Nickname !! bedrag !! aanvullingen !! geïnd
|-
| Dutchmartin || €300 || || Nee
|-
| PPaul || €100 || || Nee
|-
|Yorick
|€75
|
|Nee
|-
|SA007
|€253.57
|De aanvulling naar 'Combo'
|Nee
|-
|
|
|
|}

MetaMeet24x09x10

2024-09-03T18:07:10Z

SA007: /* Agenda */

{{Event
|Name=Metameet
|DateStart=2024-09-10 20:00
|DateEnd=2024-09-10 21:00
|InfoLocation=Hackerspace_Nijmegen
}}

[[Category:Event]]
[[Category:Metameet]]

=Agenda=
# Wie notuleert
# Financiele update
## Huidige inkomsten en uitgaven
# Huisvesting
## Wat vinden we momenteel van de huidige locatie?
## Is verhuizen naar een permanente locatie mogelijk?
## Zijn er dingen die we willen verbeteren aan de space?
### Verwarming.
### Toegang tot pand.
#Mensen naar de space trekken, suggesties (met als doel nieuwe deelnemers vinden).
##Workshops?
##Eerste vrijdag vd maand weer organiseren?

# Status-updates, mededelingen, verzoeken om hulp en WVTTK

=Notulen=
* TODO

VerwarmingIdeeen

2023-08-09T20:54:22Z

SA007: /* Collectief */

Hier volgt een verzameling ideen om hsnijmegen en optioneel de andere ateliers te verwarmen in de winter.

==Alleen de space==
Eisen:
* Goedkoop in gebruik en aanschaf.
* Zonder modificaties aan het pand te plaatsen.
Nice to have:
* Netwerkbediening zodat hij aan kan 'voor' de space open gaat.

{| class="wikitable" style="margin:auto"
! Idee van !! Ideenaam !! Kosten !! Opmerkingen
|-
| SA007 || Airco / Lucht WP || 150ish, elektraprijs/3 voor warmte || Op MP wel eentje goedkoop te vinden, plaatsen kunnen we zelf.
|-
| SA007 || 'Diesel'heater || 150ish, weet gezamelijk oude olie verzamelen? || Op ALi ~130 euro, komt nog wat pijpwerk enzo bij.
|}

==Collectief==
Eisen:
* Geen hobbyoplossing, anders zijn we de hele winter techsupport.
* Afrekenen per gebruiker op verbruik.
* Niet alleen door ons te plaatsen.

Noteer prijzen op basis van makkelijk bulk verkrijgbaar, niet op marktplaats prijzen die alleen vandaag gelden.

{| class="wikitable" style="margin:auto"
! Idee van !! Ideenaam !! Kosten !! Opmerkingen
|-
| SA007 || Airco / Lucht WP || ~550/stuk, elektraprijs/3 voor warmte || goedkopeaircos.nl, mensen zelf laten plaatsen, wij afmonteren?
|-
|SA007
|Straalkachels
|~150/stuk, elektraprijs
|Alleen een stopcontact met kabels aanleggen, kachel zelf regelen.
|}

VerwarmingIdeeen

2023-08-09T20:51:59Z

SA007: Nieuwe pagina aangemaakt met 'Hier volgt een verzameling ideen om hsnijmegen en optioneel de andere ateliers te verwarmen in de winter. ==Alleen de space== Eisen: * Goedkoop in gebruik en aanschaf. * Zonder modificaties aan het pand te plaatsen. Nice to have: * Netwerkbediening zodat hij aan kan 'voor' de space open gaat. {| class="wikitable" style="margin:auto" ! Idee van !! Ideenaam !! Kosten !! Opmerkingen |- | SA007 || Airco / Lucht WP || 150ish, elektraprijs/3 voor warmte || Op MP w...'

Tool:Ultimaker 2 (3D printer)

2023-03-16T14:30:03Z

SA007: Added settings

[[Bestand:Ultimaker-2.jpeg|x400px|right]]

We have an Ultimaker 2 3D printer at the space.

It has an octoprint connected to it, login can be requested.

Some settings that are needed in cura to make a good print:

It is an ultimaker 2, but after setting is to ultimaker 2, change these settings to print via octoprint:

G-code flavor "Marlin"

Start G-code:
G21 ;metric values
G90 ;absolute positioning
M82 ;set extruder to absolute mode
M107 ;start with the fan off
G28 Z0 ;move Z to bottom endstops
G28 X0 Y0 ;move X/Y to endstops
G1 X15 Y0 F4000 ;move X/Y to front of printer
G1 Z15.0 F9000 ;move the platform to 15mm
G92 E0 ;zero the extruded length
G1 F200 E10 ;extrude 10 mm of feed stock
G92 E0 ;zero the extruded length again
G1 Y50 F9000
;Put printing message on LCD screen
M117 Printing...
End G-code
M104 S0 ;extruder heater off
M140 S0 ;heated bed heater off (if you have it)
G91 ;relative positioning
G1 E-1 F300 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
G1 Z+0.5 E-5 X-20 Y-20 F9000 ;move Z up a bit and retract filament even more
G28 X0 Y0 ;move X/Y to min endstops, so the head is out of the way
M84 ;steppers off
G90 ;absolute positioning
;Version _2.6 of the firmware can abort the print too early if the file ends
;too soon. However if the file hasn't ended yet because there are comments at
;the end of the file, it won't abort yet. Therefore we have to put at least 512
;bytes at the end of the g-code so that the file is not yet finished by the
;time that the motion planner gets flushed. With firmware version _3.3 this
;should be fixed, so this comment wouldn't be necessary any more. Now we have
;to pad this text to make precisely 512 bytes.

Bestand:Hsnmgnlaser.tar.gz

2019-04-08T19:45:52Z

SA007:

Projects:40W Lasercutter

2019-04-08T19:36:26Z

SA007:

== Getting started ==

First you need some tools to work with the lasercutter.
For starters you need a drawing program like [https://inkscape.org/ Inkscape] that is capable of making 2d vector drawings.

The you need [https://visicut.org/ Visicut] as a program to hook the 2 together.

Visicut has a plugin for inkscape so you can press 'Extensions '''>''' Lasercut path '''>''' Open in VisiCut' from Inkscape :)

For Visicut you need a definition file (xml) that contains the laser settings, you can get a rudimentary one here: [[Bestand:hsnmgnlaser.tar.gz]]

Import this using Options -> Lasercutters, it is a good idea to change the job prefix under edit -> job to your own name so you can find your files again.

== Basic operation ==
* Turn on the machine AND the air assist compressor thingy.
* Send the file using visicut (i'm not including an entire inkscape/visicut tutorial, plenty online to be found).
* Turn on the power to the tube with the 'Engraving On' button, this only works if all lids are closed.
* Using the Black&Blue dial (by pressing and rotating it) navigate to Play -> sd/ -> <your prefix><number>.gcode.
* The program now starts.

Using the emergency stop you can turn off the entire machine if something bad happens.

== Troubleshooting ==
* Laser power very low/none, check if the 'Power regulator' isn't turned way down, you can check with the 'Test' button.

== Materials it can cut/engrave? ==
* Wood -> most types it can cut and engrave, up to about 5mm.
* Plastics PLA/ABS/PET/PS are fine, PVC is a REALLY bad idea, cut and engrave up to 5mm.
* Cardboard/Paper -> see wood, paper can catch fire, which is a lot better with airassist.
* Metals -> No, but engraving is possible by removing a coating of $material such as paint.
* Cookies -> Engrave Work fine, still eatable afterwards.
* Chocolate/Sugary stuff engraves fine.
* Wet foods -> No.

== History: ==

== Why is there suddenly a lasercutter ==
It was donated to hackerspace nijmegen by hack42 during the [https://hack42.nl/wiki/Hack42_on_Tour Hack42 on Tour] weekend.

Short backstory: A #42 member saved it from the dumpster, it was ''in working order'' but since this is a crappy old machine it was replaced.

Hack42 already has a very similar machine, rebuild into a nice useable one and no real intrest in haveing two, so it was donated.

== So what does ''in working order'' mean? ==
That it should work as designed, but the design is horrid.

== What todo do with it ==
In my (SA007) opinion the steps should be.

* Verify the ''in working order'' claim
** Make sure the 230V wiring is usable, i've seen it with a negligible amount or actual metal in the wires. (Done 12-11-18, wires aren't great but useable)
** Connect the ground to the ground terminal of the power connector. (Done 12-11-18, casing and HV supply are now grounded via the power connector)
** Make the cooling system work (pump, bucket, hoses, see if there are leaks and if the flow is usable). (In progress, there seems to be a blocked pipe) (13-11-18, pipe is unblocked, flow seems good, there is now some cleaner in it to remove crud) (3-12-18, Cooling 'done' for now, has 4L cooling circulating nicely)
** Power the laser up, put some wood under the head and hit test, it should burn the wood, if not, check the alignment. (Very short test done, tube isn't broken, yay)
** Optional: Actually hook it up to an old windows pc and install the supplies software. (Board removed, no longer an option).
* Add loads of safety's, there aren't any...
** Switches on the covers, so it can't turn on the high voltage/laser if a cover is opened.
** Emergency stop switch. (SA007: Done 19-11-18)
** Temperature/water flow sensors are also nice, also ordered.
** Covers for the bit holes in the casing (most are needed for alignment, but can have removable covers. (13-11-2018 In progress using ducktape'd alufoil, laser can't cut trough the alufoil) (Done 3-12-18, all relevant slots have been covered)
** Covers for the slits and gaps in the main/all covers (you should not be able to directly look into the laser bed, with exception of the window. (Done 3-12-18, all relevant slots have been covered)
* Replace electronics
** There are several options for the main electronics, such as smoothieboard (or clone), laos and several 3d-printerboard are usable as well. The one at hack42 is a laos one, from experience it is 'really meh' so I would pick something else (mks / smoothieboard clone and wires ordered by themba paid by crowdfunding).
** Replace a lot of the wiring. (12-11-2018 Not as much needed as expected)
** Probably upgrade the endstops (more range, better accuracy)
** Add display? (Also ordered, not crowdfunded)
** Add timer? (laser tubes have a limited life, you want to keep track and/or make people pay for usage)
* Upgrade cooling
** Keeping the tube cool is important.
** A 'closed' system is great, a chiller even better.
** Temps need to be below 30 celcius, 18 is best for long life.
* Upgrade ventilation
** The exhaust needs to go outside (maybe via the ventilation slits) (Outside airvent is installed)
** The fan sucks air from the wrong place (alignment sucks) (Alignment is improved)
** Maybe a (carbon)filter
* Added features
** Air assist is really awesome, cutting results greatly improve, you can build a cheap one from a fridge compressor.
** Usable switchable light, 25W bulb is useless.
** Switched/monitored cooling/ventilation, so you don't run without it.
** Honeycomb bed
** Is someone gets creative, a focus adjustment would be nice.
* Calibrate/adjust the machine
** Align/clean the mirrors.
** Calibrate the axes, more accuracy.
** More to come.

== Sources for information ==
We have a SF40 laser, very similar to K40, which has been modified extensively.

Ask SA007 on IRC/Mail/Whatever

== Costs? ==
It will probably be around 200 euro to get parts such as replacement electronics, safety gear etc.

Current costs:

{| class="wikitable"
! Item
! Price (Paid by)
|-
| Lasercutter
| Free
|-
| [https://www.aliexpress.com/item/3D-Printer-Parts-Controller-Board-MKS-SBASE-V1-3-32-bit-Open-Source-Platform-Smoothieboard-Compatible/32853515280.html Electronics]
| 40,34 (Themba)
|-
| [https://www.aliexpress.com/item/3d-printing-touch-screen-RepRap-controller-panel-MKS-TFT28-V1-2-display-color-TFT-support-WIFI/32808421021.html Display]
| 24,43 (Themba)
|-
| EStop
| Free
|-
| Shielding materials
| 11,50 (SA007)
|-
| [https://www.groku.de/fileadmin/web/pdf/EZE5600_en.pdf Bucket]
| Free
|-
| Subtotal
| 76,27
|-
| Coolant
| 8,70 (SA007)
|-
| Exhaust hose
| 6,95 (SA007)
|-
| Wiring/plugs
| 5ish (SA007)
|}

Currently funded: 50 euro.

There is a donation box on top of the lasercutter.

== Looking for materials: ==
* Fridge compressor (anyone an old fridge thats going to be dumped?)
* Watercooling items (radiator+fans, hoses, pump etc)

== Small tasks list: ==
* Add/wire interlock switches.
* Extend Y motor wire
* Change plugs on endstops.
* Find / connect PWM signal.
* Hook pcb up to power.
* Mount temperature sensor somewhere properly to measure coolant temp.
* Fix/connect led strip and find/mount a psu for them.

== More specs? ==
It is '40W' laser tube, more realisticly it is 30-35W it runs on really high voltage (~2kV).

It is a CO2 laser, they run at 10600nm, which is really really infrared.

Event:Workshop Series (hopefully) 'What does it do'

2019-02-07T22:09:07Z

SA007:

'''By:''' SA007

'''When:''' Date: '''Monday February 10th, 2019''' Time: '''20:00'''

'''Adience:'''
Anyone who is interested

'''Topic:''' I'm doing a series of 'workshoppy' lectures about interesting tech.

Length is somewhere between 30minutes and an hour.

Idea is to take 'some' device and show/dismantle/analyse/reuse it.

== Previous installments ==
{| class="wikitable"
! Date
! About
|-
| Nov 27 2018
| GFI / RCCB / Aardlekschakelaars.
|-
| Feb 10 2019
| Electricity meters.
|}

Idea's for this series: ping me.

HSNWiki:Migration from Gitwiki

2019-02-06T13:03:08Z

SA007: /* Hostname + SSL */

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. [[#Discussion group e-mail|See the e-mail to the list for details.]]

Use ✓ for "done", ❌ for "not done".

= Settings =

* ✓ MediaWiki Installation
* ✓ Allow account creation
* ❌ [[HSNWiki:Proposed Editors|Add a nice WYSIWYG editor for pages]]
** The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
* ❌ [[HSNWiki:Account Approval|Require manual approval for making accounts]]
* ❌ Allow sending e-mail from wiki
* ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
* ✓ [[MediaWiki:Sidebar|Add Github etc. links to the sidebar]]
* ❌ [[HSNWiki:Proposed Extensions|Other extensions we'd like to see]]
* ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

== Settings, if possible? ==

* ❌ How to make some pages public, some pages private?
* ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
** "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
* ❌ Can we show edit history of pages only to logged-in accounts?
* ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
* ❌ Make a calendar/agenda containing all events on the wiki
* ❌ Make an auto-generated index of all pages on the home page?

== Theming ==
* ❌ @Joep to find some nice mediawiki themes to base our theme upon.
* ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
* ❌ @Sjors will give them access to the current installation to experiment with how it looks.
* ❌ @Michiel to send graphics to @Joep and @Robert.

== Backups ==
* ❌ @Sjors to make local backups on the VM for now.

= Page migration =

All pages to migrate:

* ✓ <del>README.md</del> (empty page)
* ✓ [[Budgets|docs/budgets.md]]
* ✓ [[Hackerspace_Nijmegen_(working_title)_zoekt_deelnemers!|docs/callforparticipation.md]]
* ✓ [[Statuten|docs/statuten.md]]
* ✓ <del>docs/knittingmachine.md</del> (added into [[Projects:Knitting Machine to laptop]])
* ✓ [[ProjectOne:Planning|docs/projects/ProjectOne/planning.md]]
* ✓ [[ProjectOne:Mini_RC_Hovercrafts|docs/projects/ProjectOne/MiniRCHovercrafts.md]]
* ✓ [[ProjectOne:Project_Ideas_that_are_too_big_to_do_on_my_own|docs/projects/ProjectOne/proposals.md]]
* ✓ [[ProjectOne:Project_One_Main_Page|docs/projects/ProjectOne/index.md]]
* ✓ [[Projects:40W_Lasercutter|docs/projects/lasercutter.md]]
* ✓ [[Projects:Knitting Machine to laptop|docs/projects/knittingmachine.md]]
* ✓ [[Projects:Anonycaster|docs/projects/anonycaster.md]]
* ✓ [[Projects:Music_at_HSN|docs/projects/musicplayer.md]]
* ✓ [[About Hackerspace Nijmegen|docs/contact.md]]
* ✓ [[Minutes_2018-03-27|docs/minutes/2018-2.md]]
* ✓ [[Minutes_2018-03-20|docs/minutes/2018-1.md]]
* ✓ [[Main page|docs/index.md]]
* ✓ [[Contributing|docs/contributing.md]]
* ✓ [[Wishlist for the new space|docs/wishlist.md]]
* ✓ [[Event:CTF night|docs/events/ctfnight.md]]
* ✓ [[Event:Workshop_Friday_28th_of_September:_Kicad|docs/events/workshops/kicad101.md]]
* ✓ [[Event:Workshop Series (hopefully) 'What does it do'|docs/events/workshops/whatdoesitdo.md]]
* ✓ [[Event:November_1st:_Invited_speaker:_Property_testing|docs/events/workshops/propertytesting.md]]
* ✓ [[Event:Smallish_demo_about_signal_integrity.|docs/events/workshops/signal_intergrity.md]]
* ✓ [[Event:Getting_started_with_the_Ultimaker_2_3d-Printer|docs/events/workshops/3dprintergettingstarted.md]]
* ✓ [[Event:Workshop_Friday_7th_of_September:_Milling_printed_circuit_board_using_cheap_chinese_CNC_mill|docs/events/workshops/pcbmilling.md]]
* ✓ [[Event:Hack42_On_Tour_is_visiting|docs/events/hack42_on_tour.md]]
* ✓ [[Event:Movie night|docs/events/movienight.md]]
* ✓ [[Event:board_game_night|docs/events/boardgamenight.md]]
* ✓ [[Event:Christmas_dinner|docs/events/christmas_dinner.md]]
* ✓ [[Event:Open Day 2018|docs/events/openday2018.md]]
* ✓ [[Notes on opening the new space|docs/spaceopening.md]]
* ✓ [[About Hackerspace Nijmegen|docs/about.md]]
* ✓ [[Event:Opening party|docs/openingparty.md]]
* ✓ [[Naming|docs/naming.md]]
* ✓ <del>docs/empty.md</del> (empty page)
* ✓ [[Milling PCB's with 3018 Chinese Desktop CNC|docs/pcbmilling.md]]

= Hostname + SSL =

* ✓ Old wiki is down.
* ✓ Link wiki.hackerspacenijmegen.nl to this wiki.
* ✓ Make SSL certificate.

= Discussion group e-mail =

<nowiki>Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.</nowiki>

Hackerspace Nijmegen

2019-02-06T12:32:49Z

SA007:

=== Welcome to the new hackerspace nijmegen wiki ===

Currently all the content has been migrated to mediawiki, but we aren't there yet.

[[HSNWiki:Migration_from_Gitwiki|Click here to find out how far we are!]]

== How to contribute to this wiki ==

* [[Speciaal:GebruikerAanmaken|Request an account]]
* Request approval from one of the wiki admins
* Edit away!

Don't forget: '''it's a wiki'''. Improve things! We maintain regular meetings about 'controversial topics', which you can join if you want, and we prefer you report changes of main pages / settings in #hsnwiki on ircnet (same network as #hsnijmegen) so we can keep each other up to date.

== About MediaWiki ==

Check the [https://meta.wikimedia.org/wiki/Special:MyLanguage/Help:Contents manual] for information on the usage of MediaWiki.

HSNWiki:Migration from Gitwiki

2019-02-06T11:41:41Z

SA007: /* Page migration */

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. [[#Discussion group e-mail|See the e-mail to the list for details.]]

Use ✓ for "done", ❌ for "not done".

= Settings =

* ✓ MediaWiki Installation
* ✓ Allow account creation
* ❌ [[HSNWiki:Proposed Editors|Add a nice WYSIWYG editor for pages]]
** The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
* ❌ [[HSNWiki:Account Approval|Require manual approval for making accounts]]
* ❌ Allow sending e-mail from wiki
* ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
* ✓ [[MediaWiki:Sidebar|Add Github etc. links to the sidebar]]
* ❌ [[HSNWiki:Proposed Extensions|Other extensions we'd like to see]]
* ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

== Settings, if possible? ==

* ❌ How to make some pages public, some pages private?
* ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
** "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
* ❌ Can we show edit history of pages only to logged-in accounts?
* ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
* ❌ Make a calendar/agenda containing all events on the wiki
* ❌ Make an auto-generated index of all pages on the home page?

== Theming ==
* ❌ @Joep to find some nice mediawiki themes to base our theme upon.
* ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
* ❌ @Sjors will give them access to the current installation to experiment with how it looks.
* ❌ @Michiel to send graphics to @Joep and @Robert.

== Backups ==
* ❌ @Sjors to make local backups on the VM for now.

= Page migration =

All pages to migrate:

* ✓ <del>README.md</del> (empty page)
* ✓ [[Budgets|docs/budgets.md]]
* ✓ [[Hackerspace_Nijmegen_(working_title)_zoekt_deelnemers!|docs/callforparticipation.md]]
* ✓ [[Statuten|docs/statuten.md]]
* ✓ <del>docs/knittingmachine.md</del> (added into [[Projects:Knitting Machine to laptop]])
* ✓ [[ProjectOne:Planning|docs/projects/ProjectOne/planning.md]]
* ✓ [[ProjectOne:Mini_RC_Hovercrafts|docs/projects/ProjectOne/MiniRCHovercrafts.md]]
* ✓ [[ProjectOne:Project_Ideas_that_are_too_big_to_do_on_my_own|docs/projects/ProjectOne/proposals.md]]
* ✓ [[ProjectOne:Project_One_Main_Page|docs/projects/ProjectOne/index.md]]
* ✓ [[Projects:40W_Lasercutter|docs/projects/lasercutter.md]]
* ✓ [[Projects:Knitting Machine to laptop|docs/projects/knittingmachine.md]]
* ✓ [[Projects:Anonycaster|docs/projects/anonycaster.md]]
* ✓ [[Projects:Music_at_HSN|docs/projects/musicplayer.md]]
* ✓ [[About Hackerspace Nijmegen|docs/contact.md]]
* ✓ [[Minutes_2018-03-27|docs/minutes/2018-2.md]]
* ✓ [[Minutes_2018-03-20|docs/minutes/2018-1.md]]
* ✓ [[Main page|docs/index.md]]
* ✓ [[Contributing|docs/contributing.md]]
* ✓ [[Wishlist for the new space|docs/wishlist.md]]
* ✓ [[Event:CTF night|docs/events/ctfnight.md]]
* ✓ [[Event:Workshop_Friday_28th_of_September:_Kicad|docs/events/workshops/kicad101.md]]
* ✓ [[Event:Workshop Series (hopefully) 'What does it do'|docs/events/workshops/whatdoesitdo.md]]
* ✓ [[Event:November_1st:_Invited_speaker:_Property_testing|docs/events/workshops/propertytesting.md]]
* ✓ [[Event:Smallish_demo_about_signal_integrity.|docs/events/workshops/signal_intergrity.md]]
* ✓ [[Event:Getting_started_with_the_Ultimaker_2_3d-Printer|docs/events/workshops/3dprintergettingstarted.md]]
* ✓ [[Event:Workshop_Friday_7th_of_September:_Milling_printed_circuit_board_using_cheap_chinese_CNC_mill|docs/events/workshops/pcbmilling.md]]
* ✓ [[Event:Hack42_On_Tour_is_visiting|docs/events/hack42_on_tour.md]]
* ✓ [[Event:Movie night|docs/events/movienight.md]]
* ✓ [[Event:board_game_night|docs/events/boardgamenight.md]]
* ✓ [[Event:Christmas_dinner|docs/events/christmas_dinner.md]]
* ✓ [[Event:Open Day 2018|docs/events/openday2018.md]]
* ✓ [[Notes on opening the new space|docs/spaceopening.md]]
* ✓ [[About Hackerspace Nijmegen|docs/about.md]]
* ✓ [[Event:Opening party|docs/openingparty.md]]
* ✓ [[Naming|docs/naming.md]]
* ✓ <del>docs/empty.md</del> (empty page)
* ✓ [[Milling PCB's with 3018 Chinese Desktop CNC|docs/pcbmilling.md]]

= Hostname + SSL =

* ✓ Old wiki is down.
* ❌ Link wiki.hackerspacenijmegen.nl to this wiki.
* ❌ Make SSL certificate.

= Discussion group e-mail =

<nowiki>Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.</nowiki>

HSNWiki:Migration from Gitwiki

2019-02-06T11:39:44Z

SA007: /* Page migration */

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. [[#Discussion group e-mail|See the e-mail to the list for details.]]

Use ✓ for "done", ❌ for "not done".

= Settings =

* ✓ MediaWiki Installation
* ✓ Allow account creation
* ❌ [[HSNWiki:Proposed Editors|Add a nice WYSIWYG editor for pages]]
** The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
* ❌ [[HSNWiki:Account Approval|Require manual approval for making accounts]]
* ❌ Allow sending e-mail from wiki
* ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
* ✓ [[MediaWiki:Sidebar|Add Github etc. links to the sidebar]]
* ❌ [[HSNWiki:Proposed Extensions|Other extensions we'd like to see]]
* ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

== Settings, if possible? ==

* ❌ How to make some pages public, some pages private?
* ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
** "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
* ❌ Can we show edit history of pages only to logged-in accounts?
* ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
* ❌ Make a calendar/agenda containing all events on the wiki
* ❌ Make an auto-generated index of all pages on the home page?

== Theming ==
* ❌ @Joep to find some nice mediawiki themes to base our theme upon.
* ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
* ❌ @Sjors will give them access to the current installation to experiment with how it looks.
* ❌ @Michiel to send graphics to @Joep and @Robert.

== Backups ==
* ❌ @Sjors to make local backups on the VM for now.

= Page migration =

All pages to migrate:

* ✓ <del>README.md</del> (empty page)
* ✓ [[Budgets|docs/budgets.md]]
* ✓ [[Hackerspace_Nijmegen_(working_title)_zoekt_deelnemers!|docs/callforparticipation.md]]
* ✓ [[Statuten|docs/statuten.md]]
* ✓ <del>docs/knittingmachine.md</del> (added into [[Projects:Knitting Machine to laptop]])
* ❌ [[ProjectOne:Planning|docs/projects/ProjectOne/planning.md]]
* ❌ [[ProjectOne:Mini_RC_Hovercrafts|docs/projects/ProjectOne/MiniRCHovercrafts.md]]
* ❌ [[ProjectOne:Project_Ideas_that_are_too_big_to_do_on_my_own|docs/projects/ProjectOne/proposals.md]]
* ❌ [[ProjectOne:Project_One_Main_Page|docs/projects/ProjectOne/index.md]]
* ❌ [[Projects:40W_Lasercutter|docs/projects/lasercutter.md]]
* ✓ [[Projects:Knitting Machine to laptop|docs/projects/knittingmachine.md]]
* ❌ [[Projects:Anonycaster|docs/projects/anonycaster.md]]
* ❌ [[Projects:Music_at_HSN|docs/projects/musicplayer.md]]
* ✓ [[About Hackerspace Nijmegen|docs/contact.md]]
* ✓ [[Minutes_2018-03-27|docs/minutes/2018-2.md]]
* ✓ [[Minutes_2018-03-20|docs/minutes/2018-1.md]]
* ✓ [[Main page|docs/index.md]]
* ✓ [[Contributing|docs/contributing.md]]
* ✓ [[Wishlist for the new space|docs/wishlist.md]]
* ✓ [[Event:CTF night|docs/events/ctfnight.md]]
* ❌ [[Event:Workshop_Friday_28th_of_September:_Kicad|docs/events/workshops/kicad101.md]]
* ✓ [[Event:Workshop Series (hopefully) 'What does it do'|docs/events/workshops/whatdoesitdo.md]]
* ❌ [[Event:November_1st:_Invited_speaker:_Property_testing|docs/events/workshops/propertytesting.md]]
* ❌ [[Event:Smallish_demo_about_signal_integrity.|docs/events/workshops/signal_intergrity.md]]
* ❌ [[Event:Getting_started_with_the_Ultimaker_2_3d-Printer|docs/events/workshops/3dprintergettingstarted.md]]
* ❌ [[Event:Workshop_Friday_7th_of_September:_Milling_printed_circuit_board_using_cheap_chinese_CNC_mill|docs/events/workshops/pcbmilling.md]]
* ✓ [[Event:Hack42_On_Tour_is_visiting|docs/events/hack42_on_tour.md]]
* ✓ [[Event:Movie night|docs/events/movienight.md]]
* ✓ [[Event:board_game_night|docs/events/boardgamenight.md]]
* ✓ [[Event:Christmas_dinner|docs/events/christmas_dinner.md]]
* ✓ [[Event:Open Day 2018|docs/events/openday2018.md]]
* ✓ [[Notes on opening the new space|docs/spaceopening.md]]
* ✓ [[About Hackerspace Nijmegen|docs/about.md]]
* ✓ [[Event:Opening party|docs/openingparty.md]]
* ✓ [[Naming|docs/naming.md]]
* ✓ <del>docs/empty.md</del> (empty page)
* ✓ [[Milling PCB's with 3018 Chinese Desktop CNC|docs/pcbmilling.md]]

= Hostname + SSL =

* ✓ Old wiki is down.
* ❌ Link wiki.hackerspacenijmegen.nl to this wiki.
* ❌ Make SSL certificate.

= Discussion group e-mail =

<nowiki>Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.</nowiki>

Projects:Music at HSN

2019-02-06T11:39:24Z

SA007: Copied from old wiki - last change Aug 14, 2018

We have a Music Player (MPD) at Hackerspace Nijmegen. If you'd like some music,
you can turn it on.

To use the commands listed on this page, you need to be connected to the HS-NMGN
wifi network or be otherwise connected to the HSN network.

Questions? Ask Sjors!

== Starting it ==

Find out MPD's status by running `mpc -h barometer status`. The output may look
something like:

Maduk - Liquicity Yearmix 2016 (Mixed By Maduk)
[playing] #1/1 2:37/64:15 (4%)
volume: 77% repeat: off random: off single: off consume: on

Play state is on the second line. If it says 'playing', and you don't hear
anything, check audio settings on `barometer@bar-o-meter` :-(

If it says 'paused' or 'stopped', run `mpc -h barometer play`. If that doesn't
help, restart it.

If it's not running, or broken in some way, you can `ssh barometer@bar-o-meter`
and run `./startmpd.sh`. That'll stop it if it's running, then restart it. It
starts mpd, but also ashuffle, a tool to keep the playlist always filled.

== Stopping it ==

Done with the music? Last person to leave the space? `mpc -h barometer pause`.

== Adding your own music ==

`barometer` is running an NFS mount. Try:

sudo mkdir -p /media/music
sudo mount -t nfs barometer:/media/music /media/music

Make your own directory on it, and add your stuff! Please don't touch other
people's stuff, and don't download any music from it, get it somewhere legally!

Currently there's only about 128 GB of space, so don't upload your entire music
database; if it fills up further, I'll probably add a disk or something.

== Queueing your own music ==

Take the path to your file, then run:

mpc -h barometer add 'yourname/Path To Your Music/Some Artist - His Track (Someones Remix).mp3'

== TODO ==

Not in any particular order:

* It sometimes doesn't start with the correct audio interface. Why?
* Nicer speakers
* Automatic `mpc pause` when the space state is switched to closed, and *perhaps* "mpc play" when switched to open
* Revbank plugin for mpd!
* A (matrix LED?) screen that displays what song is currently playing, perhaps some nice animations
* A Something like https://github.com/notandy/ympd on a screen for people who don't care for CLIs
* A fair queueing system
* Force consume mode on (perhaps by patching mpd? Or just a cronjob every minute)

HSNWiki:Migration from Gitwiki

2019-02-06T11:34:26Z

SA007: /* Page migration */

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. [[#Discussion group e-mail|See the e-mail to the list for details.]]

Use ✓ for "done", ❌ for "not done".

= Settings =

* ✓ MediaWiki Installation
* ✓ Allow account creation
* ❌ [[HSNWiki:Proposed Editors|Add a nice WYSIWYG editor for pages]]
** The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
* ❌ [[HSNWiki:Account Approval|Require manual approval for making accounts]]
* ❌ Allow sending e-mail from wiki
* ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
* ✓ [[MediaWiki:Sidebar|Add Github etc. links to the sidebar]]
* ❌ [[HSNWiki:Proposed Extensions|Other extensions we'd like to see]]
* ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

== Settings, if possible? ==

* ❌ How to make some pages public, some pages private?
* ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
** "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
* ❌ Can we show edit history of pages only to logged-in accounts?
* ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
* ❌ Make a calendar/agenda containing all events on the wiki
* ❌ Make an auto-generated index of all pages on the home page?

== Theming ==
* ❌ @Joep to find some nice mediawiki themes to base our theme upon.
* ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
* ❌ @Sjors will give them access to the current installation to experiment with how it looks.
* ❌ @Michiel to send graphics to @Joep and @Robert.

== Backups ==
* ❌ @Sjors to make local backups on the VM for now.

= Page migration =

All pages to migrate:

* ✓ <del>README.md</del> (empty page)
* ✓ [[Budgets|docs/budgets.md]]
* ✓ [[Hackerspace_Nijmegen_(working_title)_zoekt_deelnemers!|docs/callforparticipation.md]]
* ✓ [[Statuten|docs/statuten.md]]
* ✓ <del>docs/knittingmachine.md</del> (added into [[Projects:Knitting Machine to laptop]])
* ❌ [[ProjectOne:Planning|docs/projects/ProjectOne/planning.md]]
* ❌ [[ProjectOne:Mini_RC_Hovercrafts|docs/projects/ProjectOne/MiniRCHovercrafts.md]]
* ❌ [[ProjectOne:Project_Ideas_that_are_too_big_to_do_on_my_own|docs/projects/ProjectOne/proposals.md]]
* ❌ [[ProjectOne:Project_One_Main_Page|docs/projects/ProjectOne/index.md]]
* ❌ [[Projects:40W_Lasercutter|docs/projects/lasercutter.md]]
* ✓ [[Projects:Knitting Machine to laptop|docs/projects/knittingmachine.md]]
* ❌ [[Projects:Anonycaster|docs/projects/anonycaster.md]]
* ❌ docs/projects/musicplayer.md
* ✓ [[About Hackerspace Nijmegen|docs/contact.md]]
* ✓ [[Minutes_2018-03-27|docs/minutes/2018-2.md]]
* ✓ [[Minutes_2018-03-20|docs/minutes/2018-1.md]]
* ✓ [[Main page|docs/index.md]]
* ✓ [[Contributing|docs/contributing.md]]
* ✓ [[Wishlist for the new space|docs/wishlist.md]]
* ✓ [[Event:CTF night|docs/events/ctfnight.md]]
* ❌ [[Event:Workshop_Friday_28th_of_September:_Kicad|docs/events/workshops/kicad101.md]]
* ✓ [[Event:Workshop Series (hopefully) 'What does it do'|docs/events/workshops/whatdoesitdo.md]]
* ❌ [[Event:November_1st:_Invited_speaker:_Property_testing|docs/events/workshops/propertytesting.md]]
* ❌ [[Event:Smallish_demo_about_signal_integrity.|docs/events/workshops/signal_intergrity.md]]
* ❌ [[Event:Getting_started_with_the_Ultimaker_2_3d-Printer|docs/events/workshops/3dprintergettingstarted.md]]
* ❌ [[Event:Workshop_Friday_7th_of_September:_Milling_printed_circuit_board_using_cheap_chinese_CNC_mill|docs/events/workshops/pcbmilling.md]]
* ✓ [[Event:Hack42_On_Tour_is_visiting|docs/events/hack42_on_tour.md]]
* ✓ [[Event:Movie night|docs/events/movienight.md]]
* ✓ [[Event:board_game_night|docs/events/boardgamenight.md]]
* ✓ [[Event:Christmas_dinner|docs/events/christmas_dinner.md]]
* ✓ [[Event:Open Day 2018|docs/events/openday2018.md]]
* ✓ [[Notes on opening the new space|docs/spaceopening.md]]
* ✓ [[About Hackerspace Nijmegen|docs/about.md]]
* ✓ [[Event:Opening party|docs/openingparty.md]]
* ✓ [[Naming|docs/naming.md]]
* ✓ <del>docs/empty.md</del> (empty page)
* ✓ [[Milling PCB's with 3018 Chinese Desktop CNC|docs/pcbmilling.md]]

= Hostname + SSL =

* ✓ Old wiki is down.
* ❌ Link wiki.hackerspacenijmegen.nl to this wiki.
* ❌ Make SSL certificate.

= Discussion group e-mail =

<nowiki>Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.</nowiki>

Projects:40W Lasercutter

2019-02-06T11:34:04Z

SA007: Copied from old wiki - last change Dec 7, 2018

== Why is there suddenly a lasercutter ==
It was donated to hackerspace nijmegen by hack42 during the [https://hack42.nl/wiki/Hack42_on_Tour Hack42 on Tour] weekend.

Short backstory: A #42 member saved it from the dumpster, it was ''in working order'' but since this is a crappy old machine it was replaced.

Hack42 already has a very similar machine, rebuild into a nice useable one and no real intrest in haveing two, so it was donated.

== So what does ''in working order'' mean? ==
That it should work as designed, but the design is horrid.

== What todo do with it ==
In my (SA007) opinion the steps should be.

* Verify the ''in working order'' claim
** Make sure the 230V wiring is usable, i've seen it with a negligible amount or actual metal in the wires. (Done 12-11-18, wires aren't great but useable)
** Connect the ground to the ground terminal of the power connector. (Done 12-11-18, casing and HV supply are now grounded via the power connector)
** Make the cooling system work (pump, bucket, hoses, see if there are leaks and if the flow is usable). (In progress, there seems to be a blocked pipe) (13-11-18, pipe is unblocked, flow seems good, there is now some cleaner in it to remove crud) (3-12-18, Cooling 'done' for now, has 4L cooling circulating nicely)
** Power the laser up, put some wood under the head and hit test, it should burn the wood, if not, check the alignment. (Very short test done, tube isn't broken, yay)
** Optional: Actually hook it up to an old windows pc and install the supplies software. (Board removed, no longer an option).
* Add loads of safety's, there aren't any...
** Switches on the covers, so it can't turn on the high voltage/laser if a cover is opened.
** Emergency stop switch. (SA007: Done 19-11-18)
** Temperature/water flow sensors are also nice, also ordered.
** Covers for the bit holes in the casing (most are needed for alignment, but can have removable covers. (13-11-2018 In progress using ducktape'd alufoil, laser can't cut trough the alufoil) (Done 3-12-18, all relevant slots have been covered)
** Covers for the slits and gaps in the main/all covers (you should not be able to directly look into the laser bed, with exception of the window. (Done 3-12-18, all relevant slots have been covered)
* Replace electronics
** There are several options for the main electronics, such as smoothieboard (or clone), laos and several 3d-printerboard are usable as well. The one at hack42 is a laos one, from experience it is 'really meh' so I would pick something else (mks / smoothieboard clone and wires ordered by themba paid by crowdfunding).
** Replace a lot of the wiring. (12-11-2018 Not as much needed as expected)
** Probably upgrade the endstops (more range, better accuracy)
** Add display? (Also ordered, not crowdfunded)
** Add timer? (laser tubes have a limited life, you want to keep track and/or make people pay for usage)
* Upgrade cooling
** Keeping the tube cool is important.
** A 'closed' system is great, a chiller even better.
** Temps need to be below 30 celcius, 18 is best for long life.
* Upgrade ventilation
** The exhaust needs to go outside (maybe via the ventilation slits) (Outside airvent is installed)
** The fan sucks air from the wrong place (alignment sucks) (Alignment is improved)
** Maybe a (carbon)filter
* Added features
** Air assist is really awesome, cutting results greatly improve, you can build a cheap one from a fridge compressor.
** Usable switchable light, 25W bulb is useless.
** Switched/monitored cooling/ventilation, so you don't run without it.
** Honeycomb bed
** Is someone gets creative, a focus adjustment would be nice.
* Calibrate/adjust the machine
** Align/clean the mirrors.
** Calibrate the axes, more accuracy.
** More to come.

== Sources for information ==
We have a SF40 laser, very similar to K40, which has been modified extensively.

Ask SA007 on IRC/Mail/Whatever

== Costs? ==
It will probably be around 200 euro to get parts such as replacement electronics, safety gear etc.

Current costs:

{| class="wikitable"
! Item
! Price (Paid by)
|-
| Lasercutter
| Free
|-
| [https://www.aliexpress.com/item/3D-Printer-Parts-Controller-Board-MKS-SBASE-V1-3-32-bit-Open-Source-Platform-Smoothieboard-Compatible/32853515280.html Electronics]
| 40,34 (Themba)
|-
| [https://www.aliexpress.com/item/3d-printing-touch-screen-RepRap-controller-panel-MKS-TFT28-V1-2-display-color-TFT-support-WIFI/32808421021.html Display]
| 24,43 (Themba)
|-
| EStop
| Free
|-
| Shielding materials
| 11,50 (SA007)
|-
| [https://www.groku.de/fileadmin/web/pdf/EZE5600_en.pdf Bucket]
| Free
|-
| Subtotal
| 76,27
|-
| Coolant
| 8,70 (SA007)
|-
| Exhaust hose
| 6,95 (SA007)
|-
| Wiring/plugs
| 5ish (SA007)
|}

Currently funded: 50 euro.

There is a donation box on top of the lasercutter.

== Looking for materials: ==
* Fridge compressor (anyone an old fridge thats going to be dumped?)
* Watercooling items (radiator+fans, hoses, pump etc)

== Small tasks list: ==
* Add/wire interlock switches.
* Extend Y motor wire
* Change plugs on endstops.
* Find / connect PWM signal.
* Hook pcb up to power.
* Mount temperature sensor somewhere properly to measure coolant temp.
* Fix/connect led strip and find/mount a psu for them.

== More specs? ==
It is '40W' laser tube, more realisticly it is 30-35W it runs on really high voltage (~2kV).

It is a CO2 laser, they run at 10600nm, which is really really infrared.

== Materials it can cut/engrave? ==
* Wood -> most types it can cut and engrave, up to about 5mm.
* Plastics PLA/ABS/PET/PS are fine, PVC is a REALLY bad idea, cut and engrave up to 5mm.
* Cardboard/Paper -> see wood, paper can catch fire, which is a lot better with airassist.
* Metals -> No, but engraving is possible by removing a coating of $material such as paint.
* Cookies -> Engrave Work fine, still eatable afterwards.
* Chocolate/Sugary stuff engraves fine.
* Wet foods -> No.

HSNWiki:Migration from Gitwiki

2019-02-06T11:23:35Z

SA007: /* Page migration */

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. [[#Discussion group e-mail|See the e-mail to the list for details.]]

Use ✓ for "done", ❌ for "not done".

= Settings =

* ✓ MediaWiki Installation
* ✓ Allow account creation
* ❌ [[HSNWiki:Proposed Editors|Add a nice WYSIWYG editor for pages]]
** The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
* ❌ [[HSNWiki:Account Approval|Require manual approval for making accounts]]
* ❌ Allow sending e-mail from wiki
* ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
* ✓ [[MediaWiki:Sidebar|Add Github etc. links to the sidebar]]
* ❌ [[HSNWiki:Proposed Extensions|Other extensions we'd like to see]]
* ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

== Settings, if possible? ==

* ❌ How to make some pages public, some pages private?
* ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
** "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
* ❌ Can we show edit history of pages only to logged-in accounts?
* ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
* ❌ Make a calendar/agenda containing all events on the wiki
* ❌ Make an auto-generated index of all pages on the home page?

== Theming ==
* ❌ @Joep to find some nice mediawiki themes to base our theme upon.
* ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
* ❌ @Sjors will give them access to the current installation to experiment with how it looks.
* ❌ @Michiel to send graphics to @Joep and @Robert.

== Backups ==
* ❌ @Sjors to make local backups on the VM for now.

= Page migration =

All pages to migrate:

* ✓ <del>README.md</del> (empty page)
* ✓ [[Budgets|docs/budgets.md]]
* ✓ [[Hackerspace_Nijmegen_(working_title)_zoekt_deelnemers!|docs/callforparticipation.md]]
* ✓ [[Statuten|docs/statuten.md]]
* ✓ <del>docs/knittingmachine.md</del> (added into [[Projects:Knitting Machine to laptop]])
* ❌ [[ProjectOne:Planning|docs/projects/ProjectOne/planning.md]]
* ❌ [[ProjectOne:Mini_RC_Hovercrafts|docs/projects/ProjectOne/MiniRCHovercrafts.md]]
* ❌ [[ProjectOne:Project_Ideas_that_are_too_big_to_do_on_my_own|docs/projects/ProjectOne/proposals.md]]
* ❌ [[ProjectOne:Project_One_Main_Page|docs/projects/ProjectOne/index.md]]
* ❌ docs/projects/lasercutter.md
* ✓ [[Projects:Knitting Machine to laptop|docs/projects/knittingmachine.md]]
* ❌ [[Projects:Anonycaster|docs/projects/anonycaster.md]]
* ❌ docs/projects/musicplayer.md
* ✓ [[About Hackerspace Nijmegen|docs/contact.md]]
* ✓ [[Minutes_2018-03-27|docs/minutes/2018-2.md]]
* ✓ [[Minutes_2018-03-20|docs/minutes/2018-1.md]]
* ✓ [[Main page|docs/index.md]]
* ✓ [[Contributing|docs/contributing.md]]
* ✓ [[Wishlist for the new space|docs/wishlist.md]]
* ✓ [[Event:CTF night|docs/events/ctfnight.md]]
* ❌ [[Event:Workshop_Friday_28th_of_September:_Kicad|docs/events/workshops/kicad101.md]]
* ✓ [[Event:Workshop Series (hopefully) 'What does it do'|docs/events/workshops/whatdoesitdo.md]]
* ❌ [[Event:November_1st:_Invited_speaker:_Property_testing|docs/events/workshops/propertytesting.md]]
* ❌ [[Event:Smallish_demo_about_signal_integrity.|docs/events/workshops/signal_intergrity.md]]
* ❌ [[Event:Getting_started_with_the_Ultimaker_2_3d-Printer|docs/events/workshops/3dprintergettingstarted.md]]
* ❌ [[Event:Workshop_Friday_7th_of_September:_Milling_printed_circuit_board_using_cheap_chinese_CNC_mill|docs/events/workshops/pcbmilling.md]]
* ✓ [[Event:Hack42_On_Tour_is_visiting|docs/events/hack42_on_tour.md]]
* ✓ [[Event:Movie night|docs/events/movienight.md]]
* ✓ [[Event:board_game_night|docs/events/boardgamenight.md]]
* ✓ [[Event:Christmas_dinner|docs/events/christmas_dinner.md]]
* ✓ [[Event:Open Day 2018|docs/events/openday2018.md]]
* ✓ [[Notes on opening the new space|docs/spaceopening.md]]
* ✓ [[About Hackerspace Nijmegen|docs/about.md]]
* ✓ [[Event:Opening party|docs/openingparty.md]]
* ✓ [[Naming|docs/naming.md]]
* ✓ <del>docs/empty.md</del> (empty page)
* ✓ [[Milling PCB's with 3018 Chinese Desktop CNC|docs/pcbmilling.md]]

= Hostname + SSL =

* ✓ Old wiki is down.
* ❌ Link wiki.hackerspacenijmegen.nl to this wiki.
* ❌ Make SSL certificate.

= Discussion group e-mail =

<nowiki>Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.</nowiki>

Projects:Anonycaster

2019-02-06T11:22:39Z

SA007: Copied from old wiki - last change Oct 9, 2018

The page of this project is located on dsprenkels' etherpad: https://etherpad.dsprenkels.com/p/anonycaster

Projects:Knitting Machine to laptop

2019-02-06T11:21:20Z

SA007: SA007 heeft de pagina HSNWiki:Knitting Machine to laptop hernoemd naar Projects:Knitting Machine to laptop zonder een doorverwijzing achter te laten

There you go. My objective for the rest of the year is getting my knitting
machine connected to my laptop (serial to usb), so i can create and replace the
knitting patterns and create new ones.

Ultimately, the idea is to knit bitmaps.

Model: Brother KH-930e. It works but the electronics are old.

Next steps:

* create the serial to usb cable
* install stuff (python)

First encounter to the matter was [Electro-knit
Hacking the Brother KH-930e knitting machine](https://learn.adafruit.com/electroknit/software)

Specs and updates will follow.

W

Projects:Knitting Machine to laptop

2019-02-06T11:18:20Z

SA007: SA007 heeft de pagina Knitting Machine to laptop hernoemd naar HSNWiki:Knitting Machine to laptop zonder een doorverwijzing achter te laten: Projects namespace

HSNWiki:Migration from Gitwiki

2019-02-06T11:04:06Z

SA007: /* Page migration */

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. [[#Discussion group e-mail|See the e-mail to the list for details.]]

Use ✓ for "done", ❌ for "not done".

= Settings =

* ✓ MediaWiki Installation
* ✓ Allow account creation
* ❌ [[HSNWiki:Proposed Editors|Add a nice WYSIWYG editor for pages]]
** The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
* ❌ [[HSNWiki:Account Approval|Require manual approval for making accounts]]
* ❌ Allow sending e-mail from wiki
* ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
* ✓ [[MediaWiki:Sidebar|Add Github etc. links to the sidebar]]
* ❌ [[HSNWiki:Proposed Extensions|Other extensions we'd like to see]]
* ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

== Settings, if possible? ==

* ❌ How to make some pages public, some pages private?
* ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
** "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
* ❌ Can we show edit history of pages only to logged-in accounts?
* ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
* ❌ Make a calendar/agenda containing all events on the wiki
* ❌ Make an auto-generated index of all pages on the home page?

== Theming ==
* ❌ @Joep to find some nice mediawiki themes to base our theme upon.
* ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
* ❌ @Sjors will give them access to the current installation to experiment with how it looks.
* ❌ @Michiel to send graphics to @Joep and @Robert.

== Backups ==
* ❌ @Sjors to make local backups on the VM for now.

= Page migration =

All pages to migrate:

* ✓ <del>README.md</del> (empty page)
* ✓ [[Budgets|docs/budgets.md]]
* ✓ [[Hackerspace_Nijmegen_(working_title)_zoekt_deelnemers!|docs/callforparticipation.md]]
* ✓ [[Statuten|docs/statuten.md]]
* ✓ <del>docs/knittingmachine.md</del> (added into [[Knitting Machine to laptop]])
* ❌ [[ProjectOne:Planning|docs/projects/ProjectOne/planning.md]]
* ❌ [[ProjectOne:Mini_RC_Hovercrafts|docs/projects/ProjectOne/MiniRCHovercrafts.md]]
* ❌ [[ProjectOne:Project_Ideas_that_are_too_big_to_do_on_my_own|docs/projects/ProjectOne/proposals.md]]
* ❌ [[ProjectOne:Project_One_Main_Page|docs/projects/ProjectOne/index.md]]
* ❌ docs/projects/lasercutter.md
* ✓ [[Knitting Machine to laptop|docs/projects/knittingmachine.md]]
* ❌ docs/projects/anonycaster.md
* ❌ docs/projects/musicplayer.md
* ✓ [[About Hackerspace Nijmegen|docs/contact.md]]
* ✓ [[Minutes_2018-03-27|docs/minutes/2018-2.md]]
* ✓ [[Minutes_2018-03-20|docs/minutes/2018-1.md]]
* ✓ [[Main page|docs/index.md]]
* ✓ [[Contributing|docs/contributing.md]]
* ✓ [[Wishlist for the new space|docs/wishlist.md]]
* ✓ [[Event:CTF night|docs/events/ctfnight.md]]
* ❌ [[Event:Workshop_Friday_28th_of_September:_Kicad|docs/events/workshops/kicad101.md]]
* ✓ [[Event:Workshop Series (hopefully) 'What does it do'|docs/events/workshops/whatdoesitdo.md]]
* ❌ [[Event:November_1st:_Invited_speaker:_Property_testing|docs/events/workshops/propertytesting.md]]
* ❌ [[Event:Smallish_demo_about_signal_integrity.|docs/events/workshops/signal_intergrity.md]]
* ❌ [[Event:Getting_started_with_the_Ultimaker_2_3d-Printer|docs/events/workshops/3dprintergettingstarted.md]]
* ❌ [[Event:Workshop_Friday_7th_of_September:_Milling_printed_circuit_board_using_cheap_chinese_CNC_mill|docs/events/workshops/pcbmilling.md]]
* ✓ [[Event:Hack42_On_Tour_is_visiting|docs/events/hack42_on_tour.md]]
* ✓ [[Event:Movie night|docs/events/movienight.md]]
* ✓ [[Event:board_game_night|docs/events/boardgamenight.md]]
* ✓ [[Event:Christmas_dinner|docs/events/christmas_dinner.md]]
* ✓ [[Event:Open Day 2018|docs/events/openday2018.md]]
* ✓ [[Notes on opening the new space|docs/spaceopening.md]]
* ✓ [[About Hackerspace Nijmegen|docs/about.md]]
* ✓ [[Event:Opening party|docs/openingparty.md]]
* ✓ [[Naming|docs/naming.md]]
* ✓ <del>docs/empty.md</del> (empty page)
* ✓ [[Milling PCB's with 3018 Chinese Desktop CNC|docs/pcbmilling.md]]

= Hostname + SSL =

* ✓ Old wiki is down.
* ❌ Link wiki.hackerspacenijmegen.nl to this wiki.
* ❌ Make SSL certificate.

= Discussion group e-mail =

<nowiki>Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.</nowiki>

ProjectOne:Mini RC Hovercrafts

2019-02-06T11:01:57Z

SA007: Copied from old wiki - last change Jul 18, 2018

== Prototype notes: ==
To get started, it was suggested that we start with one and we don't immediately go for miniature but rather try to get some experience first. Like: what are important design characteristics? Is the outer shape important? How much motor/airflow do you need? Does a regular rc propeller work or do you need something with lower speed and more air movement per rotation? Which factors influence stability? How does one make the skirt?

So we first mock about a little with some quadcopter parts to get a better feeling for what is important when designing something smaller.

If people want to get started I suggest to start with a v0.0 prototype that has only hover and no propulsion made out of cardboard/foam/mdf/whatever you can find.

=== What you'll likely need to get lift-off: ===

* board/mdf and a (manual/electric) jigsaw
* plastic bag and sciccors to make a skirt
* arduino to translate between receiver and motor controller(esc). I believe the former to output pulse-width-modulated signal and the latter to take pulse-density modulated signals. I believe that in theory the speed controller can be flashed to take pwm directly but I don't have a clue how. An arduino inbetween has the added benefit that a low signal can be translated to a full-off which is not possible with a direct connection.

=== Here are some more thoughts: ===

* In the purple crate there are 4 spare (silver) motors. One of them has a bent shaft. look out for that one ;-) It is not in the same box as the three good ones. The quadcopter was not flying properly last time I used it. I believe that at least one of the red motors that are currently mounted on it has an issue too. The safe bet is to use one of the three silver motors from the cardboard box in the crate.
* please be carefull with motors with props on them ;-) Always verify that they twist the way you expect before letting them spin with props or even nuts on them (i.e. such that the nut tightens itself and not loosens when rotating). If you spin a prop clockwise on a motor with normal clockwise thread the nut WILL come of and kill someone. The direction of fastening should always be the opposite of the direction the prop will spin.
* I suggest you use one of the mdf quadcoper arms to hold the motor in place. Simply hotglue that to a baseplate with a large hole. We can add something fancy later.
* One of the things I've seen people do is to cut a propeller to a smaller diameter to get better results. You have my permission to cut some props if you believe this is needed.
* The ESC (electronics speed controllers) are designed to feed logic level voltage (3.3 or 5V I don't remember) back to a microcontroller through the 3-pin input plug. orange wire is signal. They won't be damaged if more than one is feeding the microcontroller at the same time.
* You have my permission to unsolder unneeded ESC's from the power distribution board.

== Basis idea ==
Build miniature hovercrafts for racing around the space or outdoor depending on how small we can make them and how well they work.

== Alternatives ==
The simplest form would have one remote for each hovercraft. Maybe that is a good starting point.

Alternatively, they could be centrally controlled and perform some choreography (e.g. making a lightshow by also adding some RGB leds to each craft?).

Alternatively, they could be autonomous. There would have to be some vision processing? Or maybe we can come up with some other way for them to know where they are? I guess GPS is (besides relatively expensive) not precise enough. Or the track could have some special markers so that the crafts know where to go. It would be cool if they can autonomously race against each other. Maybe there can even be some kind of generic racing algorithm so that they get better over time? This is the most ambitious version and the least feasible.

Maybe they can see each other through some qr tags or other markers (doesn't have to be visible can be IR leds blinking out identifyable patterns, etc...). That way they don't know where they are but they can flock together. That could look kinda cool?

== Base features ==
The most basic craft should have:
* a frame with a skirt
* a battery
* a controller
* 1 brushless motor (combining lift and propulsion)
* propellors
* esc to control the motor speed
* one servo attached to a rudder for steering
* a receiver
* a transmitter (if we use wifi or some custom 433MHz/2.4GHz protocol this could be shared, individual control could go via smartphone or something like that).

== Sub-projects ==
Could be:
* hardware/skirt/steering
* electronics/uC
* communication and remote control

== Rough cost estimation ==
Bare minimum: 25 euro/craft

Assuming we have one shared transmitter and some app so we don't have to buy a transmitter for each unit:

{| class="wikitable"
! What
! How much
! How
|-
| frame
| 5
| laser-cut base + skirt from trash bag + 3d printed stuff
|-
| battery
| 5
| ~1000mAh from hobbyking?
|-
| controller
| 3
| arduino/nodemcu alike
|-
| bldc
| 5
| the absolute cheapest I saw on hobbyking
|-
| propellor
| 1
| if bought in bulk
|-
| esc
| 5
| BLHeli-like controller, don't know which one exactly
|-
| servo
| 1
| 9g micro; just search aliexpress
|-
| receiver
| 0
| if we use nodemcu/esp8266
|-
| total
| 25
| still seems expensive to me :,-(
|}

Any kind of computer vision immediately add rpi-like hardware at 25 euros each + plus the cost of a camera.

IR communication or sensing hardware is probabaly cheap in aliexpress/ebay.

== Feasibility ==
Problems will certainly arise, but RC hovercrafts are not new so it can be done. The challenge is to make them cheap and to make them small. The former could result in problems if we use cheap hardware it may become harder to control. The latter may cause problems because more bottom surface means more stability.

== Tools needed ==
* 3d printer could be usefull for brackets/handles etc
* soldering iron and supplies
* programmer? depending on controller

== Skills needed ==
A bit of everything. We need software, we need electronics, we need hardware. We could delve into radio-stuff if someone like to do that kind of stuff, but we can do with standard radio transmitters/receivers.

== How much time will this take ==
Let's aim to come up with a rough design in 1 or 2 weeks, have a one-off prototype ready after 2-3 months. Then plan a workshop where people can build their own and then we have a fleet to race against each-other ;-)

== Number of people involved ==
This is really flexible. See sub-projects above. It would be nice to make sub-teams of 1-3 people, so I'd say anything between 2 and 10 is feasible.

== Wild ideas ==
=== single propeller for everything ===

With 2 servo's controlling "flaps" that release air from the propeller shroud it could be possible to steer the craft. (essentially making it a 2-servo-1-bldc instead of 2-blcd-1-servo operation). Note also how air escapes even in neutral position, such that lift is constant no matter what the steering is doing.

[[Bestand:hovercraft_steering.png]]

Bestand:Hovercraft steering.png

2019-02-06T11:01:50Z

SA007:

ProjectOne:Project One Main Page

2019-02-06T10:53:07Z

SA007: Copied from old wiki - last change Jun 20, 2018

== Pages: ==
* [[ProjectOne:Project_Ideas_that_are_too_big_to_do_on_my_own|Proposals]]
* [[ProjectOne:Planning|Planning]]

== Idea: ==
Hack together on a semi-large project because hacking together is much more fun than hacking alone.
Plus, I had some funky ideas for projects that are simply too large to face on my own.

I am hoping to collect a small team of people and collaborative work on one of these because hacking is more fun when done together.
The list is not exhaustive and the ideas are open to suggestions and refinement.

== Communication: ==

* Discussion is on IRC in the #hsnijmegen channel.
* Meetings are on our regular tuesday until further notice
* Meetings start around 20

If you'd like to join, talk to themba on irc or email [[Bestand:email.png]]

ProjectOne:Planning

2019-02-06T10:52:39Z

SA007: Copied from old wiki - last change Jun 20, 2018

=== Week 25: ===
Brainstorm about project ideas/proposals

=== Week 26: ===
'''Before meeting:''' finish long-list of proposals. Add your ideas to the wiki or they don't count!

'''At start of meeting:''' I will make a round asking everyone: what are the top-2 things you find important in a project? What is your current top-2 of proposals that you have heard about?

'''In meeting:''' create a shortlist of concrete project proposals.

=== Week 27: ===
''' Before meeting:''' discuss propsals on irc.

'''At start of meeting:''' Observe that consensus has been reached or vote on project proposals.

'''In meeting:''' divide sub-projects and make a planning.

=== Week 28 onwards: ===
'''TBD'''

ProjectOne:Project Ideas that are too big to do on my own

2019-02-06T10:48:58Z

SA007: Copied from old wiki - last change Jun 25, 2018

These are some ideas I have collected. They are too big to take on by myself.
I was hoping to collect a small team of people and collaborative work on these because hacking is more fun when done together.
The list is not exhaustive and the ideas are open to suggestions and refinement.
I think it would be best to pick another night than tuesday for working on this community project.

If you'd like to join, talk to themba on irc or email [[Bestand:email.png]]

Critical mass is 3.

=== mini RC hovercraft racing ===
Using drone parts, build RC hover crafts (see youtube) and a race track/obstacle track on the "pleintje" behind the space.
We could also try to miniaturize the hover crafts so that they can be used indoors.

=== 3d printer XXL ===
Build the biggest/fastest 3d printer ever. One that can print a functional chair in one part. Preferably within an hour.
I was thinking 3mm filament and 2mm nozzle. We'll have to come up with a very strong extruder and a way to prevent oozing of material during travel. These are just 2 problems that I can foresee.

=== Cubic music control ===
Create a music service (on the bar pc?) that plays pre-created play-lists. Then create a wireless remote in the shape of a cube.
Ideally the cube has no markings, no buttons and no lights. You control the music via an imu/accelerometer/compas/gyro in the cube. If you rotate the cube while it's lying on the table you turn the volume op/down.
Flipping it over an edge could have one of several effects. Effects that I would like to see are: skip track, replay previous track, change play-list (we could have several for different moods).
But I don't really know yet how the user would distinguish them. Maybe we do have to embed some symbols on the edges or the faces of the cube. From each face you have 4 sides that you can turn to. They could be next/prev track and next/prev playlist. Or each face could have a meaning. In the latter case not the flip, but the upside face after the flip determines what is playing.
It would be cool if you can also turn the music off: Maybe you have to put it in a dock that it somehow recognizes (maybe the cube is balanced on a corner when it's in the dock or it has wireless charging inside?) to turn the music off. Alternatively you could just pause the playback when volume reaches 0.
A cool feature could be that it randomizes the playback when you shake the cube.

=== Cooperative Multi-player cardboard VR game ===
A while ago I was playing some cooperative cardgames with friends and they are a lot of fun. Cooperative games are games where all players win together or lose together. Usually you play against a randomized adversary.
I would like to make a cooperative cardboard VR game. The google cardboard sets are inexpensive but you can also have more rigid phone-to-vr adapters for a few bucks nowadays (look in the Action).
They don't have the quality of an occulus but it is certainly quite nice. One of the drawbacks is that there is limited input capabilities. This could either be solved by choosing a game that requires no input.
(E.g. cooperative pacman where you play the ghosts and you simply walk in the direction that most closely aligns with your viewing direction. I can really see this working as a collaborative game if players cannot see the maze but can score upgrades where they can fly up for a while to tell the others which way they should go).
Alternatively, we have to create hand-held controllers (could be as simle as a hand-held trigger, it could contain accelerometer+compas etc, or even a wiimote like setup (I've heard wiimotes are quite hacker friendly so we may even try to repurpose some)). Either connected to the usb port on your phone (most new androids have usb-otg that I believe could be used from inside an app but I don't know for sure) or via wifi.
I think it would be great if we could "upgrade" an arcade classic like pacman, bomberman, space invaders or asteroids (imagine that one player steers the ship, another fires lasers and another does long range scanning or something like that) to the VR domain.
There is also "empty epsilon" (it's a bit obscure but I know the creator so we may be able to get support on that) which we could try to upgrade to VR. The big plus of that is that (for an open source game) there has been done relatively much work on fun missions to play. Imagine how cool something like that could be...

=== Drawing machine XXL ===

extent our drawing machine to draw huge paintings/drawing on walls, as
big as you can imagine them to be. For this we need to scale up the
mechanical parts (motors, belts) and reinvent the drawing part (should
be move to paintgun?).

We could exploit the drawing machine for assignments of companies and
governments, and for our own PR. One first deadline could be the weekend
7-9 September for the Big Draw Nijmegen festival http://www.thebigdrawnijmegen.nl/

=== Graffiti-app ===

With this app you could use your mobile device to put drawings and tags
everywhere where the is a wall our a static object. The drawings you
make/spray will be visible by others that use the app, and are tagged on
a (openstreetmap) map so that other can find your piece of art. This app
could develop to be a game, a art-exhibition or a social experiment.

game-aspect: find a secret route with arrows, and hints marked on spot
you can only access with the app. Will this be the next pokemon?

art-exhibition: invite people to make a drawing somewhere, like real
street-artist. After a while a city full of piece of art emerge.

HSNWiki:Migration from Gitwiki

2019-02-05T23:11:30Z

SA007: /* Page migration */

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. [[#Discussion group e-mail|See the e-mail to the list for details.]]

Use ✓ for "done", ❌ for "not done".

= Settings =

* ✓ MediaWiki Installation
* ✓ Allow account creation
* ❌ [[HSNWiki:Proposed Editors|Add a nice WYSIWYG editor for pages]]
** The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
* ❌ [[HSNWiki:Account Approval|Require manual approval for making accounts]]
* ❌ Allow sending e-mail from wiki
* ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
* ✓ [[MediaWiki:Sidebar|Add Github etc. links to the sidebar]]
* ❌ [[HSNWiki:Proposed Extensions|Other extensions we'd like to see]]
* ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

== Settings, if possible? ==

* ❌ How to make some pages public, some pages private?
* ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
** "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
* ❌ Can we show edit history of pages only to logged-in accounts?
* ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
* ❌ Make a calendar/agenda containing all events on the wiki
* ❌ Make an auto-generated index of all pages on the home page?

== Theming ==
* ❌ @Joep to find some nice mediawiki themes to base our theme upon.
* ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
* ❌ @Sjors will give them access to the current installation to experiment with how it looks.
* ❌ @Michiel to send graphics to @Joep and @Robert.

== Backups ==
* ❌ @Sjors to make local backups on the VM for now.

= Page migration =

All pages to migrate:

* ✓ <del>README.md</del> (empty page)
* ✓ [[Budgets|docs/budgets.md]]
* ✓ [[Hackerspace_Nijmegen_(working_title)_zoekt_deelnemers!|docs/callforparticipation.md]]
* ✓ [[Statuten|docs/statuten.md]]
* ✓ <del>docs/knittingmachine.md</del> (added into [[Knitting Machine to laptop]])
* ❌ docs/projects/ProjectOne/planning.md
* ❌ docs/projects/ProjectOne/MiniRCHovercrafts.md
* ❌ docs/projects/ProjectOne/proposals.md
* ❌ docs/projects/ProjectOne/index.md
* ❌ docs/projects/lasercutter.md
* ✓ [[Knitting Machine to laptop|docs/projects/knittingmachine.md]]
* ❌ docs/projects/anonycaster.md
* ❌ docs/projects/musicplayer.md
* ✓ [[About Hackerspace Nijmegen|docs/contact.md]]
* ✓ [[Minutes_2018-03-27|docs/minutes/2018-2.md]]
* ✓ [[Minutes_2018-03-20|docs/minutes/2018-1.md]]
* ✓ [[Main page|docs/index.md]]
* ✓ [[Contributing|docs/contributing.md]]
* ✓ [[Wishlist for the new space|docs/wishlist.md]]
* ✓ [[Event:CTF night|docs/events/ctfnight.md]]
* ❌ [[Event:Workshop_Friday_28th_of_September:_Kicad|docs/events/workshops/kicad101.md]]
* ✓ [[Event:Workshop Series (hopefully) 'What does it do'|docs/events/workshops/whatdoesitdo.md]]
* ❌ [[Event:November_1st:_Invited_speaker:_Property_testing|docs/events/workshops/propertytesting.md]]
* ❌ [[Event:Smallish_demo_about_signal_integrity.|docs/events/workshops/signal_intergrity.md]]
* ❌ [[Event:Getting_started_with_the_Ultimaker_2_3d-Printer|docs/events/workshops/3dprintergettingstarted.md]]
* ❌ [[Event:Workshop_Friday_7th_of_September:_Milling_printed_circuit_board_using_cheap_chinese_CNC_mill|docs/events/workshops/pcbmilling.md]]
* ✓ [[Event:Hack42_On_Tour_is_visiting|docs/events/hack42_on_tour.md]]
* ✓ [[Event:Movie night|docs/events/movienight.md]]
* ✓ [[Event:board_game_night|docs/events/boardgamenight.md]]
* ✓ [[Event:Christmas_dinner|docs/events/christmas_dinner.md]]
* ✓ [[Event:Open Day 2018|docs/events/openday2018.md]]
* ✓ [[Notes on opening the new space|docs/spaceopening.md]]
* ✓ [[About Hackerspace Nijmegen|docs/about.md]]
* ✓ [[Event:Opening party|docs/openingparty.md]]
* ✓ [[Naming|docs/naming.md]]
* ✓ <del>docs/empty.md</del> (empty page)
* ✓ [[Milling PCB's with 3018 Chinese Desktop CNC|docs/pcbmilling.md]]

= Hostname + SSL =

* ✓ Old wiki is down.
* ❌ Link wiki.hackerspacenijmegen.nl to this wiki.
* ❌ Make SSL certificate.

= Discussion group e-mail =

<nowiki>Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.</nowiki>

Event:Getting started with the Ultimaker 2 3d-Printer

2019-02-05T22:52:20Z

SA007: Copied from old wiki - last change Apr 27, 2018

By: ''' Themba '''

When: Date: '''Friday May 4th 2018''' Time: '''19:00'''

Who: _add your name here or send an email to_ [[Bestand:email.png]]

* s
* sharkattack
* person
* person

Where: ''' the space (Elzenstraat 4A) '''

'''Audience:''' This workshop is primary intended for our regulars but external participants with an interest in 3d printer are welcome to join.

'''Prerequisites:'''
No knowledge is required. Please bring a laptop. Try to install [https://ultimaker.com/en/products/ultimaker-cura-software Cura] (preferably version >3) but don't worry if you cannot succeed before the workshop.

'''Topic:'''
The Ultimaker 2 3d-printer is a dangerous (and expensive) machine and, although it is relatively easy to operate and hard to damage, it should not be used without receiving proper instructions beforehand. The easiest way to receive those instructions is by following this workshop. The idea is that anyone who attended is not only capable of using the machine but can also educate others to do so. Let the knowledge spread!

''' help wanted:'''
If you already have experience with operating this machine or other 3d printers your input is welcome. I have sufficient knowledge of 3d printing to give this workshop comfortably but I am not the final expert so you may have more and/or better tips than I do. Please join the workshop.

== Contents: ==
* 3d printer capabilities and limitations
* preparing print jobs
* starting a print
* changing filament
* common problems and how to solve them
* plastic policy
* unattended printing

If time permits on request any of these topics may be discussed:

* materials and their merits
* bed leveling
* xy-axis calibration
* 3d cad design
* machine upgrades

Event:Workshop Friday 28th of September: Kicad

2019-02-05T22:43:23Z

SA007: Copied from old wiki - last change Sep 22, 2018

'''By:''' stef

'''When:''' Date: '''Friday September 28th, 2018''' Time: '''20:00'''

'''Who:''' (if you want add your name here or send an email to stef or themba))

*

'''Where:''' the space (Elzenstraat 4A)

'''Adience:'''
Anyone who is interested

'''Prerequisites:'''

If you want to click along, bring a computer with kicad 5 installed.

'''Topic:'''
Entry-level kicad electronics design.

If other people are more experienced with kicad I would love to have their contributions during the workshop.

Event:Workshop Friday 7th of September: Milling printed circuit board using cheap chinese CNC mill

2019-02-05T22:32:11Z

SA007: Copied from old wiki - last change Sep 7, 2018

[[Bestand:diy-circuitboard.jpg]]
[[Bestand:diy-soldermask.jpg]]

'''By:''' Themba

'''When:''' Date: '''Friday September 7th, 2018''' Time: '''19:00'''

'''Who:''' (add your name here or send an email to [[Bestand:email.png]]

* themba
* Sjors
* hacker[m]
* Rob
* Robert
* Simon
* thvdburg +1
* Erik
*

'''Where:''' the space (Elzenstraat 4A)

'''Adience:'''
Anyone who is interested

'''Food:'''
Workshop starts at 19:00. If there is sufficient interest, food will be ordered to be delivered at 18:00. Deadline for food ordering is 16:00.

'''Prerequisites:'''
None.
If you want you can bring a digital design (gerber) of a circuit board that you would like to make. I cannot guanrantee that we have time to make all.

'''Topic:'''
DIY printed circuit board fabrication. I have recently spent some time to develop the procedure to make printed circuit boards at home. This evening I will walk you through the steps involved. It will be a bit like an interactive walk-through.

If other people are more experienced with etching (or even completely different methods of pcb fabricarion) I would love to experiment with that as well during the workshop. Maybe we can compare results/pros/cons.

There is some more info on my procedure [[Milling_PCB's_with_3018_Chinese_Desktop_CNC]]

== Contents: ==
* drawing circuit board
* isoluation routing
* machine setup
* milling
* drilling
* double sided boards
* solder resist layer

Bestand:Diy-soldermask.jpg

2019-02-05T22:30:02Z

SA007:

Bestand:Diy-circuitboard.jpg

2019-02-05T22:29:51Z

SA007:

Event:November 1st: Invited speaker: Property testing

2019-02-05T22:25:56Z

SA007: Copied from old wiki - last change Oct 29, 2018

'''By:''' Nick van den Broeck

'''When:''' Date: November 1st: '''21:00'''

'''Who:''' Registration is not mandatory but you risk missing important announcements if you don't (if you want, add your name here or send an email to [[Bestand:email.png]]

* Nick
* themba
*
*
*
*
*
*
*

'''Where:''' the space (Elzenstraat 4A)

'''Audience:'''
Anyone who is interested

'''Prerequisites:'''

None.

'''Topic:'''
A talk about Code testing and subsequent discussion possibility.

Abstract:

Think maintenance and debugging are boring?
There is a solution, and it's easier than you thought!
The solution is to test your code. Now, that might sound
anti-climactic. Let's be fair, testing has been around for ages.
Also, it's hard, time-absorbing.. Not a very good solution.
This is why I want to talk about a recent development in the
field of testing: property testing! Property testing is an easy,
fast and fun way to test your code very thoroughly.

Come to my talk and find out how you can code without
hundreds of hours debugging!

Event:Smallish demo about signal integrity.

2019-02-05T22:22:51Z

SA007: Copied from old wiki - last change Jan 18, 2019

'''By:''' SA007

'''When:''' Date: '''Tuesday January 22th, 2019''' Time: '''20:00'''

'''Adience:'''
Anyone who is interested

What is that about:

* How do chips/devices talk to each other.

* Common mistakes why things don't work.

* Some explination about terms like pull-up/pull-down, open-collector etc.

* Demo's about slew-rate, etc.

Event:Workshop Series (hopefully) 'What does it do'

2019-02-05T22:16:14Z

SA007: Copied from old wiki - last change Nov 22, 2018

'''By:''' SA007

'''When:''' Date: '''Tuesday November 27th, 2018''' Time: '''20:00'''

'''Adience:'''
Anyone who is interested

'''Topic:''' I'm starting a series of 'workshoppy' lectures about interesting tech.

Length is somewhere between 30minutes and an hour.

Idea is to take 'some' device and show/dismantle/analyse/reuse it.

Start is Nov 27 with GFI / RCCB / Aardlekschakelaars.

Idea's for this series: ping me.

Event:board game night

2019-02-05T22:06:25Z

SA007: Copied from old wiki - last change Oct 22, 2018

Board/card games are fun.

There is a copy of "Hacker - the computer crime card game" in the space. It is an award-winning card game from 1992 by Steve Jackson games (the makers of Muchkin).

Other games could be fun too.

'''Organizer:''' you?

'''Where:''' the space (Elzenstraat 4A)

== Next up: ==

When: '''TBD by organizer'''

== Past occurances: ==
=== None ===

== Organizer wanted: ==
Organizing is simple: set a date, anounce event, bring games (or make sure at least someone else does)

=== Announcing events ===
* send email to hackerspacenijmegen@lists.hsbp.org and events.hackerspacenijmegen@lists.hsbp.org.
* anounce on irc (and add to topic)
* put on meetup: themba [[Bestand:email.png]] and allurb4se have write access on our meetup group.

Event:Christmas dinner

2019-02-05T22:03:51Z

SA007: Copied from old wiki - last change Dec 18, 2018

Let's do christmas dinner!

The idea is: everyone brings some dishes/drinks and we share everything. If everyone brings 1.5 person worth of calories that should work out more or less. Of course salads can be a little less. Also keep in mind that it would be nice if there is enough to make 10 to 15 reasonable sized portions so everyone can have at least one serving/try of each dish.

''' When: Tuesday December 18th at 19:00 '''

== Who/what: ==
Add your name or send an email to [[Bestand:email.png]]:

{| class="wikitable"
| who
| what
| note
|-
| themba
| home-made christmas "stol" and salad
|
|-
| cyb3rgh0st
| desert
|
|-
| michiel
| (veg.) snert and ginger ale
|
|-
| SA007
| sushi
|
|-
| priseko
| eggplant curry
|
|-
| joanna
| gyros salad or polish dumplings
| arrive at 20:30
|-
| natalia
|
| arrive at 20:30
|-
| Ed
| pasta and soup
| veg.
|-
| floris
| see above
|
|-
| stf
| wine
|
|-
| viola
|
| gluten free
|-
| MacGyver
|
|
|-
| minnozz
| quiche loraine
|
|-
| walter
| icecream and crisps and gluhwein
|
|-
| add more rows if needed...
|
|
|}

== Food restrictions/allergies: ==
if you have any, please come forward

Known so far:

* gluten (1x)
* meat (1x)

== Other notes: ==
* Depending on the number of participants there may not be enough cutlery in the space. Please consider bringing some from home.
* There is a microwave oven so things can be reheated but besides that there are not a lot of preparation facilities in the space.
* Volunteers wanted for christmassy space decorations (please don't bring a real tree :s).
* bonus points will be awarded to people who can come up with hacker-related ingredients/dishes...

Event:CTF night

2019-02-05T21:55:54Z

SA007: Copied from old wiki - last change Oct 22, 2018

Capture-the-flag and wargames are online challenges to learn pen-testing step-by-step. There are tons of challenge websites out there to choose from in a range of difficulty levels (even for complete novices) and on a wide variety of topics, ranging from javascript vulnerabilities to stack-overflow exploits.

These games are particularly fun when played as a "race" against other people in the same room.

'''Organizer:''' you?

'''Where:''' the space (Elzenstraat 4A)

== Next up: ==

When: '''TBD by organizer'''

== Past occurances: ==
=== None ===

== Organizer wanted: ==
Organizing is simple: set a date, anounce event, bring your laptop

=== Announcing events ===
* send email to hackerspacenijmegen@lists.hsbp.org and events.hackerspacenijmegen@lists.hsbp.org.
* anounce on irc (and add to topic)
* put on meetup: themba [[Bestand:email.png]] and allurb4se have write access on our meetup group.

Event:Movie night

2019-02-05T21:50:27Z

SA007: Copied from old wiki - last change Oct 22, 2018

'''Organizer:''' you?

'''Where:''' the space (Elzenstraat 4A)

== Next up: ==

When: '''TBD by organizer'''

Movie: ''' TBD '''

== Past occurances: ==
=== None ===

== Organizer wanted: ==

Organizing is simple: set a date, anounce event, make a poll for a (hacker-themed) movie, buy popcorn.

=== Announcing events ===
* send email to hackerspacenijmegen@lists.hsbp.org and events.hackerspacenijmegen@lists.hsbp.org.
* anounce on irc (and add to topic)
* put on meetup: themba [[Bestand:email.png]] and allurb4se have write access on our meetup group.

Bestand:Email.png

2019-02-05T21:47:59Z

SA007:

Event:Open Day 2018

2019-02-05T21:34:02Z

SA007: Copied from old wiki - last change Apr 18, 2018

'''April 22nd 2018, from 11:00 till 17:00'''

''' Elzenstraat 4A '''

== To see: ==

* ASCII-art by Walter van der Cruijsen
* Retro-TV’s by Jaap Meijers (see: http://retromedia.nl/ )
* and more...

== To do: ==
* 3d printing
* V-Plotter machine in action
* hands-on Scratch
* and more...

== About Hackerspace Nijmegen ==
Hackerspace Nijmegen is a new (since april 2018) hackerspace where people with an interest in science, art, technology, (cyber)security or a combination thereof get together. It is a relaxing place for discussion and meeting new people, a social place for organizing workshops and lectures and a tool collection for collaborating on cool projects.

During the open day you can walk in and out whenever you want. There will be people at least from 11 till 17. You can talk to us, see the projects we are working on, try some things yourself, and taste a Club Mate (our preferred caffeine source). There are numerous artist in the same building who also have open day on the same day:

[[Bestand:Flyer_openday_2018.jpg]]

Bestand:Flyer openday 2018.jpg

2019-02-05T21:33:27Z

SA007: EXPO OOST poster

== Beschrijving ==
EXPO OOST poster

Event:Hack42 On Tour is visiting

2019-02-05T21:12:42Z

SA007: Copied from old wiki - last change Oct 17, 2018

Hack42 is organising an awesome tour and vititing all hackerspaces.
Of course also visiting Hackspace Nijmegen.

* Date: 3 and 4 November, 2018.
* Time: The entire weekend
* Location: Elzenstraat 4a, Nijmegen
* More info: Contact Hack42 or SA007.

== On Tour? ==

There is going to be a full touring bus full of hackers coming by.

The entire touring schedule is at the [https://hack42.nl/wiki/Hack42_on_Tour Hack42 wiki page]

Hackerspace Nijmegen will be visited on Sunday 4th of November at roughtlyish 10:30.

It would be awesome if the space isn't empty and a great way to meet more hackers.

Naming

2019-01-30T20:47:18Z

SA007: Copied from old wiki - last change 3 april 2018

== We Chose A Name ==

latest email announcing the results:

: the winner is:
: https://github.com/hackerspace-nijmegen/hsnmgn-name-ballot/blob/master/result.txt#L1

: drums:

: Hackerspace Nijmegen

: badumts!

: for the rankings submitted and the script that evaluated this, check the repo:
: https://github.com/hackerspace-nijmegen/hsnmgn-name-ballot

: the Schulze method as been applied by using
: https://github.com/bradbeattie/python-vote-core/
: with the version marked by commit: 7791d72930e72aceea8b0f4bfe6baea7099aff84

: in total we received 10 rankings, thanks to all who participated in this.

: happy hacking,
: s

: ps: have fun today in the new space!

== Looking For A Name ==

email announcing the voting phase, closing the nomination phase:

== Voting phase Info ==

hey all,

nomination phase is over since yesterday.

modified deadline for the voting phase is 3rd April 17:00 UTC+0200

(it was originally 3rd April 17:00 UTC+0100 but then stupid daylight savings
came in)

plesase look at this spreadsheet:
https://ethercalc.org/554is070k6b2

and create a ranking of your favorite names. either one name per line in order
of 'decreasing' preference, or as a json list of names in a similar order.
then send it to me.

you can do so until: 3rd April 17:00 UTC+0200

for the evaluation of the votes we use the schulze method:
(https://en.wikipedia.org/wiki/Schulze_method) as it is being used by projects
such as the debian, gentoo, pirate party, fsfe and others.

eligibility
who is eligible for voting? anyone on the list of people contributing to our
monthly costs, the mailing list and on our irc channel.

what is a ranking?

: a ranking is an ordered list of names starting with the most preferred in
: decreasing order of preference. you can also have multiple names at the same
: preference, in this case write the names separated in one line. you do not
: have to list all names from the ethercalc sheet, all omitted names are
: considered least preferred without any order among these.

: if you want to help making this as easy as possible for us to evaluate, send
: the ranking as a json list of lists:
: [ ['most prefered name1', 'similarly ranked #1 name'],
: ['2nd ranked name'],
: ['3rd ranked name'],
: ....
: ['last ranked name']]

: we will publish all votes anonymously on the wiki, where you can verify that
: your vote is included and that the schulze method has been applied correctly.

happy hacking^Wvoting,
s

== Nomination Phase ==

On Wed, Feb 07, 2018 at 05:09:41PM +0100, Hackerspace Nijmegen wrote:
: [...snip...]
: It is suggested that "Hackerspace Nijmegen" is too generic. It is a good
: name for the foundation ("Stichting Hackerspace Nijmegen"), but for the
: club of people or the physical space we could most probably invent a
: better name.

: That is why we started to collect names. The names are stored in an
: online ethercalc spreadsheet. It is a brainstorm list. Please get
: inspired by the names already there, and add your suggestions to the list.

: https://ethercalc.org/554is070k6b2

== Nominations Phase ==

we have currently 112 suggestions. we should hurry up with choosing a name if
we don't have one by the time we have our opening party the generic
hackerspacenijmegen will stick. to facilitate a quick and fair selection we
should stop making new suggestions on the above quoted ethercalc sheet by 28th
March 17:00 UTC+0100. this is the nominations deadline.

== Voting Phase ==

With the end of the '''Nominations Phase''' we move onto the second stage, the
voting of our name. for this we use the widely used Schulze method
(https://en.wikipedia.org/wiki/Schulze_method) as it is being used by projects
such as the debian, gentoo, pirate party, fsfe and others.

=== Eligible Voters ===
who is eligible for voting, anyone on the list of people contributing to our
monthly costs, the mailing list and on our irc channel. (this is open to
debate)

=== How to Vote ===
how to vote, send a mail to me (may be we'll have a better voting box than
this by that time) after the deadline of phase 1 (nominations) and
before the voting deadline of 3rd April 17:00 UTC+0100 with a ranking of your
favorite names.

=== What Is A Ranking? ===

A ranking is an ordered list of names starting with the most preferred in
decreasing order of preference. you can also have multiple names at the same
preference, in this case write the names separated in one line. you do not
have to list all names from the ethercalc sheet, all omitted names are
considered least preferred without any order among these.

if you want to help making this as easy as possible for us to evaluate, send
the ranking as a json list of lists:

[ ['most prefered name1', 'similarly ranked #1 name'],
['2nd ranked name'],
['3rd ranked name'],
....
['last ranked name']]

=== Publishing of Votes ===

we will publish all votes anonymously on the wiki, where you can verify that
your vote is included and that the schulze method has been applied correctly.

We will publish the results of the final tally asap.

Notes on opening the new space

2019-01-30T20:40:07Z

SA007: Copied from old wiki - last change 24 may 2018

(things said after the [[Minutes_2018-03-20|boring meeting]])
these are some notes from a meeting among Stf, Themba, Michiel, Ed & Joep (joined later) of things needed to get the space started. Please feel free to contribute

== Action list: ==
* '''Stf''' will get some club mate before the opening party.
* '''Stf''' will write an email about the name of the space and explain the voting mechanism.
* '''Themba''' will make a wishlist and publish it for others to add.
* '''Ed''' will start a party-committee.

== Topics discussed ==
=== 1. Club Mate: ===
AP[Stf] will get some club mate before the opening party.

=== 2. Name of the space: ===
It needs to be decided quickly or “Hackerspace Nijmegen” will stick forever
Decision: We implement a fast version of the previous plan: one week for more suggestions, one week for voting
Stf will write an email about the name of the space and explain the voting mechanism.

=== 3. Decorating and furnishing the space: ===
We’ll need lots of things
Themba will make a wishlist and publish it for others to add.

=== 4. Opening party and/or open day: ===
AP[ed] will start a party-committee
Some ideas of things to have:
* lightning talks (introduce yourself, your last project and your next project?)
* food and drinks
* demos
* invited speakers
* music
* more things that will bring in money

Some ideas that are more appropriate for an open day:
* Stuff for children
* soldering
* art installations
* workshops
* more things to attract donations

On Sunday April 22nd there will be an open day in the complex. We should definitely have an open day then (albeit delayed from the other dutch hackerspaces).
Saturday April 21st is then by far the most logical options for the opening party.

'''Note:''' there are therefore two days of festivities at the space!!! First the opening party on saturday, the goal of which is to celebrate, get to know more hackers (invites should go to other dutch hackerspaces). Then, on sunday, an open day, intended for the general public. Both events are, of course, excellent opportunities to attract more participants and/or one-time donations.

{| class="wikitable"
! Date
! Event
|-
| Saturday April 21
| TBD
|-
| Sunday April 22
| Open day
|}

Wishlist for the new space

2019-01-30T20:31:36Z

SA007: Copied from old wiki - last change 11 april 2018

If it's not on the list doesn't mean we don't want it. Please get in touch ;-)

This is just a brainstorm, not all of these can be bought or donated, some need to be produced (such as space telemetry). Not all of these are a strict requirment to operate the space from the beginning but some are pretty essential.

Please add missing information. E.g., how many would be needed? put your name after the item if you can get one.

{| class="wikitable"
|-
! Item
! Needed
! Who is working on it
! Note
|-
| **Furniture:**
|
|
|
|-
| trashbin
| 1
|
| large one, we have 3 small ones
|-
| Couches
| 2
|
| we have one good one and one that smells of cigarettes
|-
| workbenches
| 1
|
| we have one that needs to be raised a little
|-
| working tables
|
| michiel
| Michiel has many options available, I think that is sufficient
|-
| donation box
| 1
|
| big, fat, red, flashing
|-
| accent lighting
|
|
| we have tl floodlight already
|-
| spot lighting
|
|
|
|-
| blinds or curtains
|
|
|
|-
| nameplate
| 2
|
| for both front door and internal door? maybe wait a little to see if the logo is final
|-
| coat hanger
| 1
|
| can be 3d printed?
|-
| toolboard
|
| michiel
| we'll use an old schoolboard with screws in it
|-
| small ladder/steps
| 1
|
| to reach the ceiling
|-
| **Apparel:**
|
|
|
|-
| coffee machine
| 1
|
| we already have senseo
|-
| pot for tea
| 1
|
|
|-
| cups for the above
| 10
|
|
|-
| disposable cutlery
|
|
| chack what we have already before buying
|-
| labelwriter
| 1
|
|
|-
| large flatscreen or beamer
| 1
| sa007
| for presentations
|-
| music installation
|
|
| possibly using the digiboard?
|-
| network cables
|
|
|
|-
| digital locks
|
| sa007
| sa007 is making an inventory of what is possible/needed
|-
| space telemetry
|
|
| open/closed status
|-
| space server
| 1
| cyberghost
| for space telemetry, spacenet ldap, revbank, rfid door stuff will probably all require at least some on-site infrastructure
|-
| soldering equipment
| 5
|
|
|-
| logic analyzer
| 1
|
| old scope we have
|-
| tools
|
|
| hammer, hacksaw, pliers, calipers, etc. everying is welcome
|-
| consumables
|
|
| resistors, transistors, leds, nodemcu's, arduino's, etc.
|-
| power extension cords
|
|
|
|-
| co2 extinguisher
| 1
|
|
|-
| clock
| 1
| themba
| a really cool wordclock
|-
| **Decorations**
|
|
|
|-
| posters
|
|
|
|-
| character increasing hackery elements
|
|
|
|-
| plants?
|
|
|
|-
| outward facing sign
|
|
| like an led-banner?
|-

Hackerspace Nijmegen (working title) zoekt deelnemers!

2019-01-30T20:22:08Z

SA007: Copied from old wiki - last change 15 may 2018

'''Update: Het minimum bedrag is bereikt, maar meer deelnemers zijn nog steeds welkom en van belang om de kosten per deelnemer te kunnen verlagen en om de space een succes te maken.'''

Ben jij als hacker, maker, security specialist, kunstenaar of anderszins geïnteresseerd om gelijkgestemden te ontmoeten? Bijvoorbeeld door samen aan projecten te werken, workshops te bezoeken of te organiseren? Wordt dan deelnemer bij de nieuw op te richten hackerspace in Nijmegen!

Kijk op [https://hackerspaces.nl hackerspaces.nl] voor meer uitleg over wat een hackerspace is of op [https://hackerspacenijmegen.nl hackerspacenijmegen.nl] voor meer info over deze nieuwe space.

Er is zicht op een ruimte, maar we hebben voor komende vrijdag (16 maart 2018) nog een aantal extra deelnemers nodig om de kosten te kunnen dekken! Maandelijkse sponsoring zonder deelnemer te worden is natuurlijk ook welkom.

[https://my.hidrive.com/share/cgbt10k7oi#$/ Hier] zijn foto's van de ruimte die we willen huren.

[https://lite.framacalc.org/Elzenstraat-contribution Hier] is een inventarisatie van de kosten en huidige donateurs.

Wil je ons steunen met een maandelijkse bijdrage en deelnemer worden: zet dan je naam in de lijst en stuur even een emailtje naar info@hackerspacenijmegen.nl zodat we weten wie er achter de naam op de lijst staat!

Meer info en contact: info@hackerspacenijmegen.nl