Dear all, Following a previous thread debate about Unknown Horizons: 1) I'm available to maintain unknown-horizons (UH) in Fedora and EPEL (RHEL6); 2) For 1) to happen I would like to maintain also FIFE, which doesn't seem to see much love for quite some time; I ask this because FIFE flagship product is UH itself and the development of both is very close... A FIFE release always preceeds a UH release; 3) If 1) and 2) happen, then I need to maintain also python-enet, which provides the python bindings for ENet. In case ENet needs some love, then I don't mind taking it also. For this to happen, I could use information on the following: 1) How to check who currently maintains those packages; 2) The correct 'modus operandi' to take ownership of those packages; Consider that: 1) I already provide packages for Fedora and RHEL for at least 1 year through OBS. This packages are the ones supported by upstream; Providing them on Fedora means I would remove them from OBS and replace the current information for Fedora users on UH main website; 2) I have been sharing jokes and enjoying UH experience with upstream, so any issues found can properly be addressed to upstream and a rapid response is expected; 3) In extreme situations I can take ownership of all dependencies required (ex: guichan, scons, etc); 4) I don't know the Fedora way, so I would rather stick with FIFE and UH at the start and when I'm more confortable I can take ownership of the rest of the dependencies; Is this OK? Should I re-open BZ718430? [1] - https://bugzilla.redhat.com/show_bug.cgi?id=718430 NM -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
