bors-ng / bors-ng.github.io

bors.tech

The https://bors.tech web page

For more information, see the bors-ng/bors-ng repository. This repository is just a bunch of meta stuff surrounding it.

This site is generated using jekyll. For simple changes, you can just edit right on GitHub (GitHub's own Markdown preview will match up with the website's rendering as long as you don't use inline HTML or Liquid templates). If you're moving a lot of stuff around, though, you'll want to install Jekyll, clone this repo, and use jekyll serve to preview it.

bors-ng.github.io's Issues

Suggestion: Verify the `bors.tech` domain with GitHub

Since you own the bors.tech domain, it would be pretty quick and easy for you to verify the domain with GitHub. (https://help.github.com/en/articles/verifying-your-organizations-domain)

Doing so gives you a nice green "Verified" badge on the https://github.com/bors-ng page. There aren't really any other benefits, but certainly it looks nice to have your organization be "verified".

Include the Code of Conduct document on the main site

It's probably a good idea to have that document somewhere other than just the bors-ng/bors-ng repo, since https://bors.tech/conduct/ is way better than https://github.com/bors-ng/bors-ng/blob/master/CODE_OF_CONDUCT.md.

You don't need to find a place to link to it within the main site, since it's a moot point unless they click the "Edit this page on GitHub" button and we can make sure github itself mentions it in the contributing doc and pull request template. We'll probably want to have a whole page just for "community resources" once we have enough community resources to fill the page, and the CoC will be on top of that.

Right now, though, it's just nice to have a permalink to the thing.

Get someone other than notriddle to read the ToS

Make sure it's reasonable.

Use AMP?

https://www.ampproject.org/

Since bors.tech is already running out of CloudFlare, and is already pretty heavily optimized, I'm not sure if this would actually improve perf or not.

Projects that have been, or may in the future be, featured in TMIB

These have already been featured, so don't feature them again:

• mirrord
• eris
• devshell
• canape
• git-aliases-f18
• geoengine
• go-workwx
• dada-lang
• NixOps
• mailu
• voiceflow
• go-csv
• brevy
• zeebe
• awoos
• salsa-rs
• AdaSockets
• Mtac2
• once_cell
• meilisearch-php
• VersionVigilante.jl
• rust-sgx
• pest
• marionette_client
• JuliaGPU see their documentation about it here
• podman-py
• rust-uuid
• serde_with
• pursuedpybear
• AWSCore.jl
• crossbeam
• grmtools
• hiring-without-whiteboards
• Lean 3 community fork
• titun
• PredictMD.jl
• cerebrumcorp - https://cerebrumcorp.com/
• unit
• rust-analyzer
• openenclave
• wasmer
• multipass
• parking_lot
• bundler
• tock
• tink
• sodiumoxide
• therapist
• Pkg.jl
• rust-unic
• option-t.js
• Daedalus of Freedom
• how_is
• amethyst (and ron)
• pathfinding
• mozilla/normandy and buildhub2
• cockroachdb
• rust-num
• ddnet
• crates.io
• fusionapp
• Mir
• rayon
• hiredis
• specs
• ammonia
• pyvisa
• gfx-rs
• intellij-rust
• IMA-WorldHealth
• nix-rust
• hgrecco/pint
• georust
• nubisonline
• emberwatch/ember-language-server

If no other proposals are made, consult this list for projects that have been using bors-ng for more than two months; make sure they're still using it before featuring them. @notriddle is trying to make sure that most of the featured projects aren't Rust, even though most of bors-ng's users currently are Rust users, because we want this tool to be adopted outside of that clique:

• rust-french-numbers
• mcfunction-langserver

Add a link to the "Reference" document to the home page

There's a reference document at https://bors.tech/reference/ (the code for it is at /reference.md.

The only place that links to it is the Getting Started guide, and that's awful for discoverability. It would probably be better if the "quick reference" in the home page was replaced by a link to that (newer) document.

The "how to test" blog post

Interested in having blog posts other than the newsletter, should probably write a blog post about good unit and integration testing practices.

Update docs to include GitHub Actions example

I think it would be useful to add a GitHub Actions example

Remove inline JavaScript

DO NOT FIX THIS BUG UNTIL AT LEAST SIX MONTHS AFTER THE NEW CHROME WITH THIS FIX GOES OUT

Right now, the bors.tech home page combines inline CSS with a little bit of Javascript to asynchronously load the main CSS. It's there to get slightly quicker initial paint, particularly an initial paint with that nice blurb in it:

The annoying part is that it's based on JavaScript and DOMContentLoaded, and it's done by putting weird display:none rules in the inline first-paint CSS. In other words, a bunch of weird, finicky code that only exhibits bugs during a brief flash of partial content.

Once the new Chrome goes out, Chrome, Firefox, and Edge will all align on asynchronously loading CSS links in the <body> tag. So we'll be able to drop all those display:none rules and the home page will be truly free of JavaScript code (though it'll have to have an empty script tag with a single space in it 😋).

• https://jakearchibald.com/2016/link-in-body/
• https://www.chromestatus.com/feature/5696805480169472
• https://bugs.chromium.org/p/chromium/issues/detail?id=481122#c93
• https://chromereleases.googleblog.com/