Here’s the third draft. The last point is also aimed at existing users.
FAQ: How to create a successful proposal?
- Python has a very strict Backwards Compatibility Policy, and it can be the sole reason to reject your idea
- Python is a volunteer project, if you make a proposal, you are volunteering to make it happen. At a bare minimum we assume you will do research, manage the discussion, respond to and address comments & criticism. Don’t expect others to do tasks you aren’t willing to do. Read more in the Code of Conduct & Setting expectations for open source participation
- Read & summarize previous discussion, including of similar proposals. Don’t create a thread if you have nothing to add or to address the reasons they were rejected
- Especially the PEP Index
- The Ideas & Python Help categories on this forum
- The old python-ideas mailing list
- The issue tracker
- Explain why the other ways of achieving the same goals as your idea, i.e its potential alternatives or workarounds, are insufficient
- For instance, before asking for something to be included in the standard library, ask yourself why it can’t be shared differently, as a snippet or as a PyPI package
- Give clear examples describing how your idea would work
Post followups instead of editing previous posts. Mailing list users only see edits within 10 minutes after posting- There should be no discussion about the contents of your idea before these points have been addressed
Should we add a list of frequently posted suggestions?