Users Discussion, Technical Questions or Issues
If you need help with CKAN or want to ask a question about CKAN, use either the ckan-dev Google Group 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 [email protected], rather than creating a public issue on GitHub.
If you just want to discuss your CKAN development, please come and say hi in the CKAN Gitter channel.
Contributing to CKAN
For contributing to CKAN or its documentation, see CONTRIBUTING.
If you have an idea for a new feature that you would like to discuss, open an issue in the Ideas and Roadmap repository.
If you want to talk about CKAN development say hi to the CKAN developers in the CKAN Gitter channel.
- RT @datopian : 🗓️On Monday 6/4, we'll introduce the 7t @INSPIRE_EU #Hackathon challenge we are co-mentoring 👉We'll talk, amongst others, ab… 2 months ago
- RT @BCSOSSG : At our evening of talks on Funding #OpenSource in MAy 2018, @shevski recounted the challenges and successes of funding @CKANpr … 2 months ago
- @brimwats @hannah_odaniel @omeka @ArchivesSpace @webrecorder_io @unleasharchives @accesstomemory @archivematica … http://t.co/RDhq8Y5PF9 2 months ago