Log::Any::Proxy::Null has no owner
I'm getting an error when trying to upload new Log-Any releases containing a package Log::Any::Proxy::Null > Status: Permission missing > == > > module : Log::Any::Proxy::Null > version: 1.042 > in file: lib/Log/Any/Proxy/Null.pm > status : Not indexed because permission missing. Current registered > primary maintainer is unknown. Hint: you can always find > the legitimate maintainer(s) on PAUSE under "View > Permissions". When I look up the permissions on pause.perl.org <http://pause.perl.org/>, they show JSWARTZ as a co-maint on that package, but no owner. Can I get the ownership permission bit? Or should I rename the package? Thanks, Doug Bell d...@preaction.me
Re: Adopting Log::Any::Adapter::Syslog into the core Log-Any distribution
Hello, Just a quick follow-up to try to get in contact with you about adopting Log::Any::Adapter::Syslog into the core Log::Any distribution. I've talked with SDT, a co-maint and the latest releaser for the module (https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4 <https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4>), and he agrees that this would be a good idea. But I can't do that without at least co-maint permissions for Log::Any::Adapter::Syslog. If you could log in to pause.perl.org <http://pause.perl.org/> and add me to the co-maint list, or transfer primary maintainership, I could add this module to the core Log-Any to make it available to everyone using Log::Any. Thanks, Doug Bell d...@preaction.me > On Dec 7, 2016, at 6:00 PM, Doug Bell wrote: > > Hi, > > I was thinking it'd be nice to be able to log to a system's native log > facilities out-of-the-box in Log::Any. To do this, it'd be easiest to adopt > the Log::Any::Adapter::Syslog package into the Log-Any distribution. Would > you be willing to give me co-maintainership (or even transfer primary > maintainership) so that I could do this? I would be transferring the full Git > history and maintaining the appropriate copyright attributions from the > existing project. > > Here's the discussion that SDT and I have been having on Github: > https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4 > <https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4> > > Thanks, > > > Doug Bell > d...@preaction.me <mailto:d...@preaction.me> >
Re: Adopting Log::Any::Adapter::Syslog into the core Log-Any distribution
Yep, that'll do it, thanks! Doug Bell d...@preaction.me > On Jan 11, 2017, at 8:43 AM, Daniel Pittman wrote: > > Made PREACTION primary maintainer of Log::Any::Adapter::Syslog. > > > ...which I think should be what is required here? Sorry for being slow to > respond. > > > On Tue, Jan 10, 2017 at 4:04 PM Doug Bell <mailto:d...@preaction.me>> wrote: > Hello, > > Just a quick follow-up to try to get in contact with you about adopting > Log::Any::Adapter::Syslog into the core Log::Any distribution. I've talked > with SDT, a co-maint and the latest releaser for the module > (https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4 > <https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4>), and he agrees that > this would be a good idea. But I can't do that without at least co-maint > permissions for Log::Any::Adapter::Syslog. > > If you could log in to pause.perl.org <http://pause.perl.org/> and add me to > the co-maint list, or transfer primary maintainership, I could add this > module to the core Log-Any to make it available to everyone using Log::Any. > > Thanks, > > > > Doug Bell > d...@preaction.me <mailto:d...@preaction.me> > > > >> On Dec 7, 2016, at 6:00 PM, Doug Bell > <mailto:d...@preaction.me>> wrote: >> >> Hi, >> >> I was thinking it'd be nice to be able to log to a system's native log >> facilities out-of-the-box in Log::Any. To do this, it'd be easiest to adopt >> the Log::Any::Adapter::Syslog package into the Log-Any distribution. Would >> you be willing to give me co-maintainership (or even transfer primary >> maintainership) so that I could do this? I would be transferring the full >> Git history and maintaining the appropriate copyright attributions from the >> existing project. >> >> Here's the discussion that SDT and I have been having on Github: >> https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4 >> <https://github.com/sdt/Log-Any-Adapter-Syslog/issues/4> >> >> Thanks, >> >> >> Doug Bell >> d...@preaction.me <mailto:d...@preaction.me> >> >
Recover PAUSE ID: PREACTION
I short-sightedly associated my former employer's e-mail address with my PAUSE ID, and now that I am no longer with the company, I am unable to recover my password. How can I reset the e-mail address associated with my PAUSE ID? Doug Bell madcity...@gmail.com
Re: Recover PAUSE ID: PREACTION
For obvious reasons I try to keep my e-mail off the interwebs. I'll send a LinkedIn connection request, which should give you permission to see my e-mail address. I'm also an admin for the Chicago.PM (under both of it's names). Could personal references work? Like a web of trust thing? I've also got twitter.com/preaction, facebook.com/preaction, preaction.tumblr.com, github.com/preaction, and I'm preaction on freenode and irc.perl.org, but none of that should get you my e-mail address (if I've done it right), so that's all pretty useless. Doug Bell madcity...@gmail.com On Dec 22, 2012, at 4:55 PM, David Golden wrote: Hi, Doug. You need to demonstrate that your current email address is actually you. A public profile associated with it would work. Others have sent me linkedin invites, for example, or show it on a google plus profile. David Golden PAUSE admin for IDs On Dec 22, 2012 3:31 PM, "Doug Bell" wrote: > I short-sightedly associated my former employer's e-mail address with my > PAUSE ID, and now that I am no longer with the company, I am unable to > recover my password. How can I reset the e-mail address associated with my > PAUSE ID? > > Doug Bell > madcity...@gmail.com > > > >
Net::Stomp co-maintainership
Hello, I'd like to do some work on the Net::Stomp module (specifically to make Net::Stomp::Frame usable for a server as well as a client, and with that to add some tests). I also took the liberty of merging in all of the disparate github forks into a single one. The result of all the merges is here: https://github.com/preaction/net-stomp I'd like to also take the time to clean up the RT, there are some patches there from some time ago that look to be pretty useful. To do all this, would it be possible to get co-maintainer status so I can update Net-Stomp on CPAN? Thanks, Doug Bell madcity...@gmail.com
Re: Net::Stomp co-maintainership
PREACTION, the other one should probably be deleted (if that's a thing) Doug Bell madcity...@gmail.com On Mar 15, 2013, at 3:44 AM, Leon Brocard wrote: > On Thu, Mar 14, 2013 at 07:21:46PM -0500, Doug Bell wrote: >> To do all this, would it be possible to get co-maintainer status so I can >> update Net-Stomp on CPAN? > > That looks great. It's fine with me, but I'd handed over developement to > Jason. Jason? > > Regards, Léon.
Re: Net::Stomp co-maintainership
Thanks for the help! Doug Bell madcity...@gmail.com On Mar 17, 2013, at 2:06 PM, Leon Brocard wrote: > On Fri, Mar 15, 2013 at 10:19:08PM -0500, Doug Bell wrote: >> PREACTION, the other one should probably be deleted (if that's a thing) > > Done: > > Added PREACTION to co-maintainers of Net::Stomp. > Added PREACTION to co-maintainers of Net::Stomp::Frame. > > Leon
