----- Original Message -----
> From: "Jun Aruga" <[email protected]>
> To: "Ruby SIG mailing list" <[email protected]>
> Sent: Tuesday, May 25, 2021 9:12:57 PM
> Subject: Give or orphan my rubygem-* packages
> 
> Hi Ruby-SIG,
> 
> Recently I started to work on the upstream Ruby project as a committer
> to workin on CI and non-x86 things to keep the pipelines stable. While
> it is beneficial for Fedora Ruby SIG, it gave me an opportunity to
> rethink how to use time. I need to stop something to start something.
> 
> So, while I continue to contribute to the rubygem-* dist-git
> repositories as ruby-packagers-sig role, I would like to communicate
> with you first to give you my main-admin role or to orphan by
> following the process to orphan packages.
> https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers
> 
> Here is a list of the packages I am the main admin for, and I want to
> give the main admin role or orphan. If you are interested in being the
> main admin, please let me know as a reply to this email thread.
> Considering the importance of the packages, maybe the plan would be
> like this. I will communicate with the co-maintainer later if it is
> needed.
> 
> 1. Dependencies of RSpec => Need to maintain.
> 2. Dependencies of Rails
> 2-1. Required on rawhide rubygem-rails => Need to maintain.
> 2-2. Was required by the old Rails 5.2.0 (as far as I know), now not
> required by the rawhide Rails 6.1.3.2. => ?
> 3. Dependencies of Sinatra => Need to maintain. Maybe.
> 4. Dependencies of Resque => Orphan
> 5. Others => Orphan

Feel free to move 'main admin' acls for all rubygem-* packages to me, in case 
noneone wants them (I'll need them for Ruby on Rails anyway).

That is, if you don't want to orphan them instead (e.g. in case nothing depends 
on the gem).

> 
> ## 1. Dependencies of RSpec
> 
> * rubygem-coderay
>   * a dependency of RSpec (rubygem-rspec-core) and rubygem-asciidoctor.
> 
> ## 2. Dependencies of Rails
> 
> ### 2-1. Required on rawhide rubygem-rails.
> 
> * rubygem-marcel
> * rubygem-nio4r
> * rubygem-puma
> * rubygem-rack
> * rubygem-websocket-extensions
> 
> ### 2-2. Was required by the old Rails 5.2.0 (as far as I know), now
> not required by the rawhide Rails 6.1.3.2.
> 
> * rubygem-mimemagic
>   This gem was migrated into rubygem-marcel.
> * rubygem-spring-watcher-listen
> 
> ## 3. Dependencies of Sinatra
> 
> * rubygem-mustermann
>   * a dependency of rubygem-sinatra.
> 
> ## 4. Dependencies of Resque
> 
> * rubygem-resque
>   * There is no package depending on this package.
>   * I started to manage this package in the past, because I saw that
> the 3scale team used the own forked version.
>     I thought it might be good to maintain it as RPM.
>     But actually no reason to continue to maintain this package.
> * rubygem-mono_logger
>   * a dependency of rubygem-resque.
> * rubygem-vegas
>   * A dependency of rubygem-resque.
> 
> ## 5. Others
> 
> * rubygem-thin
>   * A dependency of rubygem-vegas.
> * rubygem-redis-namespace
>   * There is no package depending on this package.
> * rubygem-ditz
>   * There is no package depending on this package.
> * rubygem-trollop
>   * A dependency of rubygem-ditz and rubygem-rbvmomi.
>   * I can not remember why I am the main admin of this package.
> * rubygem-term-ansicolor
>   * A dependency of rubygem-coveralls, rubygem-terminal-table.
>   * I can not remember why I am the main admin of this package.
> 
> Regards,
> Jun
> 
> --
> Jun | He - His - Him

Feel free to ping me on case-by-case basis, if you have any questions.

Regards,

-- 
Pavel Valena
Software Engineer, Red Hat
Brno, Czech Republic
_______________________________________________
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

Reply via email to