RavenDB has the best users
time to read 1 min | 51 words
Talk about making my job easy. Thank you Barry, and I am sorry it took me 17 minutes to get the fix out.
Ayende @ Rahien
Ayende @ Rahien
Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by email or phone:
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by email or phone:
+972 52-548-6969
FUTURE POSTS
- PR Review: Beware the things you can’t see - 2 days from now
- The right thing and what the user expect to happen are completely unrelated - 3 days from now
- PR Review: It’s the error handling, again - 4 days from now
There are posts all the way to Oct 25, 2017
RECENT SERIES
-
PR Review
(7):
20 Oct 2017 - Code has cost, justify it -
RavenDB 4.0
(15):
13 Oct 2017 - Interlocked distributed operations -
re
(21):
10 Oct 2017 - Entity Framework Core performance tuning–Part III -
RavenDB 4.0 Unsung Heroes
(5):
05 Oct 2017 - The design of the security error flow -
Writing SSL Proxy
(2):
27 Sep 2017 - Part II, delegating authentication
RECENT COMMENTS
-
By Federico Lois on PR Review: Code has cost, justify it
-
By Oleg Mihailik on PR Review: Code has cost, justify it
-
By tobi on PR Review: Code has cost, justify it
-
By Oleg Mihailik on PR Review: Code has cost, justify it
-
By Erik Heemskerk on PR Review: Code has cost, justify it
Syndication
| Main feed |
|
| Comments feed | |
Comments
You've got the best business model in the world, don't pay developers just have the community fix your product! You should start offering reduced licenses for people who find/fix bugs. That should iron out a few more kinks in the product.
@jon I hope you were being sarcastic. Most of these types of bugs are edge cases that don't show up outside of real world use. Oren has a great track record of fixing these bugs quickly. Even quicker if the customer provides a failing test. If I'm not mistaken a bug report is NOT a bug fix.
@Killman of course!
There should actually be a strong incentive for users to do this. If they provide you a failing test for an issue, chances are you will incorporate that into your automated runs. Thus, the likelihood that the issue that broke them specifically will re-emerge has dropped drastically.
I wouldn't presume to expect any form of free or reduced price for a non-OSS license just for submitting a bug report, even one that came in the form of a failing test. But, that would be a nice incentive to go so far as to fork the github project, fix the bug, then issue a pull request.
A free or reduced license for use in closed source project(s) would be a nice bonus for getting a pull request accepted into the core. But if you think about it, having ones name in the list of contributors of such a large project would be a real bonus for the old resume and the value of that might far exceed the cost of a free production license.
Comment preview