id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc 1933,Automate Tagregator settings,hlashbrooke,,"The Tagregator settings (API keys) for each WordCamp site always need to be filled in by the organisers each year. My assumption is that there is no need to generate new keys every year and, in many cases, I'm sure this is something that organisers forget to do as there are so many more pressing things to take care of when organising a WordCamp. While Tagregator is perhaps a more minor feature, we could do a lot to improve the flow of it. There are two options here I think: 1. Organisers generate and add their API keys for the first camp in their city and then subsequent years automatically copy the previous year's keys as the site is created. 2. We generate API keys for each service that are linked to the WordCamp Central and auto-populate all future WordCamp sites with them. Option 1 would be a quick win (I think), but option 2 would be even better if we could do it. The main issue that would probably come up are the usage limits for each API key, so we would need to research those for each service before we could go with option 2. If we don't do any of this, then we could at least try to improve the oAuth flow for organisers to make this whole thing a lot simpler.",enhancement,closed,normal,,WordCamp Site & Plugins,reported-upstream,needs-patch good-first-bug,