Re: Unresponsive maintainer : kanarip
Hi, I juste open a FESCO request for kanarip : https://fedorahosted.org/fesco/ticket/1387 He owns several perl and ruby package, including puppet !!! https://admin.fedoraproject.org/pkgdb/packager/kanarip/ I'm not a ruby user/dev so I won't be volunteer to take them Marianne Le 09/01/2015 15:14, Ralf Corsepius a écrit : On 01/09/2015 02:59 PM, Sérgio Basto wrote: On Sex, 2015-01-09 at 06:45 +0100, Johannes Lips wrote: Sorry to say, but this is like the hundredth time this topic came up. https://lists.fedoraproject.org/pipermail/devel/2014-July/200860.html https://lists.fedoraproject.org/pipermail/devel/2014-July/201125.html I Google it, kanarip is Jeroen van Meeuwen so you may try vanmeeuwen at kolabsys.com and kanarip at fedoraproject.org Like others already mentioned, he almost never replies. I regret, but I feel, it's time to pull the plug and to tighten up Fedora's AWOL-policy. BTW: There are other former (and current!) major Fedora contributors, to whom analogous considerations apply. Ralf -- Marianne (Jehane) Lombard Geekfeminist and sysadmin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On Fri, 09 Jan 2015 09:40:17 +0200, Yanko Kaneti wrote: Policy does require you to contact the maintainer http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL It is quite inappropriate to not have the courtesy to contact the fedora maintainer first. I have't seen that policy, but now that I've read it it seem misguided. My thinking is: - If the Fedora maintainer cared and there was no technical reason the branches would already be there. Cared? This is the fundamental problem. Care about what? About making available a package _also_ for EPEL? Or about maintaining it properly and as appropriate for the long life-cycle of the mother product RHEL? EPEL should not be treated as just another dist target to build for. Don't take it lightly. Don't dump builds into EPEL without considering what may become necessary for future bug-fixes, security-fixes or even back-ports when the build requirements of an upgrade are not met by RHEL. It is perfectly fine, if someone with special interest in EPEL volunteers as the EPEL package maintainer when the Fedora package maintainer has not created the branches for EPEL before. Be aware of the consequences of offering something for EPEL. It is not easy to make RHEL/EPEL users happy. Those, who are not affected by bugs, don't want version upgrades which may cause regression and new issues. Those, who are affected by bugs, want bug-fixes (which may make version upgrades necessary!). And there are also those, who want always new versions as if it's a drug. Finding existing packages saves them some work, but they don't care much, because they build things themselves once the existing packages are out-of-date, and they don't care either whether that may break the dist. - Most Fedora maintainers know well enough if there is or isn't any technical reason. Not sure about that. The type of maintenance which is appropriate for EPEL is underestimated. When you offer something for EPEL, you somehow need to predict whether you will be able to handle security fixes, backports and/or upgrades in the future for a long time. - I am too busy and I'll get to it later - is no good excuse for blocking people willing to do the work. True. Not responding in bugzilla in time is no good excuse either. - I beleive this package is not suitable for an LTS release, so I'll block it - is just hubris. True, too. Is there an EPEL project leadership which could review such decisions? The opposite, offering something for EPEL only to orphan it some time later, can be considered damaging, too. - Lets not put red tape for more people to do the work in a place where good sense should be more than enough to prevent conflict. Still it's too easy to release packages in the Fedora and EPEL dists and then abandon them without any notification. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On Fri, 2015-01-09 at 11:22 +0100, Michael Schwendt wrote: On Fri, 09 Jan 2015 09:40:17 +0200, Yanko Kaneti wrote: Policy does require you to contact the maintainer http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL It is quite inappropriate to not have the courtesy to contact the fedora maintainer first. I have't seen that policy, but now that I've read it it seem misguided. My thinking is: - If the Fedora maintainer cared and there was no technical reason the branches would already be there. Cared? This is the fundamental problem. Care about what? About making available a package _also_ for EPEL? Or about maintaining it properly and as appropriate for the long life-cycle of the mother product RHEL? EPEL should not be treated as just another dist target to build for. Don't take it lightly. Don't dump builds into EPEL without considering what may become necessary for future bug-fixes, security- fixes or even back-ports when the build requirements of an upgrade are not met by RHEL. It is perfectly fine, if someone with special interest in EPEL volunteers as the EPEL package maintainer when the Fedora package maintainer has not created the branches for EPEL before. Be aware of the consequences of offering something for EPEL. It is not easy to make RHEL/EPEL users happy. Those, who are not affected by bugs, don't want version upgrades which may cause regression and new issues. Those, who are affected by bugs, want bug-fixes (which may make version upgrades necessary!). And there are also those, who want always new versions as if it's a drug. Finding existing packages saves them some work, but they don't care much, because they build things themselves once the existing packages are out-of-date, and they don't care either whether that may break the dist. Look, I wholeheartedly agree with all of this. This is why I only take care of just 5 epel branches in the 35 packages that I have some say. - Most Fedora maintainers know well enough if there is or isn't any technical reason. Not sure about that. The type of maintenance which is appropriate for EPEL is underestimated. When you offer something for EPEL, you somehow need to predict whether you will be able to handle security fixes, backports and/or upgrades in the future for a long time. - I am too busy and I'll get to it later - is no good excuse for blocking people willing to do the work. True. Not responding in bugzilla in time is no good excuse either. - I beleive this package is not suitable for an LTS release, so I'll block it - is just hubris. True, too. Is there an EPEL project leadership which could review such decisions? The opposite, offering something for EPEL only to orphan it some time later, can be considered damaging, too. - Lets not put red tape for more people to do the work in a place where good sense should be more than enough to prevent conflict. Still it's too easy to release packages in the Fedora and EPEL dists and then abandon them without any notification. What I dislike seeing is for potential contributors to be turned away by our inability to trust them to do the right thing, even if we ourselves can't find the time to do it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On 01/09/2015 02:59 PM, Sérgio Basto wrote: On Sex, 2015-01-09 at 06:45 +0100, Johannes Lips wrote: Sorry to say, but this is like the hundredth time this topic came up. https://lists.fedoraproject.org/pipermail/devel/2014-July/200860.html https://lists.fedoraproject.org/pipermail/devel/2014-July/201125.html I Google it, kanarip is Jeroen van Meeuwen so you may try vanmeeuwen at kolabsys.com and kanarip at fedoraproject.org Like others already mentioned, he almost never replies. I regret, but I feel, it's time to pull the plug and to tighten up Fedora's AWOL-policy. BTW: There are other former (and current!) major Fedora contributors, to whom analogous considerations apply. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On Sex, 2015-01-09 at 06:45 +0100, Johannes Lips wrote: Sorry to say, but this is like the hundredth time this topic came up. https://lists.fedoraproject.org/pipermail/devel/2014-July/200860.html https://lists.fedoraproject.org/pipermail/devel/2014-July/201125.html I Google it, kanarip is Jeroen van Meeuwen so you may try vanmeeuwen at kolabsys.com and kanarip at fedoraproject.org Best regards, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On 09/01/15 08:40, Yanko Kaneti wrote: - I beleive this package is not suitable for an LTS release, so I'll block it - is just hubris. There are some fast moving packages out there, which are not suitable for long running releases. Of course, you're welcome to continue to support them after upstream stopped bug fixing and security fixes. Backporting of bug fixes from newer releases included. Matthias -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On Thu, 2015-01-08 at 16:54 -0600, Dennis Gilmore wrote: On Tue, 30 Dec 2014 17:09:02 +0200 Yanko Kaneti yan...@declera.com wrote: On Tue, 2014-12-30 at 14:53 +0100, Marianne Lombard wrote: Hi, A bug is open for perl-XML-TreePP since July (for opening a epel 7 branch) with no reaction (https://bugzilla.redhat.com/show_bug.cgi?id=1123681) I need this package so I'm volunteer to maintain it This bug seems unnecessary. AFAIK all it takes to create a branch for a package is a willing maintainer who's already a packager, in this case you, to make a SCM request for it in the package review request Policy does require you to contact the maintainer http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL It is quite inappropriate to not have the courtesy to contact the fedora maintainer first. I have't seen that policy, but now that I've read it it seem misguided. My thinking is: - If the Fedora maintainer cared and there was no technical reason the branches would already be there. - Most Fedora maintainers know well enough if there is or isn't any technical reason. - I am too busy and I'll get to it later - is no good excuse for blocking people willing to do the work. - I beleive this package is not suitable for an LTS release, so I'll block it - is just hubris. - Lets not put red tape for more people to do the work in a place where good sense should be more than enough to prevent conflict. https://bugzilla.redhat.com/show_bug.cgi?id=607878 http://fedoraproject.org/wiki/Package_SCM_admin_requests#Package_Change_Requests_for_existing_packages Make sure to list yourself as a owner of the new branch. Only do that after contacting the Fedora maintainer Its perfectly understandable for a primary POC of a package on the Fedora branches to not want to deal with the EPEL packaging. It is quite understandable and acceptable, but you do need to contact them to check first and not just go and branch a package. branching is not without cost, as things are setup Fedora maintainers will still get bug reports and email. there may also be a very valid reason for not branching a package. From what I've seen the new pkgdb interface makes it very clear who is responsible for any particular branch. Regards Yanko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
Sorry to say, but this is like the hundredth time this topic came up. https://lists.fedoraproject.org/pipermail/devel/2014-July/200860.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 30 Dec 2014 17:09:02 +0200 Yanko Kaneti yan...@declera.com wrote: On Tue, 2014-12-30 at 14:53 +0100, Marianne Lombard wrote: Hi, A bug is open for perl-XML-TreePP since July (for opening a epel 7 branch) with no reaction (https://bugzilla.redhat.com/show_bug.cgi?id=1123681) I need this package so I'm volunteer to maintain it This bug seems unnecessary. AFAIK all it takes to create a branch for a package is a willing maintainer who's already a packager, in this case you, to make a SCM request for it in the package review request Policy does require you to contact the maintainer http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL It is quite inappropriate to not have the courtesy to contact the fedora maintainer first. https://bugzilla.redhat.com/show_bug.cgi?id=607878 http://fedoraproject.org/wiki/Package_SCM_admin_requests#Package_Change_Requests_for_existing_packages Make sure to list yourself as a owner of the new branch. Only do that after contacting the Fedora maintainer Its perfectly understandable for a primary POC of a package on the Fedora branches to not want to deal with the EPEL packaging. It is quite understandable and acceptable, but you do need to contact them to check first and not just go and branch a package. branching is not without cost, as things are setup Fedora maintainers will still get bug reports and email. there may also be a very valid reason for not branching a package. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUrwq9AAoJEH7ltONmPFDR3+cP/0eBoIGjwePG8OBEIGjzAo/y 0ra+FqSwIMHHnXCe2/OFXMxUVszKClK37eEt+ZYDWDIdOqUFPlwXD1ZsI9Nfwcr7 dSaD+7nS8CRXqxqUx7ZdnSZjmUDf6lJFeG3qMd4S6RqFUYM9FMenjIMrXgWhjl45 gGrwpmgVCZ4QmuHFWbIIq653c2+vicSscDzIyJHp4CrZxZHFxDZH9hGsEDMrXn40 1L1+nQY8fn7SMCLtI3U/sycts9GEa/msy0vBzBu4wZKw73BYNdAit2Sx8lN+2oOe Qjvrf/SuRclpTSic7/gYLC2I66vqa60CQ7N3nH/Okoa4fzXcFRXwf4puZHvh/5Em Uvv4IDeEoBNjooPzoJPsBDFr9UXtMbiqbKHxSIxoqLnx9wcto4HTMd+wR62p+Y42 PZNvo+WttqszV95W6o6lKVi3zqPXg88h6wGZfjiQ8bAsgjmUzZgTph4QpLY66Y/b 6mq0xpC6ePSRHWAgCXzKeqMUMWLSzwSl1ZbSdVmyvL1oxSOrR+jFCojvhUSyekkf QUaApmRPIRxI9TutUdpzGAII8wqHO4ZqwESGaPc+66K1y0Jb3O3Mfyop/2kLzFHQ fFGykrZvhu8krz15F7kfp0uAYDu+4AzlqwZOoE6ID5eNs0AqUZOTw9j5PA0TcBU2 tBSFUQzohOPcUbH91Dcq =rgs9 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On 8 January 2015 at 15:54, Dennis Gilmore den...@ausil.us wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 30 Dec 2014 17:09:02 +0200 Yanko Kaneti yan...@declera.com wrote: On Tue, 2014-12-30 at 14:53 +0100, Marianne Lombard wrote: Hi, A bug is open for perl-XML-TreePP since July (for opening a epel 7 branch) with no reaction (https://bugzilla.redhat.com/show_bug.cgi?id=1123681) I need this package so I'm volunteer to maintain it This bug seems unnecessary. AFAIK all it takes to create a branch for a package is a willing maintainer who's already a packager, in this case you, to make a SCM request for it in the package review request Policy does require you to contact the maintainer http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL It is quite inappropriate to not have the courtesy to contact the fedora maintainer first. Or the policy can be revisited if potential maintainers are having problems getting replies from current maintainers. https://bugzilla.redhat.com/show_bug.cgi?id=607878 http://fedoraproject.org/wiki/Package_SCM_admin_requests#Package_Change_Requests_for_existing_packages Make sure to list yourself as a owner of the new branch. Only do that after contacting the Fedora maintainer Its perfectly understandable for a primary POC of a package on the Fedora branches to not want to deal with the EPEL packaging. It is quite understandable and acceptable, but you do need to contact them to check first and not just go and branch a package. branching is not without cost, as things are setup Fedora maintainers will still get bug reports and email. there may also be a very valid reason for not branching a package. I thought the problem was that the maintainer was not responding (eg what the subject line says.) Since the person is not responding.. what is needed next. -- Stephen J Smoogen. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
On Tue, 2014-12-30 at 14:53 +0100, Marianne Lombard wrote: Hi, A bug is open for perl-XML-TreePP since July (for opening a epel 7 branch) with no reaction (https://bugzilla.redhat.com/show_bug.cgi?id=1123681) I need this package so I'm volunteer to maintain it This bug seems unnecessary. AFAIK all it takes to create a branch for a package is a willing maintainer who's already a packager, in this case you, to make a SCM request for it in the package review request https://bugzilla.redhat.com/show_bug.cgi?id=607878 http://fedoraproject.org/wiki/Package_SCM_admin_requests#Package_Change_Requests_for_existing_packages Make sure to list yourself as a owner of the new branch. Its perfectly understandable for a primary POC of a package on the Fedora branches to not want to deal with the EPEL packaging. Regards Yanko Cheers and seasons greetings Marianne / Jehane -- Marianne (Jehane) Lombard Geekfeminist and sysadmin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer : kanarip
Hi, I have written here because the bug was already 5 month old without a reaction and the package don't seem maintened (upstream is 0.43 and fedora is 0.39 ). I have follow your advice and made a request for epel7 Le 30/12/2014 16:09, Yanko Kaneti a écrit : On Tue, 2014-12-30 at 14:53 +0100, Marianne Lombard wrote: Hi, A bug is open for perl-XML-TreePP since July (for opening a epel 7 branch) with no reaction (https://bugzilla.redhat.com/show_bug.cgi?id=1123681) I need this package so I'm volunteer to maintain it This bug seems unnecessary. AFAIK all it takes to create a branch for a package is a willing maintainer who's already a packager, in this case you, to make a SCM request for it in the package review request https://bugzilla.redhat.com/show_bug.cgi?id=607878 http://fedoraproject.org/wiki/Package_SCM_admin_requests#Package_Change_Requests_for_existing_packages Make sure to list yourself as a owner of the new branch. Its perfectly understandable for a primary POC of a package on the Fedora branches to not want to deal with the EPEL packaging. Regards Yanko Hi, I have written here because the bug is already 5 month old without a reaction and the package don't seem maintained (upstream latest release is 0.43 and fedora package is 0.39 ). I have follow your advice and made a request for epel7. Regards Marianne PS : please excuse the noise, I'm still a newbie packager -- Marianne (Jehane) Lombard Geekfeminist and sysadmin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
Dne 16.7.2014 19:54, Pierre-Yves Chibon napsal(a): On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote: On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote: On Wed, Jul 16, 2014 at 11:00:16AM +0200, Vít Ondruch wrote: Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... On the infra side we have not seen his emails bounce for few days already. Pierre I just got one yesterday: Reporting-MTA: dns; bastion01.phx2.fedoraproject.org X-Postfix-Queue-ID: D5C40215B8 X-Postfix-Sender: rfc822; or...@fedoraproject.org Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC) Final-Recipient: rfc822; kana...@kanarip.com Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=kanarip.com type=A: Host found but no data record of requested type And indeed I can't find any A or MX records for kanarip.com. I'm not sure how it's supposed to be someone else's responsibility to fix his email address in FAS. I assume the fix is to be applied not in FAS but at the DNS/domain level. Pierre This was my assumption as well ... dunno :/ Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Wed, Jul 16, 2014 at 7:54 PM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote: On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote: On Wed, Jul 16, 2014 at 11:00:16AM +0200, Vít Ondruch wrote: Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... On the infra side we have not seen his emails bounce for few days already. Pierre I just got one yesterday: Reporting-MTA: dns; bastion01.phx2.fedoraproject.org X-Postfix-Queue-ID: D5C40215B8 X-Postfix-Sender: rfc822; or...@fedoraproject.org Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC) Final-Recipient: rfc822; kana...@kanarip.com Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=kanarip.com type=A: Host found but no data record of requested type And indeed I can't find any A or MX records for kanarip.com. I'm not sure how it's supposed to be someone else's responsibility to fix his email address in FAS. I assume the fix is to be applied not in FAS but at the DNS/domain level. Well but you could change the FAS address to a working one, so that it doesn't bounce, no? Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Thu, Jul 17, 2014 at 11:02:57AM +0200, Johannes Lips wrote: On Wed, Jul 16, 2014 at 7:54 PM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote: On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote: On Wed, Jul 16, 2014 at 11:00:16AM +0200, VAt Ondruch wrote: Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... On the infra side we have not seen his emails bounce for few days already. Pierre I just got one yesterday: Reporting-MTA: dns; bastion01.phx2.fedoraproject.org X-Postfix-Queue-ID: D5C40215B8 X-Postfix-Sender: rfc822; or...@fedoraproject.org Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC) Final-Recipient: rfc822; kana...@kanarip.com Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error A A for name=kanarip.com type=A: Host found but no data record of requested A A type And indeed I can't find any A or MX records for kanarip.com. A I'm not sure how it's supposed to be someone else's responsibility to fix his email address in FAS. I assume the fix is to be applied not in FAS but at the DNS/domain level. Well but you could change the FAS address to a working one, so that it doesn't bounce, no? Assuming we would agree to change someone's personal information, how would we know which email to change it to ? Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
El 2014-07-17 11:21, Pierre-Yves Chibon escribió: Assuming we would agree to change someone's personal information, how would we know which email to change it to ? I wrote to his email address at @kolabsys.com but I didn't have any response. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Thu, Jul 17, 2014 at 11:21 AM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Thu, Jul 17, 2014 at 11:02:57AM +0200, Johannes Lips wrote: On Wed, Jul 16, 2014 at 7:54 PM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote: On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote: On Wed, Jul 16, 2014 at 11:00:16AM +0200, VAt Ondruch wrote: Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... On the infra side we have not seen his emails bounce for few days already. Pierre I just got one yesterday: Reporting-MTA: dns; bastion01.phx2.fedoraproject.org X-Postfix-Queue-ID: D5C40215B8 X-Postfix-Sender: rfc822; or...@fedoraproject.org Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC) Final-Recipient: rfc822; kana...@kanarip.com Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error A A for name=kanarip.com type=A: Host found but no data record of requested A A type And indeed I can't find any A or MX records for kanarip.com. A I'm not sure how it's supposed to be someone else's responsibility to fix his email address in FAS. I assume the fix is to be applied not in FAS but at the DNS/domain level. Well but you could change the FAS address to a working one, so that it doesn't bounce, no? Assuming we would agree to change someone's personal information, how would we know which email to change it to ? Of course I meant, that he should change it himself. If he doesn't show any interest in his packages, why not just simply orphan them? Johannes Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Qui, 2014-07-17 at 11:21 +0200, Pierre-Yves Chibon wrote: On Thu, Jul 17, 2014 at 11:02:57AM +0200, Johannes Lips wrote: On Wed, Jul 16, 2014 at 7:54 PM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote: On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote: On Wed, Jul 16, 2014 at 11:00:16AM +0200, VAt Ondruch wrote: Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... On the infra side we have not seen his emails bounce for few days already. Pierre I just got one yesterday: Reporting-MTA: dns; bastion01.phx2.fedoraproject.org X-Postfix-Queue-ID: D5C40215B8 X-Postfix-Sender: rfc822; or...@fedoraproject.org Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC) Final-Recipient: rfc822; kana...@kanarip.com Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error A A for name=kanarip.com type=A: Host found but no data record of requested A A type And indeed I can't find any A or MX records for kanarip.com. A I'm not sure how it's supposed to be someone else's responsibility to fix his email address in FAS. I assume the fix is to be applied not in FAS but at the DNS/domain level. Well but you could change the FAS address to a working one, so that it doesn't bounce, no? Assuming we would agree to change someone's personal information, how would we know which email to change it to ? I Google it, kanarip is Jeroen van Meeuwen so you may try vanmeeu...@kolabsys.com and kana...@fedoraproject.org IIRC some weeks ago someone wrote on this list the email of kanarip , thing his domain kanarip.com is down for a while. Pierre -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
Dne 16.7.2014 07:03, Orion Poplawski napsal(a): On 07/07/2014 06:48 AM, Vít Ondruch wrote: Dne 27.6.2014 18:34, Juan Orti Alcaine napsal(a): El Sábado, 28 de junio de 2014 00:31:26 Christopher Meng escribió: On Sat, Jun 28, 2014 at 12:17 AM, Bruno Wolff III br...@wolff.to wrote: He is or was a Red Hat employee. No. Please use this email address: (...) Thank you. Hi Juan, Have you tried to contact kanarip? Have you any response? I am asking since hes email is still bouncing ... Vít I'm getting bounces as well. Would be nice to get this cleaned up. Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote: On Wed, Jul 16, 2014 at 11:00:16AM +0200, Vít Ondruch wrote: Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... On the infra side we have not seen his emails bounce for few days already. Pierre I just got one yesterday: Reporting-MTA: dns; bastion01.phx2.fedoraproject.org X-Postfix-Queue-ID: D5C40215B8 X-Postfix-Sender: rfc822; or...@fedoraproject.org Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC) Final-Recipient: rfc822; kana...@kanarip.com Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=kanarip.com type=A: Host found but no data record of requested type And indeed I can't find any A or MX records for kanarip.com. I'm not sure how it's supposed to be someone else's responsibility to fix his email address in FAS. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote: On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote: On Wed, Jul 16, 2014 at 11:00:16AM +0200, Vít Ondruch wrote: Well, I contacted kanarip off-list and he responded that somebody else should supposedly fix this for him. So as always, he is not completely unresponsive ... On the infra side we have not seen his emails bounce for few days already. Pierre I just got one yesterday: Reporting-MTA: dns; bastion01.phx2.fedoraproject.org X-Postfix-Queue-ID: D5C40215B8 X-Postfix-Sender: rfc822; or...@fedoraproject.org Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC) Final-Recipient: rfc822; kana...@kanarip.com Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=kanarip.com type=A: Host found but no data record of requested type And indeed I can't find any A or MX records for kanarip.com. I'm not sure how it's supposed to be someone else's responsibility to fix his email address in FAS. I assume the fix is to be applied not in FAS but at the DNS/domain level. Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On 07/07/2014 06:48 AM, Vít Ondruch wrote: Dne 27.6.2014 18:34, Juan Orti Alcaine napsal(a): El Sábado, 28 de junio de 2014 00:31:26 Christopher Meng escribió: On Sat, Jun 28, 2014 at 12:17 AM, Bruno Wolff III br...@wolff.to wrote: He is or was a Red Hat employee. No. Please use this email address: (...) Thank you. Hi Juan, Have you tried to contact kanarip? Have you any response? I am asking since hes email is still bouncing ... Vít I'm getting bounces as well. Would be nice to get this cleaned up. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
Dne 27.6.2014 18:34, Juan Orti Alcaine napsal(a): El Sábado, 28 de junio de 2014 00:31:26 Christopher Meng escribió: On Sat, Jun 28, 2014 at 12:17 AM, Bruno Wolff III br...@wolff.to wrote: He is or was a Red Hat employee. No. Please use this email address: (...) Thank you. Hi Juan, Have you tried to contact kanarip? Have you any response? I am asking since hes email is still bouncing ... Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
Dne 27.6.2014 18:37, Christopher Meng napsal(a): On Sat, Jun 28, 2014 at 12:34 AM, Juan Orti Alcaine juan.o...@miceliux.com wrote: El Sábado, 28 de junio de 2014 00:31:26 Christopher Meng escribió: Thank you. It's better to nofity him about his archaic email address IMO, as he uses his working address in the %changelog[1] but not in the whole system. [1]---http://pkgs.fedoraproject.org/cgit/libkolabxml.git/tree/libkolabxml.spec#n305 Actually, bouncing his email address is one think, but it would be nice if Kanarip can take care about his packages. Looking at Koji [1], it is more then one year since he did his last build of any package. He has not touched any of his Ruby packages in more than 2 years. These pacakges should be reassigned to people who do the actual work Vít [1] https://koji.fedoraproject.org/koji/userinfo?userID=438 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Mon, Jun 30, 2014 at 4:19 PM, Vít Ondruch vondr...@redhat.com wrote: Actually, bouncing his email address is one think, but it would be nice if Kanarip can take care about his packages. Looking at Koji [1], it is more then one year since he did his last build of any package. He has not touched any of his Ruby packages in more than 2 years. These pacakges should be reassigned to people who do the actual work Yes but I haven't seen anyone's request to take them over. Seems Kanarip only concerns about the kolab packages now: http://pkgs.fedoraproject.org/cgit/libkolabxml.git/tree/libkolabxml.spec#n305 Yours sincerely, Christopher Meng Noob here. http://cicku.me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
Dne 30.6.2014 10:23, Christopher Meng napsal(a): On Mon, Jun 30, 2014 at 4:19 PM, Vít Ondruch vondr...@redhat.com wrote: Actually, bouncing his email address is one think, but it would be nice if Kanarip can take care about his packages. Looking at Koji [1], it is more then one year since he did his last build of any package. He has not touched any of his Ruby packages in more than 2 years. These pacakges should be reassigned to people who do the actual work Yes but I haven't seen anyone's request to take them over. That is just partial true. I tried it 3 years ago. At that time, Kanarip responded, so it was over of that call, but nothing changed with regard to his packages ... and I'd rather spent my time maintaining that packages then following non-responsive maintainer policy. Seems Kanarip only concerns about the kolab packages now: http://pkgs.fedoraproject.org/cgit/libkolabxml.git/tree/libkolabxml.spec#n305 And even the line you are referencing was cherry-picked from suse and was not committed by him [2]. Vít [1] https://lists.fedoraproject.org/pipermail/devel/2011-June/152911.html [2] http://pkgs.fedoraproject.org/cgit/libkolabxml.git/commit/?id=d40d420b2ee22a38ddcec151ff8e8a4c0dba21c6 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Fri, Jun 27, 2014 at 17:50:31 +0200, Juan Orti Alcaine juan.o...@miceliux.com wrote: FAS user kanarip is comaintainer of one of my packages, and I receive mail bounces of their email address kana...@kanarip.com. It seems like the domain is no longer valid: Following the policy, I ask the list if anyone knows how to contact this person. He is or was a Red Hat employee. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Sat, Jun 28, 2014 at 12:17 AM, Bruno Wolff III br...@wolff.to wrote: He is or was a Red Hat employee. No. Please use this email address: vanmeeuwen.kolabsys@com (@ - .) Thanks. Yours sincerely, Christopher Meng Noob here. http://cicku.me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
El Sábado, 28 de junio de 2014 00:31:26 Christopher Meng escribió: On Sat, Jun 28, 2014 at 12:17 AM, Bruno Wolff III br...@wolff.to wrote: He is or was a Red Hat employee. No. Please use this email address: (...) Thank you. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unresponsive maintainer: kanarip
On Sat, Jun 28, 2014 at 12:34 AM, Juan Orti Alcaine juan.o...@miceliux.com wrote: El Sábado, 28 de junio de 2014 00:31:26 Christopher Meng escribió: Thank you. It's better to nofity him about his archaic email address IMO, as he uses his working address in the %changelog[1] but not in the whole system. [1]---http://pkgs.fedoraproject.org/cgit/libkolabxml.git/tree/libkolabxml.spec#n305 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
