Re: RFC: Moving git-gui development to GitHub

[Birger Skogeng Pedersen <birger.sp@gmail.com>]

Hi,

I would _love_ to see git-gui development moved to GitHub (or a
similar solution like Gitlab or Bitbucket). I have only submitted a
few patches, comments and new topics to this project. But I find the
use of mailing lists to be a _lot_ less efficient than using a
repository hosting service (like GitHub).

Advantages with GitHub
- Tidier than emails (very much so). Threads are neatly separated in a
single list, comments to threads are listed under their respective
thread. Threads can be linked.
- It's a lot easier to get a total overview of all issues. Especially
useful when you'd want to see open issues. Pratyush mentions he has a
text-file on his computer where he lists all the currently open
issues. We can't see this text-file. And even if we could, we'd still
have to navigate the mail archives to find the discussions and read
the emails one page at a time.
- It's a lot less hassle to submit patches (PRs), easier for everyone.

Disadvantages
- Git GUI contributors must have a GH account.
- All the data (threads, discussions, patches, etc) is not backed up
to such a large extent as it is when everyone has a copy of everything
in their email inboxes.


Best regards,
Birger