—————————————
(1) Top-Level-Comment-Format:
- IDEA: (One sentence)
- VALUE: (who needs what and why)
- ESTIMATES: Time & Resources
- VALIDATION: How will you know success happened? How would you compare it’s success with prior efforts? How would you know to when to failure happens or related efforts should end? (EDIT: Clarification of meaning “validation” — that being the topic of validation is limited to validation of the “value” not validation of anything else, including but not limited to validation of a given implementation technically, roadmap, etc.)
One idea per top-level comment to enable clear understanding of votes.
—————————————
(2) Top-Level-Comment-Response-Suggestions:
- FEEDBACK: on idea
- VARIATIONS: of idea
- VOLUNTEER: Planning, Beta, Coding, supporting, financial, maintenance
Suggest limiting each top-level comment to a single topic to enable clear views of voting.
—————————————
(3) META-COMMENTS:
Lastly, I will create a top-level comment for meta-comments on the idea of “Ask HN: Ideas to Improve HN“ — which is where all comments about this post should go; all other top-level comments should be “Ideas to Improve HN”.
—————————————
DISCLAIMER: Other than having a meaningful understanding of HN/YC, I have no relationship with either. That said, if this makes the home page, I’ll ping the HN mods to insure they’re aware of it.
>> “I will create a top-level comment for meta-comments on the idea of “Ask HN: Ideas to Improve HN“ — which is where all comments about this post should go; all other top-level comments should be “Ideas to Improve HN”.”
- VALUE: It would be cool if HN used native JavaScript features
- ESTIMATES: Week, people rewrite HN all the time shouldn't be that hard.
- VALIDATION: Should be able to tell from viewing in devtools.