Sorry! I hadn't expected much non-niche interest in the campaign when I wrote the copy. Neo4django is a Django ORM replacement for the Neo4j graph database. I'm the primary dev, but since our startup supporting the project is on hold, I'm trying to find time to keep up development- this campaign will help me complete the next milestone.
He was expecting someone browsing Hacker News, familiar with the content of his software, to gain interest and donate. He was not expecting John Smith the Front End Guru to donate.
Maybe I'm a little jaded, but isn't feedback "your copy is confusing, doesn't explain the project or why I should support it" sufficiently actionable advice?
If you really care about this project, I recommend taking the initiative on everything instead of waiting for someone to give you the answers.
IANACW, but for me, something energetic and concise like "Help support bringing the world's leading graph DB to Django" helps me get my head in the game a lot faster. I'm closer to "he's making a DB interface for Django" instead of "what is neo4j".
Or even just your opener in your README "neo4django is an Object Graph Mapper that let's you use familiar Django model definitions and queries against the Neo4j graph database" is useful for identifying the players.
Considering the HN audience Django would be known but I'm not sure how many people would know about neo4j. (I hadn't heard of it)
Django has an ORM that works with Postgre, MySQL, and other relational databases. Neo4django mimics the Django ORM, but connects to a graph database- Neo4j. It's a way to use Django with Neo4j, while supporting Django nice-to-haves like the auth library and admin site, in a way that's already familiar to Django developers.
Maybe it's just inside-baseball that I don't understand, but I think you need rework your pitch page.