This is in regard to the Fedora Electronics Lab Spin. It hasn't gotten any maintenance in years and currently has non-working, broken, and outdated packages included in it. I would like to volunteer myself to take over the spin as maintainer. I started the process a month ago, and two days ago heard from Chitlesh saying that he hasn't been in the Fedora Project since 2010 and is no longer interested in maintaining anything, and to take over his position. Since I heard from him, I inquired at a FPC meeting as to how I should proceed (as, in my mind it technically didn't count as "unresponsive" anymore), and was told to just file the FESCo ticket as unresponsive. So...
Here is a link to the bug: [0] Here is a link to the mail that was sent: [1]
Please let me know if I need to do anything else to get the process rolling!
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1739872
[1] https://lists.fedorahosted.org/archives/list/devel@lists.fedoraproject.org/message/LO3EWU4IGOJNBZNGPIEUH5QXML52FEFN/
+1
Metadata Update from @churchyard: - Issue tagged with: nonresponsive maintainer
@coremodule What component (package) do you need access to?
Metadata Update from @churchyard: - Issue assigned to churchyard
@chitlesh Are you still interested in maintaining the Lab and your packages?
I have mentioned this every year for the last 6 years.=20 Please opt me out from Fedora package development. I no longer have my fedora credentials=20
Chitlesh
Sent from my iPhone
On 14 Sep 2019, at 20:04, Miro Hron=C4=8Dok pagure@pagure.io wrote: =20 =20 churchyard added a new comment to an issue you are following: @chitlesh Are you still interested in maintaining the Lab and your package= s? =20 To reply, visit the link below or just reply to this email https://pagure.io/fesco/issue/2220
@chitlesh Are you still interested in maintaining the Lab and your package= s?
OK.
Metadata Update from @churchyard: - Issue tagged with: pending announcement
Giving rpms/dgc to orphan Giving rpms/dia-CMOS to orphan Giving rpms/dia-Digital to orphan Giving rpms/dia-electric2 to orphan Giving rpms/dia-electronic to orphan Giving rpms/drawtiming to orphan Giving rpms/espresso-ab to orphan Giving rpms/hct to orphan Giving rpms/kicad to orphan Giving rpms/mcu8051ide to orphan Giving rpms/qucs to orphan Giving rpms/teal to orphan
Also removed @chitlesh from co-maintainer slots.
Also note https://bugzilla.redhat.com/show_bug.cgi?id=1752228 for anyone taking things over. That requires a PR to fedora-comps repo cleaning up that group...
Metadata Update from @psabata: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Metadata Update from @churchyard: - Assignee reset
Sorry, somehow this slipped my radar. @churchyard I am looking to take over chitlesh's place and be the maintainer of the electronics-lab with access to all the packages, and specifically the comps.xml for this lab.
Metadata Update from @coremodule: - Issue status updated to: Open (was: Closed)
What does "all the packages" mean? Is that everything in the above list?
You access comps.xml via Pull Requests. I do it as well and I maintain a Lab.
Yes, everything from the above list that Chitlesh had previously been responsible for, I would like to take responsibility over.
Also, I realize that's how comps.xml works; my inclusion of it in that statement was a nonsequitur.
Giving rpms/dgc to coremodule Giving rpms/dia-CMOS to coremodule Giving rpms/dia-Digital to coremodule Giving rpms/dia-electric2 to coremodule Giving rpms/dia-electronic to coremodule Giving rpms/drawtiming to coremodule Giving rpms/espresso-ab to coremodule Giving rpms/hct to coremodule Giving rpms/kicad to coremodule Giving rpms/mcu8051ide to coremodule Giving rpms/qucs to coremodule Giving rpms/teal to coremodule
Please, don't forget to assign all the bugzillas to you:
Metadata Update from @churchyard: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Thank you @churchyard ! :)
Thank you @coremodule for taking the packages.
Login to comment on this ticket.