Last week, I added a couple new sources that more than tripled the number of conference CFPs listed on our site. Unfortunately, I made an assumption that any publicly available API would be okay to integrate with, and one of the new sources got a little bothered about my cross-posting their listings. In order to increase transparency, I’m going to show you where I get all the data for this site, and outline my policy on sharing this data.
CFP Source Data
First of all, my immediate goal for CFP Land is to provide a free feed of all the upcoming CFPs for tech conferences that I can find.
With that in mind, I want to give credit to the sources I use to find out about CFPs:
- Confs.tech - An open source list of conferences that I and many others have contributed to.
- Calling All Papers - An open source list and API that aggregates CFPs from joind.in, papercall.io, and lanyrd (which I believe is now defunct).
- Twitter searches and retweets - People often mention @cfp_land with new conferences, but I also have a few Twitter searches set up to help me find new CFPs.
- Conference Speaker Slack channel - I am a part of a Slack channel for conference speakers where we often pass CFPs around. I add many of these to my list as well.
- User submissions - Finally, I’m getting an increasing number of submissions from subscribers. This is really helpful, and I plan on making it even easier to do in the future.
Enhancing Source Data
Getting the upcoming CFPs is the first part of the process. Next, I manually review each one, make sure it’s categorized, that the location is accurate, and I add data about whether they cover travel and hotel costs for speakers. This takes me an increasing amount of time each week, but I’m working to automate it. 🤖
I also have scripts that add logos, Twitter accounts, descriptions, and other metadata.
Acceptable Data Use
All the data I have is available to the public for any purpose (including building tools that directly compete with CFP Land!) here on the website, in this RSS feed, or through the API. Seriously, if you want to build something cool with it, go for it. I’d love to hear about it! One guy sent me a message about a CFP Land Telegram Bot that he built. 👍
I don’t currently show CFPs that have closed or CFPs that are closing in more than 3 weeks, but I am working on making them available too.
My long-term goal for this project is to make it self-sustaining.
I do occasionally find sponsors for the newsletter, and I’m exploring building a CFP submission management tool for speakers. If it makes enough to pay for my hosting and email client bills someday, that would be pretty cool. If not, I’ll probably try to do as much as can be fully automated and stop doing as much cleanup.