Maintainer-ship is typically granted to contributors with a long-term history of contributions to a certain package/project.

In any case, you don't need owner perms to branch and submit updates/patches to the packag, only if you want to directly commit changes to science/vtk-m. The latter route is frowned upon anyway, as it prevents a 2nd set of eyes to review the changes. Is there any specific reason you think that requires you be made a maintainer?

I understand that this permission is not granted lightly.

Maintainer-ship is typically granted to contributors with a long-term history of contributions to a certain package/project.

I assume that authoring the package and being the release manager for this specific project would qualify, also still learning, I have been contributing to the OBS here and there for a couple of years already. Note that I am requesting maintainer perms for this package solely, not the science project.

Part of my job is to manage the packages in different platforms. I figured that the science project (and OpenSUSE) might benefit for having me listed as one more maintainer for this package so that I can directly be reached when errors, questions, request arises. This will ease me keeping this package timely updated/patched (not intending to bypass the request review process). On another topic I intent to further help with other Kitware projects that I am involved so this can be a good training ground :)

All righty then, please make an addrole request for maintainer and I will accept it