# Contributing - what issues are best?
**URL:** https://discuss.elastic.co/t/contributing-what-issues-are-best/29965
**Category:** Kibana
**Created:** [September 25, 2015, 6:52am UTC](https://discuss.elastic.co/t/contributing-what-issues-are-best/29965 "2015-09-25T06:52:40Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@dotfold](https://discuss.elastic.co/u/dotfold)
#### Post date: [September 25, 2015, 6:52am UTC](https://discuss.elastic.co/t/contributing-what-issues-are-best/29965/1 "2015-09-25T06:52:40Z")
Hey Kibana team.
I'm very interested in getting involved and taking on some issues to feed back into Kibana core. Aside from the contributing guidelines which is super detailed and informative - do you have a policy on what is best for the community to take on? For example, I see the label `adoptme` - is this the best place to start? Do you prefer contributions to be developed against `master` ?
One that I have particular interest in is [https://github.com/elastic/kibana/issues/4565](https://github.com/elastic/kibana/issues/4565) - since plugin development is a no-go for now - can I develop this as a core plugin?
Any guidance is much appreciated. Cheers!
---
### Author:  [@tbragin](https://discuss.elastic.co/u/tbragin)
#### Post date: [September 26, 2015, 5:17am UTC](https://discuss.elastic.co/t/contributing-what-issues-are-best/29965/2 "2015-09-26T05:17:18Z")
> [@dotfold](#):
>
> I'm very interested in getting involved and taking on some issues to feed back into Kibana core. Aside from the contributing guidelines which is super detailed and informative - do you have a policy on what is best for the community to take on? For example, I see the label adoptme - is this the best place to start?
The best place to start as a new Kibana contributor is actually the "low fruit" tag. These tend to be very simple enhancements. The "adoptme" tag indicates issues that we'd like to see in the product but don't have the bandwidth to work on, and they usually tend to be more involved.
> [@dotfold](#):
>
> Do you prefer contributions to be developed against master ?
You should fork Kibana to your own Github account, develop in your own branch, tracking against master, and then submit a pull request.
> [@dotfold](#):
>
> One that I have particular interest in is [Traffic light style visualisation · Issue #4565 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/4565) - since plugin development is a no-go for now - can I develop this as a core plugin?
Until plugins are officially endorsed, that seems like a good call.
---
### Author:  [@dotfold](https://discuss.elastic.co/u/dotfold)
#### Post date: [September 28, 2015, 12:15am UTC](https://discuss.elastic.co/t/contributing-what-issues-are-best/29965/3 "2015-09-28T00:15:38Z")
Thanks Tanya, that helps a lot!
Maybe my first contribution can be summarizing this in the CONTRIBUTING.md for future people 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:12pm UTC](https://discuss.elastic.co/t/contributing-what-issues-are-best/29965/4 "2017-07-06T14:12:18Z")