|Version 3 (modified by hasienda, 2 years ago) (diff)|
Care to squeeze a bug?
I'm open to contributions. I'll try my best to apply reasonable improvements to the source in a timely manner, as my spare time permits. This is valid even if a ticket doesn't explicitly state «Patch welcome». I really don't mind opening a ticket even for very small changes, as it's much easier to track them this way.
If you decide to work on an issue, please drop me a note ASAP. This is just to ensure to minimize duplication of efforts. Sometimes preparation and testing of patches takes a long time, so you may not be aware of a pending change/solution from reading the ticket comments alone. Similar rule may apply to bug reports with patches, even if you feel your fix isn't already good enough for commit. Sharing it, may enable collaboration for a much quicker, better result.
I may feel, that there are not enough information to resolve some tickets.
I'm just asking for assistance in testing.
Or it's unclear, if the issue in question is still relevant at all.
Following tickets match this category needinfo:
- Extend AccountManager to allow non-password-based authentication methods
- login via https, client certificate should anyway allow to set a password or create an account
- HTTP Auth allows for groups, why not use them?
- [patch] Users can't get verification email
- [patch] Add a RadiusAuthStore to AccountManagerPlugin
- French translation
- IOError: (22, "invalid mode ('r') or filename")
- Reset password still valid after first login
- Provide confirmation when password is changed
As there wasn't much support some time ago, I tend to leave these tickets open for a fair amount of time.
But I may still close them after 6 months or so, counting down from time of tagging for clearance, if there's no substantial response.