General enquiries

Questions

Questions about TaskCollect are welcome! If you are unsure about anything, or want to find out something about TaskCollect, you can talk with us via the following contact methods:

Please be mindful of the fact that the TaskCollect development team is busy and works on TaskCollect outside of working hours, during our free time. Our response times may reflect this.

Reporting issues

If you have encountered an issue in TaskCollect, please email taskcollect-discuss with a description of your problem. Your email should include:

  1. A concise summary of the issue in the subject line (max 70 characters)
  2. A detailed description of the problem
  3. The full details of when the problem occurs
  4. The version (and build, if applicable) of TaskCollect you are running
  5. The operating system and CPU architecture of both the web server and browser
  6. The name and version of your web browser
  7. The names of any installed browser add-ons that change the content of webpages (e.g. adblockers, dark mode plugins)

Please be courteous and respectful when reporting issues. Our team dedicates time and effort to working on TaskCollect, which is unpaid volunteer work done during our free time. Please be considerate of this fact and be mindful that our capabilities are very limited. Rude and offensive discourse will not be tolerated and will result in moderator action.

Feature requests

You may request a feature for TaskCollect by emailing taskcollect-discuss. We will try to consider your request as much as we can but it is also possible that we may decline your request. This may because we believe the underlying problem may be solved in a more effective way, that the request would harm our project goals, or potentially for some other reason.

When filing a feature request, you should be ready to discuss why you need the feature and what your use case is. We try to find the most effective way to solve problems, and sometimes users don't know what exactly the best solution for them is. On the other hand, we don't fully understand all the nuances of the problems users experience. This is why we try to turn feature requests into discussions, so that we can give something everyone will be happy with.