Not especially, you mean like for a blog entry?

Its important that only the team members listed do the work, but there's nothing that says you cannot work in public if you wanted to

thats what i meant - and a github repo

can you pin to here a url to the contest rules and such?

set the channel topic: https://adobe-cold-fusion-hackathon.meetus.adobeevents.com/registration/form

Set URL for hackathon main page as topic

Can one person have multiple entries? Perhaps one entry as a part of a team and one entry as an individual?

During the ACF 2025 beta stage, Adobe did some demos on different topics regarding the new features/enhancements of ACF 2025. May I ask if those links are still available please?

Monte, they are all posted to the youtube site. https://www.youtube.com/adobecoldfusion/videos

When submitting a project for the hackathon, I assume there should be a general write up of what the process accomplishes?

Alrighty, we're off to the races as of this morning! Hopefully folks are having fun building ALL THE THINGS!

I can't wait to see all the awesome projects you build 🙂

I had asked this previously, but to confirm - we're ok to talk publicly about our submission? I mean technically someone could 'steal' from you if you do, but I also figure in this community that would be pretty evident 😉

Sure thing! Heck, if someone wanted to "steal" and improve, the end point of that is something even better for the community at the end of the day (though you may miss out on a prize haha). All good buddy 🙂

i need to write a Friday blog post no one will read 😉

Hey all, remember that you have all weekend to work on this! Ending time is 11:59PM CST on June 16th. I'm already getting submissions from folks, which is FINE, but I want everyone to know and understand you DO have more time. Being "first in queue" does not confer an advantage lol. 🙂

I want to thank all of the wonderful folks who registered and competed in our hackathon this year. It is my honor and a great pleasure to announce the winners of this year's contest. 3rd Place Team Name: “BCWHS” | Team Members: Wade Bachelder | Project: CISA CVE Vulnerability A “One Man Show” entry from Wade, this project showcased an important functionality (security) while leveraging a wide array of both CF2025 and older CF features in a cohesive whole. Some quotes from the judges: “_Solves a real-world problem by pulling data from the CISA vulnerabilities feed._” “_This project presents a useful tool for scanning CISA alerts specific to Adobe ColdFusion, offering a valuable utility to developers and administrators concerned with security_.” “_Interesting and creative use of CF2025 features._” 2nd Place Team Name: “That’s Kablamo” | Team Members: Ben Nadel | Project: Sitter Snacks Ben’s entry was a fun, useful and impressive showing of what you can really pull off with a ColdFusion application. Some quotes from various judges: “_The integration of features is seamless and highly effective… showing thoughtful design and cohesive implementation._” “_This app is really well put together and surprisingly easy to follow. The code is pretty impressive and it pulls a good number of features._” 1st Place Team Name: “Syreta” | Team Members: Christian Immitzer, Roman Schick, Michael Wiesmeyr | Project: LogScope Team Syreta really showed us what an amazing project looks like. Some quotes from various judges: “_Impressive and looks really cool... Code is modern and well architected with proper separation of concerns._” “_With further technical refinement and more modern code organization, it could set a new standard for CF2025-based tools._” “_Overall, it’s a smooth, well-thought-out tool that just works._” All other participants have won a free basic+ pass for each team member to Adobe ColdFusion Summit 2025! Participants, stay tuned for an email detailing how you'll be receiving your prizes. <!here>

if we are speaking at Summit, could we give away our ticket?

I believe you will be given a code to use, so you could ask Kishore if that's an option.

cool - dont want it to go to waste 🙂

By the way, we'll be sharing the code for all the participants out in the official GitHub later next month so folks will be able to check them out (we want to convert some of the pdf/word docs to markdown and maybe fix a couple issues to make the code on some projects easier to use).

I just want to say, judging this was HARD. All the projects had amazing aspects to them. Creativity, technical excellence, fantastic integration, execution at a high level. All 5 judges had their work cut out for them 🙂

hmmm - for those who submitted and shared GitHub repos, wouldn't it be best to link back to them? And if corrections are being made (which is great!), why not do so as PRs?

A few reasons: 1. All code in one spot 2. We control the updates/changes. If the current repos were deleted by the authors the code would be lost

if a team wants to continue working on their project, are you suggesting they literally give up their own repo? will adobe add us as contributors to the new repo? i can see the reason for 1, definitely, but 2 feels like a bad idea for projects that are ongoing. is there really no reason to not contribute fixes back to the authors?

I will chat with the team, but I will say that when folks signed up, they gave us rights to use the code however we wanted (including incorporating it into CF). We're not sure if we'll do exactly that, but having the code in the Adobe/ColdFusion repo makes more sense than having all of the projects spread out across the Github universe. I'll see about adding the original authors as contributors, but that might be problematic since this is the official Adobe Github and there may be issues about adding collaborators who are not employees. I need to double check that.

i guess if its one repo and all the projects under it, there's no 'duplicate project' per se, id just really ask yall to consider: a) in the readme for each submission, in the first paragraph, link to the 'real' repo b) please please please consider not just doing fixes in your copy, but submitting fixes as a PR to the original author as well. otherwise, we need to clone the repo and do a file by file comparison (ok, in my case its one file, so not a big deal, but still)

I will definitely pass those suggestions on, they're good ones.

thanks for hearing me out 😆

Always sir ❤️