(This is the author, Mike Heins, speaking.)
I am interested in creating a better MiniVend. However, it has become pretty popular and you should not expect individual support.
What I will typically do:
Follow up on cogent bug reports, usually with fairly quick response. A bug is not that you cannot install MiniVend -- it is a demonstrated fault in the program logic that can be duplicated. A cogent bug report is detailed and concise, and includes HTML/code snippets that demonstrate the problem.
Take note of faults in the demo. Any fixes will be discussed on the mailing list and may be fixed in the next release version of MiniVend. The demos are demos -- not a finished application.
Take note of faults in the documentation and update the next release version of MiniVend. If you provide edited replacement text it is appreciated. The documentation source is available if you would like to see how it is maintained.
Try to answer some of the well-presented questions that appear on the mailing list.
Try to constantly and incrementally improve the FAQ and other supporting information.
All of these are things I try to do. There is no commitment -- check your license for MiniVend. All are done on a time-available basis. If you don't include all relevant information I will probably ignore the question. I answer on the mailing list so that information can get to more people and be archived for posterity.
What I will not do:
Accept phone calls about MiniVend.
Answer questions that are URGENT or cry for HELLLPPP!!!!
Conduct tutorials.
Visit a URL to look at a problem.
Conduct a Q&A to extract needed information.