Hello everyone,

I am stepping down as project owner of Mock project, and I want to introduce 
Pavel Raiskup, who takes over the
maintenance of Mock.

I was nearly 5 years ago when Clark Williams gave the maintenance of Mock to 
me. Since then, Mock went through two major
versions. I focused on simplifying release engineering part of Mock, split the 
configs from the code, and we have two
relatively independent packages: mock and mock-core-configs. I spent much time 
documenting things. We have a nice wiki
page (https://github.com/rpm-software-management/mock/wiki), which documents 
plugins, features, configs etc. We had nice
release-notes for every release. I tried to be a good maintainer and review all 
community contributions. And we have
many of them: migration to DNF, bootstrap chroot, isolation using 
systemd-nspawn, container images.

I spent a lot of time on Mock, but I am slowing down. I feel that somebody else 
can give the project more.

Pavel Raiskup (praiskup on IRC) agreed to take over the maintenance. He is one 
of the Copr developers; he was/is a
maintainer of PostgreSQL, tar, autotools, and some other rpm packages. For this 
reason, he has reasonably good knowledge
of what maintainers needs and wants. Pavel already contributed to Mock, e.g., 
subscription-manager support.

Pavel has some ideas for improvements. E.g., more tests to reveal regressions 
in Mock.

I am not going away completely from this project. I will be hanging around. You 
may see my PR or my comments in PR of
others. But the main decisions and releases will be done by Pavel.

The upcoming 1.5.1 release - you may expect it soon - will be mixed. Most of 
the changes there are my decisions, but
Pavel will be doing the release.

Last but not least - I want to thank all contributors who make the Mock live 
and vibrant project. Thank you.

-- 
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
_______________________________________________
buildsys mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to