Fixme.ch - User contributions [en]

13th Anniversary

2023-01-06T21:49:40Z

Pherjung: /* Proposed activities */

[[Category:Ongoing_Projects]]
== Information ==
* TBD

== Programme ==

== Activities ==

=== Chosen activities ===

=== Proposed activities ===
* atelier (workshop, famille)
* sexy show
* tombola
* 13 en ternaire c'est 111
* soirée costumée
* vendredi 13, XII la BD, les 13 jours de la semaine, les 13 mousquetaire, les 13 petits nègres, les 13 salopard, l'armée des 13 singes, 1 homme, les 13 cantons, les 13 desserts de noel, numéro atomique de l'aluminium, le nombre d'étoiles sur le drapeau valaisan, nombre de valeurs de cartes différente dans un jeu standard de 52 cartes
* BAK XII
* marché de trucs fait maison (DIY)
* hot dog personnalisé
* concert, dj
* piano cocktail (marie)
* velo urbain
* conférences
* CTF
* radioham
* combats antique
* theme cirque celte
* jacuzzi
* LEDs show (orbital, jacuzzi, etc)

== Matériel ==
* TBD

== Administratif et autorisations ==
* Demander l'autorisation à la commune de Renens, car c'est une manif ouverte au public (courrier si possible max 1 mois avant)
* Demande pour vente de boissons avec alcool : http://www.vd.ch/themes/economie/police-du-commerce/manifestations/vente-de-boissons-alcooliques-lors-dune-manifestation/
Demandes faites et autorisations reçues de la police du commerce et des propriétaires

== Pictures ==
* TBD

== See also ==
* [[1st_Anniversary]]
* [[5th_Anniversary]]
* [[10th_Anniversary]]

Main Page

2018-05-11T17:18:13Z

Pherjung: /* Top projects */

__NOTOC__
{{Boite
| titre=Welcome to FIXME
| bordure=black
| fond=lightgray
| couleurTitre=black
| couleurTexteTitre=white
| largeur=75%
| flotte=left
}}
This is the working wiki of the FIXME Hackerspace, main website is at https://fixme.ch
{{BoiteFin}}

<div class="nomobile">
{{Boite
| couleurTexteTitre=white
| largeur=20%
| flotte=right
}}
https://fixme.ch/sites/default/files/hackerspace_status.png
[http://foo.fixme.ch/trigger.html Open/close the space]
{{BoiteFin}}
</div>

{{Boite
| titre=[[:Category:Projects|Projects]]
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Projects.png}}
* [[:Category:Ongoing_Projects|Ongoing]] | [[:Category:Proposed_Projects|Proposed]] | [[:Category:Closed_Projects|Closed]] | [[:Category:Canceled_Projects|Canceled]]
* [[Project template]] | [[Projects Ideas]]

===Top projects===
* [[Coursera_Microcontroleur]]
* [[Langage_VHDL]]
* [[SDR|Software Defined Radio]]
* [[SpaceAPI|MyHackerspace]]
* [[Multicopter]]
* [[MetaFoo]], [[Bellatrix]] Kubernetes, MAAS
* [[Gyrophare]]
* [[LED_Lighting]]
* [[Tron_Restore]]
* [[AG_2018]]
* [[Repair_cafe]]
{{BoiteFin}}

{{Boite
| titre=Events
| flotte=right
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Events.png}}

===Recuring events===
* '''Wednesdays''':
** Every wednesdays [[Weekly Meetings]] (social meeting, newcomers welcoming)
** Last wednesday of the month: Monthly Cleaning
* '''Thursdays''':
** Third Thursday is [[3D Thursdays]]!
* '''Fridays''':
** Every first fridays: Working on the FIXME infrastructure: [[Network]], [[Foo]], [[MetaFoo]], [[Bellatrix]]
** Some fridays Afterwork

=== Canceled events ===

If somebody wants to revive an event, you're welcome to do so!

* Every first sunday of the month: [[GameDev|Game development group]]
* First thursday of the month: [[LUG]] (GNU/Linux help/discussions)
* Every fridays [[Electronics evening]]
* Some friday evening [[CTFriday]] (hacking challenges)
* Second Tuesday of the month: [[dbms workshop]] (Work with RDBMS or ohers DBMS)
* Third Tuesday of the month : Création du [[ FIXME Coin ]]
* Forth Tuesday of the month : [[Raspberry Pi Buy|Workshop Raspberry Pi]]
* First Thursday: [[Spacenerd]]
* Thursday, once a month: [[CTF]] (CTF meeting, writeups, courses)

===Ponctual events===
* [[:Category:CodingNight|Coding Night]]
* [[:Category:Workshops|Workshops]]
* [[:Category:WeekendProjects|Weekend Projects]]
* [[:Category:ShortTalks|Short Talks]]
* [[:Category:Debates|Debates]]
* [[:Category:Conferences|Conferences delegation]]
* [[:Category:BoardGamesNight|Board Games Night]]
* [[Suggestion box]]

====[[How to create an event?]]====
{{BoiteFin}}

{{Boite
| titre=Fablab
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* We're sharing our local with Renens Fablab
* [[PCB_Etching]]
* 3D Printers
** Gigabot
** [[Ultimaker]]
** Ultimaker 3
** Delta
** ...
* Laser cutter
* CNC
{{BoiteFin}}

{{Boite
| titre=Electronic
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* [[Parts Order]]
* [[:Category:ElectroKit|Electronic kits]]
* [[Electronic FAQ]]
* [[CPU_Boards]]
* [[Electro_docs]]
* [[Kicad]]
* [[Stock_electronique]]
* Documentation
** [[ESP8266]]
{{BoiteFin}}

{{Boite
| titre=More
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* Equipment
** [[What do we provide ?]]
** [[What are we looking for ?]]
* [[Foo]], our internal services server
* [[Resources]] (local associations, events and shops)
* [[Movies|Geek movies]]
* [[Modele XP]]
* [[Sandbox]] for syntax tests
* [[Burgers]]
* [[Podcasts]]
* [[OpenData]]
* [[Raspberry_Pi]]
* [[Bitcoin_ATM]]
* [[Chat]]
* [[:Category:IOT]]
{{BoiteFin}}

{{Boite
| titre=Administration
| flotte=right
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Administration.png}}

=== Meetings ===
* [[:Category:Meetings|All Meetings]]
* [[:Category:ProjectMeetings|Project Meetings]]
* [[:Category:AG|General Assemblies]]
* [[:Category:BoardGames| BoardGames/Jeux de plateau]]

=== Association ===
* [[Internal Regulation]] [French]
* [[Utilité_publique]]: [https://pad.fixme.ch/p/letter_to_lausanne subventions], ...
* [[Membership_admin]]
* [[Accounts|What to do with new member?]]
* [[History]]
* [[Odoo]]
** Register expense
** Pay membership
** etc.

=== Other ===
* [[Openings]]
* [[Communication]]
* [[:Category:Weekmail|Weekly mail]] on upcoming activities
* [[Press_reviews]]
* [[Press_kit]]
* [[Network]]
* [[:Category:Services]]
* [[Logo]]
* [[Local]]
* [[Sheets]] (various documents)
* [[HowToWiki|How to edit the wiki]]
* [[FIXME2_TODO]]
* [[SonicPI]]
{{BoiteFin}}
{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}

LibreEtVous2018

2018-04-29T13:19:35Z

Pherjung: /* Stand */

[[Category:Ongoing_Projects]]
== Description ==
* Participation à l'événement Libre Et Vous à Lausanne au centre Pôle Sud
* https://libreetvous.ch/

== Goal ==
* Avoir un stand pour présenter l'association
* Donner un atelier Scratch d'introduction à la programmation

== Component ==
=== Atelier scratch ===
* Des laptops avec scratch installé ou si accès internet qui puisse faire tourner la version html5
* https://preview.scratch.mit.edu/
* On a 12 clés USB installées avec un Linux et Scratch, il faut tester ça sur 10-12 laptops

=== Stand ===
* Printrbot (Rorist)
* Ecran avec Rpi pour présenter l'association
* Petits montages electronique
* Lock picking
* Drapeau et stickers FIXME
* Pulseaudio + Nokia N900 (FM Transmitter) + Radio FM

== Schedule ==
* Stand: Samedi 12 mai 11h-17h
* Atelier: Samedi 12 mai 14h-14h45

== Participants ==
* [[User:Rorist]]
* [[User:Pherjung]]
* [[User:Marv]]
* [[User:Oenvoyage]]
* [[User:BinaryBrain]]
* you

LibreEtVous2018

2018-04-29T13:18:33Z

Pherjung: /* Atelier scratch */

[[Category:Ongoing_Projects]]
== Description ==
* Participation à l'événement Libre Et Vous à Lausanne au centre Pôle Sud
* https://libreetvous.ch/

== Goal ==
* Avoir un stand pour présenter l'association
* Donner un atelier Scratch d'introduction à la programmation

== Component ==
=== Atelier scratch ===
* Des laptops avec scratch installé ou si accès internet qui puisse faire tourner la version html5
* https://preview.scratch.mit.edu/
* On a 12 clés USB installées avec un Linux et Scratch, il faut tester ça sur 10-12 laptops

=== Stand ===
* Printrbot (Rorist)
* Ecran avec Rpi pour présenter l'association
* Petits montages electronique
* Lock picking
* Drapeau et stickers FIXME

== Schedule ==
* Stand: Samedi 12 mai 11h-17h
* Atelier: Samedi 12 mai 14h-14h45

== Participants ==
* [[User:Rorist]]
* [[User:Pherjung]]
* [[User:Marv]]
* [[User:Oenvoyage]]
* [[User:BinaryBrain]]
* you

LibreEtVous2018

2018-04-27T09:16:02Z

Pherjung: /* Participants */

[[Category:Ongoing_Projects]]
== Description ==
* Participation à l'événement Libre Et Vous à Lausanne au centre Pôle Sud
* https://libreetvous.ch/

== Goal ==
* Avoir un stand pour présenter l'association
* Donner un atelier Scratch d'introduction à la programmation

== Component ==
=== Atelier scratch ===
* Des laptops avec scratch installé ou si accès internet qui puisse faire tourner la version html5
* https://preview.scratch.mit.edu/

=== Stand ===
* Printrbot (Rorist)
* Ecran avec Rpi pour présenter l'association
* Petits montages electronique
* Lock picking

== Schedule ==
* Stand: Samedi 12 mai 11h-17h
* Atelier: Samedi 12 mai 14h-14h45

== Participants ==
* [[User:Rorist]]
* [[User:Pherjung]]
* [[User:Marv]]
* [[User:Oenvoyage]]
* [[User:BinaryBrain]]
* you

User:Phervieux

2018-04-27T09:15:39Z

Pherjung: Blanked the page

User:Pherjung

2018-04-27T09:15:33Z

Pherjung: /* My projects (old and active): */

Hi, I'm pherjung :)

At Fixme I mostly do speaking, but I'm trying to do nice stuff too :)

* [https://twitter.com/pherjung Twitter]
* [https://github.com/phervieux Github]
* [https://git.fixme.ch/pherjung Gogs]
* contact: patrick [dot] hervieux+wiki_fixme 100 0000 pherjung 010 1110 ch

== My projects (old and active): ==
* [https://git.fixme.ch/FIXME/autoclose Autoclause.sh] with the help of [[User:Rorist|Rorist]]
* [https://git.fixme.ch/gustavo/spectro-pointer Spectro Pointer] with Gustavo from Hackuarium
** I'm not the leader of this project and I'm only trying to bring my small knowledge to Gustavo
* Workshop with [[ArduBlock]]

User:Pherjung

2018-04-27T09:15:05Z

Pherjung:

Hi, I'm pherjung :)

At Fixme I mostly do speaking, but I'm trying to do nice stuff too :)

* [https://twitter.com/pherjung Twitter]
* [https://github.com/phervieux Github]
* [https://git.fixme.ch/pherjung Gogs]
* contact: patrick [dot] hervieux+wiki_fixme 100 0000 pherjung 010 1110 ch

== My projects (old and active): ==
* [https://git.fixme.ch/FIXME/autoclose Autoclause.sh] with the help of [[User:Rorist|Rorist]]
* [https://git.fixme.ch/gustavo/spectro-pointer Spectro Pointer] with Gustavo from UC
** I'm not the leader of this project and I'm only trying to bring my small knowledge to Gustavo
* Workshop with [[ArduBlock]]

User:Phervieux

2018-04-27T09:13:08Z

Pherjung:

Hi, I'm pherjung :)

At Fixme I mostly do speaking, but I'm trying to do nice stuff too :)

* [https://twitter.com/pherjung Twitter]
* [https://github.com/phervieux Github]
* [https://git.fixme.ch/pherjung Gogs]
* contact: patrick [dot] hervieux+wiki_fixme 100 0000 pherjung 010 1110 ch

== My projects (old and active): ==
* [https://git.fixme.ch/FIXME/autoclose Autoclause.sh] with the help of [[User:Rorist|Rorist]]
* [https://git.fixme.ch/gustavo/spectro-pointer Spectro Pointer] with Gustavo from UC
** I'm not the leader of this project and I'm only trying to bring my small knowledge to Gustavo
* Workshop with [[ArduBlock]]

Repair cafe

2018-03-28T18:56:07Z

Pherjung: /* Comment */

Projet en collaboration avec l'EVAM. En bref, monter une mesure d'occupation pour les requérants d'asile et bosser ensemble sur un Repair Café ouvert au publique.

== Acteurs ==

* EVAM
* FIXME
* Requérants d'asile

== Meta-objectifs ==

* Partager le savoir faire technique des membres de FIXME en faveur d'une population marginalisé.
* Favoriser le contact entre les requérants d'asile et la population pour perde "la peur de l'autre".
* Lutter contre l'obsolescence programmé, il faut réparer au lieu de jeter.

== Comment ==

# S'entraîner avec du matériel défectueux issu des déchetteries
# Former les requérants à devenir réparateurs.
# Mini-conferences (20 min) sur des sujets et concepts de bases.
# Utiliser les réparateurs pour faire le pont avec la communauté de requérants, et leurs rendre un service qui leurs est utile.
# A travers des cafés réparation donner au publique la possibilité de réparer leurs possession et aprende a connaître leurs appareils.

== Axes de Formation ==

* Electricité: Fer à souder et voltmètre, les bases de l'électronique.
* Demos: Senseurs d'Android, comment votre smartphone fait pour être si magique, suite demo VR.
* Demistification: Oser ouvrire son appareil, expliquer le fonctionnement.
* Boot process: Que ce passe entre le hardware et le OS, introduction au dual-boot.
* Root process: prendre control de son téléphone, via install party.
* Organisation d'atelier: quels outils utiliser, ou les trouver, conseils de sécurité, competances transversales en environnement technique.
* Productivité: Comment utiliser son smartphone pour autre chose que Facebook et WhatsApp, comment s'intégrer a la société technologique Suisse.
* Configuration: Comment se débarrasser du BloatWare, via checklist et recommandations d'apps. Introduction au système de permissions Android.
* Contrôle parental: limiter les comportements nocifs de votre enfant sur Android.

== Ligne directrice ==

La mesure est destiné à des requérants aillant une prédisposition technique, pour les encourager à poursuivre une formation ou un travail dans les domaines STEM. L'accent est mis sur la découverte et la maîtrise des notions de base, surtout le savoir être en milieu professionnel.

== Wishlist matérielle ==
* Kits de réparation iFixIt
* Fers à souder
* Rétroprojecteur
* Kit Chromecast
* Four pour les vitres de smartphone
* Aspirateur de PC

== Participants ==
* [[User:pherjung]]
* [[User:silent]]
* [[User:binarybrain]]

Repair cafe

2018-02-01T18:06:46Z

Pherjung: /* Repair Café */

Projet en collaboration avec l'EVAM.

== Participant ==
* [[User:pherjung]]

Repair cafe

2018-02-01T18:06:35Z

Pherjung: Created page with "= Repair Café = Projet en collaboration avec l'EVAM. == Participant == * User:pherjung"

= Repair Café =
Projet en collaboration avec l'EVAM.

== Participant ==
* [[User:pherjung]]

T-shirt FIXME

2016-12-01T10:58:01Z

Pherjung: /* Printing companies */

[[Category:Ongoing_Projects]]

== Information ==
* Order custom T-shirts for FIXME
* Sizes: http://www.doodle.com/vwqkhkhf2yck9vk4
* TODO: A tshirt with the Mateist logo on the back http://hsbp.org/polo&highlight=mateist

== Printing companies ==
* Artist making shirts: http://ybdesign.ch/
* http://creacom.ch/
* http://shirtcity.com/ (t-shirt à l'unité possible)
* http://www.affirmatif90.com/ (the one we used for the 1st batch in 2012, website out of date)
* http://unitedprint.ch/?sid=5348421d1f4593f58e255d98487036ee&pg=kalkulieren&item_group=75&view_group=2&element_id=17450

== 2015 batch ==
* <s>Vote: https://framadate.org/89v4c47n2j9aihh5</s>
* Vote: https://framadate.org/ivsdse29otvvm58w

=== Everysky ===
[[File:everysky_version_0.jpg|150px]]

=== Crazygolem ===
'''Back'''<br>
[[File:Proposition tshirt crazygolem.jpg|150px]]
* This is not the final design!
** It should have 59 labeled "holes" (if I counted correctly)
** Also it will probably have holes around the "FIXME" text too, instead of the frame
** The circuits might be drawn as in real life (e.g. optimized for length or other factors unknown to me)
* The design should be big enough to fill the t-shirt on the back, at least in width

'''Front'''<br>
The FIXME logo and text on the chest.

=== Rorist ===
==== Version 1 - The Greedy ====
* The hackerspace [[Media:rocket.svg|rocket]], with the moto on the front
* The FIXME text logo on the back
* The head logo on the shoulders
[[File:Proposition_tshirt_rorist.svg|100px]]
* Version 1b (the lesser greedy):
[[File:Proposition_tshirt_rorist_B.svg|100px]]

==== Version 2 - The Simple ====
* The FIXME text logo on the front, on the heart
* Hackerspace Lausanne text on the back
[[File:Proposition_tshirt_rorist2.svg|100px]]

==== Version 3 - The Mateist ====
* The FIXME text logo on the front, with the Mateist in the center
* Hackerspace Lausanne text on the back
[[File:Proposition_tshirt_rorist3.svg|100px]]

=== Nemen ===
==== Proposition 1: Massacre au drone ====
[[File:2015_nemen_tshirt_1.png|100px]]

==== Proposition 2: Hack! ====
[[File:2015_nemen_tshirt_2.png|100px]]

==== Proposition 3: Fixme since 2010 ====
[[File:2015_nemen_tshirt_3.png|100px]]

==== Proposition 4: Fixme College ====
[[File:2015_nemen_tshirt_4.png|100px]]

== 2012 batch ==
=== First proposition ===
[[File:Proposition_tshirt.svg|100px]]

* It can be cool to have custom t-shirt for everyone with (IRC) nickname (or other string like HACKER, MAKER, ROOT, STAFF, TEAM, TROLL :) ) on the back, but it can be optionnal.
* All remarks are welcome :)

=== Second proposition ===
We can realise a broderie polo for 21 Fr at http://www.art-image.ch/cgi-bin/marquages_textiles.php. I would propose to only have the fixme logo with fixme under it. They only make batch of 100 pieces.

=== Third proposition ===
* This has been ordered on the on december 2012
[[File:Proposition_tshirt2.svg|100px]]
[[File:Proposition_tshirt3.svg|100px]]
[[File:Proposition_tshirt4.svg|100px]]
[[File:Proposition_tshirt5.svg|100px]]
[[File:Proposition_tshirt6.svg|100px]]

==== Order at Quotation Affirmatif90 ====
http://www.affirmatif90.com/

* They provides 2 types of T-shirts:
** 150 g/m2 [[File:T-SHIRT-150G-B&C.pdf‎]]
** 190 g/m2 [[File:T-SHIRT-190G-B&C.pdf‎]]
* Submitted quantities: 12 M, 14 L, 8 XL and 2 XXL
* First batch (with do-ocraty spelled like in [https://en.wiktionary.org/wiki/democraty 1913])
[[File:Proposition_tshirt6.svg|200px]]
[[File:tshirt-final1.png|200px]]
* They did cost 13.70 CHF (Total TTC 404.73 Euro for 36 shirts)

{| class="wikitable centre" width="80%"
|-
! scope=col | Quantities !! scope=col | Description !! scope=col | P.U. !! scope=col | Total
|-
| width="10%" | 36 || width="50%" | B&C 150 G || width="20%" | 8.43 € || width="20%" | 303.48 €
|-
| width="10%" | 36 || width="50%" | B&C 190 G || width="20%" | 9.40 € || width="20%" | 338.40 €
|}

== Participant ==
* [[User:Nemen]]
* [[User:Rorist]]

== See also ==
* [[Logo]]

How to create an event

2016-10-01T13:48:12Z

Pherjung: /* Makerspace */ Fix typography error

Fixme is an excellent place to organise all your awesome events. We welcome everything relating to technology, electronics, hacking, making, meetups, cryptocurrencies, competitions, talks, conferences, (relevant) politics, and much more! We already hold numerous events every month - at least one event a week, with one large event a month at a minimum. Check out our [https://www.google.com/calendar/ical/sruulkb8vh28dim9bcth8emdm4%40group.calendar.google.com/public/basic.ics calendar]!

== Location ==
=== Fixme ===
'''Capacity''': 20 people

You are encouraged to organize events here at any time! (Wednesday evenings may be a bit cramped though)

=== Makerspace ===
'''Capacity''': however many you can fit in 250m²

You can organize events here for anything to do with electronics, making, woodworking, laser cutting, plasma cutting, CNC machining, or other projects that wouldn't fit into fixme. Usage of machines requires a belt, and if your belt color isn't blue or higher, someone with that has to be present. The exact protocol for organizing events here is still in beta; '''you need to talk to Marc (the makerspace manager) before planning anything'''.

=== Meetup space ===
'''Capacity''': 60+ people

Great for larger events, generally unavailable on Wednesday evenings, more and more solicited on Tuesday and Thursday nights. '''You need to talk to UniverCité's Community Manager before planning anything.''' Requires being added to UC calendar (see below) AFTER that to avoid overbooking.

=== Coworking Rooms ===
'''Capacity''': 10 people for big one (aka coworking meeting room), 5 people for small one (aka le bocal / la war room)
'''Priority is always given to coworkers. You need to talk to UniverCité's Community Manager before planning anything.''' Requires being added to UC calendar (see below) AFTER that to avoid overbooking.

== Questions to answer first ==
* What is the topic? (i.e. Coding Night, Cryptoparty, Talk, Workshop, ...)
* What is the target? (i.e. Fixme members, extern people, adults, children, ...)
* What resources are required? (i.e. the hackerspace, electronics tools, electronics parts, ...)
* Who can help me to organize? (i.e. things can be done faster/easier if you do not try to do it alone)
* Is the date available ?

== Plan the event ==
The person responsible for events is [[User:Pherjung|Pherjung]], feel free to contact him (''pherjung at fixme dot ch'') at any time to organize events. If you want to organize events in the UniverCité (UC) space, please cc Carmelo (''carmelo dot bisognano at inartis dot ch'') as well.
* Create a wiki page using the [[Project_template|project template]].
* Get/Order the resources to be sure to get it on time.
* Check the [https://www.google.com/calendar/embed?src=sruulkb8vh28dim9bcth8emdm4%40group.calendar.google.com&ctz=Europe/Zurich Fixme Event] calendar to find possible dates for the event.
* Check the [https://www.google.com/calendar/embed?src=eru0rpe6q4ra6l966v11pcp1a0%40group.calendar.google.com&ctz=Europe/Zurich UC event calendar] to make sure the room you have in mind is not booked already ([https://www.google.com/calendar/ical/eru0rpe6q4ra6l966v11pcp1a0%40group.calendar.google.com/public/basic.ics UC iCal])
* Open a [http://framadate.org/ Framadate] and spread the word (Mailing-List, IRC, weekmail, twitter, facebook, ...).
* Select the most popular date (yes, it's obvious, I know...)
* Plan the event early: 1 month is good most of the times, the earlier the better

== Communicate about the event ==
* Think about a poster to promote your event (There is a poster template for Fixme events). [[File:poster.tgz]]
* Once the date is known, [[Communication|promote!]]
** spread the info on the [https://lists.saitis.net/cgi-bin/mailman/listinfo/hackerspace-lausanne mailing list],
** update the wiki page with this date,
** update the topic on #Fixme IRC chan,
** create an event on the Fixme Facebook page,
** post the event and date on Twitter,
** prepare a short description for the weekmail.
** <s>You may use events script to create event https://github.com/fixme-lausanne/events (FIXME it's broken)</s>
* Communicate 1 week and the day before the event (people tend to forget)

How to create an event

2016-10-01T13:47:31Z

Pherjung: Fix some spelling errors

Fixme is an excellent place to organise all your awesome events. We welcome everything relating to technology, electronics, hacking, making, meetups, cryptocurrencies, competitions, talks, conferences, (relevant) politics, and much more! We already hold numerous events every month - at least one event a week, with one large event a month at a minimum. Check out our [https://www.google.com/calendar/ical/sruulkb8vh28dim9bcth8emdm4%40group.calendar.google.com/public/basic.ics calendar]!

== Location ==
=== Fixme ===
'''Capacity''': 20 people

You are encouraged to organize events here at any time! (Wednesday evenings may be a bit cramped though)

=== Makerspace ===
'''Capacity''': however many you can fit in 250m^2

You can organize events here for anything to do with electronics, making, woodworking, laser cutting, plasma cutting, CNC machining, or other projects that wouldn't fit into fixme. Usage of machines requires a belt, and if your belt color isn't blue or higher, someone with that has to be present. The exact protocol for organizing events here is still in beta; '''you need to talk to Marc (the makerspace manager) before planning anything'''.

=== Meetup space ===
'''Capacity''': 60+ people

Great for larger events, generally unavailable on Wednesday evenings, more and more solicited on Tuesday and Thursday nights. '''You need to talk to UniverCité's Community Manager before planning anything.''' Requires being added to UC calendar (see below) AFTER that to avoid overbooking.

=== Coworking Rooms ===
'''Capacity''': 10 people for big one (aka coworking meeting room), 5 people for small one (aka le bocal / la war room)
'''Priority is always given to coworkers. You need to talk to UniverCité's Community Manager before planning anything.''' Requires being added to UC calendar (see below) AFTER that to avoid overbooking.

== Questions to answer first ==
* What is the topic? (i.e. Coding Night, Cryptoparty, Talk, Workshop, ...)
* What is the target? (i.e. Fixme members, extern people, adults, children, ...)
* What resources are required? (i.e. the hackerspace, electronics tools, electronics parts, ...)
* Who can help me to organize? (i.e. things can be done faster/easier if you do not try to do it alone)
* Is the date available ?

== Plan the event ==
The person responsible for events is [[User:Pherjung|Pherjung]], feel free to contact him (''pherjung at fixme dot ch'') at any time to organize events. If you want to organize events in the UniverCité (UC) space, please cc Carmelo (''carmelo dot bisognano at inartis dot ch'') as well.
* Create a wiki page using the [[Project_template|project template]].
* Get/Order the resources to be sure to get it on time.
* Check the [https://www.google.com/calendar/embed?src=sruulkb8vh28dim9bcth8emdm4%40group.calendar.google.com&ctz=Europe/Zurich Fixme Event] calendar to find possible dates for the event.
* Check the [https://www.google.com/calendar/embed?src=eru0rpe6q4ra6l966v11pcp1a0%40group.calendar.google.com&ctz=Europe/Zurich UC event calendar] to make sure the room you have in mind is not booked already ([https://www.google.com/calendar/ical/eru0rpe6q4ra6l966v11pcp1a0%40group.calendar.google.com/public/basic.ics UC iCal])
* Open a [http://framadate.org/ Framadate] and spread the word (Mailing-List, IRC, weekmail, twitter, facebook, ...).
* Select the most popular date (yes, it's obvious, I know...)
* Plan the event early: 1 month is good most of the times, the earlier the better

== Communicate about the event ==
* Think about a poster to promote your event (There is a poster template for Fixme events). [[File:poster.tgz]]
* Once the date is known, [[Communication|promote!]]
** spread the info on the [https://lists.saitis.net/cgi-bin/mailman/listinfo/hackerspace-lausanne mailing list],
** update the wiki page with this date,
** update the topic on #Fixme IRC chan,
** create an event on the Fixme Facebook page,
** post the event and date on Twitter,
** prepare a short description for the weekmail.
** <s>You may use events script to create event https://github.com/fixme-lausanne/events (FIXME it's broken)</s>
* Communicate 1 week and the day before the event (people tend to forget)

Main Page

2016-10-01T13:37:14Z

Pherjung: /* Association */ Fix typography error

__NOTOC__
{{Boite
| titre=Welcome to FIXME
| bordure=black
| fond=lightgray
| couleurTitre=black
| couleurTexteTitre=white
| largeur=75%
| flotte=left
}}
This is the working wiki of the FIXME Hackerspace, main website is at https://fixme.ch
{{BoiteFin}}

<div class="nomobile">
{{Boite
| couleurTexteTitre=white
| largeur=20%
| flotte=right
}}
https://fixme.ch/sites/default/files/hackerspace_status.png
[http://foo.fixme.ch/trigger.html Open/close the space]
{{BoiteFin}}
</div>

{{Boite
| titre=[[:Category:Projects|Projects]]
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Projects.png}}
* [[:Category:Ongoing_Projects|Ongoing]] | [[:Category:Proposed_Projects|Proposed]] | [[:Category:Closed_Projects|Closed]] | [[:Category:Canceled_Projects|Canceled]]
* [[Project template]] | [[Projects Ideas]]

===Top projects===
* [[Coursera_Microcontroleur]]
* [[Langage_VHDL]]
* [[SDR|Software Defined Radio]]
* [[SpaceAPI|MyHackerspace]]
* [[Long_André]]
* [[Multicopter]]
* [[EuropeanMakerWeek2016]]
{{BoiteFin}}

{{Boite
| titre=Events
| flotte=right
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Events.png}}

===Recuring events===
* '''Wednesdays''':
** Every wednesdays [[Weekly Meetings]] (social meeting, newcomers welcoming)
** Last wednesday of the month: Monthly Cleaning
* '''Thursdays''':
** Third Thursday is [[3D Thursdays]]!
** Once a month: [[CTF]] (CTF meeting, writeups, courses)
* '''Fridays''':
** Some fridays Afterwork

=== Canceled events ===

If somebody wants to revive an event, you're welcome to do so!

* Every first sunday of the month: [[GameDev|Game development group]]
* First thursday of the month: [[LUG]] (GNU/Linux help/discussions)
* Every fridays [[Electronics evening]]
* Some friday evening [[CTFriday]] (hacking challenges)
* Second Tuesday of the month: [[dbms workshop]] (Work with RDBMS or ohers DBMS)
* Third Tuesday of the month : Création du [[ FIXME Coin ]]
* Forth Tuesday of the month : [[Raspberry Pi Buy|Workshop Raspberry Pi]]
* First Thursday: [[Spacenerd]]

===Ponctual events===
* [[:Category:CodingNight|Coding Night]]
* [[:Category:Workshops|Workshops]]
* [[:Category:WeekendProjects|Weekend Projects]]
* [[:Category:ShortTalks|Short Talks]]
* [[:Category:Debates|Debates]]
* [[:Category:Conferences|Conferences delegation]]
* [[Suggestion box]]

====[[How to create an event?]]====
{{BoiteFin}}

{{Boite
| titre=Makerspace
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* 230m^2 UniverCity workshop
* [[Atelier_machines]]
* [[PCB_Etching]]
* 3D Printers (currently within FIXME)
** [[Ultimaker]]
** [[PrintrbotSimple]]
{{BoiteFin}}

{{Boite
| titre=Electronic
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* [[Parts Order]]
* [[:Category:ElectroKit|Electronic kits]]
* [[Electronic FAQ]]
* [[CPU_Boards]]
* [[Electro_docs]]
* [[Kicad]]
* [[Stock_electronique]]
* Documentation
** [[ESP8266]]
{{BoiteFin}}

{{Boite
| titre=More
| flotte=left
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Other.png}}
* Equipment
** [[What do we provide ?]]
** [[What are we looking for ?]]
* [[Foo]], our internal services server
* [[Resources]] (local associations, events and shops)
* [[Movies|Geek movies]]
* [[Modele XP]]
* [[Sandbox]] for syntax tests
* [[Burgers]]
* [[Podcasts]]
* [[OpenData]]
* [[Raspberry_Pi]]
* [[Bitcoin_ATM]]
* [[Chat]]
{{BoiteFin}}

{{Boite
| titre=Administration
| flotte=right
| bordure=black
| fond=lightgray
| couleurTitre=gray
| couleurTexteTitre=white
| largeur=49%
| icon=Administration.png}}

=== Meetings ===
* [[:Category:Meetings|All Meetings]]
* [[:Category:ProjectMeetings|Project Meetings]]
* [[:Category:AG|General Assemblies]]

=== Association ===
* [[Internal Regulation]] [French]
* [[Utilité_publique]]: [https://pad.fixme.ch/p/letter_to_lausanne subventions], ...
* [[Membership_admin]]
* [[Accounts|What to do with new member?]]
* [[History]]
* [[Odoo]]
** Register expense
** Pay membership
** etc.

=== Other ===
* [[Openings]]
* [[Communication]]
* [[:Category:Weekmail|Weekly mail]] on upcoming activities
* [[Press_reviews]]
* [[Press_kit]]
* [[Network]]
* [[:Category:Services]]
* [[Logo]]
* [[Local]]
* [[Sheets]] (various documents)
* [[HowToWiki|How to edit the wiki]]
{{BoiteFin}}
{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}

Raspberry Pi

2016-10-01T13:31:55Z

Pherjung: Add link to verified SD Cards

Page showing some useful RPi information. Don't hesitate to contribute! Keep in mind that this is aimed at people who aren't necessarily competent with linux or electronics in general.
== Setup ==
# Download [http://downloads.raspberrypi.org/NOOBS_lite_latest NOOBS], a simple to use installer that requires no command line knowledge
# Find an empty [http://elinux.org/RPi_SD_cards SD or microSD] card (minimum 2gb/class 6, 4gb/class 10 recommended - try to find cards with UHS-1), make sure it's FAT32, and then extract all the files from the NOOBS zip onto it
# Plug in the SD card, an HDMI or composite display, a ethernet cable, usb keyboard + mouse, and a ''good'' 5v power supply (seriously - a lot of issues come from low power/fake power supplies) [[File:RasperrySetup.jpg|500px]]
# Power on the Pi, and wait a few seconds until you reach the screen below. Select Raspbian, click install, and wait a few minutes - the Pi should take 20-60 minutes to install depending on your internet connection and SD card. [[File:NOOBS.png|500px]]
# After installation is complete, the 'Raspberry Pi Software Configuration Tool' pop up. You can skip this step ''but'' it's recommended that you change the following: [[File:Raspi-config.png|500px]]
## '''Change User Password''' to something that you can remember - default one is raspbian
## '''Enable boot to Desktop''' select whether you want to boot to console (ideal for servers and remote access), or desktop (for projects that display something, or if you want to set up the pi directly on itself)
## '''Internationalisation Options'''
### '''Change locale''' to en_US.UTF-8 for everything, other options will break things later
### '''Change keyboard layout''' to German Switzerland -> Swiss French, this part is a must if you're used to fr_ch keyboards
## '''Advanced Options''' -> '''Hostname''' to something easy to find, such as 'raspberrypi-yourname'
# Click on finish, reboot your Pi, and you're good to go!

<pre>

Hackers guide, only do this if you know what you're doing - you could wipe the wrong device!

wget http://downloads.raspberrypi.org/raspbian_latest && unzip raspbian_latest
umount /dev/sdd1
dd bs=4M if=2015-02-16-raspbian-wheezy.img of=/dev/sdd
##progress won't be evident, run 'pkill -USR1 -n -x dd' in another window to see it
sync
##remove SD card and copy steps 3 and 5 above

## Configuration tool with menus / Outil de configuration par menu :
raspi-config

## Ddefault user / Utilisateur par défaut : pi

</pre>

=== WiFi ===
If you have a WiFi stick that is directly compatible with Raspbian, follow the instructions bellow. If it's not, then you'll need to troubleshoot with Google.

[http://www.debuntu.org/how-to-wifi-roaming-with-wpa-supplicant/ WPA supplicant setup] with different settings for different networks

=== Headless setup ===

If you don't want to connect a keyboard and monitor to your RPi, you can perform a [[Raspberry Pi: Headless installation|headless installation of Raspbian]] instead of using NOOBS.

== Screen blanking ==
add the following lines to /etc/xdg/lxsession/LXDE/autostart, remove the line with the screensaver option

@xset s off
@xset -dpms
@xset s noblank

== Software ==
=== Web server (Apache) ===
sudo apt-get install apache2

Then you can edit files in /var/www/
=== Wiki ===
==== Intro ====
Utiliser un Raspberry Pi pour remplacer un serveur AMD 64 bit est ce réaliste pour héberger un wiki?

Lors de la sortie du modèle B+ en novembre je me suis lancé dans l'aventure d'installer un wikimedia sur le Raspberry Pi en ma possession .

==== mediawiki ====

Afin de minimiser l'utilisation des ressources et compte-tenu de mon besoin j'ai opté pour une installation avec sqllite3 .

Et si le wiki est visible il est d'une lenteur affligeante :-( voyez par vous même belorne .

La faute me semble-t-il à PHP et à la programation de mediadwiki qui est bien trop lourde pour une si petite machine.

Il faut oublier une telle idée, si ce n'est pour jouer .

==== Une autre solution ====

Oui biensur il y en a bcp mais pour une tel machine , la solution la plus ligth mais aussi la plus simple c'est MDwiki.

Un wiki en langage de description de page Markdown.

Je ne vais pas décrire les étapes de cette installation , juste vous donner des liens permettant de comprendre comment cela est faisable.

Les composants :

* Un rapsberry Pi B+
* Os Raspbian 3.12.35+
* Mdwiki [[http://dynalon.github.io/mdwiki/#!index.md Site]]
* 2 comptes Google Drive
* [[https://www.insynchq.com/ insync]] version RaspberryPi

Voici le [[http://boizot.ch/ résultats]]

Comment cela marche ?

Trés trés simplement. de mon portable je peux éditer n'importe quel fichier du site , en changer les liens....
Le tout est quasi immédiatement mise à jour sur le dossier de mon Raspberry Pi qui est synchroniser en temps .

==== Conclusion ====
Biensur on est bien loin de Mediawiki ou de MoinsMoins.

Then you can edit files on your laptop.

=== Push notifications ===
You can send push notifications with Pushbulltet on various events, such as booting your Pi. Let's start off with a script that sends you a push notification with your IP when you turn on your Pi:
nano piip.sh
Paste this inside, and replace the example keys with your own keys:
#!/bin/bash
ipVar=$(/sbin/ifconfig eth0 | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}')
curl https://api.pushbullet.com/v2/pushes \
-u <paste_your_API_key_here>: \
-d device_iden="<device_ID_of_your_phone>" \
-d type="note" \
-d title="Pi IP address" \
-d body=$ipVar \
-X POST

Set permissions to allow it to execute:
sudo chmod 777 piip.sh

Open the crontab:
sudo crontab -e

Then paste at the bottom of the crontab:
@reboot /home/pi/piip.sh

[https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=79151 Documentation]

== Hardware ==
=== GPIO ===
git clone git://git.drogon.net/wiringPi
cd wiringPi/
./build

Then set a pin to output
gpio [-g] mode <pin> in/out/pwm/up/down/tri
gpio -g mode 13 out #for example

Use the pin
gpio -g write 13 1

[https://projects.drogon.net/raspberry-pi/wiringpi/the-gpio-utility/ Documentation]

[https://github.com/sarfata/pi-blaster PWM library]

Accounts

2016-05-11T18:49:05Z

Pherjung: /* Checklist for new comer */

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create mattermost account
* Send welcome PDF
* Invite new member to create a wiki account
* Pass on our [[Internal_Regulation|internal regulation]]
* Pass on our [https://fixme.ch/status status]
* Reception subscription date (form)
* Get his address

== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
* Enable access on Google Docs
* Give the key to the comitee locker

=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website

== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
* Disable access on Google Docs
* Get back the comitee locker key
* Date reception e-mail to quit Fixme

=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

Accounts

2016-05-09T21:33:17Z

Pherjung: /* Checklist for new comer */

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create slack account
* Invite new member to create a wiki account
* Pass on our [[Internal_Regulation|internal regulation]]
* Pass on our [https://fixme.ch/status status]
* Reception subscription date (form)
* Get his address

== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
* Enable access on Google Docs
* Give the key to the comitee locker

=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website

== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
* Disable access on Google Docs
* Get back the comitee locker key
* Date reception e-mail to quit Fixme

=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

Arduino Day 2016

2016-04-22T07:05:29Z

Pherjung:

[[Category:Ongoing_Projects]]
== Description ==
* Participation à l'événement global Arduino Day 2016
* Date: samedi 2 avril 2016
* Horaires: TBD (10h -> 18h?)
* Pad d'organisation: https://pad.fixme.ch/p/arduino-day

== Goal ==
* Attirer un large public pour découvrir et/ou manipuler Arduino
* Promouvoir Fixme
* Inclure les associations amies (Hackuarium, PTL, Chêne 20, etc.)

== Animations ==

=== Workshops ===
Workshop d'environ 45min à 1h30 pour des jeunes de 10 ans à 90 ans.

=== Présentations ===
* TBD

=== Stands ? ===
* Fixme
* Partenaires

== Obstacles ==
* Financement des cartes Arduino et composants pour les workshops

== Account (French) ==
You will find the account in french [[File:Arduinoday.txt]]
== Participants ==
* [[User:Pherjung]] (co-Leader)
* [[User:nemen]] (co-Leader)
* [[User:philoux]]

File:Arduinoday.txt

2016-04-22T06:52:59Z

Pherjung: Compte rendu de l'Arduino Day ayant eu lieu début avril 2016.

Compte rendu de l'Arduino Day ayant eu lieu début avril 2016.

Arduino Day 2016

2016-04-22T06:49:32Z

Pherjung: /* Goal */ Fix error on name fablab Renens

[[Category:Ongoing_Projects]]
== Description ==
* Participation à l'événement global Arduino Day 2016
* Date: samedi 2 avril 2016
* Horaires: TBD (10h -> 18h?)
* Pad d'organisation: https://pad.fixme.ch/p/arduino-day

== Goal ==
* Attirer un large public pour découvrir et/ou manipuler Arduino
* Promouvoir Fixme
* Inclure les associations amies (Hackuarium, PTL, Chêne 20, etc.)

== Animations ==

=== Workshops ===
Workshop d'environ 45min à 1h30 pour des jeunes de 10 ans à 90 ans.

=== Présentations ===
* TBD

=== Stands ? ===
* Fixme
* Partenaires

== Obstacles ==
* Financement des cartes Arduino et composants pour les workshops

== Participants ==
* [[User:Pherjung]] (co-Leader)
* [[User:nemen]] (co-Leader)
* [[User:philoux]]

Accounts

2016-04-13T17:59:01Z

Pherjung: /* Checklist for a person leaving the comité */

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create slack account
* Invite new member to create a wiki account
* Pass on our [[Internal_Regulation|internal regulation]]
* Pass on our [https://fixme.ch/status status]
* Reception subscription date (form)

== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
* Enable access on Google Docs
* Give the key to the comitee locker

=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website

== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
* Disable access on Google Docs
* Get back the comitee locker key
* Date reception e-mail to quit Fixme

=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

Accounts

2016-04-13T17:50:33Z

Pherjung: /* Checklist for new comer */

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create slack account
* Invite new member to create a wiki account
* Pass on our [[Internal_Regulation|internal regulation]]
* Pass on our [https://fixme.ch/status status]
* Reception subscription date (form)

== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
* Enable access on Google Docs
* Give the key to the comitee locker

=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website

== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
* Disable access on Google Docs
* Get back the comitee locker key

=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

Accounts

2016-04-10T16:35:25Z

Pherjung: /* Checklist for a person leaving the comité */

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create slack account
* Invite new member to create a wiki account
* Pass on our [[Internal_Regulation|internal regulation]]
* Pass on our [https://fixme.ch/status status]

== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
* Enable access on Google Docs
=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website

== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
* Disable access on Google Docs
=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

Accounts

2016-04-10T16:33:41Z

Pherjung: /* Checklist for new comer in comité */

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create slack account
* Invite new member to create a wiki account
* Pass on our [[Internal_Regulation|internal regulation]]
* Pass on our [https://fixme.ch/status status]

== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
* Enable access on Google Docs
=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website

== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

Accounts

2016-04-10T11:37:49Z

Pherjung: /* Checklist for new comer */

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create slack account
* Invite new member to create a wiki account
* Pass on our [[Internal_Regulation|internal regulation]]
* Pass on our [https://fixme.ch/status status]

== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website
== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

Accounts

2016-04-09T09:37:31Z

Pherjung: Created page with "= Checklist for creating or deleting accounts = == Checklist for new comer == * Bulding key * Local key * Compartement key and number * Create slack account * Invite new membe..."

= Checklist for creating or deleting accounts =
== Checklist for new comer ==
* Bulding key
* Local key
* Compartement key and number
* Create slack account
* Invite new member to create a wiki account
== Checklist for new comer in comité ==
* Create @fixme.ch address
* Add personal @fixme.ch address in group comite@fixme.ch
* Invite user at channel #comite
* Create Odoo account
=== Checklist for communication responsable ===
* Access at fixme twitter account
* Access at fixme facebook account
* Access at drupal account for editing the website
== Checklist for a person leaving fixme ==
* Bulding key
* Local key
* Compartement key
* Remove slack account
== Checklist for a person leaving the comité ==
* Remove @fixme.ch address
* Remove personal @fixme.ch address in group comite@fixme.ch
* Remove user from channel #comite
* Remove Odoo account
=== Checklist for communication responsable ===
* Remove access at fixme twitter account
* Remove access at fixme facebook account
* Remove access at drupal account for editing the website

ArduBlock

2016-03-17T23:49:27Z

Pherjung:

I made some exercises and solutions using [http://blog.ardublock.com/ ArduBlock] over [https://www.arduino.cc/ Arduino] and [http://fritzing.org/home/ Fritzing] for the diagrams. [http://blog.ardublock.com/ ArduBlock] is very simple to use and that's why I would like to teach to child how to manipulate LEDs, servos and a lot of other nice small stuff with arduino. You will find the exercises on this repository: [https://git.fixme.ch/pherjung/workshop_arduino Arduino Workshop]. Feel free to contribute it !

== Participant ==
* [[User:Pherjung]]
* you... :-D

Arduino Day 2016

2016-03-17T23:49:04Z

Pherjung:

[[Category:Ongoing_Projects]]
== Description ==
* Participation à l'événement global Arduino Day 2016
* Date: samedi 2 avril 2016
* Horaires: TBD (10h -> 18h?)
* Pad d'organisation: https://pad.fixme.ch/p/arduino-day

== Goal ==
* Attirer un large public pour découvrir et/ou manipuler Arduino
* Promouvoir Fixme
* Inclure les associations amies (Hackuarium, PTL, Chene20, ...)

== Animations ==

=== Workshops ===
Workshop d'environ 45min à 1h30 pour des jeunes de 10 ans à 90 ans.

=== Présentations ===
* TBD

=== Stands ? ===
* Fixme
* Partenaires

== Obstacles ==
* Financement des cartes Arduino et composants pour les workshops

== Participants ==
* [[User:Pherjung]] (co-Leader)
* [[User:nemen]] (co-Leader)
* [[User:philoux]]

ElectroJam6

2016-03-17T23:48:47Z

Pherjung:

[[Category:Ongoing_Projects]]
== Description ==
''In French'' :

Après une très longue interruption les '''ElectroJam''' reviennent en 2016. La prochaine aura lieu le : '''le 08 janvier 2015'''

Mais qu'est-ce donc qu'une ElectroJam à FIXME : le/la participant(e) jouera à nouveau quelques partitions à base d'électronique, d'informatique et de mécanique, pour que des projets commencent à prendre vie durant cette soirée ! Cela peut aller de la modification d'éléments existant et la création d'éléments sortis droit de votre imagination... La partition que vous composerez durant cette soirée soit sera achevée en un soir (good job), ou au contraire permettra de se replonger dans d'autres soirée à Fixme...

''In English'' :

After a pause, '''ElectroJam''' will resume in 2016. The next one will be on the : the 08 January 2015

So what is this Electrojam at Fixme? It's a night dedicated to bringing our electronics, software, and hardware knowledge together, with the goal to create a minimal viable product by the end of the night. Think of it as a hackathon to make something awesome. Pizza included.

Previous events : [[ElectroJam1]] // [[ElectroJam2]] // [[ElectroJam3]] // [[ElectroJam4]] // [[ElectroJam5]]

== Schedule ==
* DATE : '''The Friday : 08 January 2016''' (le '''vendredi 08.01.2016''')
* Time : from 20:00
* Event page:

== Goal ==
''In French'' :

Le but est d'utiliser les différents éléments qu'offre Fixme (composants, outils, apport de matériels de chacun) pour laisser exprimer le côté "brut" de la technique, et ainsi commencer, poursuivre ou terminer un/des projet durant cette soirée/nuit (pour les plus courageux).

''In English'' :

The idea behind the event is that you come and use the best of what Fixme offers, in order to create, continue, or finish (a) project(s) throughout the night; or to simply hang out and express your raw passion for technology. You'll have lots of components, parts, tools, and stuff others have bought, in order to help you achieve, or even surpass your goals.

Example activities :
---------------------
* Programming (uC, uP, web page, script,...)
* Electronics (making a prototype on protoboard or on PCB; using software such as KICAD, SCILABS, ... discover electronics components and their inner workings with their datasheets)
* Mechanical (3D printing, laser cutting, plebeian cutting, sawing, drilling,... )
* People (share knowledge, find out others, ...)

== Obstacles ==
* Your limits !!!
* Arrangement

== Components ==
* Electronics components (resistors, capacitors, diodes, transistors, ICs, uCs, uPs, motors, LEDs,...)
* Macs/Others
* Electronics Books
* Google
* Pizza
* Beer
* Stuff to open your spirit ( ͡° ͜ʖ ͡°)

== Project in the back ==

''In French''

Avec le lien ci-dessous, tu peux déjà choisir sur quel projet tu aimerais venir apporter, partager ou découvrir tes connaissances... n'hésite pas non plus a rajouter ton projet

''In English''

''Abhorrent attempt of English translation removed.''

Example of project :

* 3D-printed garde-boue pour trotinette
* Affichage Hack-CFF (suite)
* DMX protocole (Special Fixme RS485 home-made protocol)
* Odometer for a bike (suite)
* [[Coursera_Microcontroleur]] continuer sur les exos de la série 4
* Fixme_My_BaBBy
* VHDL prog
* your project

== Participants ==
* [[User:Binary_Brain]]
* [[User:Nemen]] ???
* [[User:gcmalloc]] ???
* [[User:Marcha]] ???
* [[User:Noskill]] ???
* [[User:Philoux]]
* [[User:Jhu]] ???
* [[User:Sasha]] ???
* [[User:Pherjung]] je prévois d'ouvrir le local vers 18:00 - 18:30
* and you (members or non members of Fixme) ???

== Photos ==
To be completed by your photos:
<gallery>
</gallery>

== Video ==

== See also ==
* [[ElectroJam1]]
* [[ElectroJam2]]
* [[ElectroJam3]]
* [[ElectroJam4]]
* [[ElectroJam5]]

ElectroJam5

2016-03-17T23:48:31Z

Pherjung:

[[Category:Closed Projects]]
== Description ==
''In French'' :

Après une interruption les '''ElectroJam''' reviennent en 2015. La prochaine aura lieu le : TBD

Mais qu'est-ce donc qu'une ElectroJam à FIXME : le/la participant(e) jouera à nouveau quelques partitions à base d'électronique, d'informatique et de mécanique, pour que des projets commencent à prendre vie durant cette soirée ! La partition peut-être achevée en un soir, ou au contraire être modifiée par la suite...

''In English'' :

After a pause, '''ElectroJam''' will resume in 2015. The next one will be on the : TBD

So what is this Electrojam at Fixme? It's a night dedicated to bringing our electronics, software, and hardware knowledge together, with the goal to create a minimal viable product by the end of the night. Think of it as a hackathon to make something awesome. Pizza included.

Previous events : [[ElectroJam1]] // [[ElectroJam2]] // [[ElectroJam3]] // [[ElectroJam4]]

== Schedule ==
* DATE : '''The Friday : 09 January 2015''' (le '''vendredi 09.01.2015''')
* Time : from 20:00
* Event page:

== Goal ==
''In French'' :

Le but est d'utiliser les différents éléments qu'offre Fixme (composants, outils, apport de matériels de chacun) pour laisser exprimer le côté "brut" de la technique, et ainsi commencer, poursuivre ou terminer un/des projet durant cette soirée/nuit (pour les plus courageux).

''In English'' :

The idea behind the event is that you come and use the best of what Fixme offers, in order to create, continue, or finish (a) project(s) throughout the night; or to simply hang out and express your raw passion for technology. You'll have lots of components, parts, tools, and stuff others have bought, in order to help you achieve, or even surpass your goals.

Example activities :
---------------------
* Programming (uC, uP, web page, script,...)
* Electronics (making a prototype on protoboard or on PCB; using software such as KICAD, SCILABS, ... discover electronics components and their inner workings with their datasheets)
* Mechanical (3D printing, laser cutting, plebeian cutting, sawing, drilling,... )
* People (share knowledge, find out others, ...)

== Obstacles ==
* Your limits !!!
** Remember to [https://www.youtube.com/watch?v=9D-QD_HIfjA push it to the limit]
* Arrangement

== Components ==
* Electronics components (resistors, capacitors, diodes, transistors, ICs, uCs, uPs, motors, LEDs,...)
* Macs/Others
* Electronics Books
* Google
* Pizza
* Beer
* Stuff to open your spirit ( ͡° ͜ʖ ͡°)

== Project in the back ==

''In French''

Avec le lien ci-dessous, tu peux déjà choisir sur quel projet tu aimerais venir apporter, partager ou découvrir tes connaissances... n'hésite pas non plus a rajouter ton projet

''In English''

''Abhorrent attempt of English translation removed.''

Example of project :

* Fixme_Y_choice (suite)
* 3D-printed garde-boue pour trotinette
* Affichage Hack-CFF (suite)
* DMX protocole (Special Fixme RS485 home-made protocol)
* Workshop Kicad / PCB (New)
* Odometer for a bike (suite)
* [[Coursera_Microcontroleur]] continuer sur les exos de la série 4
* [[Plastic_recycling]] Finir la conception du PCB
* your project

== Participants ==
* [[User:Binary_Brain]]
* [[User:Nemen]]
* [[User:gcmalloc]]
* [[User:Marcha]] ???
* [[User:Noskill]]
* [[User:Philoux]]
* [[User:Jhu]] ???
* [[User:Sasha]]
* [[User:Pherjung]] je prévois d'ouvrir le local vers 18:00 - 18:30
* and you (members or non members of Fixme) ???

== Photos ==
To be completed by your photos:
<gallery>
</gallery>

== Video ==

== See also ==
* [[ElectroJam1]]
* [[ElectroJam2]]
* [[ElectroJam3]]
* [[ElectroJam4]]

ElectroJam4

2016-03-17T23:48:14Z

Pherjung:

[[Category:Closed Projects]]
== Description ==
''In French'' :

Après une petite interruption les '''ElectroJam''' reprennent, celles-ci auront lieu 4x par années, mais qu'est-ce donc qu'une ElectrJam à FIXME : le/la participant(e) jouera à nouveau quelques partitions à base d'électronique, d'informatique et de mécanique, pour que des projets prennent vie !!!

''In English'' :

After a pause, '''ElectroJam''' will start again, taking place 4 times a year. But what is the ElectroJam at FIXME? It's an event/hackathon where anyone can com and play with electronics, computers, and mechanical stuff, so that some projects come to live !!!

Past events : [[ElectroJam1]] // [[ElectroJam2]] // [[ElectroJam3]]

== Schedule ==
* DATE : the september 12, 2014
* Time : from 20:00
* Event page:

== Goal ==
''In French'' :

Durant cette soirée/nuit (pour les plus courageux), le but est d'utiliser les différents éléments qu'offre le Fixme (composants, outils, apport de matériels de chacun) pour laisser s'exprimer le côté "brut" de la technique, et ainsi commencer, poursuivre ou terminer un/des projet

''In English'' :

During this evening/night, the goal is to start, continue or finish a project (or several); using different resources available at Fixme (components, tools, gifts user) to leave your spirit express to begin, .

Activities examples :
---------------------
* Programming (uC, uP, web page, script,...)
* Electronics (making a prototype on protoboard or on PCB; using software such as KICAD, SCILABS, ... discover electronics components and their working with datasheet)
* Mechanical (3D printing, cutting, sawing, drilling,... )
* People (share knowledge, find out others, ...)

== Obstacles ==
* your limits !!!
* Arrangement

== Component ==
* Electronics components (resistors, <s>capacity</s> capacitors, diodes, transistors, ICs, uCs, uPs, motors, LEDs,...)
* PC's/Macs
* Electronics Book
* Google
* Pizza
* Beer
** Prix Garantie
** Maybe other beer if someone actually bothers
* [http://i.imgur.com/9SOudTJ.jpg Stuff to open your spirit]

== Project in the back ==

''In French''

Avec le lien ci-dessous, tu peux déjà choisir sur quel projet tu aimerais venir apporter, partager ou découvrir tes connaissances... n'hésite pas non plus a rajouter ton projet

''In English''

With the link below, you can choice the projet or offer your project

Example of project :

* Fixme_Y_choice (suite)
* Arbre Twitter - Fixme (suite)
* Affichage Hack-CFF (suite)
* DMX protocole (Special Fixme RS485 home-made protocol)
* Workshop Kicad / PCB (New)
* Odometer for a bike (New)
* your project

== Participants ==
* [[User:Binary_Brain]] 100% chance to be present. Loading completed.
* [[User:dgellow]]
* [[User:Nemen]]
* [[User:gcmalloc]]
* [[User:Marcha]] ???
* [[User:Noskill]]
* [[User:Philoux]]
* [[User:Jhu]] ElectroJam... for sure !
* [[User:Sasha]] yes
* [[User:Pherjung]] yes
* and you (members or non members of Fixme) ???

== Photos ==
A completer par vos photos
<gallery>
File:Twitter tree wires.jpg
File:Twitter tree lcd screen.jpg
File:fixmebus1.jpg
File:fixmebus2.jpg
</gallery>

== Video ==
[http://youtu.be/pW8l4VZCw0Q Unlisted video from last electrojam]

== See also ==
* [[ElectroJam1]]
* [[ElectroJam2]]
* [[ElectroJam3]]

Fixme love CFF

2016-03-17T23:47:40Z

Pherjung:

= Fixme Love SBB/CFF/FFS =
Alors que les CFF semblent bien partis pour nous ruiner avec les prix exhorbitants de leurs billets, il existe néanmoins certains avantages à voyager dans leurs trains, dont la possibilité de disposer durant le transport d'une certaine quantité d'énergie électrique sous 230VAC comprise dans le prix du billet. Alors pourquoi ne pas en profiter ? Quelle quantité d'énergie disposent les usagers ?

Afin de répondre à ces questions qui titillent certains esprits fixmiens depuis quelques temps, il a été convenu d'organiser une fondue plus ou moins improvisée dans un ICN pour en discuter, avec le trajet suivant : Genève - St-Gall aller-retour, la fondue étant pour le repas de midi. Chacun peut intégrer l'événement depuis n'importe quelle gare, y compris d'éventuels participants d'autres hackerspaces, voire même suisse-allemands.

L'objectif d'un tél événement est avant tout de faire découvrir les magnifiques paysages de la Suisse à certains fixmiens qui n'auraient pas quitté leur écran d'ordinateur depuis plusieurs années. Tout cela pour le plus grand plaisir de chacun, dans la bonne humeur autour d'une bonne fondue. Même si cela paraît osé et sur le fil rouge de la légalité, il s'agit de se rappeler, rappeler aux autres usagers du train ainsi qu'aux éventuels contrôleurs, que la fondue est une tradition suisse bien ancrée dans notre culture et à perpétuer !

L'objectif étant aussi de faire de la publicité pour Fixme, il va de soit que les idées ci-dessous sont toutes les bienvenues.

== Idées lumineuses ==
* Fondue pour assez de personnes (Philou, Petaflop, Pherjung, les passagers CFF ?)
* Atelier de soudure (Jhu)
* Passer l'aspirateur dans le couloir du train (Sasha le grand ?)
* Affichage extérieur avec persistance rétinienne (Nemen ?)
* ''fill-in your ideas''

== Plan de la journée ==

* Aller
:Genève / Sa, ??.05.14 / dép. 10:18 / 6 / ICN 523
:St. Gallen / arr. 14:15 / 2

* Retour
:St. Gallen / Sa, ??.05.14 / dép. 16:11 / 1 / IC 732
:Genève / arr. 20:15 / 2

== Doodle ==
http://doodle.com/b69gvmz78p2335i7

== Règlement CFF ==
; Règlement des CFF affiché dans les trains
: Voyager avec un titre de transport valable au moment du départ.
: Ne pas utiliser les secteurs de 1er classe avec un titre de transport de 2eme classe.
: Ne pas fumer dans le train.
: Ne pas endommager, ni salir le véhicule.
: N'occuper qu'une place par personne. de ne pas importuner les autres voyageurs (bruits, mendicité)
:: Le contrôleur peut, selon son humeur, demander l'arrêt de toute activité. Par exemple, l'odeur d'un produit (par contre, je pense pas que les pets fassent part de cette catégorie)
: N'occuper qu'une place par personne.
: Ne pas utiliser des produits explosif

Les contrevenants peuvent être exclus du transport et s'exposent à des demandes de réparations, au prélèvement de suppléments et à des poursuites et à des poursuites pénales.

=== To Do ===
* Vérifier le règlement
* Mettre à jour la partie "Projet"
* S'arranger quel projet est valide pour pouvoir le mettre en pratique (via un framadate)
* ...

== Participant ==
* [[User:Pherjung]]
* [[User:jhu]]
* Ruum42 (Hackerspace de St.Gall) ?
* you:: :D

How to create an event

2016-03-17T23:47:15Z

Pherjung:

Fixme is an excellent place to organise all your awesome events. We welcome everything relating to technology, electronics, hacking, making, meetups, cryptocurrencies, competitions, talks, conferences, (relevant) politics, and much more! We already hold numerous events every month - at least one event a week, with one large event a month at a minimum. Check out our [https://www.google.com/calendar/ical/sruulkb8vh28dim9bcth8emdm4%40group.calendar.google.com/public/basic.ics calendar]!

== Location ==
=== Fixme ===
'''Capacity''': 20 people

You are encouraged to organise events here at any time! (Wednesday evenings may be a bit cramped though)

=== Makerspace ===
'''Capacity''': however many you can fit in 250m^2

You can organise events here for anything to do with electronics, making, woodworking, laser cutting, plasma cutting, cnc machining, or other projects that wouldn't fit into fixme. Usage of machines requires a belt, and if your belt color isn't blue or higher, someone with that has to be present. The exact protocol for organizing events here is still in beta; '''you need to talk to Marc (the makerspace manager) before planning anything'''.

=== Meetup space ===
'''Capacity''': 60+ people

Great for larger events, generally unavailable on Wednesday evenings, more and more solicited on Tuesday and Thursday nights. '''You need to talk to UniverCité's Community Manager before planning anything.''' Requires being added to UC calendar (see below) AFTER that to avoid overbooking.

=== Coworking Rooms ===
'''Capacity''': 10 people for big one (aka coworking meeting room), 5 people for small one (aka le bocal / la war room)
'''Priority is always given to coworkers. You need to talk to UniverCité's Community Manager before planning anything.''' Requires being added to UC calendar (see below) AFTER that to avoid overbooking.

== Questions to answer first ==
* What is the topic? (i.e. Coding Night, Cryptoparty, Talk, Workshop, ...)
* What is the target? (i.e. Fixme members, extern people, adults, children, ...)
* What resources are required? (i.e. the hackerspace, electronics tools, electronics parts, ...)
* Who can help me to organize? (i.e. things can be done faster/easier if you do not try to do it alone)
* Is the date available ?

== Plan the event ==
The person responsible for events is [[User:Pherjung|Pherjung]], feel free to contact him (''pherjung at fixme dot ch'') at any time to organize events. If you want to organize events in the UniverCité (UC) space, please cc Carmelo (''carmelo dot bisognano at inartis dot ch'') as well.
* Create a wiki page using the [[Project_template|project template]].
* Get/Order the resources to be sure to get it on time.
* Check the [https://www.google.com/calendar/embed?src=sruulkb8vh28dim9bcth8emdm4%40group.calendar.google.com&ctz=Europe/Zurich Fixme Event] calendar to find possible dates for the event.
* Check the [https://www.google.com/calendar/embed?src=eru0rpe6q4ra6l966v11pcp1a0%40group.calendar.google.com&ctz=Europe/Zurich UC event calendar] to make sure the room you have in mind is not booked already ([https://www.google.com/calendar/ical/eru0rpe6q4ra6l966v11pcp1a0%40group.calendar.google.com/public/basic.ics UC iCal])
* Open a [http://framadate.org/ Framadate] and spread the word (Mailing-List, IRC, weekmail, twitter, facebook, ...).
* Select the most popular date (yes, it's obvious, I know...)
* Plan the event early: 1 month is good most of the times, the earlier the better

== Communicate about the event ==
* Think about a poster to promote your event (There is a poster template for Fixme events). [[File:poster.tgz]]
* Once the date is known, [[Communication|promote!]]
** spread the info on the [https://lists.saitis.net/cgi-bin/mailman/listinfo/hackerspace-lausanne mailing list],
** update the wiki page with this date,
** update the topic on #Fixme IRC chan,
** create an event on the Fixme Facebook page,
** post the event and date on Twitter,
** prepare a short description for the weekmail.
** <s>You may use events script to create event https://github.com/fixme-lausanne/events (FIXME it's broken)</s>
* Communicate 1 week and the day before the event (people tend to forget)

31C3

2016-03-17T23:46:27Z

Pherjung:

[[Category:Closed_Projects]][[Category:Conferences]]

December 27th–30th 2014, CCH, Hamburg

The [https://events.ccc.de/congress/2014/wiki/Main_Page 31st Chaos Communication Congress (31C3)] is an annual four-day conference on technology, society and utopia. The Congress offers lectures and workshops and various events on a multitude of topics including (but not limited to) information technology and generally a critical-creative attitude towards technology and the discussion about the effects of technological advances on society.

== People coming ==

{| class="wikitable"
|+
! Name !! Ticket !! Transport to HAM? !! Transport from HAM? !! Hotel?
|-
| [[User:sasha|Sasha]] || Yes || Plane GermanWings || Plane EasyJet || Generator Hostel
|-
| [[User:jnsc|Jonas]] || Yes || Plane Easyjet 3426 / 26.16 16h05 || Plane GermanWings 4U 7744 / 31.12 07h00 || Radisson Blu
|-
| [[User:noskill|Noskill]] || || Car || Car || Hotel Fresena
|-
| [[User:Rorist|Rorist]] || Yes || Plane Easyjet 3426 / 26.12 || Plane Easyjet 3425 / 30.12 || Radisson Blu
|-
| Kat || Yes || Plane Easyjet 3426 / 26.12 || Plane Easyjet 3425 / 30.12 || Radisson Blu
|-
| [[User:Prosouth|Prosouth]] || || Plane Easyjet 3426 / 26.12 || Plane Easyjet 3425 / 30.12 ||
InterCityHotel Hamburg Dammtor-Messe
|-
| [[User:fzn|Fzn]] || || Train (?) || Train (?) || Radisson si places
|-
| [[User:pherjung|Pherjung]] || || Bus (depuis Konstanz) || || Generator Hostel ||

|+
! Total
!
!
!
!
|}

== Tickets ==
Tickets shop has opened https://tickets.events.ccc.de/tickets/ PreSale ends December 12th, 23:59:59

== Accommodation ==
* [http://www.radissonblu.com/booking-entrance?language=en&sitaCode=HAMZA&adults_room1=1&rooms=1&children_room1=0&arrival=26/12/2014&departure=31/12/2014&paccode=31C3 Radisson Blu] - 129€ night (divided per two people, currently fully booked)
* [http://www.generatorhostels.com/de/hamburg/ Generator hostel] - 17€/night (CCC2014 coupon)
* [http://www.hotel-heimhude.de/ Heimhude], standard rooms fully booked
* [https://events.ccc.de/congress/2014/wiki/Static:Accommodation Accommodation]

== Transport ==
=== Train ===
Train ticket sales are up! [https://www.bahn.de/p/view/home/aktion/31c3.shtml]

=== Plane ===
easyJet U23426/U23425 - <s>110 CHF there & back as of 07/09/14</s> 119 CHF there & back as of 01/10/14

[[File:EasyJet-30C3.png | 100px]]

GermanWings 44.9€
http://www.lidl-reisen.de/germanwings?et_cid=10&et_lid=580227

== Congress Everywhere ==

* https://events.ccc.de/congress/2014/wiki/Static:Congress_everywhere
* Somebody willing to organize something at FIXME ?

== Phone numbers ==
Phone number registering: https://www.eventphone.de/guru2/login

=== Phone list ===
{| class="wikitable"
|+
! Name !! Extension !! Type
|-
| rorist || 9137 || GSM
|-
| Jonas || 9478 || GSM
|-
| Sasha || 8485 || GSM
|-
| Patrick || 9019946 || GSM
|-
|}

== SeidenStrasse ==

* We need to prepare 1 or 2 capsules for the SeidenStrasse !
* https://events.ccc.de/congress/2014/wiki/Projects:Seidenstrasse
* PET bottle + 3d printed parts ! FIXME Stickers and goodies of all sorts to put in

== See also ==
* [[31C3/laptop_preparation]]
* [[30C3]]
* [[29C3]]
* [[28C3]]
* [[CCCamp2015]]

Coursera Microcontroleur

2016-03-17T23:45:21Z

Pherjung:

[[Category:Workshops]]

== Description ==

Ce wiki a pour but de mettre a disposition des codes (codes sources) réalisés par les membres de Fixme ou autres, les astuces, et tous autres informations qui permettent de suivre et comprendre le cours en ligne [https://www.coursera.org/course/microcontroleurs coursera - comprendre les microcontroleurs] donné par Monsieur Jean-Daniel Nicoud & Pierre-Yves Rochat.
De plus chaque vendredi soir à partir de 20h une partie des Electronics Meeting sera consacrée à réaliser, corriger, comprendre les exercices proposés, les données seront à disposition sur cette page wiki en format pdf.

'''IMPORTANT''' : vous remarquez des erreurs, des explications erronées, vous voulez simplement contribuer à ce wiki, alors n'hésiter --> améliorer le !!!

== Matériels ==

* Carte ARDUINO UNO --> Microcontrôleur ATMEL ATMEGA3228P
* Carte EXPLORER 16 --> DSP MICROCHIP DSPic33FJ256GP710
* Carte LAUNCH PAD --> Microcontrôleur TEXAS INSTR MPS430
* Carte Starter KIT ETML-ES --> Microcontrôleur MICROCHIP PIC18F4520
* '''vos cartes'''...

[[File:Explorer 16.jpg]] - [[File:Microcontrolers.jpg|vignette|upright|alt=cartes électroniques|cartes électroniques]]

== Exercices - donnees ==
=== Exos libres ===
* Exercices libres semaine 1 : [[File:Exos_1.pdf‎ ]]
* Exercices libres semaine 2 : [[File:Exos 2.pdf‎ ]]
* Exercices libres semaine 3 : [[File:Exos 3.pdf ]]
* Exercices libres semaine 4 : [[File:Exos 4.pdf ]]

=== Exas ===
* Questionnaire semaine 1 : [[File:Questionnaire_1.pdf‎]]
* Questionnaire semaine 2 : [[File:Questionnaire_2.pdf‎]]

== Solus de nos memmbres : Aperçu & Codes & Astuce ==
=== Solus Exos session 1 ===

* Réponse exos 1.1 : ~ 520 Ohms
* Réponse exos 1.2 : /OR
* Réponse exos 1.3 : voir fichier pdf -->[[File:Exos serie1.pdf]]
* Réponse exos 1.4 : voir fichier pdf -->[[File:Exos serie1.pdf]]
* Réponse exos 1.5 : voir réponse détaillée à venir
* Réponse exos 1.6 : 1) 0b 101 2) 0b 1100 3) 0b 11 1111 4) 0b 1 0000 0001 5) 0b 101 0000 0000
* Réponse exos 1.7 : 1) 0x37 2) 0x5F 3) 0xE4D9 4) 0x179
* Réponse exos 1.8 : 1) 2 3 5 9 2) ce n'est pas un code BCD
* Réponse exos 1.9 : voir fichier pdf -->[[File:Exos serie1.pdf]]
[[File:Exos 1 9 dauphin.jpg]]

=== Solus Exos session 2 ===

* Réponse exos 2.1 : voir fichier type .txt => renommer le fichier en .dophin [[File:FiBo.txt‎]] => utilisation de l'émulateur dauphin
* Réponse exos 2.2 : un microcontrôleur contient un microprocesseur, car RAM / ROM / ALU - CPU est directement dans le même boitier.
* Réponse exos 2.3 : non, car une valeur 32bits peut être réalisées avec des champs de 16 ou 8bits, voir même des champs de 4bits
* Réponse exos 2.4 : non, le traitement des données va dépendre de plusieurs paramètres comme bus d'adresse, bus de données, jeu d'instructions, etc
* Réponse exos 2.5 :
DSPic (carte Explorer) : [[File:Exo_2_5_DSPic.c‎]] - langage C classique avec utilisation Timer et interruption
Arduino langage : [[File:Exo_2_5_ARD.c‎]] - langage C classique avec paramètre lié à l'arduino
* Réponse exos 2.6 :
DSPic (carte Explorer) : [[File:Main_2_6_DSPic.c]]‎ - langage C classique avec utilisation Timer et interruption / sans de gestion de rebonds
* Réponse exos 2.7 :
DSPic (carte Explorer) : [[File:Main_2_7_DSPic_V1.c‎ ]]‎ - langage C classique sans utilisation de Timer / ni de gestion de rebonds
DSPic (carte Explorer) : [[File:Main_2_7_DSPic_V2.c‎ ]]‎ - langage C classique utilisation Timer + gestion anti-rebond (aller voir code sur la page du wiki de la carte Explorer 16)
* Réponse exos 2.8 :
DSPic (carte Explorer) : [[File:Main_2_8_DSPic.c‎ ]]‎ - langage C classique sans utilisation de Timer / ni de gestion de rebonds
DSPic (carte Explorer) : [[File:Main_2_8_DSPic_v2.c‎ ]]‎ - langage C classique avec utilisation Timer + gestion anti-rebond (aller voir code sur la page du wiki de la carte Explorer 16)
* Réponse exos 2.9 :
DSPic (carte Explorer) : [[File:Main_2_9_DSPic_Modif.c‎ ]]‎ - langage C classique avec utilisation Timer + gestion anti-rebond (aller voir code sur la page du wiki de la carte Explorer 16)

* Réponse exos 2.10 :
DSPic (carte Explorer) : [[File:Main 2 10 DSPic MAP.c ]]‎ - langage C classique sans Timer et ni gestion d'anti-rebond

=== Solus Exos session 3 ===

* Réponse exos 3.1 : 1) '''11 ou 0x0B''' 2) '''253 ou 0xFD''' 3) '''2''' 4) '''251 ou 0xFB''' 5) '''2''' 6) '''0''' 7) '''83''' 8) '''1'''
Code en C (sous CodeBlock) : [[File:Exos 3 1.c]]‎ - langage C classique

* Réponse exos 3.2 :
int i = 0;
while(i < 10){i++;...}

* Réponse exos 3.3 :
DSPic (carte Explorer) : [[File:Main_3_3_DSPic.c‎]]‎ - langage C classique avec utilisation Timer + gestion anti-rebond (voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

* Réponse exos 3.4 :
DSPic (carte Explorer) : [[File:‎Main_3_4_DSPic.c]]‎ - langage C classique avec utilisation Timer (voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

* Réponse exos 3.5 :
DSPic (carte Explorer) : [[File:Main 3 5 DSPic.c]]‎ - langage C classique avec utilisation Timer (voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

* Réponse exos 3.6 : on peut écrire la déclaration suivante '''DDRC = 0b01000001''' comme ceci : DDRC = 0x41, mais la encore la visibilité n'est pas très claire quand au sortie que l'on veut activé ou DDRC = (1 << DDC6) | (1 << DDC0) <= ici c'est plus clair quand au pin que l'on veut mettre en état de sortie

[[Rappel]] DDRC = Data Direction Register (C est le port avec lequel on veut travailler)

* Réponse exos 3.7 :
DSPic (carte Explorer) : [[File:Main_3_7_DSPic.c‎]]‎ - langage C classique avec utilisation Timer + gestion anti-rebond(voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

* Réponse exos 3.8 :
DSPic (carte Explorer) : [[File:Main_3_8_DSPic.c‎]]‎ - langage C classique avec utilisation Timer + gestion anti-rebond(voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

* Réponse exos 3.9 :
DSPic (carte Explorer) : [[File:Main_3_9_DSPic.c‎ ]]‎ - langage C classique avec utilisation Timer + gestion anti-rebond(voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

* Réponse exos 3.10 :
DSPic (carte Explorer) : [[File:Main_3_10_DSPic.c]]‎ - langage C classique avec utilisation Timer + gestion anti-rebond(voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

* Réponse exos 3.11 :
DSPic (carte Explorer) : [[File:Main_3_11_DSPic.c‎]]‎ - langage C classique sans gestion de touche ou timer (voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

=== Solus Exos session 4 ===

* Réponse exos 4.1 :
DSPic (carte Explorer) : [[File:Main_4_1A_DSPic.c‎ ]]‎ - langage C classique avec gestion des touches avec une fonction d'anti-rebond et du timer (voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)
DSPic (carte Explorer) : [[File:Main 4 1B DSPic.c]]‎ - langage C classique avec gestion des touches avec une fonction d'anti-rebond et du timer (voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)
DSPic (carte Explorer) : [[File:Main 4 1C DSPic.c]]‎ - langage C classique avec gestion des touches avec une fonction d'anti-rebond et du timer (voir codes sur la page du wiki de la carte Explorer 16 -> lien en bas de page)

'''Remarque''': pour réaliser ces exercices, une carte d'extension a été utilisée (réalisée à Fixme) et connectée à la carte Explorer 16 (voir les lien interne en bas de page).

=== Solus Exas session 1 ===

* Réponse exas Q1 : 2)
* Réponse exas Q2 : 3)
* Réponse exas Q3 : < 2500 ohm
* Réponse exas Q4 : 1)
* Réponse exas Q5 : 1)
* Réponse exas Q6 : 2) & 5)
* Réponse exas Q7 : 1) & 3) & 6)
* Réponse exas Q8 : 33
* Réponse exas Q9 : 0b010101010101
* Réponse exas Q10 : 2) & 6) & 7)

=== Solus Exas session 2 ===

* Réponse exas Q1 : 3)
* Réponse exas Q2 : OUI
* Réponse exas Q3 : 1) & 4) & 5)
* Réponse exas Q4 : 1) & 4) & 5)
* Réponse exas Q5 : 4 000 000
* Réponse exas Q6 : 2) & 4) & 5)
* Réponse exas Q7 : 2) & 3) & 4)
* Réponse exas Q8 : 1) & 4) --> la solution 2 est admise comme correcte mais il subside un tout ?? A vos remarques

=== astuce ===

Regarder le champs discussion : https://fixme.ch/wiki/Talk:Coursera_Microcontroleur

== Liens utiles ==

=== liens: interne --> wiki ===
*[https://fixme.ch/wiki/Electro_docs page de composants utiliser sur les projets de Fixme]
*[https://fixme.ch/wiki/PIC Outils pour programmée des PICs]
*[https://fixme.ch/wiki/Explorer_16_DSPIC Quelques codes pour la carte Explorer]
*[https://fixme.ch/wiki/Extension_Explorer_16 Extension pour la carte de développement Explorer 16]

=== liens : documentation PDF ===
* [http://ww1.microchip.com/downloads/en/DeviceDoc/Explorer%2016%20User%20Guide%2051589a.pdf Doc PDF Carte Explorer 16]
* [http://ww1.microchip.com/downloads/en/DeviceDoc/70593d.pdf Doc PDF Datasheet DSPIC33FJxxx]
* [http://ww1.microchip.com/downloads/en/DeviceDoc/70186E.pdf Doc PDF Complément Datasheet --> Oscillateur]
* [http://www.didel.com/C/FichiersImportes.pdf Doc PDF pour l'importation de fichier sous Android]
* [http://www.bricobot.ch/kits/Miaou.pdf Doc PDF montrant le montage d'un nourrisseur de chat à distance]

=== liens : documentation Site Internet ===
* [https://www.coursera.org/epfl Lien sur les différents cours proposer par l'EPFL en ligne & ligne]
* [http://www.epsitec.ch/dauphin/ Simulateur de mini PC Daulphin]
* [http://www.arduino.cc/ Site de l'Arduino]
* [http://arduino.cc/en/Hacking/PinMapping168 Pining de l'ATMEGA328P]
* [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en024679 Site Microchip - détails sur le DSP]
* [http://fr.openclassrooms.com/informatique/cours/l-aleatoire-en-c-et-c-se-servir-de-rand-1 théorie sur le pseudo-aléatoire en C]
* [http://fr.wikipedia.org/wiki/C_(langage) Wiki sur le langage C - Rappel de la taille des types]

== Bibliographie ==

* Le langage C - Tony Zhang - CampusPress - ISBN:2-7440-1518-0 => livre de poche bien sympas pour se remémorer quelques notions de C (perdue), malgré certaines coquilles

== Autre ==
* Pour ceux cherchant la facilité, regardez du côté de [[ArduBlock]]. La page est en anglais, mais en cas d'incompréhension, je peux sans problème la traduire dans la langue de Molière. Merci donc de contacter [[User:Pherjung]] pour toute question en rapport avec [[ArduBlock]].

== Participant ==
* [[User:Philoux]]
* [[User:Nemen]]
* [[User:Pherjung]]
* you... :-D

User:Pherjung

2016-03-17T23:44:05Z

Pherjung: Created page with "Hi, I'm Patrick ! I'm also know as pherjung. I'm at present apprentice as IT technician, generalist option (CFC). At Fixme I do mostly speaking, but I'm trying to do nice stuf..."

Hi, I'm Patrick !
I'm also know as pherjung. I'm at present apprentice as IT technician, generalist option (CFC). At Fixme I do mostly speaking, but I'm trying to do nice stuff too :) I do some bash script and I love python <3.

* [https://twitter.com/pherjung Twitter]
* [https://github.com/phervieux Github]
* [https://git.fixme.ch/pherjung Gogs]
* contact: hervieuxpatrick 100 0000 gmx 010 1110 ch
== My projects: ==
* [https://git.fixme.ch/FIXME/autoclose Autoclause.sh] with the help of [[User:Rorist|Rorist]]
* [https://git.fixme.ch/gustavo/spectro-pointer Spectro Pointer] with Gustavo from UC
** I'm not the leader of this project and I'm only trying to bring my small knowledge to Gustavo
* Workshop with [[ArduBlock]]