hackathon-topics.json

[
    {
        "title": "Documentation Summit",
        "homepage": null,
        "description": "Brainstorming ideas and active work session to improve the over-all official documentation for NixOS, Nix and Nixpkgs.",
        "host": "disassembler",
        "required_experience": "The experience level does not matter, everyone is welcome and can contribute to our documentation efforts!"
    },
    {
        "title": "Has Nix a future? The future of Nix(Ops) in the age of containers, orchestrators and microservices",
        "homepage": null,
        "description": "<p>I'd like to trigger a discussion by stating a controversial idea and see where this leads us.</p><p>The utility of Nix/nixpkgs as a development tool is still unparalleled. However, the industry is moving towards containers and orchestrators, and I argue that NixOS and NixOps are becoming less relevant now that the industry is moving to this new model.</p><p>These changes might actually pose an existential threat to Nix, given that (container) build systems might get \"good enough\". Alternatives that operate in the same area are Bazel by Google, Habitat by Chef, the new BuildKit by Docker.</p><p>My question to you is: how could we leverage this move to containers/orchestrators, and archieve World Domination?</p>",
        "host": "moretea",
        "required_experience": null
    },
    {
        "title": "Python & Nix tooling improvement",
        "homepage": null,
        "description": "We do have pypi2nix, pip2nix and some good ideas about how to make the experience for Python developers better. I would like to update each other, put thoughts together, maybe tweak a few things around those.",
        "host": "johbo",
        "required_experience": "Prior usage of pypi2nix or pip2nix useful."
    },
    {
        "title": "Teach Us Hydra",
        "homepage": null,
        "description": "Teach us hydra: We would like to learn how to set up hydra and build some simple overlay. We promise to create some sort of documentation in return!",
        "host": "disassembler & gilligan",
        "required_experience": "You should know hydra better than we do :)"
    },
    {
        "title": "Board please? :-)",
        "homepage": null,
        "description": "There are a lot of discussions on whether or not to install more rules and procedures for NixOS and which those should be. I believe that before we can even have this discussion we need what most other projects of comparable size have: some sort of steering committee. One potentially non-controversial way to determine initial members of this board would be to nominate all prior release managers",
        "host": "gilligan",
        "required_experience": null
    },
    {
        "title": "Typing Nix",
        "homepage": null,
        "description": "The typing-nix project ended up with a nice theoretical system. This now needs to be refined and implemented in order to be a real thing, for which I will need the hep of the community.",
        "host": "regnat",
        "required_experience": "Some haskell is most probably needed for the implementation itself, but everyone is welcome to submit ideas and discuss the design"
    },
    {
        "title": "Test ALL the things",
        "homepage": null,
        "description": "<p>I will work on the package tests I introduced in <a href=\"https://www.youtube.com/watch?v=6bLF7zqB7EM\">my talk</a>.</p><p>If you want to help, have questions or want to know how to write tests for your package, please join me!</p>",
        "host": "Profpatsch",
        "required_experience": null
    },
    {
        "title": "taggedUnion type for the module system",
        "homepage": null,
        "description": "<p>Tagged unions, also called sum types, can represent different values which have a nested type themselves. A practical example where this is useful is <code>hdparm -a</code>, which represents different semantic values with ranges in one byte. In nixos we could represent that with <code>type = taggedUnion { off = unit; low = int.between 1 127; high = int.between 128 254; };</code>.</p><p>I am having a bit of trouble with how to define the merge function, so please shout if you know the insides of the module system.</p>",
        "host": "Profpatsch",
        "required_experience": "a bit of nix to help OR the module system to help a lot"
    }
]