Feedback: Difference between revisions
| Line 11: | Line 11: | ||
* for [[:Category:DOCK|DOCK software development]], write to dock-dev at docking.org. | * for [[:Category:DOCK|DOCK software development]], write to dock-dev at docking.org. | ||
= | = WHEN REPORTING BUGS = | ||
Please | Please be as clear and complete as you can be so that we can fully understand the problem and reproduce it. For instance, include ZINC ID or DOCK Blaster JOB ID or SMILES or the website you are referring to. Enumerate the steps to reproduce the problem. One reason for a slow response can be that we simply did not understand what you are asking us. | ||
[[Category:Problems]] | [[Category:Problems]] | ||
Revision as of 14:33, 14 May 2014
We welcome feedback, good and not so good! There are many ways to communicate with us, depending on the topic and the urgency.
URGENT PROBLEMS
If our website appears down, please email support at docking.org or call +1 (415) 937-1461. Please do not use this address for non-urgent communication. If you are a lab member and need something done, write to Sysadmins by email please.
QUESTIONS, COMMENTS, DISCUSSION
In general, you may write on this wiki, write on our blog, post on our facebook or post to our twitter stream.
- for ZINC, write to the ZINC community at zinc-fans at docking.org, post on our facebook page.
- for DOCK, write to the DOCK user community at dock-fans at docking.org.
- for Category:DOCK Blaster, write to the DOCK Blaster user community at blaster-fans at docking.org.
- for DOCK software development, write to dock-dev at docking.org.
WHEN REPORTING BUGS
Please be as clear and complete as you can be so that we can fully understand the problem and reproduce it. For instance, include ZINC ID or DOCK Blaster JOB ID or SMILES or the website you are referring to. Enumerate the steps to reproduce the problem. One reason for a slow response can be that we simply did not understand what you are asking us.