Support
If you want to report issues or suggest improvements to CHICKEN, there are a couple of possibilities (see below). Please choose the one that is more convenient for you.
When reporting bugs, please check the "How to report issues" section below on what information to provide.
Via e-mail
Send a description of the issue/suggestion you want to report to the chicken-users mailing list.
If you are not subscribed to the mailing list (and don't want to subscribe), no problem. Your e-mail will end up in a moderation queue. No need to resend your e-mail -- it will be eventually aproved by the moderators. Please add a note in your message indicating that you are not subscribed to the mailing list, so that we know that we must explicitly add your address to the list of recipients of the message when replying.
Using tick
tick is a command line tool to interface with the git repository used to store CHICKEN tickets. Currently only CHICKEN maintainers have write access to this repository, but you can still use tick to submit patches to it. See the Submitting ticket changes via email section in the tick documentation for more information.
If you are not subscribed to the chicken-janitors mailing list (and don't want to subscribe), no problem. Your e-mail will end up in a moderation queue. No need to resend your e-mail -- it will be eventually aproved by the moderators. Please add a note in your message indicating that you are not subscribed to the mailing list, so that we know that we must explicitly add your address to the list of recipients of the message when replying.
Via IRC
Use the #chicken channel on Libera.Chat to report issues/suggestions.
Relevant information when report issues
When reporting issues, please make sure to, whenever possible, the following information:
- the CHICKEN version you are using
- the C toolchain used with CHICKEN and its version
- in case of issues involving eggs, the version of the eggs involved (hint: use chicken-status to obtain information on version of eggs)
- operating system and hardware platform where the issue is occurring
- a minimal case for developers to reproduce the issue you are facing
Any other additional information you think can be relevant to the description of the problem is welcome, naturally.