For Maintainers: Triaging Issues

Tagging

When new issues are submitted, non-admins cannot tag them, so part of triage is to tag issues. This enables filtering them by type.

If it's a bug;
- Can you reproduce it?
- If 'no' then leave a comment or close the issue.
- If 'yes' then comment verifying that you reproduced the bug, with your browser and OS.
  - Add the relevant tags:
    - ios, android, desktop-web, chrome, ie, linux, etc.
    - Also add the bug tag
Tag with difficulty if it is potentially easy
- good-first-bug (easy)
- Everything else is considered difficult
If it's not a bug, tag with the category:
- support for questions about how to use Draft.js
- question for questions about Draft.js itself, or any question that is not support.
- enhancement for requests for new features
- documentation for requests to change or improve docs
- discussion for open ended questions
- big picture for long term discussion items and roadmap or announcement issues
If more info is needed, leave a comment asking for that info and tag as needs-more-info
Bonus: Since we are in the midst of migrating users from 0.9.1 to 0.10 and 0.11, please tag any questions or issues related to the API changes with the tag v0-10-api-migration

Some guidelines about when we can close an issue:

If there is a PR which fixes the issue and was merged - they may have commented on the issue but never closed it.
If the issue is old and the bug no longer can be reproduced in recent versions of Draft.js.
If there is a needs-more-info tag and nobody has responded for more than a week.
If it is a feature request which we don't plan to add in the near future.