Changeset 39882 in project


Ignore:
Timestamp:
04/08/21 19:48:15 (4 months ago)
Author:
felix winkelmann
Message:

added schedule to coding jam page

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/event/coding-jam-2021

    r39877 r39882  
    3535presentations and demonstrations.
    3636
    37 Everybody is welcome, so check your calendars.
    3837
    39 Current list of development proposals:
     38=== Schedule
     39
     40Discussion and coordination will take place in the IRC channel #ChickenCodingJam on
     41irc.freenode.net. The channel will be created Friday morning, so feel free to join.
     42
     43Presentations and talks may be prerecorded. We still show them in the video sessions,
     44but include a Q+A session after each talk, as time permits. Links to prerecorded
     45talks will be made available shortly before each presentation begins to reduce bandwidth.
     46
     47==== Friday, 2012-04-09
     48
     49* 12:00 UTC - Official start of the event
     50
     51* 19:00 UTC - Start of 1st video session, Welcome.
     52
     53* 19:30 UTC - Discussion panel: State of the CHICKEN 2021 survey:
     54
     55Discussion on the results of the [[//surveys.call-cc.org/state-of-chicken/2021/|State of CHICKEN 2021 survey]]
     56
     57* 20:30 UTC - Testing CHICKEN and eggs (by mario-goulart)
     58
     59* 21:30 UTC - Presentation: Towards a better Duckyscript toolchain (by Vasilij "wasamasa" Schneidermann):
     60
     61I'll present [[https://depp.brause.cc/plucky/|plucky]], a [[https://github.com/hak5darren/USB-Rubber-Ducky/wiki/Duckyscript|Duckyscript]] compiler I wrote out of frustration with the existing toolchain. It processes a BASIC-style language describing human keyboard input, intended to be used for red teaming security assessments.
     62
     63* 22:30 UTC - End of 1st video session
     64
     65==== Saturday, 2012-04-10
     66
     67* 19:00 UTC - Start of 2nd video session
     68
     69* 19:30 UTC - Experiences using Chicken in a corporate compute environment for design automation (by Matt Welland):
     70
     71I'll give a quick overview of Megatest, logpro, refdb and sauth and then cover challenges encountered, mistakes made, lessons learned and end with a few thoughts on what might help us from the Chicken side.
     72
     73* 21:00 UTC - Bintracker: Writing a chiptune music editor in Chicken. (by utz)
     74
     75* 22:00 UTC - End of 2nd video session
     76
     77==== Sunday, 2012-04-11
     78
     79* 12:00 UTC - Official end of event
     80
     81The IRC channel will be open until an undetermined time, so there is still a lot of time for discussions, hacking and chatting.
     82
     83=== Current list of development proposals:
    4084
    4185* [[/c6-proposal-pump|New event dispatching system]] (by felix)
    42 
    43 Current list of presentations:
    44 
    45 * Testing CHICKEN and eggs (by mario-goulart)
    46 
    47 * Experiences using Chicken in a corporate compute environment for design automation (by Matt Welland): I'll give a quick overview of Megatest, logpro, refdb and sauth and then cover challenges encountered, mistakes made, lessons learned and end with a few thoughts on what might help us from the Chicken side.
    48 
    49 * Towards a better Duckyscript toolchain (by Vasilij "wasamasa" Schneidermann): I'll present [[https://depp.brause.cc/plucky/|plucky]], a [[https://github.com/hak5darren/USB-Rubber-Ducky/wiki/Duckyscript|Duckyscript]] compiler I wrote out of frustration with the existing toolchain. It processes a BASIC-style language describing human keyboard input, intended to be used for red teaming security assessments.
    50 
    51 * Bintracker: Writing a chiptune music editor in Chicken. (by utz)
    52 
    53 Current list of discussion panels:
    54 
    55 * Discussion on the results of the [[//surveys.call-cc.org/state-of-chicken/2021/|State of CHICKEN 2021 survey]]
    56 
    57 
    58 More details will follow.
    59 
    60 
    61 Till then,
    62 
    63 felix
Note: See TracChangeset for help on using the changeset viewer.