Last Saturday, I finally managed to ship all t-shirts with some much appreciated help from a friend and my SO! You should hopefully get yours soon (I'd imagine starting today for people from Germany). I'd really appreciate it if you could send me a quick mail (email@example.com) or ping me on IRC (#qutebrowser on Freenode) if yours arrived (and in what country you are).That helps me to keep track of how things look, since all shirts are sent without tracking.
We ended up bringing a big ~18kg parcel to the post office containing 55 envelopes:
As usual, not everything went quite to plan - here's a list of the mistakes we thankfully caught:
- I accidentally discarded a sheet of labels which still had three labels on it. This was caught by counting the envelopes at the end, and easy to re-print.
- Someone almost got a lady-cut M instead of a regular-cut one. Really glad we caught that one before it was too late.
- The glue on the padded envelopes didn't really hold well, so one opened while we were handling them. It turns out others were really close to opening as well - we were really lucky this happened while they were still at our place, and fixed it with some additional tape.
- It turns out a "big letter" shipped worldwide has a bigger maximum size than the same thing to Germany - there, a "maxi letter" is apparently needed. We only found out at the post office, and had to put some additional stamps on there - thankfully, this was only on 8 envelopes going to Germany.
- While I wrote some code to add additional text to the labels telling us what to pack (which streamlined things extremely compared to last year!), I forgot that I promised 10/15/20 stickers depending on the pledge levels. The ones with 20 stickers were easy to find (as they have two t-shirts), for others there was a pragmatic solution: Simply giving 15 stickers to everyone :)
I do hope everything else went according to plan, but if something is wrong with what you got, please contact me.
I've also been hard at work on per-domain settings, and I have a first prototype to show:
It's in the per-url branch, but not quite ready yet - if you want to try it, make sure to make a backup of your config directory first. As you can see, it requires a reload to apply the settings currently. I'll look into avoiding that where possible, but I can't quite tell yet to what extend that will be possible.
- Current state of per-domain settings
- qutebrowser v1.0.0 released!
- qutebrowser v1.0.0 is coming closer
- New config merged!
- Config revolution - Part 1 finished
- Refactoring more things, a working YAML config, and more!
- Refactoring all the things!
- First week
- First 2 days
- Getting started again
- Second qutebrowser crowdfunding launched!
- qutebrowser v0.10.0 released
- Wrapping up and looking at the future
- Days 39/40/41: Lots of features!
- Days 37/38: Hints in master, tests
- Day 36: Hints!
- Days 33-35: Mouse functionality, and rewriting hints
- Days 31/32: More web elements
- Days 29/30: Web elements
- Days 27/28: Settings and web inspector
- Day 24-26: Refactoring the WebElement API
- Day 21-23: After Europython and releases
- Day 19/20: Bugs everywhere!
- qutebrowser v0.8.0 released
- Day 17: Printing and searching
- Sending out qutebrowser and pytest stickers
- Day 15/16: Merged!
- Day 13/14: Almost merged!
- Day 12: Tests running!
- Day 10/11: Refactoring!
- Day 9: A bit of everything
- Day 8: More fixing and pytest sprint/training
- Day 7: Fixing things
- Day 6: Branching off
- qutebrowser v0.7.0 released
- Day 4: Playing whack-a-mole
- Day 3: Last pull requests and managing requirement files
- Day 2: More pull requests and nicer test output
- Day 1: Merging pull requests, and a stupid bug
- About and Timeline