Good for you and good luck. Here's my thinking on an approach: What can happen? a) No one responds b) you get harshed on c) people communicate interest. You ca

Good for you and good luck. Here's my thinking on an approach: What can happen? a) No one responds b) you get harshed on c) people communicate interest. You can't control b) so ignoreit, a) is the same result as not publishing anything but at least now you have a story. Put the effort into to making it easy for c). In terms of interest, what specifically are you looking for in response to putting the project forward? A response to the idea, or a response to the effort? In terms of the idea, tell your audience: - Who is "it" for, what's it for? If it's for you, generalize to people like you, eg "developers who are trying to keep track of their ideas" - What's the bet you are making? eg "it uses clustering to group ideas that you can then label as themes" - What would you like to know? eg "would this help you?, or how do you organize your notes and ideas now?" In terms of the storytelling, lead with a demo or example that shows it doing something. If the code's not all there yet, mock that up. Above all, show what it does. In terms of the effort, it's telling us the idea plus: - How does it work? eg "I used X Y and Z. It does A B and C". - How I solved it: eg" The hard part was designing A, where I first tried this, and then that, and what worked was this other thing". - What I don't know how to solve yet. This last thing the may be what gets you the most feedback, so don't bury that.