Re: Are Email::* modules unmaintained?
* p...@cpan.org [2019-01-17T06:25:04] > I'm really disappointed as you have not wrote anything about this topic > as people are already there... I'm not dead. I am avoiding this list because I find your messages and attitude about it to be really off-putting, and whenever I come back, I feel like I'd rather go do something else. My position remains: this code works, and any change needs to be well vetted, and so far I haven't spent enough time to be satisfied that it's okay to go. Maybe I'll have a go at it again soon. When you first showed up to work on Email::MIME headers code, I said "you'll probably be happier if you just fork it," but you didn't. Now you're talking about trying to take the namespace over, which won't happen as long as I'm responsive to PAUSE admins. Which I am. I am happy to work on this project some, but when I show up and see obnoxious messages about how I owe anybody anything, or how I'm a deadbeat, it's a pretty good way to get me to say, "Hey, I'm just going to say it works well enough and also now I'm going away." I'll make another pass through the PRs next week. For now, I'm going to go do something more enjoyable. -- rjbs signature.asc Description: Digital signature
Re: Are Email::* modules unmaintained?
On Thursday 17 January 2019 12:25:04 p...@cpan.org wrote: > Hi Ricardo! > > On Monday 25 June 2018 08:31:08 Ricardo Signes wrote: > > So: you can wait for me to have more time, or people with some vested > > interest can agree to step up to do more in general. > > I'm really disappointed as you have not wrote anything about this topic > as people are already there... > > E.g. see my email from August 2018: > > On Monday 13 August 2018 17:02:38 p...@cpan.org wrote: > > Hi Ricardo! Branislav (https://github.com/happy-barney) is interested in > > doing some sort of code review for your Email:: modules. He already > > wrote you an email. So hopefully this can speed up development... > > Or email from October 2018: > > On Monday 08 October 2018 14:30:57 p...@cpan.org wrote: > > On Thursday 09 August 2018 15:34:27 p...@cpan.org wrote: > > > Just in case, I have there open pull requests for more then year. If > > > Ricardo does not have time to look at them yet, can somebody else do > > > review? There is support for IDN email addresses or long and Unicode > > > file names in attachments. > > > > > > https://github.com/rjbs/Email-MIME-ContentType/pull/9 > > > https://github.com/rjbs/Email-MIME-ContentType/pull/10 > > > https://github.com/rjbs/Email-MIME-ContentType/pull/11 > > > > > > https://github.com/rjbs/Email-MIME/pull/49 > > > https://github.com/rjbs/Email-MIME/pull/50 > > > https://github.com/rjbs/Email-MIME/pull/51 > > > https://github.com/rjbs/Email-MIME/pull/54 > > > > > > https://github.com/rjbs/Email-Simple/pull/17 > > > > @rjbs: some of pull requests were already checked by @gedge. > > Does it mean that you rejected it? > > And my email from November 2018 ... > > On Tuesday 20 November 2018 09:30:14 p...@cpan.org wrote: > > Ricardo, since June nothing happened... People are still asking for > > changes in created pull requests and now downstream distribution > > maintainers started to creating fork of your cpan distributions just to > > address problems which were not fixed/reflected in upstream cpan. > > > > Please, can you clarify state of your cpan modules? Are you going to > > maintain them in near future? And if not, can you take ownership or > > maintenance to other people, e.g. those who are started to create > > downstream distribution fork? > > > > Because having fixes and patches just in system distribution and not on > > cpan is really bad situation which just say that upstream cpan is dead! > > > > Also this would cause incompatibility for applications in system > > distributions which starts depending on fixes/features available in > > system, but not on cpan... > > ... is unanswered. > > There are more people interested in development of Email:: modules, > there are lot of open pull requests and we have not heard from you > anything about future development. > > Can you clarify current status of Email:: modules? There is no reply for 11 months... and people are still asking for updates/fixes in Email:: modules. Also without replies. There were more people interested in Email:: develop (see above emails). I think now it is good time for starting process of takeover of Email modules until those people who were interested in development would not loose they interested just because of silence and inactivity of maintainers.
Re: Are Email::* modules unmaintained?
Hi Ricardo! On Monday 25 June 2018 08:31:08 Ricardo Signes wrote: > So: you can wait for me to have more time, or people with some vested > interest can agree to step up to do more in general. I'm really disappointed as you have not wrote anything about this topic as people are already there... E.g. see my email from August 2018: On Monday 13 August 2018 17:02:38 p...@cpan.org wrote: > Hi Ricardo! Branislav (https://github.com/happy-barney) is interested in > doing some sort of code review for your Email:: modules. He already > wrote you an email. So hopefully this can speed up development... Or email from October 2018: On Monday 08 October 2018 14:30:57 p...@cpan.org wrote: > On Thursday 09 August 2018 15:34:27 p...@cpan.org wrote: > > Just in case, I have there open pull requests for more then year. If > > Ricardo does not have time to look at them yet, can somebody else do > > review? There is support for IDN email addresses or long and Unicode > > file names in attachments. > > > > https://github.com/rjbs/Email-MIME-ContentType/pull/9 > > https://github.com/rjbs/Email-MIME-ContentType/pull/10 > > https://github.com/rjbs/Email-MIME-ContentType/pull/11 > > > > https://github.com/rjbs/Email-MIME/pull/49 > > https://github.com/rjbs/Email-MIME/pull/50 > > https://github.com/rjbs/Email-MIME/pull/51 > > https://github.com/rjbs/Email-MIME/pull/54 > > > > https://github.com/rjbs/Email-Simple/pull/17 > > @rjbs: some of pull requests were already checked by @gedge. Does it mean that you rejected it? And my email from November 2018 ... On Tuesday 20 November 2018 09:30:14 p...@cpan.org wrote: > Ricardo, since June nothing happened... People are still asking for > changes in created pull requests and now downstream distribution > maintainers started to creating fork of your cpan distributions just to > address problems which were not fixed/reflected in upstream cpan. > > Please, can you clarify state of your cpan modules? Are you going to > maintain them in near future? And if not, can you take ownership or > maintenance to other people, e.g. those who are started to create > downstream distribution fork? > > Because having fixes and patches just in system distribution and not on > cpan is really bad situation which just say that upstream cpan is dead! > > Also this would cause incompatibility for applications in system > distributions which starts depending on fixes/features available in > system, but not on cpan... ... is unanswered. There are more people interested in development of Email:: modules, there are lot of open pull requests and we have not heard from you anything about future development. Can you clarify current status of Email:: modules?
Re: Are Email::* modules unmaintained?
On Monday 25 June 2018 08:31:08 Ricardo Signes wrote: > * p...@cpan.org [2018-06-25T05:08:32] > > So what is status of Email::* modules? Does silence now mean that > > modules are abandoned / unmaintained? I guess so. > > You are mistaken. > > The answer is the same as every other time you have asked: I am here, I am > alive, I am interested, and I am extremely busy, so these don't often make it > to the top of my list. Ricardo, since June nothing happened... People are still asking for changes in created pull requests and now downstream distribution maintainers started to creating fork of your cpan distributions just to address problems which were not fixed/reflected in upstream cpan. Please, can you clarify state of your cpan modules? Are you going to maintain them in near future? And if not, can you take ownership or maintenance to other people, e.g. those who are started to create downstream distribution fork? Because having fixes and patches just in system distribution and not on cpan is really bad situation which just say that upstream cpan is dead! Also this would cause incompatibility for applications in system distributions which starts depending on fixes/features available in system, but not on cpan...
Re: Are Email::* modules unmaintained?
On Thursday 09 August 2018 15:34:27 p...@cpan.org wrote: > On Thursday 28 June 2018 13:03:58 p...@cpan.org wrote: > > On Monday 25 June 2018 08:31:08 Ricardo Signes wrote: > > > * p...@cpan.org [2018-06-25T05:08:32] > > > > So what is status of Email::* modules? Does silence now mean that > > > > modules are abandoned / unmaintained? I guess so. > > > > > > You are mistaken. > > > > > > The answer is the same as every other time you have asked: I am here, I > > > am > > > alive, I am interested, and I am extremely busy, so these don't often > > > make it > > > to the top of my list. > > > > > > We don't have any sort of sense of community here or a practice of shared > > > code > > > review, so everything comes down to "when does Rik have the time to > > > consider > > > each change." That is "not all that often." > > > > > > If we had three or four people who committed to create a better sense of > > > group > > > responsibility, maybe we'd see more progress. > > > > On list are still more people interested in Email:: modules. Either as > > direct users or developers of other Email:: modules. > > > > So... is there somebody interested in doing some code review or > > maintenance of Email:: modules? > > Just in case, I have there open pull requests for more then year. If > Ricardo does not have time to look at them yet, can somebody else do > review? There is support for IDN email addresses or long and Unicode > file names in attachments. > > https://github.com/rjbs/Email-MIME-ContentType/pull/9 > https://github.com/rjbs/Email-MIME-ContentType/pull/10 > https://github.com/rjbs/Email-MIME-ContentType/pull/11 > > https://github.com/rjbs/Email-MIME/pull/49 > https://github.com/rjbs/Email-MIME/pull/50 > https://github.com/rjbs/Email-MIME/pull/51 > https://github.com/rjbs/Email-MIME/pull/54 > > https://github.com/rjbs/Email-Simple/pull/17 @rjbs: some of pull requests were already checked by @gedge.
Re: Are Email::* modules unmaintained?
On Monday 25 June 2018 08:31:08 Ricardo Signes wrote: > If we had three or four people who committed to create a better sense of group > responsibility, maybe we'd see more progress. ... > So: you can wait for me to have more time, or people with some vested > interest can agree to step up to do more in general. Hi Ricardo! Branislav (https://github.com/happy-barney) is interested in doing some sort of code review for your Email:: modules. He already wrote you an email. So hopefully this can speed up development... Anyway, is there on pep list somebody else interested in helping Ricardo with review of Email:: modules?
Re: Are Email::* modules unmaintained?
On Thursday 28 June 2018 13:03:58 p...@cpan.org wrote: > On Monday 25 June 2018 08:31:08 Ricardo Signes wrote: > > * p...@cpan.org [2018-06-25T05:08:32] > > > So what is status of Email::* modules? Does silence now mean that > > > modules are abandoned / unmaintained? I guess so. > > > > You are mistaken. > > > > The answer is the same as every other time you have asked: I am here, I am > > alive, I am interested, and I am extremely busy, so these don't often make > > it > > to the top of my list. > > > > We don't have any sort of sense of community here or a practice of shared > > code > > review, so everything comes down to "when does Rik have the time to consider > > each change." That is "not all that often." > > > > If we had three or four people who committed to create a better sense of > > group > > responsibility, maybe we'd see more progress. > > On list are still more people interested in Email:: modules. Either as > direct users or developers of other Email:: modules. > > So... is there somebody interested in doing some code review or > maintenance of Email:: modules? Just in case, I have there open pull requests for more then year. If Ricardo does not have time to look at them yet, can somebody else do review? There is support for IDN email addresses or long and Unicode file names in attachments. https://github.com/rjbs/Email-MIME-ContentType/pull/9 https://github.com/rjbs/Email-MIME-ContentType/pull/10 https://github.com/rjbs/Email-MIME-ContentType/pull/11 https://github.com/rjbs/Email-MIME/pull/49 https://github.com/rjbs/Email-MIME/pull/50 https://github.com/rjbs/Email-MIME/pull/51 https://github.com/rjbs/Email-MIME/pull/54 https://github.com/rjbs/Email-Simple/pull/17
Re: Are Email::* modules unmaintained?
On Monday 25 June 2018 08:31:08 Ricardo Signes wrote: > * p...@cpan.org [2018-06-25T05:08:32] > > So what is status of Email::* modules? Does silence now mean that > > modules are abandoned / unmaintained? I guess so. > > You are mistaken. > > The answer is the same as every other time you have asked: I am here, I am > alive, I am interested, and I am extremely busy, so these don't often make it > to the top of my list. > > We don't have any sort of sense of community here or a practice of shared code > review, so everything comes down to "when does Rik have the time to consider > each change." That is "not all that often." > > If we had three or four people who committed to create a better sense of group > responsibility, maybe we'd see more progress. On list are still more people interested in Email:: modules. Either as direct users or developers of other Email:: modules. So... is there somebody interested in doing some code review or maintenance of Email:: modules? > The last thing you wrung your hands about "we have no maintainer!" was > something for which we didn't even have a clear and isolated fix, so the task > here wasn't "nobody will review and apply this commit," but "nobody is willing > to write a fix." So, in that sense, yes, nobody is doing active maintenance > on > Email::Address much of the time, but somebody is alive. This just means that Email::Address is not going to be fixed... > With Email::MIME, keep in mind that part of maintenance is not just applying > any old patch, because people rely on this software to not change too > radically. So, there has to be not only patches, but also review and > consideration, so "we aren't adding new features" isn't always a sign of > disrepair, but can also indicate "we don't have the time to predict the impact > of these changes on existing users." I understand and I'm asking for reviewing my pull requests for longer time. Not for "blind merge". > So: you can wait for me to have more time, or people with some vested > interest can agree to step up to do more in general. > > I'm not going to be shamed into doing a release that might break things and > cause me ten times as much work as leaving things be. But doing some testing of users outside of pep mailing list would need some CPAN trial release. Yes things which could break things are problem and this needs to be done when doing review of patches.
Re: Are Email::* modules unmaintained?
Marc Bradshaw via pep said (on Mon, Jun 25, 2018 at 07:35:31p.m. +1000): > > > PS: Is somebody still active on this pep mailing list? > > Not active, but reading. +1 and can PR, etc -- Gedge
Re: Are Email::* modules unmaintained?
* p...@cpan.org [2018-06-25T05:08:32] > So what is status of Email::* modules? Does silence now mean that > modules are abandoned / unmaintained? I guess so. You are mistaken. The answer is the same as every other time you have asked: I am here, I am alive, I am interested, and I am extremely busy, so these don't often make it to the top of my list. We don't have any sort of sense of community here or a practice of shared code review, so everything comes down to "when does Rik have the time to consider each change." That is "not all that often." If we had three or four people who committed to create a better sense of group responsibility, maybe we'd see more progress. The last thing you wrung your hands about "we have no maintainer!" was something for which we didn't even have a clear and isolated fix, so the task here wasn't "nobody will review and apply this commit," but "nobody is willing to write a fix." So, in that sense, yes, nobody is doing active maintenance on Email::Address much of the time, but somebody is alive. With Email::MIME, keep in mind that part of maintenance is not just applying any old patch, because people rely on this software to not change too radically. So, there has to be not only patches, but also review and consideration, so "we aren't adding new features" isn't always a sign of disrepair, but can also indicate "we don't have the time to predict the impact of these changes on existing users." So: you can wait for me to have more time, or people with some vested interest can agree to step up to do more in general. I'm not going to be shamed into doing a release that might break things and cause me ten times as much work as leaving things be. -- rjbs signature.asc Description: Digital signature
Re: Are Email::* modules unmaintained?
> PS: Is somebody still active on this pep mailing list? Not active, but reading. -- Marc Bradshaw marcbradshaw.net[1] | @marcbradshaw[2] Links: 1. http://marcbradshaw.net/ 2. https://twitter.com/marcbradshaw
Re: Are Email::* modules unmaintained?
p...@cpan.org wrote: > PS: Is somebody still active on this pep mailing list? Mainly just a user, here. I won't ever use proprietary messaging platforms, but I can help out if stuff comes up on this list.
Re: Are Email::* modules unmaintained?
Hi, The state of these modules differs, since they are not all maintained by the same person. For example, I only maintain Email::Outlook::Message. Of course, since that module depends on Email::MIME, my module is also affected by any lack of maintenance thereof. There are procedures in place for taking over abandoned modules if necessary. Regards, Matijs On 25/06/18 11:08, p...@cpan.org wrote: > Hi! I would like to ask: What is the state of the perl Email::* modules? > Currently there are lot of open pull request without review, some of > there more then year. Who is the maintainer or supporter of Email::* > modules? Currently, rjbs as primary person does not respond to emails. > > For Email::MIME & co there is e.g. prepared change which add support for > Unicode file names and more people are asking when it will be merged. > Apparently there is no reaction on this topic. > > So what is status of Email::* modules? Does silence now mean that > modules are abandoned / unmaintained? I guess so. > > PS: Is somebody still active on this pep mailing list? > signature.asc Description: OpenPGP digital signature
