New label for "members only" issues

[rndquu]

Sometimes there are issues that should be handled only by a project's core team because:

1. Core team members deliver quality code
2. Core team must be sure that a feature is implemented in the best way possible

Examples of such critical issues:

• check that diamond storage is untouched after each pr ubiquity-dollar#636
• Unit Testing #176

So we could add a new tag, like Core or Members only which would make sure that an issue could be assigned only to an organisation member.

[0x4007]

I dislike clouding label space because other projects likely have their own label systems that we need to compete with for visual/UI real estate. The more labels we have as dependencies, the less attractive it could be to use our system for this reason.

This can be solved by explicitly delegating tasks to the core team, either via direct communication (e.g. phone call or private message) or assigning on GitHub, but most likely both.

The simple workaround could be that we don't consider those as bounties until AFTER a core team member picks it up. So we remove the Time or Priority label, making it impossible for a bounty hunter to pick up. Once a core team member is assigned (or assigns themselves using the GitHub UI) then we can add the missing label to make it eligible for the bounty.

[rndquu]

The simple workaround could be that we don't consider those as bounties until AFTER a core team member picks it up. So we remove the Time or Priority label, making it impossible for a bounty hunter to pick up

ok

[0x4007]

If you think all the points are addressed in your original discussion topic, consider closing it as completed.