Assembly:Developers for Future

From 36C3 Wiki
Description Developers supporting the Fridays for Future movement
Members ElectricMaxxx, Maxvalue
Projects create project
Self-organized Sessions create self-organized session
Subassembly of Assembly:About:future
Tags free software, development, freedom of communication, activism, digital sustainability
Provides stage no
Location for self-organized sessions no
Orga contact {{{Has orga contact}}}URIs of the form "{{{Has orga contact}}}" are not allowed.
Uses money {{{Uses money}}}"{{{Uses money}}}" is not in the list (yes we handle money, no money handling) of allowed values for the "Uses money" property.
Need fibre {{{Need fibre}}}"{{{Need fibre}}}" is not in the list (no, yes would be great, yes its essential) of allowed values for the "Need fibre" property.
Extra Power {{{Extra power}}}
Near passage {{{Near passage}}}"{{{Near passage}}}" is not in the list (whatever, yes its essential, would be great, definitively not) of allowed values for the "Near passage" property.
Character of assembly {{{Has assembly type}}}"{{{Has assembly type}}}" is not in the list (just a gathering space, place to show and meet) of allowed values for the "Has assembly type" property.
Seats needed 0
Extra seats 0
Aread needed 0
Arrival and build up

(Click here to refresh this page.)

In many countries around the globe, students have been gathering on Fridays to demonstrate for a future worth living. We as developers want to support this movement. Without influencing the kids in their work, we can help them create the software they need to network, communicate, and document their work. Striking during school doesn't mean that the kids neglect their education here. We can take the kids much closer to the real world of software development with small workshops, hacking sessions or even simple code reviews than school would ever be able to. Joining the movement also means thinking about one's own footprint in climate change. As developers it has become a matter of course that we have many computers running, for example that a CI pipeline takes over every small task for us. But what does that cost in terms of electricity? Therefore it will also be our task to question our own process and to provide new solutions if necessary.

Archived page - Impressum/Datenschutz