Regarding maintaining Ruby packages, I notice that some of the
packages I maintain have the group @ruby-packagers-sig as
co-maintainers, but not all. What is the set of packages this group
wants to have access to? I could all them to all my packages, if the
answer is "all Ruby packages".
I don't think there are any strict rules about the @ruby-packagers-sig,
but the main idea of the group is to share the packaging maintenance
workload between Ruby experienced packagers who will do the right thing
when necessary. The focus of the group are mainly Ruby on Rails related
packages, because asking permissions to each related packages does not
scale. The permissions of other ruby packages are provided based on
maintainer discretion. In Jekyll case, some of the current members
probably asked for the permissions. However, I don't like to see
@rubygem-packagers-sig to become dumping ground for packages nobody
longer cares about.
I see that Jun gave a bit different answer in his reply. In any case, my
packages form a leaf in the dependency tree. I only have Jekyll, Jekyll
plugins and dependencies that do not have any other users in Fedora at
the moment. The Rails stack or anything else will not require fixes
there for any reason. So I take that there is no particular need to add
the Rubygem packagers SIG there just because. Naturally, if access is
needed (or somebody just wants to be involved with Jekyll packaging),
access will be granted.
_______________________________________________
ruby-sig 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]
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
