Gitlab.com is down

> YP says it’s best for him not to run anything with sudo any more today, handing off the restoring to JN.

Then in the post-mortem about lack of backups:

> LVM snapshots are by default only taken once every 24 hours. YP happened to run one manually about 6 hours prior to the outage > Regular backups seem to also only be taken once per 24 hours, though YP has not yet been able to figure out where they are stored. According to JN these don’t appear to be working, producing files only a few bytes in size.

I have had (and inevitability will have again) bad days like poor YP. All I can count on is to maintain good habits, like making backups before undergoing production work like YP did.

Indeed, the feeling of dread when you do something that causes prod to go down is bad enough. I can't even imagine the feeling when accidentally deleting prod data...

I’ve actually been exploring this concept myself with a blogging side project I’m working on.

Things were “mehhh” for developer interest for the first month or so, as a I was working off of an internal todo list. I didn’t think anyone cared about my 300 line long todo.txt file, but then I started to wonder if I should find a way to put that doc out in the open for developers to follow, and possibly jump in and contribute.

I had a hinkling that I could use GitHub issues to help with this, but I believed the title “issues” would hurt my project. I was under the impression that a new open source project with a single contributor, and a ton of open “issues” would look bad to developers.

I started to inquire with devs on IH and hear about using issues for feature tracking. Much to my surprise, I got an overwhelming “yes, you need to use issues”. I was also told not to worry about the misleading “issues” title, and that enough developers were knowledgeable enough to know they weren’t just bug reports.

As I started to open issues, and ask for help; surprisingly I started getting traffic and interest. The more issues I opened, and the more open I was online about my code and plans for it; the more followers and contributors I’ve gotten.

My plan at this point is to just follow Gitlabs model, and go full open transparency with everything.

My side project mentioned above can be downloaded here: https://github.com/elegantframework/elegant-cli

i think ultimately this will not be entirely possible. if a company posts transcripts with real names of people that can be damaging for the people (they moght misbehave simply due to company culture, pressure not visible through the open process etc.) which then would give a company a cheap way out (emplyee scapegoat). since this is a possibility, i think employees amd unions etc. would resist. despite if it was an honest afair it would be awesome, and that (possible but improbable) future looks super cool :)

Yeah you can't really. It doesn't support a ton of syntax and features.

And they also said they were going to remove that ability too. Tbf to them after the inevitable response they did say they will come up with a proper solution, though that was some time ago.

Obviously the real solution is to use Bazel and not to use Gitlab CI as a crap build system.

If by local you mean local to a cloud instance that runs automated builds on every merge for specific branches, then yes.

Granted, those build instance pull from the central git repo, and are triggered from GitLab... so also, no.

Only for `script: "echo hello world"` style jobs; anything more real makes `gitlab-runner exec` a total farce

You've never come across the Linux kernel? The Linux kernels process isn't practical? Okay, that's an interesting point of view.

you don't need to send patches via email, you can push them over ssh pretty easily

For example on my team we have a few devs who push patches from laptop directly to their work desktop, as a part of day-to-day synchronization. No central ssh server involved.

I'm not sure why you think you would need to "run your own mail infrastructure" to use git send-email, but you don't.

"Only wimps use tape backup. REAL men just upload their important stuff on ftp and let the rest of the world mirror it." Linus Torvalds

Technically a git repository is a blockchain.