mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
Simplifying language
This commit is contained in:
parent
77ea8bd6c6
commit
c823392914
1 changed files with 1 additions and 1 deletions
|
@ -10,7 +10,7 @@ At any given time the Kibana team at Elastic is working on dozens of features an
|
|||
- **P5**: Highly niche or in opposition to our core goals. Should usually be closed. This doesn't mean we wouldn't take a pull for it, but if someone really wanted this they would be better off working on a plugin. The Kibana team will usually not work on P5 issues but may be willing to assist plugin developers on IRC.
|
||||
|
||||
#### How to express the importance of an issue
|
||||
Let's just get this out there: **Feel free to +1 an issue**. That said, a +1 isn't a vote. We keep up on highly commented issues, but comments are but one of many reasons we might, or might not, work on an issue. A solid write up of your use case is more likely to make your case than a comment that says *+10000*.
|
||||
Let's just get this out there: **Feel free to +1 an issue**. That said, a +1 isn't a vote. While we keep up on highly +1'd issues, a solid write up of your use case is more likely to make your case than a comment that says *+10000*.
|
||||
|
||||
#### My issue isn't getting enough attention
|
||||
First of all, sorry about that, we want you to have a great time with Kibana! You should join us on IRC ([#kibana](https://kiwiirc.com/client/irc.freenode.net/?#kibana) on freenode) and chat about it. Github is terrible for conversations. With that out of the way, there are a number of variables that go into deciding what to work on. These include priority, impact, difficulty, applicability to use cases, and last, and importantly: What we feel like working on.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue