[Hackathon-list] Results of the First Virtual RIPE NCC Hackathon

Vesna, Michael,

Thanks for sharing. I've added some thoughts inline.

On 6/14/20, 11:42 AM, "Hackathon-list on behalf of Michael Richardson" <hackathon-list-bounces at ripe.net on behalf of mcr at sandelman.ca> wrote:


    you've CC'ed hackathon-list at lripe.net.  Is that a typo?
    As I said in a bunch of emails, lists.ripe.net is not answering SMTP.
    I'm gonna remove the l, and hope hackathon-list at ripe.net actually works.

    Vesna Manojlovic <BECHA at ripe.net> wrote:
        >> It's difficult for a great number of reasons, but I would never call them
        >> Hackathon events, because there is such a different vibe.

        > coming up with a new name is always a challenge :)

    RIPEathon.
    HACKaRIPE.
    RIPE-collaborative-community

We struggled with this for the IETF Hackathon. The word "hackathon" carries some negative connotations with it, but it carries several positive and attractive ones that are very appropriate for the IETF Hackathon as well. By this point, the name is well established. Anyone who has experienced an IETF hackathon understands the nature of it, and we clearly state the collaborative native up front. Eliminating any notion of prizes or awards has helped too.

        >> But, I really think that a key part of the Hackathon experience is that it
        >> involves a focused effort of a short period of time.  As you write, the
        >> whole point is that it involves being exclusive to the activity.  Being
        >> physically close adds so many useful interactions.

An intense, primarily in-person, weekend together right before the rest of the IETF meeting has worked very well for in-person IETF meetings. We realize this will not work for virtual IETF meetings. For IETF 108 online, we are experimenting with a less intense and more loosely coordinated virtual hackathon the week before the IETF meeting. Hopefully this works well. We will use the experience to guide future virtual events and improve remote participation in future in-person events.

Cheers,
Charles

        > Unfortunately, for the rest of this year at least, physical closeness
        > will be considered more dangerous than it is beneficial..

    Yes, that's true.
    I want to point that spreading the effort over many weeks may be something
    *not* to do here.    Having a few SPIKEs of four to six hours may work well.

        > Speaking of names, we had hosted an internal RIPE NCC "collaborathon" in
        > 2018, where the goal was to involve "non-technical" people (I hate that
        > distinction!), who would be scared away by the idea that "hacking" has
        > to do only with programming...

    Fair enough.

        > Internet Measurement Village 2020: online event,
        > that aims to share the tools, datasets, and methodologies
        > of projects that measure the Internet.

        > from Wednesday, 10th June 2020 to Friday, 3rd July 2020
        > https://ooni.org/post/2020-internet-measurement-village/#schedule

    You have an event almost every day. That's a lot.

        > IETF 108 Hackathon Online
        > Monday, July 20 through Friday July 24, 2020
        > https://www.ietf.org/how/runningcode/hackathons/108-hackathon/

    Of course, I already know about this :-)

    --
    ]               Never tell me the odds!                 | ipv6 mesh networks [
    ]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
    ]     mcr at sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [