Noisebridge - User contributions [en]

Dr Enigma

2018-02-04T21:54:34Z

Jay:

Mark Baldwin (aka '[https://drenigma.org/ Dr Enigma]') is a speaker who specializes in the history of cryptography and in particular the WW2-era Enigma Machine used by the Axis powers.

He's doing a tour of the Bay Area in February 2018, and is available to provide a talk and hands-on demo with a real Enigma machine at Noisebridge on the evening of '''Wednesday 28th Feb''' in the hackitorium. (todo: reannounce during some Tuesday meetings)

There's some more information about Mark and the events he runs available at https://drenigma.org/about/

TODO: More event details / additional talks before and after?

'''When''': Wednesday 28th Feb

'''Where''': Hackitorium space, Noisebridge / streamed (but will not be recorded)

'''Organizers''': Jay Addison (@jay on Slack), Patrick

Dr Enigma

2018-02-04T21:47:42Z

Jay:

Mark Baldwin (aka '[https://drenigma.org/ Dr Enigma]') is a speaker who specializes in the history of cryptography and in particular the WW2-era Enigma Machine used by the Axis powers.

He's doing a tour of the Bay Area in February 2018, and is available to provide a talk and hands-on demo with a real Enigma machine at Noisebridge on the evening of '''Wednesday 28th Feb''' in the hackitorium. (todo: reannounce on a Tuesday)

There's some more information about Mark and the events he runs available at https://drenigma.org/about/

TODO: More event details / additional talks before and after?

'''When''': Wednesday 28th Feb

'''Where''': Hackitorium space, Noisebridge / streamed (but will not be recorded)

'''Organizers''': Jay Addison (@jay on Slack), Patrick

Dr Enigma

2018-02-04T21:47:21Z

Jay:

Mark Baldwin (aka '[https://drenigma.org/ Dr Enigma]') is a speaker who specializes in the history of cryptography and in particular the WW2-era Enigma Machine used by the Axis powers.

He's doing a tour of the Bay Area in February 2018, and is available to provide a talk and hands-on demo with a real Enigma machine at Noisebridge on the evening of '''Wednesday 28th Feb''' in the hackitorium. (todo: reannounce on a Tuesday)

There's some more information about Mark and the events he runs available at https://drenigma.org/about/

TODO: More event details / additional talks before and after?

When: Wednesday 28th Feb
Where: Hackitorium space, Noisebridge / streamed (but will not be recorded)
Organizers: Jay Addison (@jay on Slack), Patrick

Dr Enigma

2018-02-04T21:43:32Z

Jay: Created page with "Mark Baldwin (aka '[https://drenigma.org/ Dr Enigma]') is a speaker who specializes in the history of cryptography and in particular the WW2-era Enigma Machine used by the Axi..."

Mark Baldwin (aka '[https://drenigma.org/ Dr Enigma]') is a speaker who specializes in the history of cryptography and in particular the WW2-era Enigma Machine used by the Axis powers.

He's doing a tour of the Bay Area in February 2018, and is available to provide a talk and hands-on demo with a real Enigma machine at Noisebridge on the evening of '''Wednesday 28th Feb''' in the hackitorium. (todo: reannounce on a Tuesday)

There's some more information about Mark and the events he runs available at https://drenigma.org/about/

TODO: More event details / additional talks before and after?

SatNOGS

2017-07-22T19:14:14Z

Jay:

[https://satnogs.org SatNOGS] is a FOSS project centered around the creation of a volunteer run satelitte ground station network by creating an open source hardware and software platform.

Currently there's no SatNOGS ground station covering the west coast of the United States and so some Noisebridge community members have decided to create a ground station and host it on the roof of 2169 Mission St.

== People ==

A list of people to contact about this project.

* [[User:Patrickod]]
* [[User:pkropf]]
* [[User:Jay]]
* Zaki ?

== Progress ==

The project is currently in it's planning stage however we hope to build the following components:
* [https://github.com/satnogs/satnogs-rotator SatNOGS Rotator].
* [https://github.com/satnogs/satnogs-rotator-controller SatNOGS rotator controller].
* [https://github.com/satnogs/satnogs-antennas SatNOGS antenna] for UHF and VHF operation.
* Tripod, potentially a variant of the [https://github.com/satnogs/satnogs-tripod/tree/master SatNOGS tripod] with extra ballast for more stable permanent deployment

=== Update: 4/7/2017 ===

Patrick ordered PCBs of each of the following components today:
* rotary encoder (AS5040 variant)
* controller mainboard (from GH master)
* endstop (from GH master)

Will have 3x of each of these boards in the next week or so. Hope to generate a mouser cart containing the parts we'll need to populate the board.

== Costs ==

A running tally of the costs associated with the project can be found below:

{| class="wikitable"
! style="text-align: left;"| Description
! Cost
|-
| PCBs
| $35.50
|-
|}

== When ==

Schedule TBD - next meeting currently Tuesday evening, 2017-07-25 at 2169 Mission St.

SatNOGS

2017-07-09T01:11:50Z

Jay:

[https://satnogs.org SatNOGS] is a FOSS project centered around the creation of a volunteer run satelitte ground station network by creating an open source hardware and software platform.

Currently there's no SatNOGS ground station covering the west coast of the United States and so some Noisebridge community members have decided to create a ground station and host it on the roof of 2169 Mission St.

== People ==

A list of people to contact about this project.

* [[User:Patrickod]]
* [[User:pkropf]]
* [[User:Jay]]
* Zaki ?

== Progress ==

The project is currently in it's planning stage however we hope to build the following components:
* [https://github.com/satnogs/satnogs-rotator SatNOGS Rotator].
* [https://github.com/satnogs/satnogs-rotator-controller SatNOGS rotator controller].
* [https://github.com/satnogs/satnogs-antennas SatNOGS antenna] for UHF and VHF operation.
* Tripod, potentially a variant of the [https://github.com/satnogs/satnogs-tripod/tree/master SatNOGS tripod] with extra ballast for more stable permanent deployment

=== Update: 4/7/2017 ===

Patrick ordered PCBs of each of the following components today:
* rotary encoder (AS5040 variant)
* controller mainboard (from GH master)
* endstop (from GH master)

Will have 3x of each of these boards in the next week or so. Hope to generate a mouser cart containing the parts we'll need to populate the board.

== Costs ==

A running tally of the costs associated with the project can be found below:

{| class="wikitable"
! style="text-align: left;"| Description
! Cost
|-
| PCBs
| $35.50
|-
|}

== When ==

Every Monday evening from 6pm onwards at 2169 Mission St.

LWG Meeting Notes 2017 05 11

2017-05-13T22:24:05Z

Jay: /* Meeting Summary */

Date: 2017-05-11

Note-taker: Jay

== Meeting Summary ==

The library WG met to discuss writing a new library app

Attendance
----------

* jayaddison
* Munnu (monique)
* robbintt (trent)
* tymeart (tiffany)
* veloverso (kate)

Agenda
------

* Proposal by robbintt: move to a new Django-based app
* What to do with existing scanned book-db (given 50% have been thrown out since first scan)

Discussion
----------

* Level of experience with Django - some limited experience around the table, generally all keen to learn
* Trent proposes backend with django-rest & react frontend
* Jay: any existing similar django library mgmt tools?
* Trent: worth looking into
* Trent provides an overview of the existing library.noisebridge.net webapp

* Monique: how can we handle lost/checked out books?
* Trent: in a worst case scenario for a lost book we want, can re-order
* Kate: barcode scanner for check-in/out
* Trent: UPC codes can be unreliable, print OLID stickers?
* Jay: Do we have a label printer handy?
* Trent: Not certain, but can check & source/fund otherwise
* Monique: may be able to find an existing Python app to generate labels from olid
* Trent: thoughts on whether to require this in new app?
* Jay: suggestion to delay this and begin with existing functionality
* General consensus that we can wait until later to implement

* Trent proposes system design/architecture (see attachment)

[[File:Librarywg 20170511 design.jpg]]

* Volunteer groups:
* Backend: jay, monique, trent
* Frontend: kate, tiffany, trent

[[File:Librarywg 20170511 groups.jpg]]

- Discussed objectives for rest of evening:
- Create github org
- Create repos
- Initial commits for projects

Work begins...
--------------

* We now have repos!
* Slack integration for most events to #library-wg (thanks to tiffany for configuring)
* Initial gitignores / code etc pushed

Next meeting
------------

We agreed ~1 month from now - mid-June - appropriate for the next library-wg session. Date TBD.

[[Category:LWG Meeting Notes]]

File:Librarywg 20170511 groups.jpg

2017-05-13T22:23:29Z

Jay:

LWG Meeting Notes 2017 05 11

2017-05-13T22:22:09Z

Jay:

Date: 2017-05-11

Note-taker: Jay

== Meeting Summary ==

The library WG met to discuss writing a new library app

Attendance
----------

* jayaddison
* Munnu (monique)
* robbintt (trent)
* tymeart (tiffany)
* veloverso (kate)

Agenda
------

* Proposal by robbintt: move to a new Django-based app
* What to do with existing scanned book-db (given 50% have been thrown out since first scan)

Discussion
----------

* Level of experience with Django - some limited experience around the table, generally all keen to learn
* Trent proposes backend with django-rest & react frontend
* Jay: any existing similar django library mgmt tools?
* Trent: worth looking into
* Trent provides an overview of the existing library.noisebridge.net webapp

* Monique: how can we handle lost/checked out books?
* Trent: in a worst case scenario for a lost book we want, can re-order
* Kate: barcode scanner for check-in/out
* Trent: UPC codes can be unreliable, print OLID stickers?
* Jay: Do we have a label printer handy?
* Trent: Not certain, but can check & source/fund otherwise
* Monique: may be able to find an existing Python app to generate labels from olid
* Trent: thoughts on whether to require this in new app?
* Jay: suggestion to delay this and begin with existing functionality
* General consensus that we can wait until later to implement

* Trent proposes system design/architecture (see attachment)

[[File:Librarywg 20170511 design.jpg]]

* Volunteer groups:
* Backend: jay, monique, trent
* Frontend: kate, tiffany, trent

- Discussed objectives for rest of evening:
- Create github org
- Create repos
- Initial commits for projects

Work begins...
--------------

* We now have repos!
* Slack integration for most events to #library-wg (thanks to tiffany for configuring)
* Initial gitignores / code etc pushed

Next meeting
------------

We agreed ~1 month from now - mid-June - appropriate for the next library-wg session. Date TBD.

[[Category:LWG Meeting Notes]]

File:Librarywg 20170511 design.jpg

2017-05-13T22:21:48Z

Jay:

LWG Meeting Notes 2017 05 11

2017-05-13T22:15:29Z

Jay:

Date: 2017-05-11

Note-taker: Jay

== Meeting Summary ==

The library WG met to discuss writing a new library app

Attendance
----------

* jayaddison
* Munnu (monique)
* robbintt (trent)
* tymeart (tiffany)
* veloverso (kate)

Agenda
------

* Proposal by robbintt: move to a new Django-based app
* What to do with existing scanned book-db (given 50% have been thrown out since first scan)

Discussion
----------

* Level of experience with Django - some limited experience around the table, generally all keen to learn
* Trent proposes backend with django-rest & react frontend
* Jay: any existing similar django library mgmt tools?
* Trent: worth looking into
* Trent provides an overview of the existing library.noisebridge.net webapp

* Monique: how can we handle lost/checked out books?
* Trent: in a worst case scenario for a lost book we want, can re-order
* Kate: barcode scanner for check-in/out
* Trent: UPC codes can be unreliable, print OLID stickers?
* Jay: Do we have a label printer handy?
* Trent: Not certain, but can check & source/fund otherwise
* Monique: may be able to find an existing Python app to generate labels from olid
* Trent: thoughts on whether to require this in new app?
* Jay: suggestion to delay this and begin with existing functionality
* General consensus that we can wait until later to implement

* Trent proposes system design/architecture (see attachment)
* Volunteer groups:
* Backend: jay, monique, trent
* Frontend: kate, tiffany, trent

- Discussed objectives for rest of evening:
- Create github org
- Create repos
- Initial commits for projects

Work begins...
--------------

* We now have repos!
* Slack integration for most events to #library-wg (thanks to tiffany for configuring)
* Initial gitignores / code etc pushed

Next meeting
------------

We agreed ~1 month from now - mid-June - appropriate for the next library-wg session. Date TBD.

[[Category:LWG Meeting Notes]]

LWG Meeting Notes 2017 05 11

2017-05-13T22:12:32Z

Jay: Created page with "Date: 2017-05-11 Note-taker: Jay == Meeting Summary == The library WG met to discuss writing a new library app Attendance ---------- * jayaddison * Munnu (monique) * robb..."

Date: 2017-05-11

Note-taker: Jay

== Meeting Summary ==

The library WG met to discuss writing a new library app

Attendance
----------

* jayaddison
* Munnu (monique)
* robbintt
* tymeart (tiffany)
* veloverso (kate)

Agenda
------

* Proposal by robbintt: move to a new Django-based app
* What to do with existing scanned book-db (given 50% have been thrown out since first scan)

Discussion
----------

* Level of experience with Django - some limited experience around the table, generally all keen to learn
* Trent proposes backend with django-rest & react frontend
* Jay: any existing similar django library mgmt tools?
* Trent: worth looking into
* Trent provides an overview of the existing library.noisebridge.net webapp

* Monique: how can we handle lost/checked out books?
* Trent: in a worst case scenario for a lost book we want, can re-order
* Kate: barcode scanner for check-in/out
* Trent: UPC codes can be unreliable, print OLID stickers?
* Jay: Do we have a label printer handy?
* Trent: Not certain, but can check & source/fund otherwise
* Monique: may be able to find an existing Python app to generate labels from olid
* Trent: thoughts on whether to require this in new app?
* Jay: suggestion to delay this and begin with existing functionality
* General consensus that we can wait until later to implement

* Trent proposes system design/architecture (see attachment)
* Volunteer groups:
* Backend: jay, monique, trent
* Frontend: kate, tiffany, trent

- Discussed objectives for rest of evening:
- Create github org
- Create repos
- Initial commits for projects

Work begins...
--------------

* We now have repos!
* Slack integration for most events to #library-wg
* Initial gitignores / code etc pushed

Next meeting
------------

We agreed ~1 month from now - mid-June - appropriate for the next library-wg session. Date TBD.

[[Category:LWG Meeting Notes]]

NOPE - CCCamp 2015

2015-05-19T05:36:25Z

Jay: /* Are you going to camp with Noiseburg? */

[https://events.ccc.de/camp/2015/wiki/Main_Page More info about Camp]

==Are you going to camp with Noiseburg?==
First off please subscribe to the [https://www.noisebridge.net/mailman/listinfo/congress Congress mailing list] so we can communicate.

* [[user:rubin110|Rubin]]
* [[user:MCT|mct]], perhaps 30% likelihood
* [[user:Maltman23|Mitch]]
* [[user:jay|Jay]]

==Are you going but camped elsewhere?==

* Anon Hacker - Anonville