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.
Markdown formatting
ESC to close
Markdown turns plain text formatting into fancy HTML formatting.
Phrase Emphasis
*italic* **bold**
_italic_ __bold__
Links
Inline:
An [example](http://url.com/ "Title")
Reference-style labels (titles are optional):
An [example][id]. Then, anywhere
else in the doc, define the link:
[id]: http://example.com/ "Title"
Images
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Headers
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Lists
Ordered, without paragraphs:
1. Foo
2. Bar
Unordered, with paragraphs:
* A list item.
With multiple paragraphs.
* Bar
You can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning
Blockquotes
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Horizontal Rules
Three or more dashes or asterisks:
---
* * *
- - - -
Manual Line Breaks
End a line with two or more spaces:
Roses are red,
Violets are blue.
Fenced Code Blocks
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Header IDs
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Tables
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowDefinition Lists
Term 1
: Definition 1
Term 2
: Definition 2Footnotes
Body text with a footnote [^1]
[^1]: Footnote text here
Abbreviations
MDD <- will have title
*[MDD]: MarkdownDeep
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