1. 06 Oct, 2020 3 commits
  2. 28 Sep, 2020 1 commit
  3. 24 Sep, 2020 1 commit
  4. 22 Sep, 2020 1 commit
  5. 12 Sep, 2020 2 commits
  6. 20 Aug, 2020 1 commit
  7. 26 Jun, 2020 2 commits
  8. 24 Jun, 2020 1 commit
  9. 30 Apr, 2020 4 commits
  10. 27 Apr, 2020 12 commits
  11. 07 Apr, 2020 1 commit
    • Daniel Berrange's avatar
      github: enable lockdown of issues and merge requests · c4fcfc9a
      Daniel Berrange authored
      Libvirt uses GitHub as an automated read-only mirror. The goals were to
      have a disaster recovery backup for libvirt.org, a way to make it easy
      for people to clone their own private copy of libvirt Git, and finally
      as a way to interact with apps like Travis.
      
      The project description was set to a message telling people that we
      don't respond to pull requests. This was quite a negative message to
      potential contributors, and also did not give them any guidance about
      the right way to submit to libvirt. Many also missed the description and
      submitted issues or pull requests regardless.
      
      It is possible to disable the issue tracker in GitHub, but there is no
      way to disable merge requests. Disabling the issue tracker would also
      leave the problem of users not being given any positive information
      about where they should be reporting instead.
      
      There is a fairly new 3rd party application built for GitHub that
      provides a bot which auto-responds to both issues and merge requests,
      closing and locking them, with a arbitrary comment:
      
         https://github.com/apps/repo-lockdown
      
      This commit adds a suitable configuration file for libvirt, which
      tries to give a positive response to user's issue/pullreq and guide
      them to the desired contribution path on GitLab.
      Reviewed-by: Andrea Bolognani's avatarAndrea Bolognani <[email protected]>
      Reviewed-by: Pavel Hrdina's avatarPavel Hrdina <[email protected]>
      Reviewed-by: Eric Blake's avatarEric Blake <[email protected]>
      Signed-off-by: Daniel Berrange's avatarDaniel P. Berrangé <[email protected]>
      c4fcfc9a
  12. 16 Jan, 2020 1 commit
  13. 18 Nov, 2019 2 commits
  14. 12 Nov, 2019 1 commit
  15. 23 Sep, 2019 1 commit
    • Pavel Hrdina's avatar
      build: convert to Meson/Ninja build system · d98e00cf
      Pavel Hrdina authored
      Meson build system is simple and quick compared to Autotools and it's
      able to fully replace our Autotools usage.  There are few drawbacks as
      it's a fairly new build system, it requires Python 3.5 and Ninja 1.5.0,
      it's still evolving and the user base is not that large and there were
      some tweaks required to achieve the same functionality.
      
      However, there are benefits, the configure and build time is way shorter
      and build definition files are more readable and easier to maintain.
      
      There are some major changes with Meson build system:
      
          - there is no syntax-check target, the syntax-check is part of Meson
            test suite but it's still possible to run it separately,
      
          - Meson forces separation between source and build directories
      Signed-off-by: Pavel Hrdina's avatarPavel Hrdina <[email protected]>
      Tested-by: Jano Tomko's avatarJán Tomko <[email protected]>
      Reviewed-by: Fabiano Fidêncio's avatarFabiano Fidêncio <[email protected]>
      d98e00cf
  16. 18 Sep, 2019 1 commit
  17. 16 Apr, 2019 1 commit
  18. 18 Jan, 2019 2 commits
  19. 08 Jan, 2019 1 commit
  20. 11 Oct, 2018 1 commit