I count among those who are happy to see money in opensource projects.
It might raise tricky governance problem at times but in this case it
seems ok. I suppose some of the money (5-25% depending on qutebrowser
coding workload is handled) could be redistributed as bug bounties so
that other regular
+1 for set default to what ever Florian wants and we can change as needed
On Tue, Jul 26, 2016 at 2:21 AM Brent Moran wrote:
> Set any defaults you like; your user base is plenty competent to change
> them (and will probably stay that way, given the nature of the browser
> :) ). Of course, that
* Florian Bruhin [2016-07-26 14:23:28 +0200]:
> Source release and binaries for Windows/OS X are available, the Debian
> packages are still work-in-progress.
Debian packages are uploaded in the meantime.
The .dmg unfortunately was broken and qutebrowser wouldn't start at
all. I now uploaded a fi
Hi,
I'm happy to annouce the release of qutebrowser v0.8.0!
The main reason for this release is that v0.7.0 will break with
PyQt 5.7 which is soon going to be released.
I decided to do a new minor release instead of a patch release as
plenty new features have accumulated already. If your distrib
Set any defaults you like; your user base is plenty competent to change
them (and will probably stay that way, given the nature of the browser
:) ). Of course, that may mean the income from setting such a default
will be severely diminished. I guess if no one uses it, you can always
change it bac
