Page History
...
- Always provide us with as many details as you can. A paragraph description is good, but a few paragraphs with some sample use cases is even better. A single sentence description is often very hard to work with, and we may need to ask you for more information before we understand what you are asking for.
- If you have use cases , or local needs, please describe them to us. Use cases really help developers understand why this feature is important. In addition, and use cases may also help us locate other institutions with similar needs (who may be willing to help us develop this feature).
- Expect that we probably will need to ask you a few questions. Even with detailed descriptions/use cases, chances are we 'll will need to follow up with you later for a few more details, or to make sure we understand exactly what you are asking for. So, please be willing to respond to questions or requests for additional details. Anytime someone comments on your newly created issue, you will receive an email from the Issue Tracker system.
...
Overview
Content Tools