Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 599818 - Maintainership request: x11-wm/fvwm
Summary: Maintainership request: x11-wm/fvwm
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Proxy Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-15 15:19 UTC by Gábor VIDA
Modified: 2017-08-05 16:03 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gábor VIDA 2016-11-15 15:19:22 UTC
Hi!

I'd like to be a proxy maintainer of FVWM to fix the bug I found and also to support the new FVWM came out in March 2016.
Comment 1 Coacher 2016-11-16 02:08:43 UTC
(In reply to Gábor VIDA from comment #0)
> Hi!
> 
> I'd like to be a proxy maintainer of FVWM to fix the bug I found and also to
> support the new FVWM came out in March 2016.
Then you should contact the current maintainer first: i92guboj@gentoo.org
Comment 2 Jesús Guerrero Botella (RETIRED) gentoo-dev 2016-11-22 15:24:42 UTC
Please, forgive me for taking so long to respond. I can barely keep an eye on Gentoo related stuff these days due to life issues.

And please, feel free to hand or take the fvwm ebuild maintainership as needed.

To tell the truth, I never had (or at least, never used) commit permissions against the Gentoo (CVS by that time) tree. I remember working as a proxy maintainer for this single ebuild only (I think the real commits were made by Jeremy Olexa, but can't remember for sure right now, it's been years, like 7 or 8 or so...).

Don't hold back anything on my behalf. The only reason I took the dev course is because it was needed to become a forum moderator, which by the way is a title I nowadays rarely use, because my lack of time to devote to that, as well.

If you, Gábor, or anyone else, wants to step and volunteer, s/he es more than welcome, since I can't really keep an eye on this anymore.

Cheers, nice to meet you, and a lot of luck in your task as a proxy or non-proxy maintainer!
Comment 3 Jesús Guerrero Botella (RETIRED) gentoo-dev 2016-11-22 15:28:29 UTC
And please, don't try to contact me at i92guboj@gentoo.org, I am not even sure I have access to that anymore. And I, certainly, haven't used the mailbox in a while.
Comment 4 Gábor VIDA 2016-11-29 16:21:04 UTC
Thank you Jesús! Then I think we can proceed, and once I become a proxy maintainer, I can start working on x11-wm/fvwm bugs. I'm not sure how to continue. Should I do anything else?
Comment 5 Jonas Stein gentoo-dev 2016-11-29 17:26:17 UTC
Gábor, we can not explain things in bug tickets well. Please join #gentoo  #gentoo-dev-help on IRC. These channels are well suited to discuss and explain things. Feel free to ping me, when you are there.

Next step in this ticket: Attach or link your improved and well tested ebuilds.

You can create your own repository for tests and development. Mine is here for example: https://github.com/jonasstein/jstein-overlay

Good links are here: 
https://www.gentoo.org/get-involved/contribute/   Maintain Packages
Comment 6 Martin Väth 2017-04-09 06:02:25 UTC
In mv overlay, I currently maintain a current (bumped) version and also added fixes for several gentoo bugs reported concerning fvwm. So maybe you want to start off with this ebuild. See e.g.
https://github.com/vaeth/mv-overlay/tree/master/x11-wm/fvwm
Comment 7 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-05 16:03:57 UTC
We no longer use these bugs. See:

https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide#Taking_over_an_existing_package

Long story short:

1. If your request has been fulfilled already and you're the maintainer, ignore this.

2. If you have submitted the ebuilds separately, we'll handle it there. If that's via a bug, please make sure that proxy-maint@ is in CC. Feel free to ping us if things aren't moving forward for a long time.

3. If you haven't submitted anything yet, please submit a meaningful change to the package (bugfix, version bump, ebuild update...) along with the maintainer update and you'll become the maintainer when we merge it.

Sorry for the trouble.