Add new maintainer(s) to help chew through the issue and pull request backlog

[catskul]

I imagine adding new maintainers can be a bit stressful since it's a potential security concern, but seems like there's a need here considering how widely used this is and how far behind the project is on pull requests and issues.

I nominate @georgettica. Who his already a code owner:

https://github.com/go-jira/jira/pull/426 https://github.com/go-jira/jira/pull/395#issuecomment-980819086

[georgettica]

I can wholeheartedly say I'll do my best to debug and not abuse the power I am given if I am uncertain

[catskul]

@coryb I think you might need to be the one to make the call on this. I think @mikepea said he didn't feel comfortable making that decision.

[coryb]

I have added @georgettica to the maintainers list, thanks in advance for the help! fyi @ldelossa

[miguelbernadi]

Shouldn't this issue be closed now?

[georgettica]

It can, but as of now we didn't chew really on that list

[nyarly]

Are new maintainers needed? I can pitch in a little bit; I use go-jira constantly.

[georgettica]

@nyarly any help would be helpful.

currently the maintainers list is not super active but we wake up every once in a while.

I was planning to help and pitch in but am not using a JIRA project day-to-day anymore :( I guess chewing some of the recent ones might help keep the activity high

[nyarly]

Right now it looks like there's a big backlog of PRs. I don't have permissions to merge/close those.

[catskul]

@mikepea @coryb @kalbasit any input here?

[coryb]

The more the merrier! I have invited @nyarly to the maintainer's list, thanks in advance for any help you can provide! 🎉