...and in general we want a best-practise way of using images in the README (might be nice with e.g. a GIF animation in it, showing command-line usage of k6)
https://asciinema.org/ maybe?
Opinions on this? https://asciinema.org/a/5lpa1ik4bnquwh53igj7tp1e8
Animations are great, makes a repo look much more interesting.
some more points:
k6 headerinstall section should be first up(ci badges?)
(description)
(small usage example)
-> installation
-> usage
->-> scripting etc.
->-> cli usage etc.
-> contributing
The only thing I don't like is that it promises new things we don't currently have (brew and apt packages). Introducing new, unfilled dependencies is something that complicates an issue and slows down the release process for new things or updates substantially. I would have updated the README with the current installation methods and then created two new issues for creating brew and apt packages. Each issue can then stand on its own feet, is easy to resolve, and there are no dependencies.
I'm gonna get on at least homebrew packaging before the presentations next week, gonna have a shot at Debian and Ubuntu too and see how much I remember from my days maintaining KCT packages for both.
from my experience creating a homebrew tap and a formula is a 20-minute effort, so it shouldn't be a problem
You can now do:
brew tap loadimpact/k6
brew install k6
Working on Ubuntu packages.
Suggest removing the reference to Debian packages (but adding a new issue about it), adding the build instructions again, at the end of the file, and then merging this (or add the build instructions in a separate BUILD.md or similar, and just point to it in the README).
Merged!
Most helpful comment
Opinions on this? https://asciinema.org/a/5lpa1ik4bnquwh53igj7tp1e8