General CKAN Users Discussion
We have a general discussion Google Group at:
All are welcome!
Technical Questions or Issues
If you need help with CKAN or want to ask a question about CKAN, use either the ckan-dev mailing list or the CKAN tag on Stack Overflow (try searching the Stack Overflow and ckan-dev archives for an answer to your question first).
Note: If you don’t get a quick response (over 48 business hours) on StackOverflow then please email the issue URL to the ckan-dev mailing list.
If you’ve found a bug in CKAN, open a new issue on CKAN’s GitHub Issues (try searching first to see if there’s already an issue for your bug).
If you find a potential security vulnerability please email firstname.lastname@example.org, rather than creating a public issue on GitHub.
If you just want to discuss your CKAN development, please come and say hi on the #ckan IRC channel on irc.freenode.org.
Contributing to CKAN
For contributing to CKAN or its documentation, see CONTRIBUTING.
If you want to talk about CKAN development say hi to the CKAN developers in the #ckan IRC channel on irc.freenode.net.
- We just released patch releases for CKAN 2.4 to 2.7 Please upgrade to get the latest fixes 👉 http://t.co/D0MUYfYwcC 3 weeks ago
- RT @starl3n : Built with @CKANproject by @link_digital :) Another #opendata success with #FOSS http://t.co/g9WOraidoi 1 month ago
- RT @ReadDavid : CKAN DataStore made ⏩faster⏩ in new CKAN 2.7 release http://t.co/dgpVdMmX2O @CKANproject 2 months ago