# Promoting your track at Community Over Code See also: [Promoting your talk at Community Over Code](https://hackmd.io/ryeZIX6CRKG3NLhiLwC4Dg?view) Each track at Community Over Code appeals to a specific audience. As the track lead, you have more insight into who that is than the main event leads do, and we rely on you to help us reach that audience. ## Project websites Most Community Over Code tracks appeal to a certain set of Apache projects. Please ensure that each of these projects is promoting the event using the [official event promotion tool](https://www.apachecon.com/event-images/). Consider working with each project to also do a more in-depth promotion of the event on their project site front page, complete with speaker photos and a listing of a few of the more interesting (in your opinion) sessions that you'll be running. ## Project social media channels If the projects that you are working with have their own social media channels, promote the event there. Example messages might include: *Join us October 7-10 for the Search track at Community Over Code North America 2024. Register today at https://communityovercode.org/registration/* *Come see Sharan Foga talk about effective ways to attract new developers to your project, at Community Over Code 2024 in Denver, October 7-10. https://communityovercode.org/* *Come for the content, stay for our code sprint, at Community Over Code North America 2024 in Denver, October 7-10. https://communityovercode.org/* Also, watch the official event social media presences, and amplify what's posted there. ## Encourage speakers to promote their talks Contact each of your track's speakers, individually, and encourage them to promote their talk. There's more advice about this [here](https://hackmd.io/ryeZIX6CRKG3NLhiLwC4Dg?view), but you can augment that by suggesting specific text that each of them can post to their various available channels, and this will greatly increase the chance that they actually follow through with it. ## Encourage on-site partipation People get the most excited about an event when they start to understand what they can get out of it. Encourage the projects you're working with to think about doing some collaborative work at the event, such as a code sprint, a bug bash, a doc sprint, or brainstorming about the roadmap. This can usually be done during the day, in the common area at the event, or you can use your BoF (Birds of a Feather) time at the end of each day for these activities. Discussing specific goals, on the project dev@ mailing list, is a great way to engage all members of the community, and give them a concrete reason to show up for the event. The ealier you get this conversation started, the greater chance that it will actually materialize the day of the event. Planning something like this takes longer than you might thing, so don't put it off! ## Other promotional opportunities The [Voice Of Apache](https://feathercast.apache.org) will be doing promotional videos in the months leading up to the event. If you want to promote your track, contact feathercast@apache.org to figure out who you'll have on your track promotional video, and what message you want to promte.