Why the move from GitHub?

[cgarz]

I can't find any information anywhere in my searches.

The news section on the site simply says:

2019-04-13
     Megatools moved off github.

and the NEWS file doesn't go beyond 2018-07-31.

If you really don't monitor here at all anymore then I'll try email as per the readme.

[Megous]

Github was usually a source of pain due to:

• Inability to disable downloads section. Users would find megatools via github, not notice it's just used as a mirror/issue tracker and procede to download megatools from there, and run into all kinds of issues, because of not using a release tarball.

• Pull requests being annoying as hell to handle in my workflow. It may be fine in a project where requesters care to fix their mess after sending a pull request, but that's a minority on the project of this size. It's mostly drive by's. Even in big projects, like Linux kernel, pull requests are only reserved for maintainers, not for casual contributors. It's much less git ceremony for me if I just get a patch via e-mail. I can just apply it, clean it up, test it and only push it out afterwards to the master. It's 1/3 of the work.

• Final straw was getting a pink unicorn error for my IP for 24 hours, while people kept communicating with me over github. It was a nice reminder of how little control I have to fix issues, when they happen if I don't control the infrastructure. And I already have the infrastructure elsewhere... so what's the point.

Megatools was distributed since the beginning (5 years ago) via my website. I've also started hosting my repositories on my website quite some time ago. So this is just continuation of a move to self-host and to avoid pull request UI and download issues (as you can't disable any of these features on github).

I recognize users find it useful to communicate between themselves, so I'll keep the issues open, and I might even chime in if I get an e-mail notification from github, but hosting and developement will move to my infra completely.

On Sun, Apr 14, 2019 at 05:29:52PM -0700, GitHub wrote:

I can't find any information anywhere in my searches.

The news section on the site simply says:

2019-04-13
     Megatools moved off github.

and the NEWS file doesn't go beyond 2018-07-31.

If you really don't monitor here at all anymore then I'll try email as per the readme.

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/megous/megatools/issues/446

[cgarz]

Thank you very much. A very thorough explanation.

I also prefer self hosting so I wholeheartedly understand. Megatools is integral in the backup aspect of that actually. :grin:

For an issue tracker though, as you say, the more public discussion aspect of this style is well liked by many, including myself. So is it still okay to use here for issues or is there a possibility of them being missed? What is your preferred method that can maintain this public discussion structure? Could this issue tracking style also be self hosted if you want to completely discard GitHub?

Also, I should have said before, many thanks for making megatools! Super useful, I use them often :smile:

[Megous]

Keeping issues open here is fine. I only mostly got to them because of an e-mail notification, so that will not change.

I'd rather not manage a mailing list or a separate issue tracker for < 100 issues per year on avg. If I did, it would certainly see less than that amount of traffic, too. ;)

I changed the email address and all new mail to [email protected] will be public on the megatools website. So that will at least help with the openness of all the communication about the project.

On Mon, Apr 15, 2019 at 03:45:31PM +0000, GitHub wrote:

Thank you very much. A very thorough explanation.

I also prefer self hosting so I wholeheartedly understand. Megatools is integral in the backup aspect of that actually. :grin:

For an issue tracker though, as you say, the more public discussion aspect of this style is well liked by many, including myself. So is it still okay to use here for issues or is there a possibility of them being missed? What is your preferred method that can maintain this public discussion structure? Could this issue tracking style also be self hosted if you want to completely discard GitHub?

Also, I should have said before, many thanks for making megatools! Super useful, I use them often :smile:

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/megous/megatools/issues/446#issuecomment-483307526

[cgarz]

That's great I appreciate it. GitHub does seem like the best place for it.

How do I view the emails on the megaous site? I can't find info on it anywhere.

Also just noticed Google+ is still linked on the main page. Looks like its finally just discontinued now.

[Megous]

On Mon, Apr 15, 2019 at 10:15:13AM -0700, GitHub wrote:

That's great I appreciate it. GitHub does seem like the best place for it.

How do I view the emails on the megaous site? I can't find info on it anywhere.

No e-mails were sent to the new address yet. It will be on the main site, as soon as it will start making sense.

Also just noticed Google+ is still linked on the main page. Looks like its finally just discontinued now.

Thanks.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/megous/megatools/issues/446#issuecomment-483340097

[cgarz]

Ah I see. No probs. Should I now close this or leave it open for anyone else who is curious to see? Might be better to link to it from issue #445.

[Megous]

Just keep it open.

On Tue, Apr 16, 2019 at 05:52:54AM -0700, GitHub wrote:

Ah I see. No probs. Should I now close this or leave it open for anyone else who is curious to see? Might be better to link to it from issue #445.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/megous/megatools/issues/446#issuecomment-483646379

[vegnuli]

just use gitlab.. allthe things are configurable there! @megous

[afterdelight]

this is a very bad and stupid decision. the new git site looks like scramble eggs inside an ass. cant read single sh*t

[mckaygerhard]

t

@afterdelight seems you dont know how to use command line neither git.. the new git is just cgit .. has tree, comits and references just like any other git frontend.. for sure windoser