Skip to content

Labels

Labels

  • A-help wanted

    Attention: More help is needed here, as I am out of my depth
  • A-pending-review

    Attention: This is ready for review and can be merged afterwards
  • A-pr-exists

    Attention: This issue has an associated pull request already, that should be completed & reviewed
  • A-question

    Attention: There is an open question for which more input is requested
  • C-d3-vis

    Component: The D3 interactive provenance visualization
  • C-doc

    Component: The Sphinx documentation (in docs/)
  • C-graph

    Component: The graph command, showing the provenance as a Graphviz graph
  • C-jupyter

    Component: The Jupyter notebook integration (reprozip-jupyter)
  • C-packer

    Component: The packer part of reprozip
  • C-packing-gui

    Component: The Tk GUI for packing
  • C-tracer (C)

    Component: The C part of the tracer codebase (_pytracer extension)
  • C-tracer (Python)

    Component: The Python part of the tracer codebase
  • C-unpack-gui

    Component: The Qt unpacking GUI (reprounzip-qt)
  • C-unpacker

    Component: New unpacker or common unpacker functionalities
  • C-unpackers/default

    Component: The default unpackers (directory & chroot)
  • C-unpackers/docker

    Component: The Docker unpacker
  • C-unpackers/vagrant

    Component: The Vagrant unpacker
  • C-unpackers/vistrails

    Component: VisTrails integration for unpackers
  • C-website

    Component: reprozip.org website
  • good first issue

    Newcomers welcome! This should be easy and self-contained enough for someone new to the codebase
  • hacktoberfest

    Newcomers welcome! This should be easy and self-contained enough for someone new to the codebase
  • O-distributed

    Objective: supporting ReproZip in distributed contributing environments (HPC)
  • R-duplicate

    Resolution: This issue has already been filed, please refer to the other ticket
  • R-invalid

    Resolution: This is not an issue for this project
  • R-wontfix

    Resolution: This will not be fixed. The report might be wrong or out of scope
  • T-bug

    Type: A fix for unwanted behavior, NOT a new feature or a simple enhancement
  • T-enhancement

    Type: En enhancement to existing code, or a new feature
  • T-housekeeping

    Type: Dealing with organization, services/hooks, running tests, packaging, ...
  • T-task

    Type: Something to be done, neither a bugfix nor an enhancement of the code