Scikit-optimize: New maintainers

[betatim]

Hello all,

scikit-optimize has seen a lot of new contributions recently from @holgern. He contacted the current maintainers (@glouppe, @iaroslav-ai and @MechCoder) asking if he could help out with maintenance.

Welcome Holger!

The guidelines for interacting and contributing remain the same.

A main task for maintaining this project is around growing the number of people who actively contribute to the maintenance of the project in order to keep the level of quality high. This is a hard task! Depending on what part of the history of the project you look at the past maintainers did a good or a bad job at this. I look forward to seeing how new maintainers tackle this challenge and keep growing the community.

As part of this I would be happy to see more people creating PRs and increasing their involvement so that new people can join Holger in maintaining this project.

[kernc]

I would like to nominate myself as a new maintainer. :raised_hand_with_fingers_splayed:

It's a real shame if not wholly unacceptable to see a such a well-rounded drop-in library stall unmaintained, accumulating untriaged issues even to the point of incompatibilities with its dependencies and downgrades as the recommended course of action!

Having just recently evaluated several options in the Python hyperparameter optimization space, I found scikit-optimize the one to go with for one of my projects, so I have some direct interest in it remaining maintained and useful.

If you'll consider my application, please see examples of my reasoning, work, and interaction already in the issue tracker, with more available obviously in other projects I work on.

As a new maintainer, I'd like to:

• [ ] port CI to GitHub Actions (can't have CI broken or taking hours to complete),
• [ ] revise docs for less noise on the issue tracker,
• [ ] consolidate issue tracker labels (New Feature → Enhancement, Easy → "good first issue"),
• [ ] triage existing issues and PRs (assigning labels like you guys have till late 2017), _tidying up_ and hopefully making everyone again somewhat more interested in contributing,
• [ ] recruit new contributors by inviting bug reporters to investigate/patch/fix their own bugs, _responding in a timely manner_.

Thanks for your consideration.

cc: @scikit-optimize, @betatim, @glouppe, @iaroslav-ai, @MechCoder, @holgern

[betatim]

Hi @kernc 👋

thanks for taking the time to find, evaluate and then start helping out here!

It would be great to meet you to chat a bit. For me a large part of maintaining a project is about the social side of things. Not just technical skills. How could we make this happen given everyone has a busy life, timezones, etc?

[kernc]

I got an interview! :raised_hands: Sure thing. It shouldn't be too hard to sync — we're all keeping busy, but at least we're mostly locked in. :laughing: Let me send you an email.